Ticketify
Own. Trade. Experience. The Future of Ticketing.
Created on 1st February 2025
•
Ticketify
Own. Trade. Experience. The Future of Ticketing.
The problem Ticketify solves
The Problem: Traditional Ticketing Issues
- Scalping & Fraud – Tickets are often resold at inflated prices or counterfeited, leading to unfair access and financial losses.
- Lack of Ownership Control – Buyers do not have true ownership of their tickets and are restricted by platform policies.
- Complicated Resale & Transfers – Many ticketing platforms impose restrictions or high fees on resales, making secondary markets inefficient.
- Event Entry Issues – Digital and paper tickets can be lost, duplicated, or mismanaged, causing check-in problems.
- Limited Revenue for Creators – Event organizers and artists miss out on secondary market profits, which go entirely to scalpers or resellers.
The Solution: TicketNFT
- True Ownership – Attendees fully own their tickets as NFTs, allowing secure storage and easy transfers.
- Seamless Resale – Built-in resale mechanisms with price limits prevent scalping while enabling fair trade.
- Fraud Prevention – Blockchain verification ensures every ticket is authentic and uniquely tied to a seat.
- Transparent & Fair Pricing – Smart contracts regulate pricing to prevent overpricing and unfair trading.
- Revenue Sharing – Event organizers can earn royalties on secondary sales, ensuring continued value capture.
TicketNFT provides a secure, fair, and seamless ticketing experience while giving organizers control over pricing, transfers, and engagement.
Challenges we ran into
-
The initial challenge was to send meta mask account instance to all the pages because for all transactions, account instance is required and we cannot send it like cookies to another page as it is not as simple as a wallet address it rather contanins a whole bunch of functions associated with it, also it cannot be called in api routes too. So the solution was to create a our structure in such a way that there is a const navbar with wallet instance in layout file rather than page so it is accessible to all the children pages.
-
The next challenge was writing the solidity file, although webThree provides sample contract for minting and claiming and a full functional marketplace around ERC721A but soon we realised none of then alone was able to fullfill our expected functionality. So we went through documentations and sample videos on youtube to get a gist and use thirdweb modular contracts with tweaking and some other functionality, again from docs to write a basic contract through which one can claim NFT on certain price. Then we added function layer by layer many a times using ai for help and sometimes going through docs to debug as ai was not perfect sometimes.
-
On frontend side a big challenge was how to integrate this deployed contract through thirdWeb protal into our codeBase using sample videos by thirdWeb on YT soon we were able to find common patterns and were able to integrate and call basic read write function.
Tracks Applied (4)
Ethereum Track
ETHIndia
Aptos
Aptos
Open Track
Freshers Track
Technologies used