Immutable Announces Transition to Ethereum Rollup: Migration to OP Stack in 2027, Block Time Reduced to 1 Second
Author: Shenchao TechFlow
On November 6, 2026 (Beijing Time), Web3 gaming public chain Immutable officially announced its underlying infrastructure evolution roadmap, planning to upgrade Immutable Chain from a customized Geth fork to an OP Stack-based architecture in mid-2027.
According tothe official Immutable announcement, after the upgrade is completed, the network will become a standard Ethereum Rollup, with block generation time reduced from 2 seconds to 1 second, and native Ethereum state commitments replacing the current cross-chain relay solution.

Moving Away from Custom Fork Architecture to Adopt Superchain Ecosystem Standards
Since launch, Immutable Chain has maintained its underlying consensus and execution using a deeply customized Go-Ethereum (Geth) fork codebase. Maintaining a private execution-layer fork requires the team to independently shoulder the heavy engineering burden of continuously syncing with Ethereum mainnet hard forks, applying patch adaptations, and performing low-level fixes.
After transitioning tothe OP Stack developer specification, the underlying client and execution environment will align directly with Ethereum's standard mainnet. Various Ethereum Improvement Proposals (EIPs) and core EVM upgrades can be integrated smoothly without requiring the team to perform secondary refactoring, significantly reducing long-term protocol maintenance costs.
As part of the ecosystem migration, Immutable will formally integrate into the Optimism Superchain interoperability matrix.
Native Cross-Chain Bridge Cleanup, Introducing State Commitment Verification
The logic for cross-chain asset settlement is undergoing a structural reorganization. Currently, cross-chain transfers of native assets on Immutable Chain rely on a multi-party messaging mechanism based on theAxelar cross-chain network, which supports network interoperability but whose trust foundation depends on signature authorizations from intermediate network nodes.
The new architecture will reshape the bridging pathway, using state commitments published directly to the Ethereum mainnet as the sole settlement foundation. The official plan is to introduce Permissioned Fault Proofs in phases and integrate ZK Validity Proofs in subsequent engineering evolution.
The underlying verification logic will return toEthereum Rollup mechanisms, with final settlement certainty for cross-chain assets directly guaranteed by Ethereum mainnet consensus, cutting off security dependencies on external cross-chain relay protocols.
Block Production Accelerated to 1 Second; Withdrawal Cycle and Transaction Cost Adjustments
For gaming interaction experience, the network block interval will be compressed directly from the current 2 seconds to 1 second, halving confirmation latency for high-frequency on-chain actions and accommodating real-time state synchronization needs for action and real-time card games.
Performance optimization comes with specific mechanism trade-offs. Because transaction states and proof data must be submitted directly to the Ethereum data availability (DA) layer, base on-chain transaction costs will increase slightly compared with a pure sidechain model.
The native withdrawal mechanism will also change. Following the standard dispute resolution process of Optimistic Rollups, assets moved back to the Ethereum mainnet via the official native bridge will trigger an approximately 7-day anti-fraud challenge window; immediate cross-chain needs will require supplementary channels provided by external liquidity service providers.
Zero-Friction Seamless Cutover; Testnet Support to End by Year-End
Network migration will adopt a seamless state migration strategy. The existing Chain ID, all user addresses, token balances, smart contract logic, and on-chain authorization records will be fully preserved; developers and regular players will not need to manually transfer assets or redeploy contracts during migration.
The formal cutover window is planned for mid-2027. At that time, the mainnet will pause block production for several hours to complete the underlying engine replacement, and the exact downtime maintenance schedule will be announced to the community in advance.
Infrastructure cleanup will proceed in parallel. Immutable confirmed that it will officially shut down support for gaming projects on the current testnet by the end of 2026. Game developers have widely shifted to local simulation nodes and production environment validation; streamlining the independent sandbox helps the team focus on preparing for the core mainnet cutover.
Source: Shenchao TechFlow
English
English
中文
繁体
日本
한국인
русский