Tadaa-Lah

Demo

About

The problem it solves **1. Combating Ticket Fraud and Counterfeiting** **The Problem**: Traditional digital tickets (like PDFs or simple QR codes) are easily duplicated and sold to multiple people, leaving many buyers with fake, invalid tickets at the event gate. **The Solution**: Tadaa-Lah mints each ticket as a unique, non-duplicable asset on the Sui blockchain. QR Code Verification: Each ticket has a unique QR code directly linked to its on-chain ID. This makes it impossible to counterfeit, as the system can instantly validate its authenticity and ownership in real-time. Secure Resale: When a ticket is resold, ownership is transparently transferred on the blockchain. The original seller loses access, and the new buyer receives the one and only authentic ticket, eliminating the risk of buying a copy. **2. Building Trust and Protecting Buyers** **The Problem:** On secondary markets (like social media or forums), it's difficult to know if a seller is legitimate. Buyers risk sending money and receiving nothing in return or getting a fake ticket. **The Solution:** The platform introduces On-Chain Seller Verification. Sellers must complete a verification process, which is recorded on the blockchain. Verified sellers are given a "Verified Seller" badge on their profile, giving buyers confidence that they are dealing with a legitimate and accountable individual. **3. Empowering Users with True Ownership and Control** **The Problem:** In centralized systems, your ticket is just an entry in a company's database. The company has full control, can change terms, and if their system goes down, you might have issues accessing your ticket. **The Solution:** Tadaa-Lah uses Decentralized Ticket Management. Your ticket is a digital asset stored securely in your personal SUI wallet, not on a central server. This gives you true ownership and control over your ticket, allowing you to hold, sell, or use it without relying on a middleman. **4. Ensuring Secure and Transparent Transactions** **The Problem:** Traditional payment systems can be prone to fraud, high fees, and disputes. Transaction records are often hidden from the public. **The Solution:** All transactions are handled via Wallet-Based Payments and recorded on the blockchain. This creates a trustless environment where payments are sent directly and securely. Every purchase and sale is an on-chain transaction, creating a permanent, auditable record that anyone can verify, ensuring complete transparency.

How it's made

Challenges we ran into **1. Wallet Connection Issue** “One of the biggest challenges we faced was connecting the SUI wallet to our website. Initially, the connection flow would fail or not detect the user’s wallet status, especially when they tried to reconnect after logging out. We discovered that the issue was due to the wallet SDK and our front-end state not syncing properly. To solve this, we updated the @suiet/wallet-kit SDK, added a wallet status listener for real-time updates, and implemented a ‘Retry Connection’ button so users could reconnect without refreshing the page. This made the wallet integration smooth and reliable, which was crucial since SUI wallet is our only payment method.” **2. QR Code Verification Logic** “Another hurdle came when implementing the QR code verification for event entry. In early testing, some valid tickets showed as invalid because the verification page wasn’t reading the ticket’s NFT metadata fast enough from IPFS. To fix this, we added a short loading state, optimized our NFT data fetch with caching, and preloaded verification data before scanning. This not only solved the delay but also made the verification experience smoother for buyers at the event gate.” **3. NFT Metadata Not Loading on IPFS** “We also ran into issues with NFT metadata failing to load properly from IPFS, especially when files were large or the network was slow. This could cause event details or seat numbers to appear blank in the marketplace. We solved this by compressing ticket images before upload, storing essential metadata both on-chain and in a lightweight JSON format, and setting up a fallback IPFS gateway. As a result, ticket listings now load reliably regardless of network conditions.”