Base’s Denim mainnet upgrade replaces Flashblocks with full canonical blocks produced every 200 milliseconds, or five per second, according to a project statement reported by The Block. The upgrade also adds millisecond-resolution time access for smart contracts and extends controls for tokens using Base’s B20 standard.
The original report was published on November 5, 2026, at 20:00 UTC—November 6 at 04:00 UTC+8. Denim was Base’s fourth independent network upgrade, following Azul, Beryl and Cobalt earlier that year.
Block timing becomes a protocol rule
For the Coinbase-incubated Layer 2, Denim changes both block production and how applications consume updates. According to Base, each canonical block follows its parent exactly 200 milliseconds later. The protocol enforces that interval rather than relying on the sequencer’s clock.
The upgrade retires Flashblocks and changes the behavior of the pending block tag. Applications that previously depended on Flashblocks must migrate to standard canonical block subscriptions, the statement said.
Base described the resulting block-production model as “simpler, more consistent, and more reliable.” That is the project’s characterization; the supplied report does not include independent measurements of reliability or application performance.
BaseTime adds precision without changing block.timestamp
Denim introduces BaseTime, which gives smart contracts access to Unix timestamps in milliseconds. The Ethereum-compatible block.timestamp remains unchanged at whole-second resolution.
New RPC fields also provide millisecond timestamps for blocks, transactions and logs. The distinction matters for developers: finer-grained time information is being added without changing the resolution of the existing block.timestamp field.
Base linked the changes to its focus on trading, financing and payments, arguing that these applications need frequent state updates and precise reasoning about time. The report does not establish how much individual applications benefit from the new timing model.
B20 transfer and compliance controls
Denim also extends the B20 token standard in three reported ways:
- It introduces reusable compliance policies through a
NOToperator. - It extends transfer-executor restrictions to direct transfers.
- It blocks transfers, mints and seizures that would send tokens to the token contract’s own address.
These are reported implementation changes. The source does not provide enough detail to assess their complete policy semantics or security properties independently.
Where Denim fits in Base’s upgrade sequence
Base’s preceding independent upgrades established the components Denim builds on. Azul introduced a new client stack and multiproof system. Beryl introduced B20. Cobalt added conditional transactions and expanded B20 compliance features.
Denim’s central architectural change is the move from Flashblocks to a protocol-enforced cadence of full canonical blocks. For existing integrations, the explicit migration requirement is to replace Flashblocks subscriptions with standard canonical block subscriptions. Its timing and token-control additions are documented in the project’s statement, while claims about improved reliability remain unverified by independent evidence in the supplied report.
Original source: The Block — “Base deploys Denim upgrade on mainnet, replacing Flashblocks with 200ms block times”.