Loading…
Loading…
A native rollup is an L2 whose blocks Ethereum checks with its own proof program, the one it will use for its own blocks. This one runs on a local copy of bogota-devnet-2, and everything this explorer shows is rebuilt from L1 alone.
Everything this demo cannot run yet is missing from L1, not from the rollup. Each mock stands in for one L1 feature and goes away when that feature ships.
| Part | Status | What stands in | Goes away with |
|---|---|---|---|
| L1 chain with frame transactions and blobs | Real | A local copy of bogota-devnet-2 with Nethermind, Reth and ethrex | |
| L2 execution | Real | execution-specs' Bogota rules, frame transactions included, as on the L1 | |
| Stateless validation program | Real | execution-specs' program, written for Amsterdam and ported to the Bogota rules, run as ordinary code instead of inside a zkVM | |
| Block data in blobs | Real | EIP-8142's encoding, on real L1 blobs | |
| Rollup contract, L2 messenger, message proofs | Real | ||
| This explorer's L2 data | Real | Rebuilt from L1 alone by an independent follower, which re-executes every block | |
| Proof | Mock | A trusted key signs blocks that the real program accepted | A zkVM proof of the same program |
| Proof check on L1 (EIP-8288) | Mock | A frame that calls a contract checking the signature | EIP-8288, which lets L1's own proof cover it |
| Verification key registry (EIP-8357) | Real | The EIP's contract at its address. Its entry is in the L1 genesis, as the fork that activates EIP-8357 would register it, since the clients do not implement that fork, and its key hash is a placeholder, since the proofs are signatures | EIP-8357 in the clients, and a zkVM proof |
| Blob check in the program (EIP-8142) | Mock | The node checks that the blobs encode the block | EIP-8142 in the L1 program |
| Operator and users | Real | One operator runs the L2 node as the rollup's sequencer, the only account the rollup contract takes blocks from, in the book's preconfirmations customization. Users sign their own transactions, deposit claims included, and send them to the node's RPC, which this demo keeps local | |
| Preconfirmations | Real | The sequencer builds a block every 4 seconds, empty if no transaction waits, signs its hash at once, and posts it once a fixed wait, standing in for proving time, has passed. A bond in the rollup contract backs every signature: anyone who shows a broken one has it burned | |
| Claims for others | Real | Messages carry a fee for whoever claims them. A relayer on L2 and a claimer on L1 claim those whose recipients cannot, as anyone could, and recipients claim their own for free | |
| Example apps | Real | An ERC-20 bridge and a ping pong, each a contract on both chains that only accepts the calls its messenger delivers from the other. The story bridges a demo token, and spamoor plays ping pong | |
| Activity | Real | Besides the story, spamoor sends ERC-20 transfers, Uniswap swaps, EIP-7702 delegations, EIP-8141 frame transactions with EIP-7906 assertions among them, ETH in both directions and pings |
The prover key is the only trusted part. The follower checks it: it re-executes every block from L1 data alone and compares the result with what the contract accepted.
The explorer reads everything from the chains, except what an explorer takes from elsewhere too: names such as Alice or PingPong, the sources of the demo's contracts, and which chain an app's address arguments are on come from the demo's own records, as labels and verified contracts do.