01Current step
Private identity
Only your browser knows the secret
VALUE DECENTRALIZATIONPowered by Frontier ProtocolRestoring session…VALUE DECENTRALIZATIONPowered by Frontier ProtocolRestoring session…Generate a real Semaphore proof in the browser, verify one-use access off-chain, and inspect the latency and memory cost without combining them into one score.
THE IDEA IN ONE PICTURE
The gate needs proof that you are a member—not your secret identity. The same proof cannot open this gate twice.
Only its public commitment joins the group.
Your browser proves membership without sending the secret.
The server verifies the proof and rejects a second use.
Concept illustration. Real proof demo below; the latency / memory competition remains PIVOT.
START HERE · A SHORT GUIDED EXPERIMENT
Follow four real actions. Your private identity stays on this device; only its public commitment and proof leave the browser.
Make a disposable identity for this experiment. No wallet or personal details are needed.
Register only the public commitment and retrieve a membership snapshot.
Your browser creates a proof. The server checks it before opening the gate. The first download can take a little time.
Resend the retained proof. Success here means the gate refuses the second use, not that it opens again.
Learning progress only. No score, reward, AI fee, or payment. A tie is a valid result.
REAL SEMAPHORE V4 · INTERACTIVE PROOF LAB
Can you prove you belong without sending your identity secret? Build a real proof in your browser, open the Gate, then try using it twice.
Only your browser knows the secret
Send a commitment, not the secret
Prove you belong without sending the secret
Root + message + scope + nullifier checked
PRIVATE DEVICE: identity secret + proof Worker SHARED: commitment, group root and proof. The enrollment server knows your commitment and this synthetic group; this is not a production anonymity system.
A disposable local secret, not a wallet or a human identity. It is never printed in the Evidence below.
Off by default. Saved identity is unencrypted browser storage. Do not use a valuable or production identity.
Join seven fixed cover commitments. The server builds a root that expires after 30 minutes. Group size and scope are fixed safety rules, not editable strategy knobs.
Requires step 1.
The browser generates a real proof. The API verifies it and reserves the nullifier: a scope-specific marker that prevents reuse.
Start with a disposable identity. No wallet, payment or AI inference is needed.
EDIT EXECUTION, NOT CRYPTOGRAPHY
These settings change the local four-proof experiment only, not the single Gate entry above. More parallel work is not guaranteed to be faster or use less memory.
1 Worker creations across 4 proofs. This is an allocation diagram, not a time or memory forecast. Internal engine threads stay SDK-managed.
Public proof, snapshot, receipt and raw browser observations. Hashes identify evidence; browser timings do not become reproducible by hashing them.
{
"schemaVersion": "secret-gate-walkthrough-evidence-v1",
"contextHash": "0x13211e0b9afe64f980789b678ceaa008360d8d9fdc78b57c31f4d6239465c1a6",
"commitment": null,
"snapshot": null,
"entry": null,
"receipt": null,
"duplicate": null,
"storage": null,
"benchmark": null,
"limitation": "Off-chain synthetic-cohort demo. No identity secret, transaction, reward, official ranking or production anonymity claim."
}