Human Passport

Identity Toolkit / Platform

A Sybil resistance and proof-of-personhood identity toolkit (formerly Gitcoin Passport) that aggregates identity Stamps — verifiable credentials from multiple Web2 and Web3 identity providers — and computes a Unique Humanity Score for each user. Applications integrate Human Passport to gate access, protect rewards, and ensure governance participation is limited to unique humans. Originally built by Gitcoin to protect quadratic funding rounds; acquired by Holonym Foundation in February 2025 and integrated into the human.tech suite, with credentials migrating toward ZK proof-based verification via the Human Network. Over 2.1M users and 34.5M+ credentials issued; helped distribute $225M+ in grants and airdrops.

Community
Links
Visit Community

Details

License MIT / Apache-2.0; https://github.com/passportxyz — passport app, passport-scorer, passport-sdk, eas-proxy, and related repos
Dev Status 🟢 Active
Dev Status Detail Released (2.1M+ users; 34.5M+ credentials; active development; migrating to ZK-based credential issuance via Human Network on Eigenlayer)
Owner Holonym Foundation (acquired from Gitcoin/Passport XYZ in February 2025); previously Passport XYZ (spun out from Gitcoin Foundation in 2024); Kyle Weiss (CEO) and Jeremy Dillingham (co-lead) continuing in Holonym leadership
Country USA
Start Year 2022
Stack TypeScript (web app — React/Next.js); Python (scorer API and ML pipeline); Solidity (EAS attestation proxy and on-chain stamp contracts); Jupyter Notebook (data analysis)
Funding Gitcoin ecosystem funding (originally); ~$1M annual revenue at time of acquisition; Holonym Foundation acquisition (undisclosed amount); Human Network backed by Eigenlayer and Symbiotic with $1.4B+ in committed security
Last Investigated Jul 1, 2026

Use Case Domains

Identity & Trust

Identity Toolkit / Platform Attributes

Origins Public Goods / Quadratic Funding (created by Gitcoin to provide Sybil resistance for quadratic funding rounds; evolved into general-purpose proof-of-personhood infrastructure)
Database PostgreSQL (primary hosted database for Passport scorer and stamp registry); Ceramic Network (decentralized data streams for passport identity data — mutable, owner-signed); EAS (Ethereum Attestation Service — on-chain attestations across ~12 EVM networks)
Query Language REST API (Stamps API; Scorer API — primary developer integration points)
Data Formats JSON (API responses); Verifiable Credentials (W3C VC format for Stamps); JSON-LD (Ceramic data streams); on-chain attestations via EAS
Mobile Support Partial mobile support (web app mobile-accessible via browser; no dedicated native app)
Web Support Yes (app.passport.xyz — primary end-user interface; docs.passport.xyz for developers)
Native Apps N/A (no native desktop app)
Terms Freemium SaaS (free for end users to create Passport and collect Stamps; API access for developers — free tier available; paid plans for organizations; custom enterprise deployments)
Funds Undisclosed acquisition price; ~$1M ARR at acquisition; Eigenlayer/Symbiotic $1.4B+ committed security for Human Network
Based On Ceramic Network (decentralized data storage); W3C Verifiable Credentials (Stamp format); EAS — Ethereum Attestation Service (on-chain attestations); Eigenlayer (Human Network AVS post-acquisition); BrightID, ENS, Proof of Humanity, and other identity providers as Stamp sources
Permissions Application-defined (Human Passport provides the score and Stamp data; integrating applications set their own score thresholds and access rules; Passport itself does not enforce permissions — it is a scoring and credentialing service, not an access control system)
Development Tools Stamps API (REST — retrieve user stamps and scores for a given Ethereum address); Scorer API (REST — compute Unique Humanity Score; configurable scoring algorithms); Passport Embed (drop-in JavaScript widget for dApps to add passport-gating in minutes); Passport SDK (npm TypeScript libraries for Ceramic interaction and stamp management); EAS Proxy (Solidity contracts for publishing attestations on-chain); API Playground (interactive docs at docs.passport.xyz)
Authentication & Identity Ethereum wallet-based (Sign-In with Ethereum — EIP-4361; users connect wallet to create Passport anchored to Ethereum address; Stamps aggregated from multiple identity providers; ZK proofs being introduced via Human Network)
Storage Model Hybrid (Ceramic Network — decentralized mutable data streams owned by user; PostgreSQL — centralized hosted scorer database; on-chain EAS attestations across ~12 EVM networks; migrating toward ZK credential issuance via Human Network)
Interoperability Wide (aggregates 30+ identity Stamp providers including BrightID, ENS, Proof of Humanity, Google, GitHub, Discord, Coinbase, Holonym; EAS attestations compatible with any EVM chain; Stamps API and Scorer API open for any application; integrations with Snapshot, Guild, Bankless Academy, Gitcoin Grants, Lido Finance, Shape Network)
Data Portability Portable (Passport data on Ceramic is owner-controlled and portable across applications; EAS attestations portable across EVM chains; Stamps API allows any app to read user's stamp collection)
Governance & Decision Making Holonym Foundation governance (post-acquisition; foundation-governed; previously Gitcoin Foundation and Passport XYZ workstream; community input via Gitcoin governance forum)
Identity Standards W3C Verifiable Credentials (Stamps are issued as VCs); EAS (Ethereum Attestation Service — on-chain VC-equivalent attestations); SIWE / EIP-4361 (wallet authentication)
DID Methods Supported did:pkh (Ethereum address-based DID via SIWE); Ceramic ComposeDB streams (not strictly a DID method but owner-controlled identity streams)
Key Management User-controlled (Ethereum wallet — MetaMask, WalletConnect, or similar; private key held by user; Ceramic streams signed by user's wallet key)
Credential Types Aggregated Stamps (verifiable credentials from 30+ providers including social accounts, biometrics, on-chain history, government ID via ZK KYC, BrightID uniqueness); Unique Humanity Score (composite score from weighted Stamps); ZK proofs (in development via Human Network)
Verification Method Multi-source aggregation (each Stamp verified by its issuing provider — Google OAuth, GitHub OAuth, ENS ownership check, BrightID API, Proof of Humanity on-chain check, etc.); Scorer API computes weighted composite score; ZK proofs being added for privacy-preserving verification
Privacy Features No PII stored (Stamps store only hashed credential metadata; no names, emails, or IPs retained per privacy policy); selective disclosure (users choose which Stamps to share); ZK proofs being introduced to prevent credential correlation; unlinkability being developed via Human Network
Authentication Methods Sign-In with Ethereum (SIWE / EIP-4361 — primary authentication); OAuth (for Web2 Stamp providers — Google, GitHub, Discord, etc.); on-chain wallet verification
Revocation Mechanism Stamp expiry (Stamps have validity periods and must be refreshed; no formal on-chain revocation; scorer recalculates dynamically)
Agent Types Supported Humans (individuals only; designed specifically to verify unique human personhood, not organizations or agents)
Wallet/Client Types Web browser (app.passport.xyz — primary interface); any Ethereum wallet (MetaMask, WalletConnect, Coinbase Wallet, Rainbow, etc.)
Recovery Mechanisms Wallet recovery (recovery depends on Ethereum wallet recovery mechanisms — seed phrase, social recovery wallets, etc.; Passport data on Ceramic recoverable if wallet access restored)
Compliance / Regulations Privacy-by-design (no PII stored); GDPR-aligned (minimal data retention); no formal KYC/AML compliance though ZK KYC Stamp available for applications requiring it
Credential Exchange Protocols Custom REST (Stamps API — retrieve user's stamps and scores; Scorer API — compute Unique Humanity Score for an address); Passport Embed (drop-in widget for dApps); Passport SDK (npm libraries for Ceramic interaction)
Trust Framework Application-defined (integrating applications set their own score thresholds for access gating; Passport itself does not enforce permissions — it provides the score and Stamp data for applications to act on)
Cost Model Source: https://passport.human.tech/ — Human Passport current site (post-acquisition): proof of personhood tools; data services; 2M+ users; use cases (airdrops, governance, social, KYC); privacy policy | Source: https://passport.human.tech/blog/from-gitcoin-passport-to-human-passport-we-re-now-part-of-human-tech — Acquisition announcement February 2025: Holonym Foundation acquires Gitcoin Passport; Kyle Weiss CEO; Jeremy Dillingham co-lead; Human Network on Eigenlayer/Symbiotic; $1.4B+ committed security; 34.5M credentials; $225M+ distributed; ZK credential migration | Source: https://blog.ceramic.network/gitcoin-builds-passport-on-ceramic/ — Ceramic blog on Gitcoin Passport architecture: Ceramic data streams; W3C VC Stamps; quadratic funding Sybil resistance origins; GR14/GR15 history; SIWE authentication; portability principles | Source: https://github.com/passportxyz — GitHub org: passport app (TypeScript/React); passport-scorer (Python); passport-sdk (npm); eas-proxy (Solidity); PostgreSQL + Ceramic + EAS storage architecture; MIT/Apache-2.0 license
Censorship Resistance Moderate (Ceramic data streams are owner-controlled and censorship-resistant at the data layer; EAS attestations on-chain are permanent and uncensorable; however the hosted PostgreSQL scorer database and the app.passport.xyz interface are centrally operated by Holonym Foundation and subject to takedown; ZK credential migration via Human Network on Eigenlayer improves censorship resistance at the credential layer)