Skip to main content

Gnosis Chain now and Gnosis EEZ

The Ethereum Economic Zone (EEZ) is a neutral rollup framework. Gnosis EEZ is its first instance, operated by Gnosis.

Gnosis EEZ is not a new ecosystem. It is Gnosis Chain, re-based onto Ethereum through a hard fork of the existing state. If you have a contract on Gnosis Chain today, it will be on Gnosis EEZ at the same address with the same storage the moment the fork activates. You do not redeploy, migrate liquidity or ask users to switch networks. If your deployment needs any configuration for the fork, the Gnosis team will be in touch.

The transition is planned for the future, and no date is set yet. Gnosis Chain continues to run as a Layer 1 until then, and the rest of this documentation stays accurate for building on it.

If you want to be a Gnosis EEZ launch partner, deploy on Gnosis Chain now. A live deployment is how you confirm your place. Become a launch partner sets out the steps.

What stays the same​

On Gnosis Chain todayAfter the fork
Contracts and stateDeployed and verified on GnosisscanCarried over unchanged, same addresses, same storage
Gas tokenxDaixDai
GNOSecures consensus and governs through GnosisDAOContinues as the governance token. Staked GNO unlocks when the validator set retires
EVMStandard EVM, Foundry, Hardhat, viem, ethersStandard EVM. No new opcodes, no new SDK, no Solidity changes
ToolingGnosisscan, RPC providers, indexersThe same tooling, pointed at the same chain
ComponentsMonerium EURe, Safe, CoW Protocol, Gnosis Pay, Spark, Aave, Balancer, Curve, Backed, CirclesAll carried over with their contracts and liquidity

What changes​

On Gnosis Chain todayAfter the fork
Block productionA proof-of-stake validator set of over 200,000 validatorsA composer, using sequencing and prover technology
ConsensusBeacon chain, GBCThe validator set retires. Node operators drop their consensus-layer client
SecurityValidator economic securityProofs verified on Ethereum. An interim proving setup, likely TEE-based, at genesis, moving to real-time ZK proofs across more than one proof system
SettlementGnosis Chain is its own settlement layerBlocks settle to Ethereum. Data is published to Ethereum blobs
Block time5 seconds2 seconds, with a composing block every 12-second Ethereum slot
FinalityAround 2.5 minutes to hard finalitySoft confirmation in seconds. Hard finality when the proof lands on Ethereum
Reaching Ethereum mainnetNative bridge, or a third-party bridgeA synchronous call from Gnosis EEZ into Ethereum mainnet in the same transaction, with no bridge or wrapped asset
Reaching other rollupsA bridgeStill a bridge, unless the rollup is part of the EEZ
FeesOne fee, paid in xDaiPriced by route (instance only, instance to Ethereum, Ethereum to instance), still paid in xDai

For validators and node operators​

Validators keep running until the fork. At activation the validator set retires and staked GNO unlocks. RPC and archive node operators keep their execution client and drop the consensus-layer client.

The Validators section has the full guide, a checklist for each role, and how to manage withdrawals and exits until then.

What is not in the first release​

Here are the limits of the first release.

  • One direction of synchronous calls. At launch, a contract on Gnosis EEZ can call a contract on Ethereum and use the result in the same transaction. The reverse direction, Ethereum calling into Gnosis EEZ, and full nested calls follow in 2027.
  • Interim proving at genesis. The first release uses an interim proving setup, likely TEE-based, and moves to real-time ZK proving as the Zisk prover reaches its latency target.
  • Audits. The core contracts are an early-stage implementation and have not been audited. Audit results are published before mainnet activation.
  • Instance-to-instance composability. Calls between EEZ instances come after bidirectional calls with Ethereum.

Progress against each of these is tracked on the timeline.

What this means if you build on Gnosis Chain​

Deploy now and your application is on Gnosis EEZ at launch without a second deployment. The teams live before the fork are the first to run on blocks that are proven and settled on Ethereum, with mainnet assets, liquidity and prices in reach from the same transaction. Become a launch partner sets out what that includes.