The problem EZ:Ticket solves

Our journey began with the realization that traditional methods of college event ticketing often lead to frustration, with issues like counterfeit tickets and inefficient distribution processes taking away the fun of attending events. Recognizing the prevalence of ticket fraud and its detrimental impact on the student experience, we set out to reimagine the college event landscape. By leveraging Non-Fungible Tokens (NFTs) based on the ERC-721 standard, we've developed a secure and seamless ticketing solution that eliminates the risk of fraud and ensures that every ticket is authentic and verifiable.

We eliminate the risk of counterfeit tickets by utilizing NFT technology, ensuring that each ticket is unique, verifiable, and secure and with blockchain technology, users can track the entire ticket lifecycle, from issuance to resale, promoting transparency and trust in the ticketing process.

Event organizers benefit from simplified ticket management and distribution, reducing administrative overhead and ensuring smooth execution of events. Our platform further serves as a centralized hub for campus events, fostering connections among students and promoting a sense of belonging within the college community.

Whether it's a concert, a hackathon, or a sports event, we believe every student should have access to a hassle-free platform for finding and purchasing tickets.

Challenges we ran into

1.Understanding the blockchain and developing NFT smart contracts using Solidity is a complex task, we managed to overcome it by googling about it, reading articles and watching youtube videos.

2.Since deployed smart contracts on blockchain are immutable, we wrote several tests for our application to make sure it works as expected.

3.Coming up with the user aquisition and dealing with regulatory compliance was also a tricky process, we had to make sure to come up with techniques to educate the mainstream users about blockchain and considered legal requirements.

4.While creating a new wallet for the user the account id was not being shown to the user explicitly so created a flask route to fetch and then display the wallet details to the user as well as keeping it discrete and secure.

5.Meta mask integration was a hassle as Meta mask doesn't allow a overlay page so we had to separately create the meta mask route and then required the user to create their wallet.