Base Cuts Block Times Tenfold to 200ms With Denim Upgrade

Base has activated Denim, its fourth major network upgrade, cutting block times tenfold to 200 milliseconds from two seconds on the Coinbase-incubated Ethereum layer 2 mainnet. The team announced the activation on Thursday, November 5, 2026, after testing the release on the Sepolia testnet last month.

The headline change is speed, but the mechanics matter more. Denim replaces Flashblocks, Base's preview system for pending transactions, with five complete canonical blocks per second. That means every transaction included in a block is confirmed on-chain, rather than appearing first in a provisional state that could later change.

What was wrong with Flashblocks?

Previously, Base produced one canonical block every two seconds. Flashblocks streamed previews of pending transactions in between. Those previews could be dropped from the final block, which forced application developers to account for discrepancies between the preconfirmed and canonical states.

Denim removes that reconciliation burden entirely. Every 200ms block becomes part of the canonical chain. Standard RPC methods now expose the faster state directly, so developers no longer need separate Flashblocks subscriptions or custom systems to reconcile the two views of the network.

What does this change for builders? Less plumbing, fewer edge cases, and a state view that applications can trust on first read rather than after a second confirmation path.

Faster clocks for trading and payments

Base framed the upgrade around trading and payments use cases, including tokenized stocks and other assets that require faster on-chain settlement. The network said the change aims to make on-chain transactions faster and more responsive for those applications.

Denim also introduces BaseTime, which adds millisecond-level timing to smart contracts. Developers can now measure elapsed time more precisely for trading functions, auctions, order expirations and other DeFi mechanics. The faster block cadence gives lending protocols, decentralized exchanges and other applications more frequent opportunities to respond to market updates — including liquidations and rebalancing.

For a lending protocol, the practical difference is reaction time. A market move that once sat unaddressed for up to two seconds can now trigger a liquidation within a fraction of that window, tightening the risk profile of leveraged positions on the network.

Token-standard changes under B20

The upgrade carries three changes to B20, Base's token standard, with compliance and safety implications for issuers:

• Invertible policies. Issuers can now invert compliance policies through a NOT operator, reusing a single address list for both allow and block rules, according to Base.
• Executor coverage. Transfer-executor policies now apply to all transfer methods, including direct transfers initiated by token holders, making it harder to bypass issuer-defined restrictions.
• Self-transfer protection. The upgrade blocks transfers, mints and seizures that send tokens to the token contract's own address, preventing accidental transfers that could permanently lock funds.

The executor change closes a meaningful gap. If transfer restrictions applied only to certain transfer paths, holders could route around issuer rules with direct transfers. Under Denim, that bypass route is gone, which strengthens the compliance posture for asset issuers operating on Base.

The self-transfer protection is a straightforward safety rail. Accidental sends to a token contract's own address have historically trapped funds irrecoverably on other networks; Base now prevents that failure mode at the standard level.

What comes next

With Denim live on mainnet, the operational question shifts to adoption. Developers of order-book exchanges, auction mechanisms and tokenized-asset platforms now have a 200ms cadence and millisecond timing primitives to build against, and the removal of Flashblocks gives them a migration path to complete as they retire legacy preview integrations.