Optimism is targeting 200-millisecond subblocks on OP Mainnet, reducing the preconfirmation interval from 250 milliseconds in a gradual rollout aimed at Aug. 31. Subblocks, previously called Flashblocks, are incremental sequencer updates sent while a normal block is being built, allowing applications to receive information before the block is sealed. The change leaves the payload type as ExecutionPayloadFlashblockDeltaV1, so software can continue decoding the stream, but state_root, block_hash and withdrawals_root will contain all-zero values and withdrawals will be an empty list. Receipts_root and logs_bloom will continue carrying actual data. The affected fields represent a compatibility risk because successful parsing may be mistaken for proof that every field remains meaningful. Subblocks are preconfirmations rather than finalized blocks or state commitments. Direct stream consumers should treat the zeroed roots and block hash as unavailable and derive preconfirmed state by executing streamed transactions. Applications using a subblocks-aware RPC provider (a service that exposes blockchain data) and standard Ethereum methods, including the pending tag, generally rely on the provider or node to maintain a derived state view. Optimism says methods such as eth_getBalance can therefore return preconfirmed data without using a valid state root from the raw payload. The main audit burden falls on applications consuming the WebSocket stream directly and RPC providers forwarding raw fields. Operators need to identify reads of the four affected fields, prevent placeholder values from entering downstream state, balances or proof inputs, and notify customers when raw payloads are relayed. Alchemy documents 200-millisecond updates through existing Optimism RPC endpoints, while QuickNode applies the migration to its Optimism Mainnet and Sepolia JSON-RPC components. Optimism says the Aug. 31 target could change and that deployment will be gradual, with no documented network-wide completion time. Its status page showed systems operational and no recent incident notice when checked. Official and provider notices describe the zero-valued fields as a migration risk requiring preventive work, not evidence that balances or proofs have already been corrupted.