BrightID

• Name: BrightID
• URL: https://www.brightid.org/
• Category: proof-of-personhood middleware / sybil-resistance social-graph control plane
• Summary: BrightID is social-graph uniqueness middleware. The app is the shell. The real system is connection curation, seed and host admission, sponsorship, badge rules, and whatever apps decide counts as enough graph legitimacy.
• 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 computes verification status from that graph instead of exposing civil identity data to apps
  • Issues verification badges such as Meets and Bitu, with additional badge tracks layered on as BrightID changes its verification program
  • Lets apps link to a BrightID and check whether the user meets the badge threshold the app cares about, without receiving the user’s name, profile picture, or connection list
  • Uses sponsorship so a BrightID only needs initial app sponsorship once before it becomes reusable across other integrated apps
  • Extends into its own governance and infrastructure stack through Seed Groups, BrightDAO, and IDChain, where graph legitimacy and validator/community operations start to overlap
• Key claims:
  • BrightID is about uniqueness inside a system, not rich portable identity. The docs are clearer on that point than most downstream descriptions.
  • The real primitive is the social graph plus the badge rules layered on top of it. BrightID is not a neutral attestation wallet.
  • Connection labels, recovery paths, seed-group rules, and host operation show where authority actually sits: graph curation, reporting power, and badge legitimacy.
  • Sponsorship matters because apps help decide whether an identity becomes broadly usable. The bootstrap path is part of the trust model.
  • IDChain and BrightDAO matter because they show BrightID is willing to push graph legitimacy into validator and community-governance machinery, not just app login.
• 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 and human-passport.
• The useful contrast is where uniqueness authority sits: biometric/document issuance and scoring versus social-graph curation.

Control surface

• The leverage sits in host and seed admission, sponsorship, reporting thresholds, recovery handling, badge computation, and which apps decide the graph is good enough.

• Treat BrightID as graph-governed uniqueness middleware, not as a general identity app.

• Last reviewed: 2026-06-18 UTC