orange-pass-primary-sources-2026-05-13

Orange Pass primary sources

Reviewed: 2026-05-13 UTC

Core product framing

• https://docs.orangeprotocol.io/orangepass/introduction
  • Defines Orange Pass as a Chrome extension for proving Web2 information with privacy-preserving techniques and returning proofs either to third-party services or onchain storage.
  • Most important high-level source for the two-mode architecture: Proxy mode by default for performance, MPC mode for cases where proxy access is unsuitable.
• https://www.orangeprotocol.io/
  • Shows Orange’s public framing of Orange Pass as the zkTLS-powered proof layer inside a broader trustless-reputation and Orange Humanity Score stack.

Developer integration and attestation format

• https://docs.orangeprotocol.io/developer-guides
  • Documents the actual integration surface: window.orangePass.start(schemaId, recipient, proxyFirst?), extension installation checks, schema-driven proof sessions, backend verification flow, and the attestation fields returned to applications.
  • Especially useful because it lists the decisive schema parameters: pageUrl, apiUrl, responseMatches, and responseRedactions.
  • Also exposes concrete supported schema examples such as exchange account ownership, KYC status, and balance-threshold proofs for Binance, OKX, Bybit, Gate, and KuCoin.

Hidden trust model and proof-generation flow

• https://docs.orangeprotocol.io/orangepass/introduction/mpc-mode
  • Best source for the notary role. The docs describe joint TLS-session establishment, transcript commitments, notary-side attestation-body construction, private-key signing, and later verifier-side presentation checking.
  • Makes it clear that Orange Pass is not just “prove a website fact locally”; it depends on an attestation-signing intermediary whose signatures downstream apps are expected to trust.

First-party downstream use

• https://docs.orangeprotocol.io/orangepass/how-to-use
  • Shows Orange Pass being used inside Orange Humanity Score, where exchange-account proofs become score inputs.
  • Important for understanding that the product is not just a raw proof rail but a reusable input surface for reputation and sybil-resistance products.
  • Notes that the attestation contains a user_hash linked to the third-party account identifier and that the same user_hash should map to only one recipient.

Official project handle

• https://github.com/orange-protocol
  • Official GitHub organization surfaced in search results; useful as a primary-source handle even though the clearest materials in this pass were the docs pages.

Main takeaways from this pass

• Orange Pass’s main primitive is a schema-plus-notary browser-proof workflow rather than a generic identity credential.
• The decisive control surfaces are schema authorship, extension distribution, mode choice (Proxy versus MPC), and notary signing power.
• The current proof set is strategically narrow and skewed toward exchange-account ownership, KYC, and balance checks, which makes Orange Pass especially relevant for reputation and sybil-resistance analysis.
• Orange Pass is best compared not only to lower-layer web-proof systems like TLSNotary, but also to higher-layer identity and score products that reuse signed attestations as portable inputs.