human.cvhuman.cv

Resources

FAQ

The questions everyone asks first — about what human.cv proves, what stops abuse, and why it’s built the way it is.

Common questions

No, and it never claims to. Proving that a machine wasn’t involved is an unprovable trap. human.cv proves something stronger and verifiable: that a verified human claims a piece of work as theirs and takes responsibility for it — permanently.

Every contribution is signed by a key derived from your root. A claim is a cryptographic proof that the signing key descends from your Proof-of-Personhood-bound root. You can only reveal authorship of keys you actually control.

Derived keys are produced deterministically from your root using a time seed. The link from root to key exists from the moment of creation — it is simply not disclosed. Revealing is a selective-disclosure proof, not a new registration.

Recovery converges on the root. Because every derived key descends from one root, restoring the root re-derives everything and re-establishes the ‘same verified human’ property across all past contributions.

Base gives cheap, consumer-grade on-chain attestations and smart accounts. Arweave gives permanent storage — a conceptual match for leaving a legacy. You can pay for Arweave storage with ETH on Base via Irys.