Proof of Authenticity
Proof of Authenticity, in Zelf’s framework, is verification that helps establish continuity between a returning human and a previously established cryptographic identity.
Zelf Core Team
What Is Proof of Authenticity?
Proof of Authenticity answers the question: “Is it the same human?”
Verifying that someone is a live person does not establish that they are the person authorized to access an existing account. A different person could pass a liveness check while attempting to use someone else’s identity.
Proof of Authenticity addresses this distinction. In Zelf’s framework, HumanAuthn uses human-rooted cryptographic verification to help connect the person authenticating with the cryptographic identity established previously.
Here, “authenticity” refers to continuity of the human behind a digital identity. Elsewhere, the term can describe whether a document, product, or piece of media is genuine.
It also differs from verifying a legal identity. Establishing continuity with a digital identity does not necessarily establish a person’s legal name or require a government-issued document.
How Does Proof of Authenticity Work?
At a conceptual level, the process connects an initial enrollment with later authentication events.
1. Establish a Cryptographic Identity
During enrollment, the system establishes a cryptographic identity and a protected relationship between that identity and the enrolling human.
The implementation determines how human-derived information is processed, what verification material is retained, and how cryptographic secrets are protected.
2. Verify the Returning Human
When the person returns, the application requests a fresh interaction.
Liveness verification helps assess whether a live person is participating. Human-rooted verification then helps establish whether that participant corresponds to the identity enrolled earlier.
These checks address different questions: a live participant could still be the wrong person.
3. Validate the Authentication Result
The application validates the resulting cryptographic evidence and checks whether it satisfies the account’s authentication policy.
Cryptography establishes that evidence is valid under a particular key or protocol. Confidence that it represents the same human also depends on the enrollment process, human verification, and the binding between them.
This reflects a broader authentication principle: returning access should provide appropriate assurance that the participant corresponds to the previously established account identity.NIST: Digital Authentication
Why Does Proof of Authenticity Matter?
Possession of a device or knowledge of a password does not always establish who is using it. Devices can be shared or stolen, and credentials can be disclosed.
Proof of Authenticity introduces a human continuity check that can support:
Returning-user authentication: Helping establish that the enrolled person is accessing the account.
Credential protection: Adding a human verification requirement to access protected credentials or cryptographic capabilities.
Recovery processes: Supporting recovery designs that require continuity with the previously enrolled human, alongside any other required recovery material.
These applications depend on the system’s design. Human verification does not automatically replace backups, eliminate every account-takeover risk, or guarantee recovery.
Privacy safeguards are particularly important when human-derived information is involved. The system should protect verification material, minimize unnecessary collection, and explain its retention practices.
Within Zelf’s framework, Proof of Authenticity establishes continuity with the same human. Proof of Presence adds a further question: whether that human is participating in the particular event being authorized.