Immutable Plans One-Second Blocks, Seven-Day Native Withdrawals

Immutable swaps its bridge for Ethereum proofs

In the official announcement, CTO Alex Connolly and blockchain head Ermyas Abebe said the shift would replace an Axelar-based bridge with withdrawals verified against state commitments posted to Ethereum. The rollout begins with permissioned fault proofs, with zero-knowledge validity proofs intended later.

Immutable reported almost 250 million transactions and more than 18 million wallets, including over 6 million Passport users. Wallet counts do not establish an equivalent number of distinct people or active players.

The distinction between those initial and later proof systems is consequential. A roadmap toward another verification mechanism does not establish that the final design is available at launch. Nor does faster block production alone show how quickly a transaction achieves Ethereum settlement.

Optimism describes OP Stack as a configurable framework, including options for data availability, fees and gas tokens. It supports Solidity contracts and familiar Ethereum development tools. Reusing a common framework can reduce the amount of bespoke infrastructure a chain operator maintains, although a particular deployment still needs its own operational checks.

That broader migration theme also appears in GnosisDAO’s decision to pursue Ethereum settlement. The architectures differ; a shared direction does not make their launch assumptions interchangeable.

One-second blocks bring seven-day native withdrawals

Immutable says block intervals will fall from two seconds to one second, while transaction costs increase slightly. The announcement gives no numerical fee estimate. The change creates a trade-off between responsiveness inside the gaming network and moving funds back through its native Ethereum bridge.

Optimism’s withdrawal documentation explains the standard sequence: initiate on the second-layer chain, prove the withdrawal on Ethereum, then finalize after the required waiting conditions. A withdrawal proof must age sufficiently, and the relevant dispute game must resolve in favor of the proposed state.

The waiting period therefore serves a verification process. It is separate from how often the gaming chain produces a block. A player could see an interaction included quickly while a native withdrawal remains pending for much longer.

Faster liquidity routes work differently from that native process. Their practical usefulness depends on the route and available liquidity, so the seven-day native path should not be presented as the duration of every possible transfer.

The Immutable migration guide retains IMX as the gas token and attributes the fee increase to Ethereum data posting. Existing accounts, balances, contracts, approvals and the chain ID carry over. That continuity reduces migration work for ordinary users, but it does not mean all integrations can stay untouched.

Immutable developers face a 2026 testing deadline

The guide tells game developers to leave the current testnet for game usage by year-end. Infrastructure and integration partners retain access through migration and a trial period. It targets a Q1 2027 testnet migration, followed by at least two months of trials before the mainnet target.

Developers must review schedules expressed in blocks. As a simple illustration, 60 blocks represent two minutes at the old interval and one minute at the proposed interval. This arithmetic does not establish a fault in any named game. It identifies a dependency that deserves review.

A similar timing issue arose with Base’s move to 200-millisecond blocks. Changing cadence can affect application assumptions even when familiar contract interfaces remain available.

Immutable’s guide also calls for bridge integration updates and new node software. Bridging pauses before block production during cutover. The company expects several hours of interrupted block production and promises advance notice; an exact date remains unconfirmed.

Meanwhile, Alternative.me’s Bitcoin sentiment index read 25, or Extreme Fear, versus 28 the previous day when checked November 7 around 02:45 UTC. It measures broader sentiment, rather than Immutable’s readiness or gaming demand.

The next checkpoints are confirmed testing dates, migration tooling and bridge-support releases. The deployment schedule remains conditional on testing and integrity checks, leaving the final cutover arrangements and measured post-migration fees unresolved.