Base deploys Denim upgrade with 200ms blocks

Base has activated its fourth mainnet upgrade, Denim, replacing its Flashblocks system with canonical Ethereum-compatible blocks produced every 200 milliseconds. The change gives the Coinbase-incubated Layer 2 a fixed cadence of five blocks per second and requires applications that relied on Flashblocks to switch to standard canonical block subscriptions.

According to Base's Denim upgrade documentation, the network now enforces the 200-millisecond interval at the protocol level. Each block must follow its parent by exactly 200 milliseconds, rather than using time supplied by the sequencer, the component responsible for ordering transactions before they are posted to Ethereum.

The change makes the chain's normal block stream the primary source of transaction and state updates for applications. Flashblocks had offered rapid pending-block previews, but those previews were not canonical blocks and could change before being included in the chain. Denim removes that separate path and gives developers a single, predictable block feed.

Canonical blocks replace Flashblocks

The migration affects developers running trading interfaces, wallets, data indexers and automated onchain systems that previously watched Flashblocks for near-instant transaction updates.

Under Denim, applications should subscribe to canonical block data rather than the pending block tag associated with Flashblocks. Base also changed the semantics of that tag as part of the retirement process, meaning software built around the old preview stream needs to update its data-handling logic.

A canonical block is a block recognized as part of the chain's history, subject to the network's normal sequencing and settlement architecture. Producing them every 200 milliseconds can make transaction inclusion and application updates feel faster and more consistent, but it does not remove the distinction between a Layer 2 block being produced and the Layer 2's transaction batches being settled on Ethereum.

That distinction is particularly relevant for developers who use pending data to display transaction status. Flashblocks could provide a fast visual indication of transactions expected to land, while the canonical blocks introduced through Denim become the standard record applications should follow.

The protocol-enforced cadence also gives developers a more dependable timing assumption than a system tied to the sequencer's own clock. Contracts and offchain services can expect adjacent blocks to be spaced at 200-millisecond intervals, although they should not assume that every block contains the same amount of activity.

BaseTime adds millisecond timestamps

Denim also introduces BaseTime, a feature that gives smart contracts access to Unix timestamps measured in milliseconds. The standard Ethereum-compatible block.timestamp remains limited to whole seconds, preserving compatibility with existing Ethereum applications and contract assumptions.

BaseTime provides additional fields through the network's remote procedure call, or RPC, interface. Those fields expose millisecond timestamps for blocks, transactions and logs, allowing applications to read more precise timing information without changing Ethereum's established block.timestamp behavior.

The addition could be useful for applications where a one-second clock is too coarse, such as time-sensitive auctions, short-duration orders, gaming mechanics and systems that calculate fees or rewards over narrow intervals. Developers will need to decide whether millisecond precision is genuinely necessary, since contracts designed around block counts or second-level timestamps may not benefit from simply adding a more detailed clock.

The feature also avoids forcing developers to use block height as a rough substitute for elapsed time. With five canonical blocks produced each second, contracts that measure deadlines or lockups by block numbers can reach their thresholds much sooner than they would on a network with slower block production. Projects using block-based timing should review those parameters rather than treating the new cadence as a cosmetic performance change.

B20 protections expand

Denim includes several changes to Base's B20 token standard, which adds programmable compliance and transfer controls for tokens that use it.

The update adds a reusable NOT operator for compliance policies. That allows token issuers or applications using B20 rules to express exclusions more directly, such as permitting transfers under a policy except for addresses or conditions that match another policy.

Base also extended transfer-executor restrictions to direct transfers. The measure closes a route that could otherwise allow a direct token transfer to bypass controls intended to govern how transfers are executed.

Another safeguard prevents transfers, mints and seizures from sending tokens to the token contract's own address. Sending tokens to that address can create accounting and recovery problems depending on a token's design, so blocking those operations at the standard level reduces a class of avoidable errors.

These features will matter most to teams building permissioned assets, loyalty systems, regulated token products or other applications that need transfer restrictions embedded in token logic. They do not change the behavior of ordinary tokens that do not use the B20 standard.

Fourth independent upgrade since launch

Denim follows Azul, Beryl and Cobalt, three upgrades implemented by Base this year. Base described those releases as its first independent upgrades since the network launched in 2023.

The sequence shows Base increasingly adjusting the network's execution environment and developer tooling through its own upgrade process. Denim's most immediate consequence is operational: applications, indexers and bots that still consume Flashblocks must migrate to canonical block subscriptions or risk missing the data stream their software expects.

For users, the visible result should be a more regular flow of confirmed Layer 2 block updates. For builders, Denim replaces a specialized preview mechanism with a faster canonical block schedule, while adding a higher-resolution clock and tighter controls for B20 token operations.