Base activates Denim on November 5, introducing native 200 ms blocks

2 min

Base will activate its Denim upgrade on November 5 at 18:00 UTC. The network is expected to stay online during the maintenance window. Node operators must install the required release before activation, according to the network’s status notice. Denim shifts block production to native blocks every 200 milliseconds and replaces Flashblocks, which requires application changes.

Activation and network operations

Mainnet is planned to remain operational through the Denim maintenance window. Operators should complete the release upgrade ahead of the activation time listed in the status notice.

Native blocks at 200 ms and stream migration

The Denim upgrade moves from one canonical block every two seconds to five complete blocks per second. Flashblocks are removed. Applications that consumed Flashblocks must migrate to canonical block and RPC streams as described in the Denim documentation.

Impact on application throughput and responsiveness

More frequent complete blocks change how often applications process receipts, balances and UI refreshes. Exchanges may encounter more update cycles between user actions. Indexers will record more blocks and track state changes more often. Systems must keep pace to avoid creating internal backlogs when the chain accelerates.

Faster observation does not define settlement rules

Shorter block intervals improve time to observe execution. They do not set finality policies for bridges, exchanges or financial applications. Each service defines when results are reliable and when balances can be released.

Time handling and ordering rules

Denim introduces millisecond-aware time fields while preserving seconds-based fields. Systems that assume a new block always brings a new whole-second timestamp can misorder events or merge unrelated records. Storage schemas, ordering logic and monitoring must align with the millisecond cadence to maintain correct sequencing.

Post-activation checks that matter to users

Operational readiness spans nodes and application integrations. Success indicators after activation: stable block production, correct indexing, and normal deposits, withdrawals and contract interactions. Denim is scheduled infrastructure work. If activation proceeds as planned, applications will gain a different foundation for presenting progress. User experience improvements will depend on how well surrounding software adopts the new streams and timing model.