KOSUNI CRYPTO
Korea's Crypto Pulse, in English
$BTC $ETH $XRP $SOL $DOGE
News
Neutral

Optimism Completes Subblock Interval Reduction to 200ms

Published September 26, 2026 11:39 PM · 7 views $OP
Optimism Completes Subblock Interval Reduction to 200ms

Optimism (OP) mainnet has reduced its subblock production interval from 250 milliseconds to 200 milliseconds. While transaction feedback cycles have shortened, some raw data fields now show zero values, increasing verification burdens for applications and RPC providers. Optimism's status page confirmed the '200ms subblocks' transition was completed on September 1 at 5:16 a.m. KST.

The change is part of a sequencer infrastructure shift from 250ms flashblock production to 200ms subblock production. The key focus lies in data interpretation rather than speed alone. QuickNode's status notice noted that state_root, block_hash, withdrawals_root, and withdrawals fields have changed to zero values during the OP stack subblock transition, while receipts_root and logs_bloom maintain real values.

Although payload formats remain consistent, parsing errors may not immediately occur. However, if developers treat zero-value fields as actual state values, silent compatibility issues could arise in balance checks, state proofs, and withdrawal processing. Subblocks are not final confirmed blocks; OP stack specifications indicate that flashblock default time is 200ms, with certain values like blockHash potentially serving as placeholders during pre-confirm stages.

Flashblocks send partial block information at short intervals before transactions fully confirm. Layer-2 networks typically provide pre-confirm signals to reduce user latency, but these signals are not treated with the same reliability level as final block data. Public access points also have limitations: Optimism's official documentation warns that public RPC URLs for flashblocks have strong rate limits and do not support WebSocket connections, advising users to operate their own nodes or use third-party RPC providers.

External infrastructure providers like Alchemy describe OP mainnet flashblocks as providing partial block updates every 200ms. QuickNode notes that pending tags can be used to check the latest flashblock status and receive real-time data via WebSocket. In practice, public endpoints and client compatibility have become variables. GitHub discussions among Optimism developers include questions about flashblock WebSocket addresses and complaints regarding public WSS access restrictions, with some responses recommending external RPC providers instead.

Separate GitHub issues reported that op-reth Docker images encountered a 'TLS support not compiled in' error when connecting to flashblock WSS. This suggests that speed improvements may be bottlenecked by client deployments, TLS support, and WebSocket connection methods for actual service implementation.

The transition is closer to a data quality and delivery boundary issue than a network outage. Optimism's status page now shows OP mainnet as operating normally post-transition. Documentation frames the change as both performance optimization and compatibility adjustment. Market structure means this affects RPC providers, wallets, block explorers, and on-chain data services first—particularly those directly consuming subblock streams or delivering raw payloads to customers rather than relying solely on final blocks.

Domestic users may also face touchpoints: if domestic exchanges or wallets depend on external RPC providers for OP mainnet deposits/withdrawals, balance displays, or contract call statuses, they must distinguish between pre-confirm and final data. However, no reports of domestic business outages or deposit/withdrawal suspensions were cited in the material.

Optimism has recently also dealt with governance and ecosystem restructuring issues, including a previously reported approval to reallocate 546.9 million OP remaining from user airdrops into a strategic ecosystem fund. This subblock transition is separate from token allocation matters, representing an adjustment of OP mainnet execution infrastructure.

Service operators must ensure zero-value fields do not flow into state, balance, or proof inputs. Particularly if pending status and final block data are treated identically in storage or display structures, they should review flashblock reception paths, WebSocket connection methods, and RPC provider response formats together.

Korean Source

This article is an English localization of a Korean-language crypto news report. Original headline: 옵티미즘, 서브블록 200밀리초 전환 완료