Base Cuts Block Time to 200ms With Denim Upgrade Live

Base, the Ethereum layer-2 network built by Coinbase, activated its Denim upgrade at 1 p.m. ET Thursday, cutting block time from two seconds to 200 milliseconds, the Base engineering blog said.

That is five complete canonical blocks per second instead of one every two seconds. Denim replaces Flashblocks, the earlier system that streamed pending-state previews between two-second blocks. Unchained checked Base's public RPC data and reported the first 200-millisecond block, No. 53,556,127, at 18:00:01 UTC.

Timers shrink unless apps update

A layer-2 network batches transactions off Ethereum's main chain, then posts proofs back to it. Faster blocks mean apps see new state more often, which can help liquidations, oracles and keepers react sooner. Inclusion in a 200ms block is not by itself final: blocks still become safe when their batch posts to Ethereum and final when Ethereum finalizes that batch, Base says.

Because `block.number` now advances ten times faster in wall-clock time, any contract that treats a block count as a duration will see that duration shrink to one tenth of its intended length. A timelock written as 302,400 blocks, about a week at the old cadence, would run out in roughly 16.8 hours after activation. Base's Denim specification tells developers to audit timelocks, vesting schedules, cooldowns, governance periods and fixed-cardinality TWAP oracles. Contracts that read `block.timestamp` keep second-based timing; a new BaseTime predeploy adds millisecond resolution.

Node operators need base/base v1.5.1 or later. Fourteen minutes after activation, Base's status page said Denim had successfully activated and that the team was investigating periodic inclusion delays and a higher rate of empty blocks, Unchained reported. Horizen, a layer-3 that settles to Base, said earlier it could not follow Denim and set a Nov. 4 deadline for users to move assets.

In our opinion: the dry punchline is in the math. A "week" written in blocks is now closer to a workday, and Base put that warning in the upgrade docs themselves. Builders who still count time in block numbers have a short list to fix; everyone else just gets state five times a second instead of once every two.