Humanity Protocol

• Name: Humanity Protocol
• URL: https://www.humanity.org/
• Category: biometric proof-of-personhood middleware / verifier stack
• Summary: Humanity Protocol is palm-backed proof-of-personhood middleware. The real product is the enrollment, credential issuance, and verifier path between the scan and the app. Useful biometric branch, not a category center.
• What it does:
  • Uses palm-print or palm-vein enrollment flows to establish a uniqueness claim
  • Issues verifiable credentials tied to proof-of-human and related eligibility claims
  • Uses zero-knowledge and SSI-style framing so applications can verify claims without directly receiving raw biometric data
  • Exposes app integrations through SDK and OAuth-style flows such as Sign in with Humanity
  • Offers an onchain credentials-verification service for smart-contract consumption of selected claims
• Key claims:
  • Humanity’s real product is the enrollment-to-verification pipeline, not a bare biometric primitive.
  • The important trust questions sit around scanner deployment, validator admission, credential issuance, verifier-node policy, and preset claim packaging.
  • The app-facing layer matters because OAuth defaults, SDK ergonomics, and supported presets can make Humanity the easy path for biometric-backed gating.
  • Humanity is not the same kind of system as BrightID or Proof of Humanity, where social graph or challenge arbitration does more of the work.
  • It is also not the same as Human Passport, which is more of a credential-aggregation and score-mediated middleware layer than a single biometric enrollment branch.
• Whitepaper: Humanity publishes its main technical and product framing as an official documentation whitepaper rather than a separate canonical PDF. The strongest primary materials were the whitepaper, the core concepts and biometric-flow docs, the SDK/API docs, and the onchain verification-service docs. See ../whitepapers/humanity-protocol-primary-sources-2026-05-10.md.
• Sources:
  • https://www.humanity.org/
  • https://docs.humanity.org/
  • https://docs.humanity.org/whitepaper.md
  • https://docs.humanity.org/understanding-humanity/what-is-humanity
  • https://docs.humanity.org/understanding-humanity/how-biometric-proof-of-humanity-works
  • https://docs.humanity.org/understanding-humanity/core-concepts-verifiable-credentials-and-ssi
  • https://docs.humanity.org/build-with-humanity/build-with-the-sdk-api/sdk-quickstart
  • https://docs.humanity.org/build-with-humanity/build-on-chain/credentials-verification-service

Internal linkages

• Keep the comparisons pointed upward: world-id and human-passport.

Control surface

• The leverage sits in enrollment hardware, validator admission, claim presets, verifier operation, and which apps start treating Humanity proofs as good enough by default.

• Palm scans are just the intake. The power is in the operator stack that decides who can enroll, what gets issued, and how verifiers consume it.

• Last reviewed: 2026-06-18 UTC