ZisK ×
Connecting… --:--:-- UTC
Last 24 hclick or drag to go back
Live from the ZisK prover

, proven live

We prove every block as it is made, and close every batch posts to Ethereum into one validity proof seconds after it lands. Live numbers, straight from the prover.

Average time per batch
— s
from Ethereum to validity proof
p99 time per batch
— s
from Ethereum to validity proof
GPUs proving
—
NVIDIA RTX 5090
Batches proven
—
of the batches posted
How it works

Three steps, around the clock

1 makes a block every seconds

We prove the blocks in ranges as soon as they exist.

→
2 posts a batch to Ethereum

Every few minutes sends the blocks it made to Ethereum in one batch. From the moment the batch is on Ethereum, the clock runs until its validity proof is done.

✓
→
3We close it into one validity proof

One small proof of the whole batch that Ethereum can check. Three jobs:

Derive the batch from Ethereum Bind execution with derivationWrap it into a SNARK
Right now

Blocks being proven, batches being closed

Each bar is one block, green once proven, in ranges of 5 that are aggregated as they come (white). A yellow Ethereum block is a batch being closed; it turns green with a ✓ when its validity proof is done. Hover a batch to see it.

How long it takes to prove a block

Every block under s

A block's time is its share of its range's proof, witness included.

How long it takes to prove a batch

Every batch, step by step

From the moment the batch lands on Ethereum (blocktime) to its validity proof: syncing first, then proving.

Under the hood

Where the GPU time goes

The cluster has room to spare: blocks could be much bigger and we would still keep up.

Words on this page
blockA block of . One every seconds.
BatchThe blocks posts to Ethereum together, every few minutes.
ProvenWe have a proof the block was computed correctly.
AggregatedFolded, range by range, into one running proof of the batch.
Validity proofOne proof of a whole batch, small enough for Ethereum to check.
WitnessGetting the batch: our node hears of its Ethereum block and downloads it.
PrepareBuilding the proof's input from the batch, and waiting for the GPUs if they are busy.
DeriveProving the batch is exactly what posted to Ethereum.
BindTying the block proofs and the derivation into one proof.
SNARKWrapping it into the compact form Ethereum verifies cheaply.