A published roadmap, rather than a completed cutover

Immutable announced on 6 November 2026 that it plans to move Immutable Chain from its custom Geth implementation to the OP Stack. Its target is mainnet migration in the middle of 2027. The company says the chain ID and existing state will carry over, including accounts, balances, contracts and approvals.

The planned architecture would make the chain an Ethereum rollup. Immutable expects one-second target blocks instead of two-second blocks, slightly higher transaction costs and native Ethereum withdrawals taking around seven days. These are characteristics of the announced future design, not changes that users should assume have already taken effect.

The bridge transition changes what needs testing

The announcement says the present native bridge uses Axelar messaging and would be replaced by withdrawals verified against state commitments on Ethereum. Permissioned fault proofs are the initial plan, with zero-knowledge validity proofs intended later. The later proof system should not be treated as a feature delivered at the first cutover.

For an application, preserving balances is only one part of continuity. A successful migration also needs the surrounding services to recognise deposits, withdrawals and transaction receipts correctly. The operational question is whether a user's complete workflow still works when the underlying node and bridge infrastructure change.

Different users have different obligations

The migration documentation tells applications to check assumptions based on two-second blocks. It tells direct bridge integrators to move to new contracts, and infrastructure operators to replace the current client with an OP Stack node setup. RPC customers should confirm their provider's support for the migration timetable.

These distinctions explain why a broad statement that most users need no action cannot be applied to every operator. A player holding an asset may face a different task from an exchange maintaining a bridge integration. Teams need to identify their role before interpreting a general continuity assurance as an instruction to leave all infrastructure untouched.

Two deadlines should remain separate

Immutable plans to end use of the current testnet for game testing by the end of 2026. Its documentation separately targets a first-quarter 2027 testnet migration and a trial before mainnet. Dates remain subject to testing and integrity checks. The company also expects a pause in bridging and block production during the eventual cutover.

For studios and custodians, the useful next step is to map dependencies against those milestones and await confirmed migration instructions. A shorter block interval does not automatically shorten every withdrawal, while a faster liquidity bridge introduces a different route with its own terms. The November news is a concrete architecture and migration plan, with implementation work and final dates still ahead.

Photograph and reuse credit

Archival Sydney skyline, 14 June 2012. Immutable lists a Sydney company address in its privacy policy; this view does not identify its offices or depict the migration. Photograph: Douglas P. Perkins; derivative photograph by Georgfotoart. Licensed under CC BY-SA 3.0. Image unchanged. Source: https://commons.wikimedia.org/wiki/File:Sunny_Sydney_Skyline_b.jpg. Licence: https://creativecommons.org/licenses/by-sa/3.0/

Go deeper on CryptoGov

Sources & verification

Researched and published by CryptoGov Editorial Desk. Source publication and effective dates are explained in the article where relevant.