Orange Protocol primary sources
Reviewed: 2026-05-10 UTC
Core protocol framing
- https://docs.orangeprotocol.io/
- Official docs home frames Orange around decentralized identity and reputation.
- https://docs.orangeprotocol.io/overview.md
- The clearest single-page product framing in this pass: Orange describes itself as a reputation and trust minting protocol that aggregates data and Web3 reputation models to generate portable proofs as verifiable credentials or NFTs.
Architecture and control surfaces
- https://docs.orangeprotocol.io/design/architecture.md
- Documents the high-level architecture: GraphQL API server, DP manager, MP manager, dispatcher, reputation minting service, and blockchain record layer.
- https://docs.orangeprotocol.io/design/data-providers.md
- Defines Data Providers as parties that expose schemas and datasets; important for understanding where data-access power sits.
- https://docs.orangeprotocol.io/design/model-providers.md
- Defines Model Providers as parties that design the scoring or reporting logic; important for separating data supply from score computation.
- https://docs.orangeprotocol.io/configurable-reporting.md
- Shows that the protocol treats VCs and NFTs as first-class export layers for moving reputation outputs across apps and chains.
Privacy and authorization model
- https://docs.orangeprotocol.io/data-sovereignty.md
- Core source for Orange’s self-sovereignty claims: DID-linked authorization, required request signatures, selective disclosure, and non-custodial handling.
Orange Pass proving flow
- https://docs.orangeprotocol.io/orangepass/introduction.md
- Defines Orange Pass as a browser extension for proving Web2 information with privacy-preserving techniques and returning proofs to apps or onchain storage.
- https://docs.orangeprotocol.io/orangepass/introduction/mpc-mode.md
- Most useful source for the hidden trust model: notary/verifier role, TLS-session collaboration, transcript commitments, attestation signing, and selective disclosure with optional ZK proofs.
- https://docs.orangeprotocol.io/developer-guides.md
- Documents the practical proof pipeline: schema IDs, extension invocation, schema-configured
pageUrl/apiUrl/ matching rules, notary endpoints, and backend signature verification responsibilities.
- Documents the practical proof pipeline: schema IDs, extension invocation, schema-configured
First-party score surface
- https://docs.orangeprotocol.io/orange-humanity-score-ohs.md
- Shows Orange operating a first-party score product that combines linked Web2 identities, onchain activity, and outside PoH providers such as BrightID and Gitcoin Passport / Human Passport.
Official code/org surface
- https://github.com/orange-protocol
- Official GitHub organization page surfaced in search results; useful as a primary-source handle even though this pass relied mainly on docs pages.
Main takeaways from this pass
- Orange’s strongest reusable primitive is the separation of data providers, model providers, dispatcher/orchestration, and proof minting rather than a single global reputation score.
- Orange Pass introduces a distinct control surface around schema design and notary-issued attestations, making it useful for comparison with credential and proof-of-personhood middleware.
- OHS shows Orange is not just infrastructure; it also operates first-party scoring and campaign-access surfaces that import outside human-verification signals.
- The main analytical question Orange sharpens is where authority sits in a “portable reputation” system: dataset definitions, model design, schema templates, signing/notary roles, or downstream apps that decide which minted proof actually counts.