Rollup X devnet tests atomic Ethereum-rollup calls

Gnosis introduced Rollup X as a public test network on November 4, demonstrating applications that call between an Ethereum rollup and mainnet within a single transaction. The launch provides a working development environment for the Ethereum Economic Zone, an effort to reconnect liquidity and applications that have become separated across rollups.

The demonstrations matter because most cross-chain activity currently involves a bridge message followed by another transaction. That creates waiting periods and additional failure points. Rollup X instead tests whether multiple actions can execute atomically: either every part succeeds, or the entire transaction reverts.

The result is an early technical milestone, not a production deployment. Gnosis says the test network is not intended to hold significant value, while its documentation describes the contracts as early-stage and not yet audited.

Three demonstrations on a test network

At Devcon in Mumbai on November 4, Gnosis reported three demonstrations. CoW Swap filled an order initiated on Rollup X against liquidity on Ethereum mainnet and returned the resulting tokens within the same transaction. Safe demonstrated an account-owner change spanning mainnet and the rollup. A third example verified a post-quantum signature on Rollup X and used the result to authorize an action on mainnet.

These demonstrations show how the architecture is intended to work, but they do not establish its performance or security under production load. Gnosis did not publish an independent audit with the announcement, and Coinburn did not independently reproduce the transactions. The project’s documentation says its demos run on local chains and the Chiado testnet for learning purposes rather than production deployment.

Under the published design, a participating network must prove its state within an Ethereum slot and follow Ethereum through any chain reorganization. That is intended to let a contract use another network’s result before the originating transaction finishes, avoiding the asynchronous message-and-callback pattern common to conventional bridges.

Gnosis Chain plans a separate migration

Rollup X is distinct from the existing Gnosis Chain. Gnosis said it is targeting spring 2027 to convert that independent layer-one network into a zone settling on Ethereum. The proposed hard fork would preserve contracts, balances, addresses, the chain identifier and xDai as the gas token, so applications would not need to redeploy solely because of the transition.

GnosisDAO approved the direction in July 2026, according to the project timeline. The current validator set would retire when the fork activates, while GNO locked in staking would unlock. That changes the network’s security and operating model even if application state remains intact.

The timetable is still provisional. Gnosis Chain’s transition FAQ, last updated October 20, says no launch date has been set, and the project timeline says dates beyond the current quarter are indicative. No mainnet activation block has been published.

What remains unproven

The devnet narrows the gap between a design specification and executable software, but several production questions remain. The protocol still needs published audit results, a Chiado testnet fork and an announced mainnet activation block. Its behavior under congestion, adversarial conditions and real economic activity also remains unmeasured in the opened records.

Full bidirectional composability is not promised at the initial Gnosis migration. Project documentation says calls from Gnosis EEZ into Ethereum are planned first, while nested calls, calls from Ethereum into Gnosis EEZ, real-time zero-knowledge proving and communication between separate Economic Zone instances are later milestones.

The immediate development is therefore a public test environment with reported atomic cross-network demonstrations. Whether that model can safely carry Gnosis Chain’s existing state and economic activity will depend on the audits, testnet fork and final activation parameters that have yet to be published.