
Base ships Denim upgrade with native 200ms blocks, retiring Flashblocks
Base's fourth mainnet upgrade, Denim, is live. It replaces Flashblocks with five canonical blocks per second, adds millisecond time for contracts and tightens B20 compliance.
In brief
- Base now produces five canonical blocks per second, each a real block rather than a preview.
- Flashblocks is retired; apps must switch to standard RPC streams such as eth_subscribe("newHeads").
- Code that treats block.number as a duration now measures one tenth of the intended time.
What happened
Base's fourth mainnet upgrade, Denim, is live, according to the Base blog.
The chain now produces a full canonical block every 200 milliseconds, five per second, instead of one block every two seconds.
Before Denim, Base streamed Flashblocks: previews of a block still being built.
Those previews could be dropped from the block that finally landed, so apps had to be ready to walk the state back.
Denim retires Flashblocks.
Each 200ms block is canonical, and standard JSON-RPC methods such as eth_subscribe("newHeads") and eth_getLogs return sub-second state without a special client.
The upgrade also adds BaseTime, which gives contracts and RPC clients millisecond-resolution time.
Ethereum headers still store timestamps in whole seconds, so five consecutive blocks share one block.timestamp.
B20, Base's token standard, gets additional transfer checks and reusable compliance policies.
Why it matters
Inclusion in a 200ms block is not finality.
A block becomes safe when its batch is posted to Ethereum and final when Ethereum finalizes that batch, the blog says.
The faster cadence gives lending, trading and rewards protocols five chances per second to react.
Liquidations can run in the first block after a price update rather than waiting for the next two-second block.
The change also breaks assumptions. block.number now advances ten times faster, so timelocks, vesting schedules, per-block rate limits and block-based governance voting periods shrink to one tenth of their intended length.
Fixed-cardinality TWAP oracles now cover roughly half as much wall-clock history before observe() reverts, per the post.
Base advises replacing block-count durations with block.timestamp comparisons, or multiplying tunable counts by ten.
What to watch
Builders who consumed Flashblocks streams must migrate: newFlashblocks maps to newHeads, pendingLogs to logs, and the "pending" tag no longer returns preconfirmed state.
Base published a full migration mapping and a 200ms native blocks specification for the remaining edge cases.