Base Activates Denim Upgrade, Reducing Block Time to 200 Milliseconds
Base has activated its Denim network upgrade, replacing two-second blocks with a new 200-millisecond block interval. The change increases block production frequency tenfold and introduces important adjustments for developers, node operators, smart contracts, and applications previously relying on Flashblocks.
The upgrade went live on November 5, 2026, at 18:00 UTC (1 p.m. ET). Base confirmed the activation on its official network status page, marking a major change to how the Ethereum layer 2 network processes and finalizes blocks.
Base Moves to Five Blocks Every Second
Before Denim, Base produced one canonical block every two seconds. The new system generates five complete blocks per second, with each block arriving at 200-millisecond intervals. This means the network now creates ten times as many blocks over the same period.
The first reported 200-millisecond block carried number 53,556,127 and appeared at 18:00:01 UTC, approximately two seconds after the final block under the previous schedule. Each new block has its own number, hash, state root, receipts, and progression through the network's unsafe, safe, and finalized stages.
The upgrade's technical specifications are outlined in Base's 200ms Native Blocks documentation. Denim also introduces millisecond-level time information through a new BaseTime contract and additional RPC timestamp fields, while retaining the existing Ethereum-compatible, seconds-based block.timestamp value.
Block-Based Smart Contract Timers Face a Major Change
One of the most important consequences of Denim involves applications that measure time by counting blocks instead of using timestamps.
Previously, a contract waiting for 302,400 blocks would take approximately seven days to complete its timer because Base produced one block every two seconds. Under the new 200-millisecond schedule, the same block count takes approximately 16.8 hours.
This creates a potential timing problem for smart contracts with fixed block-based conditions. Timelocks, cooldown periods, vesting schedules, withdrawal delays, and expiry deadlines could all complete ten times faster than originally intended if their logic depends on a fixed number of blocks.
Base's technical documentation warns that systems treating block counts as time intervals will experience this reduction after activation. Developers should review their contracts and offchain applications for assumptions based on the previous block frequency. Immutable contracts are particularly difficult to adjust because their original block-count constants cannot be changed after deployment.
Contracts using block.timestamp retain their seconds-based timing behavior. However, developers needing sub-second precision can use BaseTime to access the additional millisecond component.
Flashblocks Are Replaced by Native 200ms Blocks
Denim also changes how applications receive early transaction information. Before the upgrade, Base used Flashblocks, a system developed with Flashbots that delivered partial block updates every 200 milliseconds while a standard two-second block was being assembled.
Flashblocks allowed applications to work with incremental pending-state information before the corresponding canonical block was completed. Denim replaces this approach with complete 200-millisecond blocks that follow the network's normal block lifecycle.
As a result, applications that previously relied on Flashblocks subscriptions must migrate to standard block and RPC streams. Base's Flashblocks migration guide identifies the required integration changes.
For example, applications using newFlashblocks subscriptions should move to standard newHeads subscriptions. Developers must also review pending transaction and log requests because the pending block tag no longer has a direct equivalent after Denim.
The change affects more than transaction notifications. Applications that depend on historical block information must review their assumptions because fixed-size block-history windows now represent less elapsed time. Base's specification also warns that systems storing a fixed number of oracle observations may cover a shorter period of real-world history.
Node Operators Must Update Their Software
The upgrade required Base mainnet node operators to install base/base v1.5.1 or later before activation. Base released version 1.5.1 on October 22, 2026, and identified it as the required software release for the Denim hard fork.
The release requirement is documented in the Base v1.5.1 GitHub announcement. Operators upgrading from older versions also needed to review configuration changes, including the removal of the --enable-experimental-validity-transactions flag if it was present in their startup commands.
Base confirmed successful activation at 18:14 UTC on November 5. However, its status page also reported an investigation into periodic transaction-inclusion delays, which were causing a higher-than-expected number of empty blocks.
Initial observations of public RPC data recorded 146 of the first 300 blocks after activation as containing only system transactions. Separate hourly samples of 300 blocks between 4 p.m. and 7 p.m. ET did not show the same pattern. These observations provide an early snapshot, rather than a long-term assessment of network performance.
Horizen's Layer 3 Shutdown Highlights Compatibility Risks
The Denim upgrade also has consequences for networks built on the OP Stack that settle to Base. Horizen, a layer 3 network operating on the OP Stack, accelerated its shutdown ahead of the upgrade because of compatibility concerns.
In an October 23 announcement, Horizen said its existing layer 3 infrastructure could not follow the upcoming Base changes. Its infrastructure provider had indicated that no available fix would prevent the compatibility issue. Horizen warned that its network could stop including user transactions approximately 40 minutes after Denim activation.
Users were instructed to move assets from the Horizen layer 3 network to Base before November 4 at 13:00 UTC. The migration included ZEN, ETH, and other supported assets. Horizen also stated that the DAO would return remaining ZEN and ETH balances to holders on Base after the funds became recoverable. The details were published in the project's official migration announcement.
What Comes Next for Base?
Denim follows several other Base network upgrades in 2026, including Azul in May, Beryl in June, and Cobalt in September. The next named upgrade, Everest, appears on Base's upgrade roadmap without a confirmed activation date.
The transition to native 200-millisecond blocks represents a substantial change in Base's infrastructure. While it creates a faster canonical block schedule, it also requires developers to reconsider timing assumptions, update application integrations, and account for shorter block-history windows.
For users, the upgrade's longer-term impact will depend partly on how applications adapt to the new system. For developers and infrastructure providers, reviewing contract logic, RPC integrations, and node compatibility is essential to maintaining reliable services after Denim.
