The problem zkUID solves

The Problem It Solves

In most events — whether online conferences, hackathons, or real-world meetups — user verification relies on centralized identity systems like emails, phone numbers, or government IDs.
These systems expose sensitive personal data, create privacy risks, and are prone to data leaks and fake registrations.

ZK-Event-Pass solves this by introducing a zero-knowledge-based verification system, where users can prove their identity or ticket ownership without revealing any personal information.

It ensures:

Privacy — no personal data is ever shared with organizers

Security — verifications are mathematically guaranteed using ZK-SNARKs

Transparency — proofs are verified on-chain via smart contracts

Trustless Validation — event organizers don’t need to “trust” a database; the blockchain does it

Ease of Use — users verify in one click using a unique, anonymous ZK-ID

In short, ZK-Event-Pass replaces trust-based identity systems with cryptographic proofs, enabling privacy-first, decentralized, and tamper-proof event verification for both Web2 and Web3 ecosystems.

Challenges we ran into

Building a fully privacy-preserving verification system using ZK-SNARKs came with multiple technical and integration challenges:

Understanding ZK Concepts — grasping how witness generation, trusted setup, and proof verification work was initially difficult.

Integrating SnarkJS with React — ensuring client-side proof generation without breaking browser compatibility or loading heavy libraries was tricky.

Poseidon Hash Implementation — importing and optimizing cryptographic libraries (like circomlibjs) for browser use caused several polyfill and buffer-related errors.

Smart Contract & Frontend Sync — maintaining consistency between on-chain verifier contracts and frontend proof outputs required deep debugging.

Performance & Memory Optimization — generating ZK proofs inside the browser demanded efficient async handling and reduced circuit complexity.

Data Privacy Balance — designing an architecture that securely stores minimal user data off-chain while keeping on-chain verification transparent was challenging.

Each of these challenges taught me how to bridge ZK cryptography, Web3, and traditional web technologies efficiently — making ZK-Event-Pass both technically robust and user-friendly.