HyperEvent

HyperEvent is a DApp that hides the on-chain activity and able to create events and their passes NFT On-chain, and for normal people it like using any other Web2 App.

Websitegithub
  • 336 Raised
  • 351 Views
  • 2 Judges

Categories

  • 02. 🚀 Hyperliquid Frontier Track
  • 08. Best use of Privy

Gallery

Description

Project Name  

HyperEvent – Seamless Event Management Service with Privy & NFT Ticket based system Using Privy and their Policies.


Idea Behind The Project

HyperLiquid is a DEX chain, everyone is working on a project related to hyperCore (money related stuff) I don't have have a good grasp of that topic. So, I thought when everyone is working to integrate HyperCore in their project, I will use only HyperEVM, to show this chain can also be used as a ethereum base chain and not bound to just a DEX with only trading option.


Description  

HyperEvent is a Dapp that lets Organizers create and manage events directly on-chain with features like- BulkMinting, CreatEvents and burn Tickets. By integrating Privy for simple authentication and wallets, users and organizers can log in with Google and instantly get a non-custodial wallet and do gaseless transactions using Privy. Every ticket is issued as an NFT, ensuring transparency, proof of ownership, and eliminating ticket fraud.


Organizers are individuals that needs to approved from a 2 authentication system in the EventManager smart contract and also in the Privy Policies.
User can be anyone that the organizer wants to mint the ticket to.


How It Works

Privy Login –

Users and organizers can sign in using their Google account. A Privy smart wallet is automatically created for them (no seed phrases, no MetaMask popups).Users need no special permission to see use the Dapp. Organizers need to have 2 permission to be able to create and Bulk mint the tickets for users.


Event Creation –

Organizers can create Events with details like (event name, no. of Tickets, and most important IPFS URI ). And the contract EventManager keeps track of sold tickets.

IPFS URI - it is the metadata of the ticket NFTs, They gave the uniqueness to every ticket that is minted and full control how the ticket must look to the organizer.

NFT Tickets – Each attendee receives an NFT ticket in their Privy wallet. This makes tickets verifiable, tradable, and tamper-proof.


bulk Minting Tickets - 

Organizer can Bulk mint tickets and send only one transaction to mint tokens to different users helping in reducing the gas fees. They can't mint tokens more than that is added in the event creation page.

Struct of Events:

struct Event {
        uint256 id;
        string eventName;
        // int eventDate; // placeholder for future
        uint256 totalTicketCount;
        uint256 ticketsMintedCount;
        string baseURI;
}


Contracts

There are 2 contracts deployed on hyperEvm that our Dapp interact with EventNft.sol and EventManager.sol:

EventNft.sol - this is a Openzeppelin implementation of ERC721 - token with burnable, with URI storage, with custom logic to display tokens and Access control so only EventManger contract can interact with it.

EventManager.sol - Main logic of the Dapp is built in this with createEvent, bulkMintTickets and checkInTickets logic. Only those with role of Oraganizer can send a transaction to this contract.  


Frontend

Built with React + Vite for fast, modern UX. Contract interactions are handled with ethers.js and Privy’s SDK for wallet management.


What makes it exciting:

- No complicated Web3 setup — users don’t even realize they’re using a wallet.

- Ownership and security of NFTs on-chain.

- A clean integration of Web2 familiarity with Web3 trust.


Demo

🎥 [Video Demo](https://youtu.be/-M3GigjKx3Y)


Project Links

-Code (Frontend + Contracts):GitHub Repository (https://github.com/Al-Ayaan-Ansari/HyperEvent)

-Live Demo: Deployed App (https://hyperevent.onrender.com/)


Team

- Ayaan [@alAyaan8466] – Developer

Attachments