Aztec Network · interactive mechanism simulation

Private functions run and prove themselves on your own device (PXE) — only a proof leaves the browser. A decentralized, staked validator set (sequencer duty rotates) executes any public functions on the AVM, batches proven transactions, and posts the rollup proof to Ethereum L1.
Your device · PXE private state + local proof proving in ~900ms Validator set 520 / 500 staked · LIVE 200,000 AZTEC bonded each Sequencer · AVM duty: validator #4d1a… verifies proofs, runs public fns Rollup batch 0 / 8 txs queued Ethereum L1 0 batches posted rollup proof + state diff
Private txs proved (client-side)
0
Public functions executed (AVM)
0
Rollup batches posted to L1
0
AZTEC staked
0
Parameters — edit me
1.2/s
900ms
520
8 txs
Controls

Illustrative simulation. Defaults mirror the researched Ignition Chain mechanism (client-side PXE proving, a decentralized validator set staking 200,000 AZTEC each, mainnet block production gated on ~500 validators, sequencer duty rotating across the set, and rollup proofs posted to Ethereum L1) — but tx sizes, timings, and validator IDs are randomized for visualization, not live onchain data. The failure button illustrates why Aztec's Gen-1 products (zk.money, Aztec Connect) were sunset in 2023: a company-run sequencer was a single point of failure, so the team renounced contract ownership and left a permanent permissionless "Ejector" withdrawal path. Part of The Onchain Experiment Atlas.