A privacy-first social identity network proposing a novel approach to proof-of-uniqueness: each person builds a social graph of connections with people who know them, and Sybil resistance is achieved by analyzing that graph rather than via government ID, biometrics, or centralized verification. Fake identities are detected algorithmically by examining the structure of the connection graph using tools like SybilRank and the Aura algorithm. Applications integrate BrightID to ensure each user holds only one account, enabling fair access to public goods, quadratic voting, and community resources.
Proof of humanity Trust graph portability Sovereign identity
Identity System / Design Attributes
OriginsDecentralized Identity / Public Goods (motivated by need for Sybil resistance in quadratic funding and DAO governance without sacrificing privacy or requiring KYC)
DatabaseIDChain (Ethereum-based PoA blockchain storing connection events and verification results as on-chain transactions); IPFS (off-chain data)
Query LanguageREST API (BrightID Node API v5 for verification queries by applications)
Data FormatsJSON (API responses); signed connection data (cryptographic key pairs); on-chain transaction records on IDChain
Mobile SupportMobile support (iOS and Android native apps — primary interface for creating BrightID, making connections via QR code, receiving verifications)
Web SupportYes (web-based Aura verification app at aura.brightid.org; Sponsorships dashboard at sp.brightid.org; Explorer)
Native AppsNative apps (iOS and Android; primary user interface)
TermsFree (no cost to end users; apps pay 1 DAI sponsorship per user lifetime to fund operations; surplus redistributed to verified users)
FundsUndisclosed; self-sustaining via sponsorship model; BrightDAO governs treasury allocation
Based OnNovel architecture — no prior identity standard; informed by social graph analysis research (SybilRank); IDChain built on go-ethereum; Aragon for DAO governance
Authentication & IdentitySocial graph web-of-trust (identity established through real-world and online connection parties; connections are cryptographically signed with user private keys; no personally identifying information stored; verification status derived from graph analysis algorithms)
Storage ModelHybrid (connection graph synchronized via IDChain PoA blockchain — permanent on-chain record of connection events; personal data such as names and photos exchanged only off-chain peer-to-peer and never stored on servers)
InteroperabilityAPI integration for any application; BrightID verifications consumable by Ethereum-compatible smart contracts via on-chain verification templates; integrated with Gitcoin, 1Hive, Giveth, Aragon, clr.fund, and others
Data PortabilitySelf-sovereign (users own their identity and connection data via private key; no central authority controls verification status; graph data is public on IDChain for auditability but names/photos are never stored)
Governance & Decision MakingBrightDAO (Aragon-based DAO on IDChain; governs budget allocation for development, research, community support; governance rights distributed to dApp and community delegates based on sponsorship metrics)
Identity StandardsNone (does not implement W3C DID, W3C VC, or other formal identity standards; novel social graph approach operates outside existing identity paradigms)
DID Methods SupportedNone (no DID method; identity is a BrightID node address derived from user keypair, not a DID)
Key ManagementUser-controlled local keypair (private key generated and stored on mobile device; connections signed with private key; social recovery mechanism available)
Credential TypesProof of Uniqueness (non-transferable; graph-analysis-derived; not a W3C Verifiable Credential — a boolean verification result queryable via API or on-chain)
Verification MethodSocial graph analysis (SybilRank algorithm; Aura algorithm run by independent verification nodes; multiple verification tiers: Meets, Bitu, Aura — each with different trust thresholds)
Privacy FeaturesNo personally identifying information stored; names and photos shared only peer-to-peer off-chain; only connection event hashes stored on IDChain; pseudonymous by design
Authentication MethodsQR code scanning (mobile app; users meet in person or online and scan each other's QR codes to form connections); deep link (brightid:// protocol)
Revocation MechanismNo formal revocation (connections can be removed; verification status recalculated dynamically by graph analysis; no time-bound expiration)
Agent Types SupportedHumans (individuals only; proof-of-uniqueness is specifically for human personhood)
Wallet/Client TypesMobile app (iOS and Android — primary client); Aura web app (secondary verification layer)
Recovery MechanismsSocial recovery (users designate recovery connections; if device lost, recovery connections can collectively restore access); Device recovery via backup
Compliance / RegulationsNo formal compliance framework; GDPR-aligned by design (no PII stored on servers); no KYC/AML
Credential Exchange ProtocolsCustom REST API (BrightID Node v5 API; applications query verification status by Ethereum address); smart contract templates for on-chain verification publishing
Trust FrameworkSocial graph web-of-trust (trust derives from real-world connections and graph analysis; seed groups serve as trusted anchor points; no government-anchored trust)
Cost ModelFree to end users; 1 DAI lifetime sponsorship fee paid by integrating applications per user; no per-query fees
Censorship ResistanceHigh (IDChain is a PoA blockchain not controlled by any single entity; BrightID nodes operated by community; graph analysis open source so anyone can run verification; no central server that can be shut down)
Relationships
How this tool connects to other tools and organizations, from relationships reviewed by the OpenHaven data steward. They describe how projects connect, not how good they are.