
Disco
Prove your access, protect your assets.
Demo
About
The problem it solves **The Utility of Disco: Redefining Privacy-Preserving Event Access** Disco is a privacy-preserving event platform that allows users to prove eligibility, such as age requirements or social media engagement, using Zero-Knowledge proofs without ever exposing their personal data. By automatically provisioning a fresh BitGo wallet for every attendee and routing all cryptographic verification through the Base network, Disco entirely eliminates the risk of doxxing your primary wallet's financial history. We transform event ticketing from a centralized data honeypot into a seamless, trustless, and completely anonymous Web3 experience. Disco fundamentally transforms how we handle identity, social engagement, and access while managing events by shifting the paradigm from "trust-based data sharing" to "trustless cryptographic proof." Here is how it elevates existing tasks and creates a safer environment for both attendees and organizers: * **Elimination of Doxxing Risks:** In the current Web3 ecosystem, token-gated events force users to connect their primary wallets. This exposes their financial history and asset holdings to organizers and network monitors. Disco generates a fresh, disposable BitGo wallet for every event, ensuring high-net-worth individuals or privacy-conscious users can participate without becoming targets. * **Privacy-Preserving Social Engagement (ZK Pass):** Event organizers and community managers often require attendees to follow a specific X (formerly Twitter) account to gain entry, secure a whitelist spot, or access exclusive perks. Traditionally, this requires users to authorize third-party apps, linking their social profiles and exposing their digital footprint. Disco integrates a ZK Pass mechanism that generates a cryptographic proof confirming the user follows the required account, without ever revealing their X handle or linking their social identity to their on-chain wallet.  * **Secure Age and Eligibility Verification:** For events requiring age verification (e.g., 21+ venues) or specific credentials, users currently hand over sensitive IDs to third-party platforms. Disco utilizes client-side Zero-Knowledge (ZK) proofs to verify a binary condition (e.g., `age ≥ 21 == true`) without exposing the underlying birthdate to the network.  * **Frictionless Entry & Automated Treasuries on Base:** While BitGo manages the programmatic wallets, **we use Base for all on-chain verification and interactions**. This ensures that ticket limits, issuance, and cryptographic verification are fully automated, highly scalable, and cost-effective. Attendees simply sign a cryptographic message at the door, streamlining entry logistics while the organizer’s treasury handles ticket revenue securely and trustlessly on the Base network. 
How it's made
Challenges we ran into **Overcoming Architecture Hurdles: ZK Social Verification & Pipeline Synchronization** Building Disco presented two intertwined technical hurdles: securely bridging Web2 social data into a Web3 ZK environment, and managing the asynchronous pipeline between proof generation, BitGo wallet provisioning, and routing all on-chain execution seamlessly through Base. The most significant roadblock was implementing the **ZK Pass** feature. We needed a way to verify that a user followed a specific X account without relying on a centralized database that mapped X handles to wallet addresses (which would defeat the entire privacy premise). Furthermore, generating this proof locally on a user’s device while simultaneously spinning up a fresh BitGo programmatic wallet created a severe race condition. Because we committed to using Base for all on-chain verification and interactions, we had to ensure that the network transactions did not bottleneck the user experience. If network congestion delayed the ZK proof, the wallet provisioning would time out before the Base smart contract could mint the ticket.