rollup.quest

COMPRESSING
TXS ROLLED UP 0
BATCH #001 PENDING
THROUGHPUT
PROTOCOL

Validity proofs compress thousands of transactions into a single cryptographic attestation. Each batch sealed on-chain carries the weight of every operation it contains, verified in constant time.

PROOF STATUS
AWAITING VERIFICATION
BATCH SIZE 0 TXS
STATE TREE
COMPRESSION

Data availability is ensured through calldata compression. The rollup posts only the minimal delta required to reconstruct state, reducing L1 costs by orders of magnitude.

BATCH #002 PENDING
EXECUTION

The sequencer orders transactions, executes them against the current state, and produces a new state root. This root becomes the claim that the validity proof must verify. Every operation is deterministic -- replay the inputs, get the same output.

GAS SAVINGS
BLOCK HEIGHT 0 BLOCKS
MERKLE ROOT
VALIDITY
GENERATING PROOF
STATE DIFF
0x7a3f...e291 0xb4c8...1f07 0x92d1...a4b3
BATCH #003 PENDING
ZK-PROOF
CIRCUIT COMPILING
PROOF TIME
VERIFICATION

The proof encodes the entire batch computation into a polynomial commitment scheme. A single elliptic curve pairing on L1 verifies what took millions of operations to compute. This is the fundamental asymmetry that makes rollups possible.

CONSTRAINTS 0 GATES
PROOF HASH
0xf1a2...9c7d 0x3e8b...52f0 0xd604...8e1a
CIRCUIT
BATCH #004 PENDING
SETTLEMENT

The final proof is submitted to L1. A single on-chain transaction verifies the entire batch, updating the canonical state root. Finality is inherited from the base layer -- once confirmed, the batch is irreversible. The rollup has compressed time itself.

L1 GAS 0 WEI
FINALITY
ON-CHAIN
SUBMITTING TO L1
BATCH ROOT
0xa8f3...7b12 0x5c91...d4e6 0x0e27...f983
FINAL STATE