Base is set to shorten its mainnet block time sharply with the Denim hard fork, scheduled for Nov. 5 at 18:00 UTC. According to the latest node release, the Coinbase-incubated layer-2 network will move from 2-second blocks to 200-millisecond blocks, producing five full blocks per second.
The change replaces Base’s current setup of slower canonical blocks plus Flashblocks, the 200ms preconfirmation layer it has used since July 2025. After Denim goes live, those fast intervals will no longer be previews: each slot will be a full block with its own block number, hash, and receipts.
Flashblocks retired as 200ms blocks become native
Base said Denim will make Flashblocks obsolete by turning every 200ms slot into a standard block onchain. That means applications still relying on Flashblocks streams, or using the “pending” tag, need to migrate to ordinary block feeds before the upgrade.
For most end users, the practical difference may be limited. Flashblocks already gave Base near-instant confirmations, so the network’s day-to-day experience is not expected to change as dramatically as the block-time number alone might suggest.
Block-based timing is the main compatibility risk
The most significant risk flagged by Base is for smart contracts and applications that use block numbers as a stand-in for elapsed time. With blocks arriving 10 times faster, any logic tied to a fixed number of blocks would complete 10 times sooner after Denim activates.
Base’s specification says this could affect timelocks, vesting schedules, cooldowns, and governance voting windows. A setting intended to last one hour at 1,800 blocks, for example, would expire in about six minutes under the new cadence. Base advised developers to use block.timestamp instead.
The network also warned that immutable contracts using block counts for timing cannot simply be adjusted after the fact, making them a particular source of concern around the transition.
Horizen plans to halt user transactions on its Base-settled L3
One project has already said it cannot accommodate the shift. Horizen stated that its OP Stack layer-3 network, which settles to Base, will permanently stop accepting user transactions roughly 40 minutes after Denim is activated.
Horizen also said bridging back to Base will close on Tuesday, Nov. 4 at 13:00 UTC, ahead of the hard fork. The announcement makes Horizen the clearest confirmed downstream impact tied to Denim so far.
Denim follows earlier Base upgrades
Base has been running Denim on Base Sepolia since Oct. 21. The hard fork is described as the network’s fourth standalone upgrade since Base diverged from Optimism’s Superchain path, following Azul, Beryl, and Cobalt.
Beyond block-time changes, Denim also introduces millisecond timestamps and updates to Base’s B20 token standard. Those technical adjustments arrive alongside the broader shift in how the network handles fast confirmations and block production.
What to watch at activation
The key test on Nov. 5 is not simply whether Base becomes faster on paper, but whether any applications or contracts still depend on block numbers as a clock. That issue, rather than user-facing latency, appears to be the central operational risk identified in Base’s own documentation.
The next confirmed step is activation at 18:00 UTC on Nov. 5, when the network will switch from 2-second blocks to five full blocks per second and disable Flashblocks. Projects built on or connected to Base are expected to complete any remaining feed or contract compatibility changes before then.
Source: www.bankless.com