Zupass primary sources
Reviewed: 2026-05-10 UTC
Core protocol framing
- https://docs.pcd.team/index
- Main PCD SDK docs and the clearest overview of Zupass as software for storing and managing Proof-Carrying Data.
- https://raw.githubusercontent.com/proofcarryingdata/zupass/main/README.md
- Canonical README; explains the PCD abstraction, example proof types, passport app, and the broad “query a user’s proofs” product thesis.
- https://github.com/proofcarryingdata/zupass
- Main repository for the passport app, SDK, and packages.
Proof and interface model
- https://raw.githubusercontent.com/proofcarryingdata/zupass/main/packages/lib/passport-interface/README.md
- Most useful source for how outside apps actually interact with the passport: popup flow, URL construction, hosted endpoint assumptions, and add/get proof requests.
- https://raw.githubusercontent.com/proofcarryingdata/zupass/main/packages/lib/pcd-types/README.md
- Concise statement of how the repo formalizes
PCDandPCDPackageas reusable interfaces.
- Concise statement of how the repo formalizes
Developer-facing examples and ecosystem context
- https://hackmd.io/@gubsheep/rk4hFy7Gn
- Lightweight developer-resource index pointing to usage examples, sample apps, and integration references.
- https://zupass.org/
- Current hosted passport endpoint / product surface.
Main takeaways from this pass
- Zupass’ distinctive mechanism is a general proof container plus app-query interface, not one fixed identity credential.
- The most important reusable abstraction is PCD itself: claims bundled with proofs under common interfaces for proving, verifying, serialization, and app transport.
- The popup / redirect interface layer is a meaningful control surface because portability depends not only on proof formats but also on how apps request and receive proofs from the hosted passport.
- Zupass is best compared against systems like Sismo and Human Passport as a lower-level proof wallet / transport layer rather than as a scoring or attestation registry product.