Mentioned in This Article
1. What is the Base Denim upgrade?
Base, the layer-2 network incubated by Coinbase, is preparing an upgrade called Denim that would cut its block time from two seconds to 200 milliseconds. Mainnet activation is targeted for November 2026, with no exact date set, and the change would raise output from one block every two seconds to five blocks every second. Base 200ms block times are the headline feature, and they replace the Flashblocks system the network has used since July 2025.
The date is a target rather than a commitment. Base's own upgrade documentation lists November 2026 for the mainnet and notes that a month without a confirmed activation timestamp is a planning goal that can change. Developers and infrastructure providers are therefore preparing for the change while waiting for the final schedule.
2. How much faster are 200ms blocks?
At the current pace of one block every two seconds, Base produces 43,200 blocks a day. Under Denim, the figure rises to 432,000 a day, a tenfold increase, with no extra time added to the day. The speed-up comes entirely from compressing the interval between blocks.
Each 200-millisecond block is a real, canonical block with its own hash, state root and receipts, rather than a forecast of what a later block will contain. That distinction matters for applications that depend on settled data. A transaction included in such a block has been recorded in the chain's history, not merely previewed.
Block timestamps will continue to be expressed in whole seconds, and a separate metadata field will carry the millisecond portion. Responses covering blocks, headers, transactions, logs and receipts gain optional fields with millisecond resolution, so software that needs finer timing can read it without breaking tools that expect the old format.
Put simply, a network that once settled a transaction within a two-second window will be able to settle it within a fifth of a second. For ordinary users the difference is the gap between a short pause and something that feels immediate, and for developers it removes a layer of complexity they have had to manage until now.
3. What are Flashblocks and preconfirmations?
A preconfirmation is a promise, made before a block is complete, about where a transaction is expected to land. On a network with two-second blocks, waiting for inclusion can feel slow, so Flashblocks split that window into smaller slices and announced what each slice would contain. A wallet or trading interface could use the announcement to update a screen almost immediately.
The limitation is that a preconfirmation is a prediction by the party producing the blocks, not a record in the chain. Applications that treat it as final carry some risk that the eventual block differs, and applications that wait for the real block lose the speed advantage. Developers therefore had to decide, case by case, how much trust to place in the early signal.
Denim resolves that tension by making the final record arrive quickly. When the canonical block comes every 200 milliseconds, there is far less need for an early forecast, because the settled answer is available almost as soon as the forecast would have been.
4. Why is Base retiring Flashblocks?
Flashblocks were introduced in July 2025 to make Base feel faster than its two-second block time implied. They provided preconfirmations, which are early signals of how a transaction is likely to land before the block containing it is finalized. A user saw a quick response, but the response was still a preview.
That design had a cost for developers. Applications wanting quick responsiveness had to build against the Flashblocks feed, in effect maintaining a second stream of data alongside the canonical chain. Denim removes that arrangement. Instead of fast previews layered on top of slower blocks, the blocks themselves become fast, and Base will stop producing Flashblocks.
The trade-off is migration work. Applications built around Flashblocks must move to the new canonical block and remote procedure call (RPC) feeds. RPC is the standard method by which applications query a blockchain for data, so the change touches wallets, trading interfaces and any service that reads from the network.
5. How does the OP Stack fit in?
Base is built on the OP Stack, an open-source framework for layer-2 networks on Ethereum. A layer-2 network processes transactions on its own chain and relies on Ethereum for security, which lets it offer lower fees and faster activity than the base layer. Using a shared framework means improvements to the software can be developed in the open and adopted by several networks.
Changes to block production, such as the one Denim describes, are among the most consequential an operator can make, because they alter how every other component interacts with the chain. Node software, indexers, analytics dashboards and wallets all assume a certain rhythm of new blocks. When the rhythm changes by a factor of ten, each of those components needs to be tested against it.
This is the reason the upgrade is staged. The specification describes the change in detail ahead of activation, giving the teams that run infrastructure time to prepare their systems and their budgets.
6. Why do block times matter on a layer-2 network?
A block is the batch of transactions a network records at one time, and the block time is the interval between those batches. A shorter interval means a transaction waits less before it is included, which shortens the delay users feel when they send a payment, place a trade or interact with an application. Layer-2 networks such as Base exist largely to offer cheaper and quicker activity than Ethereum's base layer, so block time is one of the main measures of how well they deliver on that promise.
Speed is not free, however. Producing blocks more often increases the amount of data that nodes, indexers and applications must process, and it narrows the margin for timing errors between components of the system. That is why the Denim change is as much an infrastructure story as a user-experience one: the benefit to end users depends on whether the software around the chain can keep up with the faster rhythm.
Whether faster blocks translate into a better experience in practice will depend on each application. Those already optimized around Flashblocks have the most to rework, while newer projects can design for the 200-millisecond cadence from the start.
7. What does the upgrade mean for builders and infrastructure providers?
Services that process every block, such as indexers and data platforms, can expect a heavier load. Ten times as many blocks means ten times as many block events to ingest, store and serve, and projections for those services point to roughly a tenfold rise in RPC call volume. Providers that bill by request volume may see costs shift accordingly, and the estimate is a projection rather than a measured result.
For application developers, 200-millisecond canonical blocks promise faster, settled confirmations without depending on a separate preconfirmation layer. Interfaces for trading, payments and gaming, where delays are noticeable, are the obvious beneficiaries. They would no longer need to reconcile a fast preview with a later confirmed result.
Denim is also one step in a longer sequence. Jesse Pollak, Base's lead developer, has said the upgrade is one of several rolled out in 2026, following the releases known as Azul and Cobalt, and that it focuses on performance, security and user experience. Base is built on the OP Stack, an open-source framework for layer-2 networks on Ethereum, and it has pursued this push for speed without launching a native token.
8. What should applications do before activation?
The practical advice that follows from the design is straightforward. Teams that use Flashblocks should plan their move to the canonical block and RPC feeds, and should confirm that their software handles the optional millisecond timestamp fields. Services that subscribe to new-block notifications, often called newHeads events, should expect those notifications to fire ten times as often and size their systems accordingly.
Providers of node access and data services should review their capacity and their pricing, since the load associated with each customer subscription grows with the number of blocks. Customers who pay according to request volume should ask their providers how the change will affect their bills.
None of this needs to happen overnight, because the mainnet date has not been fixed. Still, the November target leaves limited time, and the sensible course is to treat the upgrade as a firm project with a flexible deadline.
9. What is the Base mainnet timeline?
Base's documentation targets November 2026 for the mainnet, and the specification for Denim describes itself as informational, with activation times and required client versions still to be decided. Teams relying on Flashblocks should treat the coming weeks as a period for testing against the new canonical feeds rather than waiting for a firm date.
The questions to watch are the announcement of an exact activation time, the client versions that node operators will need and the guidance given to applications that currently depend on Flashblocks. Until those are published, the November target is the best available guide, and the practical effect of 200-millisecond blocks will only become clear once the network is running at the new pace.
The broader significance lies in what the change signals about competition among networks. Speed has become a selling point for layer-2 chains, and a tenfold reduction in block time places Base among the fastest options in its class, provided the supporting infrastructure keeps pace and the November activation proceeds as planned.