Proof of Humanity
- Name: Proof of Humanity
- URL: https://proofofhumanity.id/
- Category: proof-of-personhood registry / dispute-resolved identity infrastructure / sybil-resistance governance primitive
- Summary: Proof of Humanity is best understood not as a simple signup list, but as a human registry whose core mechanism combines public identity claims, social vouching, challengeability, and Kleros-mediated dispute resolution. Its newer cross-chain design adds a persistent humanity identifier that can move across chains while preserving the one-human-one-registry logic. That makes it a useful comparison class for BrightID, Human Passport, and attestation systems: those systems rely more on graphs, credential bundles, or issuer attestations, while Proof of Humanity turns uniqueness into an adversarial registry process where the decisive control surfaces are evidence, challenge rules, and the arbitration layer.
- What it does:
- Lets users submit a human profile with identifying media and social verification so they can be admitted to a sybil-resistant human registry
- Uses vouching, pending requests, and registry state transitions to determine whether an applicant or existing registrant remains accepted
- Exposes onchain registry contracts so integrators can query whether an address is human or retrieve the bound humanity identifier
- In v2, introduces a non-transferable Humanity ID that links a human to a persistent identifier rather than only to one wallet address
- Supports cross-chain deployments and tells integrators to read state through CrossChainProofOfHumanity rather than chain-local registries
- Makes the registry usable for one-person-one-vote governance, anti-sybil funding, universal-basic-income-style distributions, and other systems that need a challengeable list of humans
- Key claims:
- The official docs define Proof of Humanity as a sybil-resistant registry created from social verification plus video submission. The important analytical move is that PoH is not trying to solve generic identity; it is trying to maintain an adversarially robust list of humans.
- The central reusable mechanism is not the submission form but the dispute system. Proof of Humanity matters because any claim can be challenged, and registry membership is ultimately stabilized by Kleros-style arbitration and policy rules rather than only by upfront credential checking.
- The v2 design is especially important because it shifts the model from “is this wallet currently registered?” toward “which persistent humanity identifier is this address currently bound to?” That is a meaningful architectural change for recovery, reputation continuity, and multi-chain use.
- The cross-chain contracts make explicit that PoH is trying to become middleware. Integrations are told to rely on a chain-specific cross-chain proxy, not the local registry implementation, which means the project is standardizing a portability layer for human-status queries.
- The governance/forum materials indicate that one of the hardest problems is not proving a person exists, but managing edge cases like family custody, identity theft, profile farming, privacy layers, and how to preserve one-human-one-ID semantics under recovery or migration.
- PoH is a strong corpus entry because it reveals a different control plane from graph-based systems like BrightID. Authority sits in policy, challenge rights, evidence presentation, arbitrator design, and contract upgrade paths more than in social-graph topology.
- The reusable insight is that proof-of-personhood systems can centralize in very different places: seed hosts and graph curation in BrightID, credential vendors and score weights in Human Passport, or dispute policy and arbitration throughput in Proof of Humanity.
- Whitepaper: No standalone PoH-native whitepaper PDF surfaced as the clearest current canonical reference in this pass. The strongest primary materials reviewed here were the official PoH/Kleros docs plus the v1 and v2 contract repositories and governance materials; see
../whitepapers/proof-of-humanity-primary-sources-2026-05-10.md. - Sources:
- https://proofofhumanity.id/
- https://docs.kleros.io/products/proof-of-humanity
- https://github.com/Proof-Of-Humanity/Proof-Of-Humanity
- https://raw.githubusercontent.com/Proof-Of-Humanity/Proof-Of-Humanity/master/README.md
- https://github.com/Proof-Of-Humanity/proof-of-humanity-v2-contracts
- https://raw.githubusercontent.com/Proof-Of-Humanity/proof-of-humanity-v2-contracts/master/README.md
- https://raw.githubusercontent.com/Proof-Of-Humanity/proof-of-humanity-v2-contracts/master/contracts/interfaces/IProofOfHumanity.sol
- https://gov.proofofhumanity.id/
- https://gov.proofofhumanity.id/t/the-way-forward-for-proof-of-humanity-origin/2861
Internal linkages
-
Best reads beside this note: kleros, brightid, and human-passport.
-
Last reviewed: 2026-05-28 UTC