Sismo · interactive mechanism simulation

Accounts aggregate privately in a client-side Data Vault → a Hydra-S1 zk proof shows membership in an on-chain-committed Data Group without revealing which account → the Attester checks the proof and a one-time nullifier → a non-transferable ZK Badge is minted → a dApp verifies it to grant access. Edit the parameters and watch how demand (or its absence) moves through the pipeline.
Identity accounts wallet · ENS · GitHub · X Data Group 2,000 eligible accounts Roots Registry Merkle root, on-chain Data Vault client-side, encrypted Hydra-S1 Prover zk proof + nullifier Attester 0 nullifiers used HydraS1SimpleAttester Attestations Registry on-chain ledger ZK Badge 0 minted · non-transferable dApp / Sismo Connect verifying & token-gating Rejected proofs 0 blocked
Proof attempts
0
ZK badges minted
0
Sybil replays blocked
0
Ineligible proofs blocked
0
dApp verifications
0
Parameters — edit me
1.2/s
2,000
15%
10%
Controls

Illustrative simulation. Reflects Sismo's researched mechanism (client-side Data Vault, off-chain Data Groups committed as Merkle roots, Hydra-S1 zk proofs with per-nullifier Sybil resistance, on-chain Attestations Registry, non-transferable ERC-1155 Badges verified by dApps), but attempt sizing and timing are randomized for visualization — not live onchain data. The wind-down button illustrates Sismo's real failure mode: badges kept minting while dApp demand stalled, and the company shut down in late 2023 despite working cryptography. Part of The Onchain Experiment Atlas.