Proof of Personhood — human.cv Docs

Bind humanity to your root exactly once. Every key you ever derive inherits it — without ever re-running the check.

Why bind it once

Proof of Personhood (PoP) is expensive, awkward, and privacy-sensitive to perform. Repeating it for every identity would be both a burden and a privacy leak. So human.cv attaches PoP a single time, to the root.

Inheritance by construction

Because every derived key descends from the root, the verified human property travels with it automatically. A claim made by a derived key can be checked against the root’s personhood attestation — no re-verification, no new identity check.

Verify personhood a single time at the root.
Derive unlimited contextual identities beneath it.
Each inherits verified-human without leaking the link upward.

What PoP is — and isn’t

PoP attests that one unique human stands behind the root. It is deliberately agnostic about which tools that human uses to create. It answers “is there a single accountable person here?” — not “did a person, unaided, make this artifact?”

Pluggable verification

human.cv treats PoP as a provider interface, not a single vendor. Different communities can require different strengths of personhood — the inheritance model is the same regardless of the method.

Privacy posture

The personhood check lives at the root and is referenced by proof, not by exposure. Derived keys carry the property of being human-backed without carrying the evidence that produced it, keeping your verification material out of every downstream contribution.