Old connections can look healthy
Base, the Coinbase-backed layer 2, activated its Denim upgrade on mainnet at 18:00 UTC on Nov. 5. The upgrade retired Flashblocks data feeds. Apps that still use the old WebSocket endpoints may be able to connect, but they will not receive data. Base’s migration instructions say those endpoints still accept connections but no longer deliver updates.
That is the compatibility trap. An open connection no longer proves an app is receiving updates. Reconnecting to a retired Flashblocks endpoint leaves the underlying integration problem unresolved.
What Denim changes for apps
Denim produces complete canonical blocks every 200 milliseconds. Each block has its own hash, state root and receipts. These are the chain’s blocks, not previews of a block that is still being built.
Base directs developers to replace Flashblocks connections with subscriptions through a WebSocket-capable RPC provider or their own node. Its replacement map has three main subscription changes, so teams should check the migration details carefully.
Developers also need to review what their apps expect from the pending block tag. Base still accepts that tag, but it now resolves to the latest canonical block. It no longer exposes Flashblocks preconfirmation state, and there is no direct equivalent for that former preview. That matters for requests reading balances, transaction counts or simulated contract results against pending state. An app keeping the old assumption can mistake an accepted response for a preview even though it is reading canonical state.
Receipts and testing
Transaction handling changes too. Apps can keep polling eth_getTransactionReceipt, but a receipt becomes available once the transaction enters a canonical 200ms block. Preconfirmed receipts and preconfirmed transaction results are no longer available.
Base recommends inventorying Flashblocks subscriptions, WebSocket connections and pending-tag requests, along with flashblock_index usage and node flags. It also advises testing migrated integrations on Base Sepolia or Vibenet.
Timing is not finality
A 200ms block cadence describes how often blocks arrive. It does not promise that every submitted transaction enters the next block. Inclusion also remains separate from finality. In its Denim announcement, Base says a block becomes safe when its batch is posted to Ethereum and final when Ethereum finalizes that batch. Apps needing those stronger guarantees still have to distinguish them from the arrival of a canonical block.
Base’s Denim upgrade notice, still marked Verifying on Nov. 9, carried a Nov. 5 update at 18:14 UTC reporting an investigation into periodic transaction inclusion delays and a higher than expected rate of empty blocks. The notice contained no subsequent resolution update. Perhaps teams should treat monitoring and migration checks as ongoing work.
The post Base retires Flashblocks feeds in Denim upgrade, apps must migrate appeared first on TheCryptoUpdates .
