BrightID

• Name: BrightID
• URL: https://www.brightid.org/
• Category: proof-of-personhood infrastructure / sybil-resistance social graph / verification middleware / identity-governance control plane
• Summary: BrightID is best understood not as a generic identity app, but as a social-graph-based proof-of-uniqueness system that lets outside applications ask a narrower question: is this person likely participating only once? Its core mechanism is the combination of curated mutual connections, verification protocols computed over an anonymous social graph, app sponsorship, and a permissioned host/seed layer that can extend or revoke access. That makes it a useful comparison class for Human Passport, Proof of Humanity, OpenRank, and identity-attestation systems: those systems aggregate credentials, register humans, or compute trust scores, while BrightID centers the governance problem of who gets to bootstrap and curate a social graph that downstream apps treat as evidence of unique personhood.
• What it does:
  • Lets each user create a BrightID and make mutual connections with people who actually know them
  • Stores those connections in an anonymous social graph and runs verification protocols over that graph rather than exposing personal identity data to apps
  • Issues verification badges such as Meets and Bitu, with Aura described as an additional verification track under development
  • Lets apps link to a BrightID and check whether the user has the verification badge the app requires, without receiving the user’s name, profile picture, or connection list
  • Uses sponsorship so a BrightID only needs to be sponsored once by an app before it becomes usable across the rest of the integrated app set
  • Extends into adjacent governance and infrastructure layers through Seed Groups, BrightDAO, and IDChain, where verified unique humans can influence validator election and community operations
• Key claims:
  • The official docs consistently frame BrightID as proof of fair access rather than civil identity. That distinction matters because the product is optimized for uniqueness in a system, not for legal identity or rich credential portability.
  • The most analytically useful primitive is the anonymous social graph plus verification protocols. BrightID does not simply store attestations; it computes downstream access badges from graph structure and curated human relationships.
  • The connection-level docs show that the system depends heavily on user curation. Labels like “Already know,” “Just met,” “Suspicious,” and “Recovery” are not cosmetic — they become input into verification and recovery flows.
  • The Seed Group docs expose an important control surface: the system is not purely permissionless social proof. SeedDAO-approved hosts and seed groups can scale verification, and reporting by seed-status holders can directly strip a user’s Meets verification unless counterbalanced by other seed holders.
  • Sponsorship is another underappreciated mechanism. BrightID inserts apps themselves into the identity bootstrap process by having the first connected app usually sponsor the identity for later cross-app use.
  • IDChain shows the project’s broader political ambition: verified unique humans are not only app users but also the electorate for a proof-of-authority sidechain’s validator set. That makes BrightID a governance substrate, not just a login helper.
  • BrightID belongs in the corpus because it sharpens a recurring question across proof-of-personhood systems: when “human uniqueness” is inferred from a graph, where does real authority sit — in graph formation, seed admission, sponsorship, reporting powers, recovery rules, or the badge-computation protocols that apps actually consume?
• Whitepaper: BrightID publishes an official whitepaper page, but the most legible primary materials in this pass were the official site plus the documentation repository pages covering verification badges, connection levels, seed groups, app linking, and IDChain. See ../whitepapers/brightid-primary-sources-2026-05-10.md.
• Sources:
  • https://www.brightid.org/
  • https://www.brightid.org/whitepaper
  • https://github.com/BrightID/BrightID-Docs
  • https://raw.githubusercontent.com/BrightID/BrightID-Docs/master/README.md
  • https://raw.githubusercontent.com/BrightID/BrightID-Docs/master/verifications/README.md
  • https://raw.githubusercontent.com/BrightID/BrightID-Docs/master/verifications/making-connections/connection-levels.md
  • https://raw.githubusercontent.com/BrightID/BrightID-Docs/master/verifications/meets-verification/seed-groups.md
  • https://raw.githubusercontent.com/BrightID/BrightID-Docs/master/linking-brightid-to-applications.md
  • https://raw.githubusercontent.com/BrightID/BrightID-Docs/master/idchain/introduction.md

Internal linkages

• Best read beside world-id, proof-of-humanity, and human-passport.

• The useful contrast is where uniqueness authority sits: biometric issuance, dispute arbitration, or social-graph curation.

• Last reviewed: 2026-05-10 UTC