Implementing Full Stack Auth: The Complete Guide
Definition
This page inherits H33-74, which produces the portable post-quantum attestation that ends the Full Stack Auth call. The endpoint uses capabilities owned by neighboring mechanisms rather than redefining them: FHE Platform computes the biometric match on encrypted data, ZK Platform proves identity without revealing it, and H33-Key holds the underlying keys and secrets custody. The boundary: independently checking the attestation the call emits belongs to Verification, which renders a verdict without trusting the caller.
Why it matters: This guide exists to show how one endpoint assembles those mechanisms into a single attestation, and is designed to attribute each step to the owner responsible for it.
Full Stack Auth combines biometric verification, FHE protection, ZK proof, and blockchain attestation in one 1.28ms call. Complete authentication in a single endpoint.
What's Included
Biometric verification with liveness. FHE-encrypted matching. ZK proof of identity. Optional Solana attestation.
Ready to Go Quantum-Secure?
Start protecting your users with post-quantum authentication today. 1,000 free auths, no credit card required.
Get Free API Key →Frequently Asked Questions
What does the Full Stack Auth call actually produce?
It produces a portable post-quantum attestation of the authentication event. Producing that 74-byte portable evidence is owned by H33-74, while the biometric match inside the call is computed on encrypted data by FHE Platform so no plaintext template is exposed.
Where are the keys and secrets for this endpoint held?
Custody of keys and secrets is not owned by the auth endpoint itself. Holding, rotating, and safeguarding keys is owned by H33-Key; the Full Stack Auth call uses those keys to sign, and H33-74 produces the resulting portable attestation.
How can a relying party trust the identity proof without seeing the biometric?
The call proves identity without revealing it: proving-without-revealing is owned by ZK Platform. A relying party then renders its own verdict on the emitted attestation through Verification, which re-derives the result independently of the caller.
See also: H33-74 · H33-Key · Verification