The problem VeriPass solves

The Current Crisis in Ticketing

The events and ticketing industry faces three critical vulnerabilities that harm both organizers and legitimate attendees:

Fraud and Counterfeiting: Traditional tickets with static QR codes are vulnerable to screenshots. A single code can be resold to dozens of people, causing chaos at the door and defrauding users.
Speculation in the Secondary Market: Scalpers hoard tickets and sell them at exorbitant markups on unofficial marketplaces. The organizer loses control over the final price and receives no royalties from these secondary transactions.
Technological Friction (The Web3 Barrier): Although blockchain solves the ownership problem, requiring the average user to understand wallets, networks, and gas fees discourages mass adoption.

How Does VeriPass Solve It?

VeriPass tackles these problems by combining the security of blockchain (HashKey Chain) with a seamless user experience, built on three pillars:

Proof of Ownership with Dynamic QR: Our system generates a cryptographic QR code in real time from the user's wallet, and it expires within seconds. This makes screenshots useless and assures Staff that the person at the door is the true owner of the token.
P2P Marketplace Regulated by Smart Contracts: Tickets are traded in a controlled environment where the smart contract enforces strict rules, setting maximum resale prices (eliminating abusive speculation) and automatically paying royalties to the event Manager.
Gas Abstraction and Friendly UX: Designed so attendees can transfer, buy, and validate their tickets without worrying about the transactional complexities of the network, bringing the benefits of Web3 to mainstream users.

VeriPass gives security back to the fans and control back to the organizers.

Challenges we ran into

1. Chain ID Format Mismatch (Web3)

The problem: While integrating the frontend with MetaMask and Ethers.js, we ran into false network blocks. The DApp strictly required the HashKey Testnet (Chain ID 133), but wallets sometimes returned the value in hexadecimal format (0x85) or as a string ('133'), which triggered incorrect-network alerts and locked up the interface.

The solution: We had to normalize the network validation in our JavaScript code, adjusting the logic so the system could interpret and accept the different formats emitted by the Web3 provider without breaking the user experience.

2. Gas Estimation Failures (could not coalesce error)

The problem: When interacting with the Smart Contract to generate and transfer tickets on the P2P marketplace, Ethers.js threw a critical coercion error (could not coalesce error). This happened because the library failed when trying to automatically estimate gas costs on the HSK Testnet, along with desynchronizations of the wallet's internal nonce during testing.

The solution: Instead of relying on automatic estimation, we injected an explicit configuration object (overrides) into the contract calls, forcing a static gas limit (gasLimit). This stabilized communication with the node and allowed the transaction to pass cleanly to the wallet to be signed.

3. Cloud Infrastructure Restrictions

The problem: The original plan was to deploy the backend (FastAPI) on Azure App Service. However, we ran into highly restrictive geographic region policies (denied regions) and processing limits due to the characteristics of the student subscription, which caused infinite loops during server startup.

The solution: We applied an agile, fail-fast mindset. To avoid putting the final presentation at risk, we decided to pivot to a robust local environment, guaranteeing a zero-latency, fully stable demo of the DApp for the judges, while the source code remained clean and auditable on GitHub.