Ethereum’s Economic Zone: A Composability Design—and the Revenue Model It Still Owes

The hard part of Ethereum’s rollup-centric future is no longer only making transactions cheap. It is making a system of many execution environments behave like one economy. A user can hold assets on a rollup, find liquidity on mainnet, and still need a bridge, a relayer, a wait, and a second transaction to bring the two together.

The Ethereum Economic Zone (EEZ) is an early attempt to change that architecture. Gnosis’s July 2026 proposal would transition Gnosis Chain from a standalone L1 into the first Gnosis-operated EEZ rollup instance. Its headline technical promise is synchronous composability: an L2 contract can call a mainnet contract, use the result, and have the whole action succeed or revert together. That is a substantial claim. It is not, however, the same thing as a completed revenue-sharing system for Ethereum.

Here is the useful, evidence-first answer before the jargon.

That table is not a knock on the work. It is the boundary between a serious architectural proposal and a story that has outrun the specification. EEZ’s immediate thesis is composability and settlement alignment. Its economic thesis will only be testable once the people who pay, the people who receive, the percentages, and the enforcement path are published.

What EEZ is actually trying to make possible​

Consider a lending application on a Gnosis EEZ instance. Today, a user who wants to use mainnet collateral or liquidity from that application’s L2 usually takes an asynchronous path: bridge an asset, wait for the message or liquidity route, then submit a transaction on the destination chain. Each step has its own fee, confirmation, and failure mode. The user can finish with an asset on the wrong chain or a partially completed strategy.

The EEZ target is a different transaction shape. The L2 application prepares a call to a mainnet lending market, receives the result, then continues its local logic—say, swapping the borrowed asset—inside one atomic operation. If the mainnet call or the swap fails, the entire operation reverts. The public EEZ description calls this synchronous composability; the early codebase describes state transitions computed off-chain, verified on-chain, and coordinated through L1 contracts. Its repository is candidly marked early-stage, unaudited, and subject to interface and storage changes. EEZ’s introduction, the core-protocol repository

The components matter because they show what the proposal is—and is not—claiming:

1. A composer sequences the intended cross-environment execution.
2. Off-chain infrastructure computes the state transitions.
3. A proving system, for which EEZ names Zisk as an intended high-performance stack, provides the evidence for the transition.
4. Ethereum contracts verify the batch and coordinate the registered rollup states.
5. The call either completes as one verified operation or fails as one operation.

That can reduce integration and bridging friction. It could also create demand for proving and route execution. But potential demand is not a revenue split. The current protocol repository has per-rollup ETH accounting and proof verification machinery; it does not disclose a rule that diverts an operator’s residual revenue to Ethereum validators, ETH holders, or another named mainnet recipient. EEZ core protocol

Gnosis’s own proposed launch path is narrower than the completed vision. GIP-153 targets a December 2026 or January 2027 genesis, describes initial L2→L1 atomic calls and interim proving, and places bidirectional composability, nested calls, and real-time ZK proving on a 2027 path. The proposal also says its first proving setup will likely be TEE-based while the concrete mechanism is chosen. Those caveats are part of the product, not footnotes: the full security and composability story is still being built. GIP-153

Fee flow is not the same as economic alignment​

Rollup fees already have a fairly ordinary anatomy. A user pays an L2 fee. The rollup has to pay Ethereum for data availability and settlement, often by posting compressed transaction data in blobs, and it also has operating costs for sequencing, proving, and infrastructure. The remainder is operator economics. Ethereum’s own documentation separates state-write costs, dynamic blob gas, and L2 operator fees in much the same way. Ethereum.org’s rollup fee overview

user fee
  ├─ Ethereum blob and settlement expense
  ├─ sequencing / composer operation
  ├─ proving operation
  └─ residual: operator, treasury, tokenholders, grants, or another chosen recipient

That first line already gives Ethereum a direct economic connection to rollups: rollups buy Ethereum blockspace and settlement. EIP-4844 made that data path far cheaper by creating blob transactions, which is great for users but reduces the simple intuition that more L2 activity must translate into proportionally large L1 fees. It is also why a claim that the economic problem is solved needs to name a mechanism beyond “the rollup settles on Ethereum.”

Gnosis is unusually direct about the local motivation. GIP-153 says Gnosis Chain’s fee revenue covers only a small part of its security cost and that its treasury-funded staking subsidy dilutes non-stakers by roughly 2.3% annually. The intended pivot is from that subsidy to fee capture from network activity. Yet the same proposal says the concrete connection between xDAI revenue and GNO tokenomics is deliberately unspecified; a fee share or a buyback are both under consideration after prover economics can be observed in production. GIP-153’s economics section

That is a Gnosis-instance question, not a published Ethereum-validator revenue program. A protocol-enforced revenue primitive would need, at minimum:

• a defined base: gross fees, net fees, blob costs, proving costs, or route-specific fees;
• a percentage or formula that can be reproduced;
• a named L1 recipient and claim or distribution path;
• contracts that enforce the transfer rather than a discretionary budget;
• governance rules for changing it; and
• on-chain accounting that lets outsiders reconcile money in and money out.

Until those pieces exist, “economic alignment” should be read as a direction and an incentive hypothesis—not as a settled fee policy.

Similar words, different forms of sharing​

The distinction becomes clearer next to systems that do publish their terms. They solve adjacent problems, but not the same one.

This is why “Superchain versus EEZ” should not be reduced to one being an alliance and the other being a protocol. Optimism publishes a concrete shared-treasury formula; EEZ proposes a different technical topology. Both can create incentives, but only a disclosed fee rule tells us who receives what. Cosmos is the closest comparison for explicit security-for-revenue exchange, while Polkadot illustrates shared security plus capacity pricing. Neither makes an unannounced EEZ transfer rule real.

Incumbent adoption is the practical test. Base, Arbitrum, and Optimism have existing distribution, stacks, and economics. A new system asking them to surrender margin would have to return something that is more valuable: measurable atomic access to mainnet liquidity, lower integration cost, materially better user experience, or a security/composability capability unavailable through their current paths. There is no verified public evidence that any of those projects has committed to EEZ adoption.

The minimum evidence for “the model works beyond its founders” is straightforward: a non-Gnosis production instance, audited contracts, a public fee rule, and recurring on-chain fee-distribution data. Anything less can demonstrate a devnet or a strategic direction. It cannot demonstrate an economic zone operating at scale.

The proof burden is useful, not hostile​

EEZ does not need to win an argument about ETH/BTC to be useful. It needs to make one cross-environment action meaningfully better, safely and repeatably, for an application that would otherwise bridge and wait. Then it needs to publish the economics of that service.

For the Gnosis proposal, the near-term proof points are visible: deliver the promised initial instance, show the exact trust model for interim proving, publish the route fee schedule, and clarify what protects users from a centralized composer delaying or excluding transactions. GIP-153 says Gnosis Ltd would operate the composer at launch and that forced inclusion is an option to evaluate rather than a launch feature. The design therefore needs operational evidence as well as cryptographic evidence. GIP-153’s launch design

The longer-term proof points are harder: audited real-time ZK proving, full bidirectional and nested composability, a transparent allocation decision for GNO, and adoption by an instance whose economics do not begin with Gnosis. If an Ethereum-level revenue transfer is part of the vision, it needs the same clarity—formula, recipient, enforcement, and accounting.

That is the fair reading of the Ethereum Economic Zone today. It is an ambitious composability design, with Gnosis as a proposed first instance and Zisk as proving infrastructure. It may eventually create a more integrated economic relationship between execution environments and Ethereum. But the revenue model it would need to prove that conclusion is still owed to the public.

Sources​

• GIP-153: Should Gnosis Chain transition into the Ethereum Economic Zone?
• EEZ: Introducing the Ethereum Economic Zone
• EEZ core protocol repository
• Ethereum.org: Optimistic rollups and their fee model
• Optimism: Superchain capital allocation
• Cosmos Hub: Interchain Security
• Polkadot: Agile Coretime