Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups

Historical-source note: This article is based on a piece by 0xJaehaerys of 白话区块链, published by TechFlow on November 13, 2026, at 14:05 (UTC+8). The mechanisms and deployment figures below reflect that reporting date.

Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (1)

Liquidity and applications spread across Ethereum and multiple rollups are difficult to use in a single transaction. The Ethereum Economic Zone (EEZ) is a design intended to let connected chains call Ethereum contracts—and one another’s contracts—within the same Ethereum block. It is not described as a new chain, an Ethereum protocol upgrade, or an activated EIP. Rather, it consists of Ethereum contracts and rules for connecting participating chains.

Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (2)
Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (3)

What a chain must provide

A connected chain keeps its own virtual machine, transaction ordering and rules for admission and proof trust. To join the EEZ design, it must be able to prove its state within one Ethereum slot and roll back alongside Ethereum if a reorganization discards a block. The latter condition is meant to prevent a rollup from remaining on a history Ethereum has abandoned.

Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (4)
Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (5)

The article says advances in real-time proving make the first condition feasible: a validity proof can establish that a chain followed its rules without Ethereum re-executing its block. It reports that RISC Zero and SP1 can prove a block within a 12-second slot using 8–16 graphics cards at a cost of 1–5 cents. Those are the source’s reported performance figures, not a guarantee for every connected chain or workload. The article also says ZisK’s reported hardware requirement fell from 24 RTX 5090 cards a year earlier to four, citing Ethproofs.

Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (6)
Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (7)

How a same-block call is arranged

In the described workflow, each contract has a predictable proxy address on another connected chain, calculated with CREATE2 from the EEZ contract address, the original contract address and the chain ID. A composer simulates the transaction across the chains involved and prepares an execution table of cross-chain calls and their answers. Entries include state roots before and after a call, any calls back to Ethereum, and a rolling hash covering calls and results. One proof can cover the table.

Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (8)
Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (9)

The composer sends a bundle to a block builder. Its first transaction, postAndVerifyBatch, submits the table and verifies its proof; later transactions call proxies that read the verified answers. Under the design, a proxy answers only when the actual call matches the simulated one, its table entry arrived in a batch in that same block, and the hash of calls back to Ethereum matches. Ethereum executes those callbacks directly, including nested calls that can return through a proxy. A rollup’s onboarding rules determine which proof systems it trusts—such as ZK proofs, trusted execution environments or multisignatures—and how many proofs a batch needs.

Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (10)

This is the proposed route to a transaction that borrows USDC on Ethereum, swaps it for ETH and deposits the ETH as margin through a rollup, rather than requiring separate bridging steps. The article says the composer would not send a bundle if simulation found a failed step; if actual Ethereum execution differed from simulation, the Ethereum and rollup operations would roll back. Calls are described in all three directions: L1 to L2, L2 to L1 and L2 to L2.

Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (11)
Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (12)

Reported uses and compatibility trade-offs

The source describes examples on an EEZ test rollup called RollupX: a purchase from an Ethereum Uniswap CRV pool that minted wrapped CRV on the rollup in the same swap; a Safe proxy whose signers and permissions remained in its Ethereum contract; and a Bermuda Bay privacy pool whose swap executed on Ethereum’s Uniswap V3. It also describes a demonstration in which verifying a Falcon signature on a rollup authorized an L1 Safe payment. These are reported examples, not evidence that every rollup or application has adopted the design.

Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (13)
Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (14)

The model would let connected chains retain different execution environments and rules while accessing L1 applications. The article suggests this could reduce the need to duplicate liquidity and deployments across chains, but cross-chain calls would still consume Ethereum block space and pay L1 gas.

Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (15)
Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (16)

There are constraints. Citing a Gnosis forum discussion, the source says a chain cannot simultaneously have fast blocks, synchronous Ethereum calls and decentralized sequencing under this design: it must choose two. Its example of a 200-millisecond chain uses a centralized sequencer, with one synchronous block in every 60. Applications on that chain could reach Ethereum once every 12 seconds, even though its other blocks continue normally.

Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (17)
Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (18)

The composer must see an unencrypted transaction before block production, giving it and the builder priority access to potential cross-chain MEV. The article also reports that validators built 7% of Ethereum blocks themselves at the time; synchronous calls would not occur in those slots. For the EEZ’s reported first month, it says every batch landed in a block from an external MEV-Boost builder, with 56% in Titan-built blocks versus Titan’s usual 48% share. Those figures describe the period reported by the source, not a continuing network-wide rate.

Ethereum Economic Zone: A Design for Same-Block Calls Across L1 and Rollups (19)

Source: techflowpost.com (originally published 2026-11-13 14:05 UTC+8)

Further reading