The problem Ticketmist solves

🛠️ The Problem It Solves
Traditional ticketing systems often suffer from:

❌ Ticket Scalping: Bots or third parties buy in bulk and resell at inflated prices.

❌ Fraudulent Tickets: Fake or duplicated tickets lead to entry denial and user frustration.

❌ Lack of Ownership: Users don’t truly own their tickets — they’re just entries in a centralized database.

❌ No Interoperability: Tickets can’t be easily used across apps, resold with traceability, or verified on-chain.

❌ Limited Transparency: Event organizers have minimal visibility into real ticket holders and resale activity.

✅ How the NFT Ticketing System Helps
With NFT Ticketing on Base Sepolia using Onchain Kit, we solve these problems:

🔒 Fraud-Proof Tickets
Every ticket is a unique, verifiable NFT stored on-chain. No duplicates, no scams.

🤖 Anti-Scalping
By making NFTs non-transferable (soulbound) or limiting minting per wallet, scalping is reduced or eliminated.

🎫 User Ownership
Users fully own their tickets in their wallets. Tickets can be visualized, verified, and potentially used as collectibles.

🚀 Seamless Experience with Onchain Kit
Wallet onboarding, minting, and ticket verification become smooth and user-friendly — no complex setup needed.

🔍 Full Transparency
Both users and event organizers can track ticket supply, ownership, and usage on-chain in real time.

🧩 Composability
Ticket NFTs can be integrated with loyalty rewards, airdrops, gated experiences, or post-event POAPs.

Challenges I ran into

🐞 Challenges I Ran Into
While building the NFT Ticketing System with Onchain Kit on Base Sepolia, I encountered a few interesting hurdles:

1. ⚠️ Onchain Kit Integration Issues
   Problem:
   Onchain Kit is powerful, but getting it to work seamlessly with wagmi, viem, and Base Sepolia required proper configuration. Wallet connection would sometimes fail or not display the correct network.

Solution:
I carefully aligned the viem with Base Sepolia chain ID and ensured correct providers were used. Also updated to the latest Onchain Kit version and checked compatibility across dependencies.

2. 📦 IPFS Metadata Not Rendering Properly
   Problem:
   Even after uploading metadata to IPFS using Pinata, the NFT image and attributes weren’t loading properly on frontend or marketplaces.

Solution:
I double-checked the structure of the JSON metadata. The issue was with the formatting of the image CID — I had to ensure it followed the proper IPFS URI format (ipfs://...). Using a public IPFS gateway (like https://gateway.pinata.cloud/ipfs/) helped during local testing.

3. 🧪 Base Sepolia Faucet Limits
   Problem:
   Base sepolia is hard to get as faucets availibilty is there but they require a mainnet balance.

solution:
finally found some wallets with free baseSepolia.

4. 🔒 Soulbound NFT Logic
   Problem:
   Making NFTs non-transferable required overriding transfer functions properly — but doing so without breaking ERC-721 compatibility took careful contract structuring.

Solution:
I overrode the _beforeTokenTransfer function to restrict transfers after minting, while still allowing safe minting and viewing. I also tested using OpenZeppelin's test suite as a reference.