Goin' In!
A blockchain ticketing platform that doesn't crash when it matters most
Project Description
The Story
When Jennifer Lopez tickets went on sale in Kazakhstan in April 2025, 25,000 fans watched their screens freeze for four hours. The platform controlling 90% of the country's ticketing market simply collapsed.
This wasn't an isolated incident—when Taylor Swift announced her tour, Ticketmaster received 3.5 billion requests and had to cancel the public sale entirely. When Coldplay tickets went on sale in India, BookMyShow crashed within 10 minutes with a 1.3% success rate.
The Problem
These failures happen because traditional ticketing platforms run on centralized servers built for moderate traffic and require massive infrastructure and large teams to handle peak demand. Even with huge funding, they still crash during major sales.
The Solution
Goin' In! solves this by leveraging blockchain technology with parallel transaction execution. The blockchain approach delivers mathematical guarantees impossible with traditional platforms. While traditional blockchains process transactions one at a time like a single checkout line, parallel execution processes thousands simultaneously like having countless checkout lanes open at once.
See more on this here.
When Kazakhstan's system crashed, the CEO admitted they created "a mass of incorrectly booked orders" - on blockchain, this can't happen because the protocol itself enforces correctness.
How it's Made
Backend: Smart contracts built with Solidity 0.8.19 deployed on Arcology Network, an EVM-compatible blockchain with parallel execution capabilities. The system uses Hardhat v3 as the development framework with Ignition for deterministic deployments.
Frontend: React 18 + Vite build system with ethers.js v6 for blockchain interaction, styled with TailwindCSS v4. The architecture uses npm workspaces as a monorepo structure separating contracts and frontend.
Arcology Parallel Execution Implementation
The project's core innovation leverages Arcology's concurrent library to achieve conflict-free parallel transaction processing.
Each purchase involves three contracts (ERC-20 payment, TicketingCore logic, ERC-721 minting) executing atomically. Arcology's parallel executor processes these complex transactions simultaneously across multiple users without serialization bottlenecks.
See more details on this here.
Hardhat 3 Testing Strategy
Hardhat 3's native Solidity testing framework is used for standard contract logic—deployment, access control, time-locked withdrawals, and basic validation.
Hardhat Ignition is used for smart contract deployment management.
See more details on this here.
Envio HyperIndex Integration
The project uses Envio HyperIndex v2.31.0 to provide a real-time GraphQL API for querying blockchain state without expensive RPC calls or client-side filtering.
See more details in this here.
Disclamer
Due to a bug in Arcology DevNet implementation, rollbacked transactions are still triggering events, which may result in an inaccurate number of purchased tickets displayed in the frontend. However, based on my tests, the integrity of the smart contract data is preserved.
