Search projects, hackathons, sponsors and tech

    ← All projects

    Vent

    Cross-Chain Event Management and Payment Platform that helps organisers to collaborate without any ease and helps them

    Demo

    About

    The problem it solves Effortless Event Organization: Vent streamlines event creation and management, offering an intuitive interface for organizers. Assigning roles and spending limits to team members ensures seamless collaboration while preventing overspending. Diverse Payment Methods: Attendees experience unprecedented flexibility in payments. Direct payments in preferred currencies cater to traditional preferences. Cross-chain AUSDC transfers enable borderless transactions using Axelar's technology, erasing geographical barriers. The Squid Swap and Axelar Native Swap capabilities allow swift asset swaps across diverse blockchains, ensuring frictionless transactions. Verified Trustworthiness: Spruce ID integration guarantees event authenticity and participant credibility. Event organizers can offer verified, secure experiences, fostering trust among attendees. Global Accessibility: Vent's cross-chain nature extends events' reach. Attendees from different blockchain ecosystems can engage with ease, broadening event participation and enriching networking opportunities. Budget Control: Organizers manage expenses effortlessly with predefined spending limits. This prudent approach eliminates financial chaos, enhancing budget control and accountability. Enhanced Security: Blockchain ensures tamper-proof event records, minimizing data manipulation risks. Copious security layers, including Spruce ID, deter unauthorized access and instill user confidence. Smart Contract Reliability: Vent's Solidity-based smart contracts provide transparency and automation in transactions. Trustworthy execution of terms is assured, ensuring participants receive what they expect.

    How it's made

    Challenges we ran into Cross Chain interaction: At first its hard to learn but i got the grip to understand it State management: That i got into more scrumbles context structure without even i know but got it optimized using memo and usecallback