Human Passport primary sources — 2026-04-28

Project

• Name: Human Passport (formerly Gitcoin Passport)
• URL: https://passport.human.tech/
• Category: proof-of-personhood infrastructure / sybil-resistance control plane / identity-verification middleware / onchain reputation and compliance-attestation platform
• Whitepaper status: No canonical Human Passport or Gitcoin Passport whitepaper/litepaper found in this pass.

Primary sources reviewed

1. Official site: https://passport.human.tech/

   • Frames Human Passport as a “Sybil Protection Suite” for web3 and notes the former Gitcoin Passport identity.
   • Publicly claims 2M+ users and highlights use cases across airdrops, quadratic funding, governance, communities, gaming, sanctions checks, and AI-access gating.
   • Describes both user-facing verification and partner-facing data/verification products.

2. Developer docs home: https://docs.passport.xyz/

   • Describes Human Passport as an identity-verification application and Sybil-resistance protocol.
   • Enumerates the main developer product surface: Passport Stamps, Passport Embed, Passport Models, Individual Verifications, and Data Services.
   • Useful for understanding the platform as developer infrastructure rather than only a consumer app.

3. Models API introduction: https://docs.passport.xyz/building-with-passport/models/introduction

   • Says the Models API can score any EVM address against multiple human-vs-Sybil models using transaction-history features.
   • Explains how model-based scoring complements Passport Stamps with lower-friction and less gameable verification flows.
   • Reveals current supported model families across Ethereum and major L2s.

4. Open-source repository README: https://raw.githubusercontent.com/passportxyz/passport/main/README.md

   • Preserves the Passport XYZ / Gitcoin Passport architecture narrative and describes Passport as an identity-verification application built around verifiable credentials.
   • Documents the repo structure, local-dev flow, and data sources spanning a hosted scorer/Postgres layer, Ceramic network components, and onchain attestations.
   • Strong signal that the project is more than a marketing site: it has a substantial open-source application and infrastructure lineage.

5. Newton integration blog post: https://passport.human.tech/blog/human-passport-is-now-a-data-oracle-on-newton-protocol

   • Shows Human Passport being used as a data oracle for pre-transaction policy enforcement.
   • Clarifies the three verification signals Human Passport currently foregrounds in this integration: Passport Stamps, Models API, and Proof of Clean Hands.
   • Useful for understanding how the project is evolving from frontend/community gating toward transaction-layer policy use cases.

6. GitHub repository page: https://github.com/passportxyz/passport

   • Confirms current repository continuity under the passportxyz namespace.
   • Useful as a first-party source for repo activity, package structure, and project lineage from Gitcoin Passport to Human Passport.

Takeaways

• Human Passport is best cataloged as sybil-resistance and identity-decisioning infrastructure, not just a reputation score app.
• The most important architectural distinction is the combination of user-supplied credential aggregation, passive wallet scoring, reusable attestations, and partner data services.
• The rebrand matters, but the repo/docs lineage makes the older Gitcoin Passport identity part of the current source-of-truth surface rather than stale trivia.
• No classic whitepaper is necessary to understand the current operating model; the official site + docs + repo corpus is much more informative.