Anonibara

Anonibara is an identity platform that allows communities to recognize real builders and grant them real-world benefits — without ever exposing their personal data.

Users verify themselves by scanning their passport using Self Protocol, generating a zero-knowledge proof of humanity. This proof is tied to their ENS name, which becomes a reusable identity pass. They can then apply to join a community (like Crecimiento, Urbe, or Edge City), and if accepted, they receive an ENS subdomain (e.g. messi.crecimiento.eth) that acts as their credential for accessing gated spaces.

Communities, on the other hand, receive a simple dashboard to: • Create community access policies • Review applications • Auto-approve members based on verified zk criteria • Mint identity subdomains tied to zk-proofs • Gate access in real time via NFC, QR, or ENS resolution

Anonibara transforms messy spreadsheets, Discord role hacks, and manual onboarding into a sovereign access layer built on programmable credentials, zero-knowledge proofs, and decentralized identity.

Anonibara is built as a fullstack app combining zk identity, ENS naming, and access control flows. • Self Protocol is used to scan passports and generate zero-knowledge proofs. These proofs are either validated offchain or via Self’s onchain SDK on the Celo testnet. • ENS is used to issue both user-owned names and community subdomains (e.g. anonibara.crecimiento.eth). Credentials are linked via textRecords on ENS and verified at the point of access. • v0.dev powers the entire frontend in a fast, visually balanced component system, with flows for both “person” and “business” modes. • The backend is built with Node/Express and includes logic for: • Community creation and credential management • Credential verification • Subdomain minting • Automatic application approval based on zk-proof metadata (e.g. country, age) • NFC/QR flows are built for physical unlocks, simulating real-world interactions with doors, turnstiles, or access gates.

Notable hacks: • We used ENS textRecords as both proof pointers and policy registries — enabling a single ENS name to store zk credentials, access requirements, and status flags. • Auto-approval is implemented by resolving and interpreting the proof metadata on submission — no human interaction needed. • We simulate physical access control by integrating QR/NFC with ENS → zkProof → YES/NO resolution in <1 second.

Tech Stack: Self Protocol, ENS (L2 + Base), v0.dev, Node.js/Express, Celo testnet, NFC tools, zk-proofs, REST API.