Monad has published version 0.15.1 of its mainnet execution client, setting up a network-level hard fork at round 89,758,000. The release activates MIP-12, a consensus parameter change designed to accelerate block production by adjusting the vote pace across the validator set.
The upgrade also includes a scheduled block subsidy reduction, lowering rewards from 25 MON to 18 MON once the hard fork takes effect. Both changes are bundled into the v0.15.1 client to keep consensus and emissions parameters aligned across the network.
MIP-12 Targets Faster Block Production
MIP-12 changes the timing of validator voting steps inside Monad’s consensus process. By modifying vote pace, the upgrade is intended to shorten block intervals and improve the network’s execution rhythm.
That makes the hard fork a performance-oriented consensus update rather than a simple maintenance release. The practical effect will depend on how smoothly validators adopt the new client and how the adjusted timing behaves under live mainnet conditions.
The subsidy reduction adds a monetary-policy adjustment to the same upgrade window. Lowering the per-block reward to 18 MON changes validator reward dynamics while the network also shifts its consensus parameters.
Validators Face Migration and Rollout Requirements
Operators running client version 0.14.5 or earlier must complete a database migration before deploying v0.15.1. The migration is required to preserve chain state continuity as the network moves into the new consensus configuration.hard fork
Monad is using a cohort-based validator rollout rather than a single uniform activation across all operators. That approach gives the network a more controlled path into the hard fork while validators complete upgrades and migrations.
The hard forkMonad is scheduled for around 10:30 AM EDT on July 23, depending on when the network reaches round 89,758,000. Until then, v0.15.1 functions as the staging client for the incoming parameter changes.
Monad’s v0.15.1 release marks a coordinated mainnet upgrade covering consensus speed, emissions and validator readiness. The next useful indicators will be migration completion, validator adoption, successful activation at the target round and whether MIP-12 delivers shorter block intervals without stability issues.