⚠️ Do not upgrade your mainnet or testnet node until you receive an official announcement.
Upgrades are communicated via official channels. See upgrade instructions for details.

⚠️ Mandatory upgrade for all mainnet nodes before 2026-09-02 14:30 UTC. This release sets the MONAD_TEN activation timestamp for mainnet. A node still on v0.16.0 or earlier after that instant will continue applying MONAD_NINE rules and diverge from the network.

monad (execution) v0.16.1 Changelog

Tag: v0.16.1
Commit: 7279dfc7b

Highlights

• MONAD_TEN activation on mainnet — MIP-8 (page-encoded storage) activates on mainnet at timestamp 1788359400 (2026-09-02 14:30 UTC). Mainnet counterpart to the testnet activation shipped in v0.16.0.
• Page-encoded timeline now required on mainnet — nodes must present either a page-encoded primary (Phase C) or an active secondary timeline (Phase A/B dual-db), or they will fail to start.
• Dual-db commit support in the ethblocks runloop, allowing nodes still in Phase A/B to commit to both timelines.

Protocol changes

• Set MONAD_TEN activation timestamp for mainnet — 1788359400 (2026-09-02 14:30 UTC). MONAD_NINE remains in effect for timestamps below that. Ref: monad (execution) PR #2489
• Enforce page-encoded timeline assertion on mainnet — previously testnet-only. Nodes that have not completed Phase A (dual-db activation) will fail to start. Ref: monad (execution) PR #2489

Robustness fixes

• Allow dual-db commit in runloop_monad_ethblocks where secondary_db is optional, so Phase A/B nodes commit to both timelines. Ref: monad (execution) commit df14e67bb

Internal changes

• Consolidate dual-db mirroring behind for_each_db, replacing duplicated commit paths in runloop_monad. Ref: monad (execution) commit d836afc18

Full Changelog: v0.16.0...v0.16.1