zkPass · interactive mechanism simulation

A user's browser (TransGate) runs a 3-party TLS handshake with a data source and a zkPass verifier node, then proves a predicate about the session locally with VOLE-ZK — no raw data leaves the browser. The proof settles on-chain and a consuming dApp admits the user. Validators stake ZKP behind every verifier node.
User TransGate extension Data source bank / exchange / gov site Verifier node 3P-TLS handshake 55% MPC · 45% proxy Validator collateral 8,000 ZKP staked VOLE-ZK proof generated locally · 0 Attestation contract 0 verified onchain Consuming dApp 0 admitted (airdrop / lending)
Proofs generated
0
Users admitted
0
Validator collateral
8,000 ZKP
Schema failures / slashes
0
Parameters — edit me
1.2/s
55%
8,000 ZKP
6%
4 ZKP
Controls

Illustrative simulation. Defaults mirror the researched zkPass mechanism (3P-TLS with hybrid MPC/proxy verifier modes, local VOLE-ZK proof generation, on-chain attestations, staked validator collateral), but request timing and outcomes are randomized for visualization — not live onchain data. The "trigger colluding data source" button illustrates the documented failure mode: zkPass proves what a website said, not what is true, so a compromised or complicit data source can still mint a misleading attestation that only gets caught after settlement. Part of The Onchain Experiment Atlas.