Originally published November 13, 2026, at 14:05 (UTC+8). By 0xJaehaerys, 白话区块链, via TechFlow.

The Ethereum Economic Zone (EEZ) is an approach to a familiar Rollup problem: using a contract or liquidity pool on another chain normally requires a separate, asynchronous step. The source describes EEZ as a way for connected chains to make synchronous calls—calls that are resolved within the same Ethereum block. EEZ is not a new chain or a new Rollup stack; it consists of Ethereum contracts and rules connecting participating chains.


A connected chain keeps its own virtual machine, transaction ordering, access rules and choice of trusted proofs. To participate, it must be able to prove its state within one Ethereum slot—12 seconds—and roll back if Ethereum reorganizes. That second requirement prevents a Rollup from retaining a state tied to a discarded Ethereum block.

How a call is resolved
When an Ethereum contract calls a contract on a connected Rollup, it calls a corresponding proxy address on Ethereum. The source says these addresses are predetermined using CREATE2, the EEZ contract address, the original contract address and the chain ID. Calls can also run from a Rollup to Ethereum or between Rollups.


Before the block is built, a composer simulates the transaction across the chains involved. It records each cross-chain call in an execution table, including the answer, the Rollup’s state roots before and after the call, any calls back to Ethereum, and a rolling hash of those callbacks and their results. A proof covers the table.

The composer sends a bundle to a builder. Its first transaction, postAndVerifyBatch, submits the table and verifies its proof; subsequent transactions can then call proxies that read the verified answers. A proxy responds only if the actual call matches the simulated call, its entry arrived in a batch in the same block, and the callback hash matches. The Rollup’s onboarding rules determine which proof systems—such as ZK proofs, trusted execution environments or multisignatures—and how many proofs a batch requires.


The source says real-time proving makes this sequence possible where proofs that once took minutes or hours could not. It reports that RISC Zero and SP1 can prove a block within 12 seconds using 8–16 GPUs at a cost of 1–5 cents. Those are the source’s reported figures, not a guarantee for every chain or workload.

What the design could enable—and what was demonstrated
The source’s example is a Rollup transaction that borrows USDC from an Ethereum Aave market, swaps it for ETH on Uniswap and deposits it as margin. In the described flow, the composer prepares the results before block construction. It does not send a bundle if simulation fails; if Ethereum’s actual execution differs from the simulation, the operations on Ethereum and the Rollup revert.


The article also describes activity on a test Rollup called RollupX: a purchase using an Ethereum Uniswap pool that produced wrapped CRV on the Rollup, a Safe setup that retained signers and permissions on Ethereum, and a demonstration in which a Falcon signature verified on the Rollup authorized a Safe payment on Ethereum. These examples illustrate the mechanism; they do not establish broad adoption.

The constraints
Synchronous calls still depend on Ethereum’s block schedule and block space. The source says a chain with 200-millisecond blocks would need centralized sequencing to make synchronous Ethereum calls; in its example, only one in every 60 blocks could be synchronous. Each cross-chain call also passes through the composer, which must see the unencrypted transaction before block construction, giving the composer and builder an early opportunity to capture MEV.


Builder availability is another limit. The article reports that validators built 7% of Ethereum blocks themselves, without an external builder, and says synchronous calls would not occur in those slots. It also reports that every EEZ batch in its first month landed in a block from an external MEV-Boost builder; 56% landed in Titan-built blocks, compared with Titan’s usual 48% share. Those are figures reported for that period, not a prediction of future availability.

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