From your phone to a yes-or-no answer
Five steps carry you from a tap on your phone to a yes-or-no answer anyone can check. At every step we show what each party sees and what it signs.
As you scroll, each step of the trust flow reveals in turn. The diagram stays pinned so you never lose your place.
Reduced motion is on, so nothing animates. Every step below is shown at once, each labelled in words with its number, the party, what it sees, and what it signs.
Forward this as a one-pager. Print it or save it as a PDF (Cmd/Ctrl-P).
Step 1 of 5 — Your phone
Mint a biometric-gated key
- Sees
- Your biometric and the new private key — the only place either one ever exists.
- Signs
- Mints a keypair inside the Secure Enclave / StrongBox, unlockable only by your biometric. Nothing leaves the device.
Step 2 of 5 — Your phone
Platform TEE attestation
- Sees
- The public key and the platform (Apple / Android) attestation for it.
- Signs
- The secure hardware attests that the key was minted in a genuine TEE. The private half never surfaces.
Step 3 of 5 — Your phone
Generate the zero-knowledge proof
- Sees
- The proof inputs, kept on the phone. Nothing secret leaves the device.
- Signs
- A P-256 zero-knowledge proof, generated on the phone. The biometric never leaves it.
Step 4 of 5 — Verity server
Validate attestation, relay the proof
- Sees
- The attestation, the public key, and the finished proof — never the biometric. Relay-only on the proof path.
- Signs
- Validates the attestation, signs an issuer attestation, and relays the phone-made proof onward. It never sees the biometric and cannot forge the proof.
Step 5 of 5 — StarkNet
The chain answers is_human(address)
- Sees
- The relayed proof and the issuer attestation.
- Signs
- Records the result so anyone can read is_human(address) on-chain.