Omnid

• Name: Omnid
• URL: https://omnid.io/
• Category: identity-and-reputation middleware / zk-membership coordination / social-recovery trust-graph tooling
• Summary: Omnid is a mixed stack: wallet scoring, private commitments, anonymous group proofs, cross-chain group management, and proof relay. That bundle is the point. It shows what happens when reputation, membership, trust graphs, and delivery middleware get collapsed into one operator surface.
• What it does:
  • Aggregates many onchain and offchain signals into a signed per-address TrustScore and public profile API response
  • Supports different authentication modes for public profile access, private ZK commitments, and user-permitted vault data
  • Uses Semaphore-style group-membership proofs so users can prove inclusion without revealing identity
  • Exposes a cross-chain forwarder flow for verifying proofs and sending messages back to a base-chain GroupManager
  • Treats real-world Connections as protocol input for social recovery, trust graphs, and people discovery
  • Operates a transaction relay that submits login and membership proofs onchain while claiming gasless UX and privacy-preserving relay behavior
• Key claims:
  • The V1 API docs make the main operator surface plain: Omnid aggregates many reputation sources into one signed TrustScore, so source inclusion, weighting, recomputation, and API-signature authority matter more than any generic identity branding.
  • The authentication split is analytically useful because Omnid separates public profile access, private ZK attributes, and user-permitted vault data instead of pretending they are one thing.
  • The group-proof and cross-chain docs show Omnid wants scores and identity data to feed anonymous membership checks and cross-chain verification flows, not just dashboards.
  • The Connections layer matters because it ties trust graphs and social recovery into the same stack as wallet scoring and anonymous membership proofs.
  • The relay docs reveal another choke point: Omnid does not stop at proof creation; it also offers the delivery path for login and membership proofs, which means portability can still end in operator-managed submission.
  • The broad contract surface around GroupManager, verifier contracts, registries, metadata extensions, and the LoginApp makes this more infrastructural than the marketing copy alone suggests.
• Whitepaper: No canonical standalone Omnid whitepaper or litepaper surfaced in this pass. The strongest primary materials were the official essays, docs pages, raw docs repository, and deployment / relay docs collected in ../whitepapers/omnid-primary-sources-2026-05-10.md.
• Sources:
  • https://omnid.io/
  • https://omnid.io/essay/what-we-are-building
  • https://docs.omnid.io/
  • https://github.com/anudit/omniddocs
  • https://raw.githubusercontent.com/anudit/omniddocs/main/content/protocol/index.mdx
  • https://raw.githubusercontent.com/anudit/omniddocs/main/content/protocol/authentication.mdx
  • https://raw.githubusercontent.com/anudit/omniddocs/main/content/protocol/zk-proofs.mdx
  • https://raw.githubusercontent.com/anudit/omniddocs/main/content/protocol/cross-chain.mdx
  • https://raw.githubusercontent.com/anudit/omniddocs/main/content/protocol/connections.mdx
  • https://raw.githubusercontent.com/anudit/omniddocs/main/content/v1/api.mdx
  • https://raw.githubusercontent.com/anudit/omniddocs/main/content/integration/transaction-relay.mdx
  • https://raw.githubusercontent.com/anudit/omniddocs/main/content/integration/deployments.mdx

Internal linkages

• Best upward reads: human-passport, openrank, and brightid.
• Use Omnid when the question is how score aggregation, group admission, and proof delivery get bundled together instead of staying separate.

Control surface

• Power sits in source inclusion and weighting for TrustScore, group-manager and forwarder policy, verifier deployment, and the relay path that actually submits proofs.

• Read it as a bundled identity-control stack, not as a clean neutral primitive.

• Last reviewed: 2026-06-04 UTC