Humanity Protocol primary sources
Reviewed: 2026-05-10 UTC
Core protocol framing
- https://www.humanity.org/
- Official site frames Humanity as an internet trust layer focused on privacy-preserving verification without storing user data.
- https://docs.humanity.org/
- Developer docs entrypoint showing the two main integration paths: SDK/API for web and mobile apps, and direct onchain integration for smart contracts.
- https://docs.humanity.org/whitepaper.md
- Main protocol whitepaper; best high-level source for the Proof-of-Humanity / Proof-of-Trust framing, token model, node roles, biometric approach, and broader trust-layer thesis.
Biometric and SSI mechanism
- https://docs.humanity.org/understanding-humanity/what-is-humanity
- Concise official description of Humanity as an EVM-based biometric proof-of-humanity system.
- https://docs.humanity.org/understanding-humanity/how-biometric-proof-of-humanity-works
- Most useful short source for the enrollment split: mobile palm-print enrollment versus hardware palm-vein scanners, both wrapped in zero-knowledge-based privacy claims.
- https://docs.humanity.org/understanding-humanity/core-concepts-verifiable-credentials-and-ssi
- Best source for the internal stack: verifiable credentials, SSI framing, IPFS-backed encrypted metadata, zkProofer nodes, and the role biometrics play in uniqueness.
App-facing integration and oracle layer
- https://docs.humanity.org/build-with-humanity/build-with-the-sdk-api/sdk-quickstart
- Shows Humanity’s app wedge clearly: OAuth-style
Sign in with Humanity, scoped data requests, and directis_humanverification checks in a React app.
- Shows Humanity’s app wedge clearly: OAuth-style
- https://docs.humanity.org/build-with-humanity/build-on-chain/credentials-verification-service
- Best source for the broader claim-verification surface: smart contracts can request proof of palm verification, social-account connection, KYC, finance, loyalty memberships, and related conditions through an oracle callback flow.
Main takeaways from this pass
- Humanity’s distinguishing mechanism is a split trust stack: biometric uniqueness capture, credential issuance, privacy-preserving proofing, and app-facing verification infrastructure.
- The key governance surfaces are enrollment hardware and biometric models, issuer / Identity Validator admission, zkProofer node licensing and economics, and the preset/oracle catalog exposed to apps.
- Humanity is useful because it separates proof-of-humanity from downstream claim verification: the same stack can gate not just “unique human” status but broader identity, social, financial, and membership predicates.
- The protocol is best compared against other identity and sybil-resistance systems by asking where authority sits: graph formation, dispute resolution, credential aggregation, biometric issuance, verifier nodes, or application-facing OAuth/oracle defaults.