Base Denim Upgrade: What 200ms Blocks Mean for Builders

Base, the Ethereum layer-2 network incubated by Coinbase, just got a lot faster. Its fourth network upgrade, Denim, activated on mainnet on November 5 at 18:00 UTC, moving Base from one canonical block every two seconds to five complete blocks every second. It is one of the most meaningful performance changes the chain has shipped, and it simplifies life for developers in the process.

• Denim went live on Base mainnet November 5, 2026, after reaching Base Sepolia on October 21
• Base now produces a full canonical block every 200 milliseconds, ten times its old pace
• The upgrade retires Flashblocks, the previous preview-based system for sub-second state
• A new BaseTime predeploy lets smart contracts read time to the millisecond

What Does the Base Denim Upgrade Change?

Before Denim, Base filled the two seconds between blocks with Flashblocks, a stream of incremental pending-state previews. Apps could show users a quick preview, but a preview could be dropped from the block that finally landed, so developers had to handle walk-backs. Denim replaces that with native 200ms blocks. Each one has its own block number, hash, state root and receipts, and Base says each carries the same guarantees as every other block on the chain.

The practical upshot, according to Base's engineering team, is that every standard JSON-RPC method now returns 200ms state directly. Tools like viem, ethers, Foundry and existing indexers work without a special Flashblocks client or reconciliation layer. Base also notes that blocks cannot skip slots: each block's timestamp is exactly 200ms after its parent's, and the protocol validates that cadence.

Does Faster Block Time Mean Faster Finality?

Not by itself, and Base is clear on this point. Including a transaction in a 200ms block gets it into a canonical block quickly, but it becomes safe when its batch is posted to Ethereum and final when Ethereum finalizes that batch, just as before. Apps that need stronger guarantees can still wait for safe or finalized status.

BaseTime, B20 and What Developers Should Check

Denim adds millisecond time in two places. The BaseTime predeploy lets contracts read the sub-second part of a block's timestamp, while RPC responses gain optional millisecond fields such as timestampMs. The existing seconds-based timestamp is unchanged for compatibility. The upgrade also tightens rules for B20, Base's native token standard, and lets compliance policies be inverted with a simple NOT flag.

One item deserves attention from builders. Because block numbers now advance ten times faster in wall-clock terms, any contract that uses block counts as a measure of time, such as timelocks or cooldowns, will see those durations shrink to a tenth. Base's documentation urges teams to audit for this, and node operators need base/base v1.5.1 or later.

Why Faster Layer-2 Blocks Matter for Onchain Finance

Base frames its mission around trading, financing and payments, and all three benefit from a chain that updates state often and measures time precisely. It fits a broader push across Ethereum scaling, from the gas-limit gains in our Glamsterdam testnet coverage to fresh layer-2 launches like the Robinhood chain's first week. Follow along in our crypto section.

Sources: Base Engineering Blog — November 5, 2026; Base Documentation — 200ms Native Blocks — accessed November 7, 2026; The Block — November 5, 2026.