Skip to content
Crypto.world

The Ledger

Base Says Denim Replaces Flashblocks With Native 200ms Mainnet Blocks

Base says its Denim upgrade replaces Flashblocks with five canonical blocks per second and adds millisecond-resolution timestamps. The upgrade also changes B20 transfer checks and compliance controls.

Base Says Denim Replaces Flashblocks With Native 200ms Mainnet Blocks

Base says its fourth upgrade, Denim, went live on mainnet and replaces Flashblocks with five complete canonical blocks per second, each produced at a 200ms interval. But inclusion in one of those blocks does not by itself make a transaction final: Base says a block becomes safe when its batch is posted to Ethereum and final when Ethereum finalizes that batch.

Denim delivers native 200ms blocks

Before Denim, Base produced one canonical block every two seconds, while Flashblocks streamed incremental pending-state updates for the block being built. The upgrade replaces that arrangement with five full blocks per second; each block is canonical, not a preview of a block still being assembled. Base says blocks cannot skip slots, and the protocol validates that each block’s full timestamp is exactly 200ms after its parent’s.

Base Engineering Team writes: “eth_subscribe("newHeads"), eth_getLogs, eth_call, eth_getTransactionReceipt and every other standard JSON-RPC method return 200ms state out of the box, so viem, ethers, Foundry and existing indexers work without a Flashblocks client or a reconciliation layer.” Apps can read state from canonical blocks without reconciling a separate pending-state stream. Base says applications that need stronger guarantees can continue to wait for a block to become safe or finalized.

Applications consuming Flashblocks need to move to canonical block and RPC streams

Denim retires Flashblocks: Base no longer produces Flashblocks streams, and the “pending” block tag no longer returns preconfirmed state. Base maps newFlashblocks subscriptions to newHeads, and pendingLogs to logs. For applications that tracked new Flashblock transactions, Base’s replacement is to subscribe to newHeads and fetch each block’s transactions.

The upgrade also changes how block counts correspond to elapsed time. Base now produces ten times as many blocks per second, so contract or offchain logic that uses a block count as a duration will measure one-tenth of its intended wall-clock interval. The block.timestamp field remains unchanged and advances in whole seconds; Base advises developers to review block-number-based timelocks, vesting schedules, rate limits and governance periods.

BaseTime adds sub-second timestamps

Ethereum block headers store timestamps in whole seconds, and Denim keeps that convention for block.timestamp and the JSON-RPC timestamp field. As a result, five consecutive Base blocks share the same second-level timestamp. BaseTime supplies a millisecond clock so onchain time can move with every block.

Every Denim block carries a BaseTime metadata update at transaction index 1, immediately after the L1 info deposit. The update writes the block’s sub-second part as 0, 200, 400, 600 or 800 milliseconds to the BaseTime predeploy at 0x4200000000000000000000000000000000000030. Because the deposit runs before user transactions, contracts in the block can read its full millisecond timestamp.

Denim adds optional timestampMs fields to block and header responses, and blockTimestampMs fields to mined transactions, logs and receipt logs. The values come from authenticated BaseTime metadata, while the existing timestamp field stays in seconds. Pre-Denim blocks omit the new fields.

Denim adds B20 transfer checks and issuer-defined compliance tools

Denim adds B20 transfer checks and tools for managing issuer-defined compliance controls and policies. PolicyRegistry gains an invertedPolicyId view, allowing an issuer to invert a policy’s result with NOT while sharing the underlying address list. Base’s example combines a KYC policy with an inverted sanctions-list policy.

The upgrade also checks TRANSFER_EXECUTOR_POLICY against msg.sender for every transfer path. Before Denim, that policy applied to transferFrom calls made by someone other than the holder, leaving a holder’s direct transfer outside the check. B20 tokens launched with an executor policy inherit the new behavior; tokens that never set an executor policy retain the always-allow default.

Transfers, mints and seizures whose recipients are a B20 token’s own address now revert with the existing InvalidReceiver error. Base says the change helps prevent tokens from becoming stuck at the token contract address, which has no holder key. Self-sends, sends to other B20 tokens, approvals and burns are unaffected.

Sources

  1. Original source · Blog post Base base.org

Related stories

Explore

More articles