← All work

[ Solo ] Completed (Hackathon)

TicketVault

A Web 2.5 hybrid ticketing platform that leverages Aptos blockchain for NFT tickets with gasless transactions and offline verification.

What it is

TicketVault is a production-grade decentralized ticketing platform built on Aptos blockchain that solves critical industry problems: fraud, scalping, and blockchain adoption barriers. It implements a 'Web 2.5' hybrid architecture where tickets are NFTs with verifiable ownership, buyers enjoy gasless transactions via a relayer service, and venue staff can validate tickets offline using cryptographically signed JWT QR codes. Post-event, tickets transform into collectible digital souvenirs. The platform includes three specialized frontends (organizer dashboard, buyer marketplace, redeemer PWA), a robust Express backend with AI-powered analytics concierge, and a Move smart contract managing the complete ticket lifecycle with state transitions (LOCKED → ADMITTED → SOUVENIR).

Decisions

Build log

  1. Designed the complete system architecture with three-layer separation: Frontend (Next.js) → Backend (Express) → Blockchain (Aptos).
  2. Implemented the Move smart contract with comprehensive ticket lifecycle management and authorization patterns.
  3. Built the RelayerService for true gasless transactions, using a pre-funded Aptos account to sponsor all user operations.
  4. Developed the JWT-based offline verification system with RSA key pair generation and secure public key distribution.
  5. Created the AI Concierge with 6 pre-defined query templates and dynamic MongoDB aggregation pipeline generation.
  6. Implemented multi-layer security: sanitization middleware, rate limiters (4 tiers), and CAPTCHA integration for bot prevention.
  7. Built the Organizer dashboard with real-time analytics, redeemer authorization, and event management capabilities.
  8. Developed the Buyer marketplace with wallet integration (Petra/Martian), CAPTCHA-protected minting, and NFT ticket visualization.
  9. Created the Redeemer PWA with QR code scanning, offline JWT verification, and batch syncing for redemptions.
  10. Established a formal API contract (OpenAPI 3.0) defining all endpoints, request/response schemas, and error codes.
  11. Implemented comprehensive error handling, logging, and monitoring infrastructure for production readiness.