Original reporting: November 13, 2026, at 14:05 (UTC+8). The original article is credited to 0xJaehaerys of 白话区块链. The architecture and demonstrations below are described as reported there, not as an activated Ethereum protocol upgrade.

Ethereum’s liquidity and applications are spread across L1 and many L2s. That makes a transaction spanning them difficult to execute as one operation: borrowing USDC on mainnet, swapping it for ETH and depositing the ETH as margin on a Rollup would ordinarily involve separate cross-chain steps. The Ethereum Economic Zone (EEZ) is an approach intended to make calls between connected chains synchronous—resolved within the same Ethereum block.


What a chain would join
EEZ is described as contracts on Ethereum plus rules connecting other chains to those contracts. It is not a new chain, a new stack or an Ethereum protocol upgrade. A connected chain retains its own virtual machine, transaction ordering and rules for participation and trusted proofs. It must, at minimum, prove its state within one Ethereum slot and roll back with Ethereum if Ethereum reorganizes. The latter condition is intended to prevent a Rollup from retaining a state based on an Ethereum block that was discarded.


The one-slot requirement is central to the design. Ethereum does not execute the Rollup’s code to answer a cross-chain call; it needs a result accompanied by evidence it can verify before the block is built. The article cites RISC Zero and SP1 as able to prove a block within a 12-second slot using 8–16 GPUs at an estimated cost of 1–5 cents. Those are figures reported by the source, not a guarantee for every connected chain or workload. It also says EEZ onboarding rules determine which proof systems or other assurances—including ZK proofs, TEEs and multisignatures—a Rollup accepts, and how many are required for a batch.


How a call is assembled
In the described design, a composer simulates the transaction on each involved chain before block production and records cross-chain calls and their expected answers in an execution table. Entries include state roots before and after a Rollup call, any calls back to Ethereum, and a rolling hash of those calls and results. A proof covers the table.


The composer sends a bundle to an Ethereum block builder. Its first transaction, postAndVerifyBatch, submits the table and verifies the batch’s evidence. Later transactions can call proxies representing contracts on another chain; the proxies read answers from the verified table. Their addresses are predetermined using CREATE2, the EEZ contract address, the original contract address and the chain ID. A proxy answers only when the call matches the simulation, its entry arrived in a batch in the same block, and the rolling hash for callbacks matches. Ethereum executes calls back to its own contracts directly; the design also allows nested calls through proxies.

This is how the article says a Rollup-originating transaction could borrow USDC on Ethereum, swap it for ETH and deposit the result as margin in one block. The composer would not send a bundle if its simulation found a failed step. The article says that if actual Ethereum execution diverged from the simulation, the operations on Ethereum and the Rollup would revert.


Reported examples and constraints
The article describes several examples on RollupX, identified as a test Rollup on mainnet. In one, a purchase used an Ethereum Uniswap pool to obtain CRV even though CRV did not already exist on the Rollup; a wrapped version was minted there as part of the swap transaction. It also describes a RollupX Safe proxy whose signers and permissions remain in the mainnet Safe contract, a privacy-pool swap involving Ethereum’s Uniswap V3, and a demonstration in which Rollup verification of a Falcon signature authorized an L1 Safe payment. These are reported examples, not evidence that all Rollups can already use EEZ or that Ethereum has activated a related upgrade.


The trade-offs matter. According to the article, a connected chain cannot simultaneously have fast blocks, synchronous Ethereum calls and decentralized sequencing; it must choose two. Its example of a chain with 200-millisecond blocks would use a centralized sequencer for synchronous calls, with one synchronous block per 60 blocks—access to Ethereum every 12 seconds. Cross-chain calls also pass through a composer that must see unencrypted transactions before block production, giving the composer and builder an advantage in accessing associated MEV.


Builder participation imposes another limit. The article says validators built 7% of Ethereum blocks themselves at the time, without an external builder, and synchronous calls would not occur in those slots. It reports that every EEZ batch in its first month landed in an external MEV-Boost builder’s block; 56% landed in Titan-built blocks, compared with Titan’s stated usual 48% block share.


EEZ’s proposed coordination point is therefore the Ethereum block: connected chains could keep distinct execution rules while using L1 resources in that block. Whether a particular chain can do so depends on its proof and onboarding arrangements, sequencing choices and access to a participating builder.

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



