Your Ticket. Your Wallet. Your Proof.

Live App Demo

ChainTix is a full-stack decentralized application for creating, purchasing, and managing event tickets on the Ethereum blockchain. No middlemen. No hidden fees. Full transparency.

See OVERVIEW.md for a deep dive into the project — problem statement, architecture, and design decisions.

• Browse events by category (Music, Sports, Tech, Arts, Comedy, Conferences)
• Purchase tickets with ETH — ticket price + gas, no service fees
• Transfer tickets to any Ethereum address
• Request refunds before the organizer-set deadline
• On-chain proof of ticket ownership

• Create events with custom pricing, capacity, and refund policies
• Validate tickets at the door with on-chain verification
• Withdraw revenue directly to your wallet after event completion
• Cancel events with automatic refund eligibility for attendees

• Built against SWC Registry standards (15+ vulnerability classes checked)
• ReentrancyGuard on all ETH-transferring functions
• Checks-Effects-Interactions pattern throughout
• Pull-over-push refund mechanism (no DoS on cancel)
• Pausable emergency stop
• 100% line coverage, 93% branch coverage on smart contract

• Solidity 0.8.24 (exact pragma — no floating version)
• Foundry (forge, cast, anvil)
• OpenZeppelin Contracts (ReentrancyGuard, Pausable, Ownable)

• React 18 + TypeScript + Vite
• ethers.js v6 for blockchain interaction
• Tailwind CSS v4 with light/dark mode
• Framer Motion for animations
• React Router v6 for client-side routing

event-ticketing-dapp/
├── src/
│   └── EventTicketing.sol          # Main smart contract (602 lines)
├── test/
│   └── EventTicketing.t.sol        # 77 Foundry tests (1261 lines)
├── script/
│   └── Deploy.s.sol                # Deployment script
├── audit/
│   ├── SECURITY_AUDIT.md           # Full smart contract audit report
│   ├── FRONTEND_SECURITY.md        # Frontend security assessment
│   └── DAPP_AUDIT_CHECKLIST.md     # Reusable audit template
├── frontend/
│   ├── src/
│   │   ├── abi/
│   │   │   └── EventTicketing.json # Contract ABI
│   │   ├── components/
│   │   │   ├── events/             # EventCard, EventGrid, EventDetails, CreateEventForm
│   │   │   ├── tickets/            # TicketCard
│   │   │   ├── wallet/             # ConnectButton, WalletContext
│   │   │   ├── layout/             # Header, Footer, Layout
│   │   │   ├── theme/              # ThemeContext (light/dark mode)
│   │   │   └── ui/                 # Skeleton, StatusBadge, TransactionStatus
│   │   ├── hooks/
│   │   │   ├── useWallet.ts        # Wallet connection + chain validation
│   │   │   ├── useContract.ts      # Contract instance management
│   │   │   ├── useEvents.ts        # Event data fetching
│   │   │   └── useTickets.ts       # Ticket data fetching
│   │   ├── lib/
│   │   │   ├── constants.ts        # Chain config, env vars
│   │   │   ├── contract.ts         # Contract helpers, error parsing
│   │   │   ├── formatters.ts       # ETH, date, address formatting
│   │   │   └── seedData.ts         # Demo event data
│   │   ├── pages/
│   │   │   ├── HomePage.tsx         # Landing page (11 sections)
│   │   │   ├── EventsPage.tsx       # Event browsing + filtering
│   │   │   ├── EventPage.tsx        # Event detail + purchase
│   │   │   ├── CreateEventPage.tsx   # Create event form
│   │   │   ├── MyTicketsPage.tsx     # User's ticket collection
│   │   │   ├── OrganizerDashboard.tsx # Organizer management
│   │   │   └── NotFoundPage.tsx
│   │   └── types/
│   │       └── index.ts            # TypeScript type definitions
│   ├── index.html
│   ├── package.json
│   └── vite.config.ts
├── screenshots/
│   ├── home-page.png              # Landing page screenshot
│   ├── trending-events.png        # Event browsing screenshot
│   └── create-event.png           # Create event screenshot
├── .env.example
├── foundry.toml
├── OVERVIEW.md                     # Project deep dive & architecture
├── .github/
│   └── workflows/
│       └── test.yml                # CI: forge test on push
└── README.md

• Node.js 18+
• Foundry (curl -L https://foundry.paradigm.xyz | bash && foundryup)
• MetaMask browser extension

# Install dependencies
forge install

# Run tests
forge test -vvv

# Run tests with gas report
forge test --gas-report

# Check coverage
forge coverage

# Start local blockchain
anvil --chain-id 31337

# Deploy (in a new terminal)
forge script script/Deploy.s.sol --rpc-url http://localhost:8545 --broadcast

cd frontend

# Install dependencies
npm install

# Create .env file
cp .env.example .env
# Edit .env with your contract address from deployment output

# Start dev server
npm run dev

Smart Contract (.env):

PRIVATE_KEY=0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80
RPC_URL=http://localhost:8545

Frontend (frontend/.env):

VITE_CONTRACT_ADDRESS=0x...  # From deployment output
VITE_CHAIN_ID=31337
VITE_RPC_URL=http://localhost:8545

Note: The private key above is the default Anvil development key. Never use it with real funds.

See audit/SECURITY_AUDIT.md for the full smart contract audit report. See audit/FRONTEND_SECURITY.md for the frontend security assessment.

forge test -vvv

77 tests across these categories:

Coverage: 100% lines, 98.62% statements, 93.10% branches, 100% functions

1. No ERC-721: Tickets are tracked via mappings, not NFTs. Simpler, cheaper gas. ERC-721 is a future upgrade path for marketplace interoperability.
2. Pull-over-push refunds: cancelEvent sets status only. Users claim refunds individually via requestRefund. Prevents DoS from a single failing refund blocking all others.
3. Sequential IDs: Ticket and event IDs are sequential counters (no randomness needed, avoids SWC-120).
4. Internal balance tracking: Revenue and refunds tracked via _withdrawnAmounts and _refundedAmounts mappings. Never uses address(this).balance for business logic (SWC-132).
5. Exact payment: purchaseTickets requires exact ETH — no overpayment accepted. Eliminates excess-refund complexity.
6. Custom errors: Gas-efficient custom errors instead of revert strings for all validation failures.

• ERC-721 token standard for ticket NFTs
• Commit-reveal purchase scheme for high-demand events (anti front-running)
• Multi-chain deployment (Polygon, Base, Arbitrum)
• IPFS integration for event images and metadata
• Secondary market with royalties to organizers
• Subgraph for event indexing (The Graph)
• Mobile wallet support (WalletConnect v2)
• Fuzz testing with Foundry invariants

MIT