GreenCheck
Identity System / Design
Community
Details
License Private (gc-claims-link repo is private on GitHub under InsightNetwork org; TypeScript library with example integration code)
Dev Status 🧪 Alpha
Dev Status Detail Concept / Early MVP (requirements specification documented; greencheck.world has a working claim-and-validation web app; gc-claims-link library provides phone claim 2FA and claims retrieval; not yet widely deployed)
Owner NooNAO / NooNet (Brad DeGraf and Charles Blass); NooNet is a fiscally-sponsored project of Planetwork, a 501(c)(3); development by InsightNetwork (kfancy on GitHub)
Governing Body Planetwork (501(c)(3) fiscal sponsor for NooNet) | Fractal network cooperative with liquid democracy (intended future structure, not yet established)
Country USA
Start Year 2022
Stack TypeScript (gc-claims-link library); web-based storage (localStorage for demo, SecureStore for mobile); zustand for state management; SQLite for claims data storage; ArangoDB graph database for the trust graph backend
Funding Nonprofit / Donations (NooNet is fiscally-sponsored by Planetwork 501(c)(3); donations are tax-deductible; no VC funding documented)
Last Investigated Mar 9, 2026
Identity System / Design Attributes
Origins Decentralized identity / Proof of personhood (emerged from NooNAO vision for trust-network-based emergent coordination and collective intelligence; inspired by Vitalik Buterin's proof of personhood concept)
Database ArangoDB (graph database for the social trust graph — nodes are GCIDs, edges are validated relationships with floating-point respect vectors)
Query Language AQL (ArangoDB Query Language for graph traversal and network analytics, e.g., domain-specific authoritativeness based on network centrality)
Data Formats JSON (claims data from GreenCheck server; DID documents; verifiable credentials); microledger format (immutable JSON documents with versioned changes, per JLINC specification)
Mobile Support Yes (gc-claims-link originally built with Expo SecureStore for mobile keystore; phone-based 2FA as primary authentication flow)
Web Support Yes (greencheck.world web application for claims and validation; gc-claims-link library converted to web-based storage for browser integration)
Native Apps TBD (mobile app implied by Expo/SecureStore origins in gc-claims-link; no published app store listing)
Terms Free / Open (intended as commons infrastructure; NooNet is a 501(c)(3) fiscally-sponsored nonprofit project)
Funds Unknown (nonprofit donations; no publicly documented funding rounds)
Based On JLINC (microledger protocol for cryptographically secure portable identity); ArangoDB (graph database); comparable to Gitcoin Passport, Hello.coop, BrightID
Authentication & Identity Intersectional identity + three-friend authentication: users prove sole control of multiple attributes (email, phone via 2FA, OAuth with social services, bookmarklet login tests); uniqueness attested via web-of-trust validation by people who know the user, to a stated confidence level (e.g., 98%)
Storage Model Centralized server with federation path: GreenCheck server stores claims and issues authentication tokens; design specifies that all nodes/edges for a user can be encapsulated in a cryptographically secure microledger portable to any application independent of GreenCheck; IPFS via Ceramic/Hypercore discussed for microledger hosting
Interoperability SSO to any supporting application via GreenCheck IDs; microledger encapsulation allows any application to edit/maintain user identity data independently; blockchain-independent but Web3-friendly (designed for 'Web 2.5' via MagicLink-style onboarding); integration with NextGraph planned (gc-claims-link built for NextGraph compatibility)
Data Portability High (by design): user's complete identity graph (all nodes and edges) can be encapsulated in a portable cryptographic microledger usable by any application; multiple DIDs can be 'owned' by a single GC DID
Governance & Decision Making Fractal network cooperative with liquid democracy: intended to be structured as a self-owning, self-governing social graph; 'extreme decisioning' via trust network delegation/proxy links weighted by domain-specific authoritativeness (network centrality); based on Smartocracy whitepaper (2005 LANL) predating liquid democracy by five years
Identity Standards W3C DIDs (user can have multiple DIDs owned by their GC DID); Verifiable Credentials; JLINC microledger specification; OAuth (for social service attribute proofs)
Identity Standards - List
DID Methods Supported JLINC-based DIDs (microledger-backed); design supports multiple DIDs per user owned by a primary GC DID
DID Methods Supported - List
Key Management Cryptographic attestations for ownership claims; authentication tokens issued by GreenCheck server upon 2FA verification; mobile device keystore (SecureStore) for token storage in native contexts; web localStorage for browser contexts
Credential Types Proof of personhood (attestation of uniqueness — 'this DID corresponds to one and only one human in the GC registry'); ownership attestations (cryptographically secure verifiable claims to control of attributes like email, phone, social accounts); peer validations (other users validate ownership claims, creating trust graph edges)
Credential Types - List
Verification Method Web of trust / three-friend authentication: validators who personally know the user attest to their claims; validations include the GCIDs of validators; attestations carry a stated confidence level; graph analytics detect anomalies for sybil resistance
Privacy Features Pseudonymity (multiple DIDs owned by one GC DID); zero-knowledge attestations (can return only verification that a DID corresponds to a unique human without revealing identity); scoped information disclosure (user controls what additional information is shared beyond uniqueness proof)
Authentication Methods Phone 2FA (primary: phone number collected, GreenCheck server sends 2FA token, user verifies token to receive authentication token); OAuth roundtrips with social services; email 2FA; bookmarklet/browser extension for login-at-application proofs
Revocation Mechanism TBD (not specified in available documentation; microledger versioning could support revocation via updated entries)
Agent Types Supported Humans only (explicitly designed for proof of personhood — 'any human can get one and only one GreenCheck ID'; no organizational or machine agent support documented)
Wallet/Client Types Web application (greencheck.world); mobile-compatible library (gc-claims-link with SecureStore support); intended for embedding in host applications (library designed for NextGraph integration)
Recovery Mechanisms Three-friend authentication (implicit: the web-of-trust validators who attested to the user's identity could re-validate after recovery; microledger portability means identity persists across custodians)
Compliance / Regulations TBD (no specific regulatory compliance documented; designed for sufficient decentralization per Varun Srinivasan's framework)
Credential Exchange Protocols Custom (GreenCheck server API with basic authentication headers; claims retrieval via authenticated token; microledger exchange for portable identity)
Credential Exchange Protocols - List
Trust Framework Web of trust with economic incentives: validations have a cost/value that incentivizes high trust density; sybil and collusion resistance through cost barriers and detection mechanisms; trust density measured via graph analytics; chain of accountability through invitation-only growth (every participant has an accountability chain to their inviter)
Cost Model Free for users (nonprofit infrastructure); validations have implicit cost/value to incentivize quality; future plans for collective value capture and emergent allocation as a fractal commons
Censorship Resistance Moderate (by design): sufficiently decentralized — users own direct relationship with their audience and developers can always build on the network; microledger portability means no single custodian can revoke identity; federation of custodians planned but not yet implemented
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.