Rarimo

• Name: Rarimo
• URL: https://docs.rarimo.com/
• Category: zk identity registry / passport-proof middleware / privacy-preserving evidence layer
• Tags: ethereum-ecosystem
• Summary: Rarimo is a zk-registry stack with a passport branch, not a broad identity platform. The real machinery is the shared registry, registrar logic, client-side proving path, and the trusted-verifier fallback used when full document verification is too heavy.
• What it does:
  • Operates a permissionless ZK Registry that stores abstract private statements and commitments in a way that can later be proven without revealing the underlying data
  • Frames the registry as a dedicated ZK Rollup anchored to Ethereum, with state roots that can be synchronized to other chains for cross-ecosystem verification
  • Offers ZK Passport, which turns biometric passports into selective-disclosure identity credentials for proving uniqueness, humanity, citizenship, age, and other passport-derived facts
  • Uses two passport onboarding modes: full verification, where the client proves passport validity and integrity, and light verification, where a trusted Rarimo verifier checks issuer signatures while the client still proves integrity
  • Exposes adjacent application layers including ZK Graph for private reputation proofs, Bionetta for client-side ZKML, the Rarimo App as a self-sovereign identity wallet, and Freedom Tool for privacy-preserving voting
  • Builds toward an ERC-7812-style registry pattern where multiple application-specific registrars can share one standardized evidence layer instead of each identity app inventing its own isolated proof store
• Key claims:
  • Rarimo’s most useful primitive is the registry-and-registrar split. The docs repeatedly frame the core system as a generic statement registry rather than a single product, which makes it a better analytical comparison point for identity middleware than a simple “passport proof app” label would.
  • The full-versus-light verification split is especially important because it shows where decentralization gives way to compatibility. In light mode, a trusted Rarimo verifier checks passport issuer signatures when mobile hardware cannot handle the full path efficiently.
  • The ZK Passport docs explicitly argue for a global shared Merkle tree of passport hashes to create a “privacy network effect,” where more users and more applications make dictionary attacks harder. That is a more specific mechanism claim than generic privacy marketing.
  • The ERC-7812 draft matters because it makes Rarimo legible as a standards-oriented attempt to define a singleton evidence layer for private provable statements, not just a product bundle. That is the strongest reason to keep it in the active corpus.
  • The passport-zk-circuits repository shows that real-world passport proving is messy: different data-group layouts, signature schemes, active-auth support, and document families require parameterized verification flows. Document-support coverage and verifier fallbacks are therefore real governance and compatibility surfaces.
  • Rarimo is useful in the corpus because it separates several layers that identity discussions often flatten together: registry storage, registrar logic, local proof generation, trusted-verifier fallback, document authenticity, proof portability, and downstream app-specific nullifier / voting / reputation design.
• Whitepaper: No single canonical Rarimo whitepaper surfaced in this pass. The strongest primary materials were the official docs for the ZK Registry and ZK Passport, the ERC-7812 draft, and the passport-circuit repository; see ../whitepapers/rarimo-primary-sources-2026-05-10.md.
• Sources:
  • https://docs.rarimo.com/
  • https://docs.rarimo.com/zk-registry/
  • https://docs.rarimo.com/zk-passport/
  • https://eips.ethereum.org/EIPS/eip-7812
  • https://github.com/rarimo/passport-zk-circuits
  • https://github.com/rarimo/passport-zk-circuits-noir
  • https://rarimo.com/learning-hub

Internal linkages

• Best upward reads: self-protocol and world-id.
• Keep the note on registry roots, registrar policy, and verifier fallback rather than letting the passport app shell pretend to be the whole system.

Control surface

• The leverage sits in registry-root publication, registrar business logic, document-support coverage, light-versus-full verification policy, and how downstream apps turn private commitments into voting, uniqueness, or reputation claims.

• Treat Rarimo as registry middleware with a passport branch, not as a generic identity stack.

• Last reviewed: 2026-06-18 UTC