zkPass
You can get in, but I have zero knowledge about the ticket you own
About
The problem it solves In event management and ticketing, zkPass addresses several critical issues: **1. Counterfeiting and Fraud**: Traditional tickets are prone to counterfeiting. zkPass uses blockchain to create tamper-proof, unique NFT tickets. **2. Privacy Concerns**: Purchasing and using event tickets often compromises privacy. zkPass employs zero-knowledge proofs to verify ownership without revealing personal details. **3. Scalability and Efficiency**: Managing ticketing for large events is complex. zkPass automates and secures verification with ZKPs, reducing administrative burdens. **4. Static and Unengaging Tickets**: Traditional tickets lack engagement. zkPass offers dynamic, generative NFTs that evolve, adding collectible value and enhancing user experience. **5. User Experience**: Ticketing processes can be cumbersome. zkPass provides a seamless, end-to-end solution using blockchain and ZKPs, simplifying the entire process from purchase to event entry.
How it's made
Challenges we ran into **As I had zero knowledge about zero knowledge**, I managed to get Mina's L2 (Protokit) up and running; however, I encountered quirky bugs along the way. Sometimes I got `chain:dev: Error in inclusion of tx, skipping TypeError: Cannot read properties of chain:dev: undefined (reading 'from')` from the Protokit Indexer From time to time, My JS heap crashed from the Next.js. The most challenging part was, however, creating a seamless UI that would be very easy to use and logically implement ZK into the app. Also, hacking alone is not funny; always take friends with you.