NESSA Protocol Demo
Pick a sandbox or role. All state is in-browser — nothing is sent to a server. Proofs are simulated but semantics match the real protocol.
Sandboxes
AML Compliance Sandbox
Bank compresses compliance events across millions of customers into one succinct proof. Regulator verifies "bank is 100% compliant" without learning any customer details.
Accredited Investor Sandbox
User's local agent checks financial accounts privately. A single proof confirms the accredited investor threshold was met — the investment platform learns nothing about actual balances.
All roles
AML Compliance
Bank prover + regulator verifier
Accredited
Investor agent + platform verifier
Wallet
Your identity, credentials, sessions
Acme App
Relying party — sign-in + step-up
Issuer
Issue and revoke credentials
Bot
Delegated agent — scope & revoke demos
Gate
Ticket gate — offline + replay demo
Registry
Checkpoint state and event log
Verifier
Dev console — challenge + proof JSON
Protocol scenarios
Onboarding + First Login
Create an identity, receive a membership credential, and sign in — with 3 failure paths including replay and stale checkpoint.
Delegation
Delegate limited rights to a bot. Bot uses them, then fails when it tries an out-of-scope action or the delegation gets revoked.
One-Time Gate Entry
Issue a single-use ticket, present it at a gate offline, and see replay prevention in action.
Revocation Impact
Issuer revokes a credential mid-session. User retries login and receives a clear REVOKED reason code.
Verifier Developer View
See exactly what a relying party integrates: challenge creation, proof bundle verification, and reason codes with copyable JSON.
State resets on hard refresh. All flows are client-side only.