Human Passport

  • 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
  • Tags: ethereum-ecosystem
  • Summary: Human Passport is a proof-of-personhood decisioning stack, not just a stamp bundle or a Gitcoin rebrand. The useful surface is the combination of credential aggregation, embed flows, wallet scoring, zero-knowledge identity/compliance attestations, and partner data services that downstream apps can treat as admission or routing policy.
  • What it does:
    • Lets users build a Passport from multiple “Stamps” or verifiable credentials spanning web3 activity, web2 activity, KYC, biometrics, web-of-trust signals, and related identity evidence
    • Offers Passport Embed so apps can add Passport verification flows directly inside their own product instead of redirecting users away
    • Offers a Models API that scores any EVM address as more likely human or Sybil from transaction-history features, even if that address has never created a Passport account
    • Offers individual zero-knowledge verifications including government-ID KYC, phone, biometrics, and Proof of Clean Hands sanctions/PEP screening, with reusable onchain attestations for integrated apps
    • Provides batch data services such as Sybil classification, clustering analysis, and custom wallet analysis for ecosystem partners
    • Maintains an open-source Passport application lineage, developer tooling, and docs surface that still exposes the older Passport XYZ / Gitcoin Passport architecture, including the Passport app, IAM service, scorer dependencies, Ceramic-linked data model components, and onchain attestations
  • Key claims:
    • The official site says Human Passport has more than 2M users and positions itself as a “Sybil Protection Suite” used to secure public-goods matching pools, airdrops, governance, community tools, and other web3 programs
    • The developer docs position Passport Stamps as the core product, but make clear the broader platform includes Embed, Models API, individual verifications, and partner data services rather than a single consumer identity app
    • The Models API docs say the system can score any EVM address across ETH L1 and several L2s using hidden model features, which Human Passport frames as lower-friction and harder for Sybils to game than fully transparent scorecard systems alone
    • The open-source Passport repository says identity data spans a hosted Postgres-backed scorer/data layer, Ceramic network components, and onchain attestations across roughly a dozen networks, which is useful for understanding the project as middleware rather than only a frontend site
    • The Newton Protocol integration post shows Human Passport extending beyond frontend gating into pre-transaction policy/oracle use cases, where Stamps, Models, and Proof of Clean Hands can become enforceable contract-layer checks
    • The site explicitly emphasizes privacy-by-design language, saying it does not store names, emails, IPs, or personal identifiers and reduces verification data to hashed signals plus minimal Stamp metadata
  • Whitepaper: No canonical Human Passport or Gitcoin Passport whitepaper/litepaper surfaced in this pass. The clearest current primary sources are the official site, developer docs, open-source Passport repository, and current product blog posts; see ../whitepapers/human-passport-primary-sources-2026-04-28.md.
  • Sources:

Internal linkages

  • Best read beside world-id and self-protocol.

  • The useful contrast is whether anti-sybil authority sits in credential aggregation and scoring or in document-proof middleware.

  • Last reviewed: 2026-06-03 UTC