Coinbase’s blockchain got faster. Some apps can still connect but get no data
Developers must migrate applications to new RPC subscription methods following the Nov. 5 network update.
Quick Look
- Coinbase's Base blockchain has retired Flashblocks data feeds in its Denim upgrade.
- Developers must migrate to new WebSocket RPC subscriptions, as old endpoints no longer provide data.
- The network is also investigating reports of transaction delays.
AI-generated summary
Why It Matters
The Denim upgrade, activated on Nov. 5, introduced canonical blocks every 200 milliseconds to the Base blockchain. This update fundamentally changed how data feeds and transaction receipts are handled.
Coinbase’s Base blockchain retired its Flashblocks data feeds in the Nov. 5 Denim upgrade, requiring apps using them to migrate. The old WebSocket endpoints still accept connections but no longer deliver data, according to Base’s migration instructions.
Denim activated on mainnet at 18:00 UTC on Nov. 5. Base’s upgrade overview describes complete canonical blocks every 200 milliseconds, each with its own hash, state root and receipts. These are the chain’s blocks rather than previews of a block still being built.
The compatibility trap is that an open connection no longer establishes that an app is receiving updates. Reconnecting to a retired Flashblocks endpoint leaves the underlying integration problem unresolved.
What apps need to change
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:
newFlashblocks becomes newHeads, which follows canonical block headers.
pendingLogs becomes logs.
newFlashblockTransactions becomes newHeads, followed by fetching the transactions in each canonical block.
Developers must also 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 change matters for requests reading balances, transaction counts or simulated contract results against pending state. An application retaining the old assumption can mistake an accepted response for a preview even though it is reading canonical state.
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 advises testing migrated integrations on Base Sepolia or Vibenet.
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.
What to Watch
AI outlook — possibilities, not facts
Developers will migrate to newHeads and logs subscriptions to restore app functionality.
Very likely · Within weeks
Open Questions
- What is the status of the investigation into transaction delays?
- When will the empty block rate return to normal levels?







