Blockchain

Base goes live with Denim: 200ms canonical blocks, Flashblocks retired

Coinbase's L2 now produces five full blocks per second, adds millisecond BaseTime for contracts, and tightens B20 transfer rules.

AI-generated illustration: A focused young builder watches five glowing cyan cubes stack into a tower beside molten orange blocks
AI-generated illustration

TL;DR

  • Base's Denim upgrade went live on mainnet on Nov. 5, 2026, producing a full canonical block every 200 milliseconds (five per second), according to Base's engineering blog.
  • Flashblocks are retired; apps must migrate to standard canonical subscriptions such as eth_subscribe("newHeads").
  • BaseTime gives contracts and RPC clients millisecond Unix time via a predeploy; B20 gains NOT policies, stricter transfer-executor checks, and a block on sends to the token's own address.
  • Denim is Base's fourth independent upgrade in 2026 after Azul, Beryl and Cobalt, The Block reported.

Base said on Nov. 5, 2026 that its fourth independent network upgrade, Denim, is live on mainnet. The Coinbase-incubated Layer 2 now produces a full canonical block every 200 milliseconds — five per second — and retires the Flashblocks pending-state stream that filled the old two-second gap between blocks, according to Base's engineering blog.

Base Denim: what changes for builders
Canonical block every 200ms (5/sec); Flashblocks stream retired; BaseTime millisecond clock for contracts; B20: NOT policies + stricter executor checks; Block sends to token's own address1Canonical block every 200ms (5/sec)2Flashblocks stream retired3BaseTime millisecond clock for contracts4B20: NOT policies + stricter executor checks5Block sends to token's own address
Source: Base

What Denim changes

Before Denim, Base produced one canonical block every two seconds and used Flashblocks to stream a preview of the block still being built. Denim replaces that model with native 200ms blocks. Each block's full timestamp is exactly 200ms after its parent, and the protocol validates that progression, Base wrote. Including a transaction in a 200ms block does not by itself make it final: like every Base block, it becomes safe when its batch is posted to Ethereum and final when Ethereum finalizes that batch.

The Block reported that applications which previously relied on Flashblocks must migrate to standard canonical block subscriptions. Base's migration table maps eth_subscribe("newFlashblocks") to eth_subscribe("newHeads"), and drops Flashblocks-aware "pending" semantics for balance and call RPCs.

BaseTime and B20

Denim also ships BaseTime: a predeploy at 0x4200…0030 that exposes millisecond Unix time so contracts can expire orders, stream rewards or accrue interest at 200ms resolution. Ethereum-compatible block.timestamp stays in whole seconds; new optional RPC fields such as timestampMs expose the authenticated millisecond clock.

On the token side, Denim adds a NOT operator for reusable B20 compliance lists, extends TRANSFER_EXECUTOR_POLICY to every transfer path (including holder-initiated transfer), and reverts transfers, mints or seizures that would send tokens to the token contract's own address with InvalidReceiver.

Base warned that block.number now advances ten times faster in wall-clock time. Contracts that treat block counts as durations — timelocks, vesting, per-block rate limits, default ERC20Votes clocks — need a review; block.timestamp is unchanged.

What it means for Web3 teams – Analysis

Sub-second canonical state is a different product from sub-second preconfirmations. Teams that built reconciliation against Flashblocks get a cleaner path, but any block-number clock just got ten times shorter. Issuers with a restrictive transfer-executor policy should check whether holders can still initiate transfers at all. This is infrastructure news, not a trading call.

FAQ

When did Base Denim go live?

Base's engineering blog dated Nov. 5, 2026 said Denim is now live on mainnet. The Block reported the same day.

What replaces Flashblocks?

Full canonical blocks every 200 milliseconds. Apps should use standard subscriptions such as eth_subscribe("newHeads") instead of Flashblocks streams.

Does a 200ms block mean finality?

No. Base says a transaction becomes safe when its batch is posted to Ethereum and final when Ethereum finalizes that batch.

What is BaseTime?

A Denim predeploy and matching RPC fields that expose millisecond Unix timestamps so contracts and clients can reason about sub-second time while block.timestamp stays in seconds.

Sources

  1. Base
  2. The Block

News summary based on the sources above. Not investment, legal or tax advice. Editorial policy & corrections · Report an error

Building in Web3? Turn the news into trust.

Positioning, KOL programs, LinkedIn systems and claim-safe content for Web3 and fintech teams.

Related

Book a free call