BitCtrl logoBitCtrl
← Back to Pulse
Monad logoOperationsMonadBlockchainAlert

MONAD_NINE Activated on Mainnet - RPC Semantics and EVM Behavior Updated

The v0.13.x upgrade line is now live on mainnet, introducing earlier-state RPC responses and core EVM execution changes.

BitCtrl Ops•Protocol & Node Desk•Mar 19, 2026•4 min read
Monad MONAD_NINE mainnet activation and node operations visual

MONAD_NINE Activated on Mainnet - RPC Semantics and EVM Behavior Updated

Overview

Written on March 19, 2026. Monad's official mainnet changelog lists MONAD_NINE as the mainnet revision boundary at March 19, 2026, 14:30 UTC (timestamp 1773930600). This is a mandatory hard-fork window: nodes that missed the compatible v0.13.x rollout diverge from the canonical chain after the fork boundary.

The protocol release itself is v0.13.0, with Monad's release notes describing it as the canonical MONAD_NINE hard-fork version. Monad also published v0.13.1 on March 16, 2026 as a patch release for State Archive node RPC issues, which means operators may now be running a patched v0.13.x line even though the fork payload remains the v0.13.0 MONAD_NINE revision.

Context

The most visible downstream change is RPC semantics. The latest block tag now resolves to proposed block state instead of finalized state, while websocket subscriptions such as newHeads and logs surface voted blocks earlier in the block lifecycle. For indexers, bots, dashboards, and alerting systems, that is a behavioral break unless explicit confirmation logic is already in place.

MONAD_NINE also ships core EVM changes: MIP-3 linear memory, MIP-4 reserve balance precompile, and MIP-5 Osaka activation including the CLZ opcode. Together, those changes improve execution predictability for memory-heavy workloads and expand the execution-layer features available to Monad applications and infra tooling. For operators, the post-fork task is less about config churn and more about semantic correctness. The upgrade guidance does not require new node.toml or systemd override changes, but it does require version verification, downstream RPC audits, and monitoring recalibration so early-stage chain data is not misread as finalized state.

What Changed at the Protocol Level

  • latest now returns proposed block state rather than waiting for finalized state.
  • Websocket newHeads and logs subscriptions now emit voted blocks earlier in the pipeline.
  • MIP-3 introduces linear EVM memory pricing.
  • MIP-4 adds the reserve balance precompile.
  • MIP-5 activates Osaka functionality including the CLZ opcode.

Operator Impact

  • Nodes that did not upgrade to the compatible v0.13.x line before the fork boundary are no longer aligned with canonical mainnet.
  • RPC consumers that assumed finalized state at the edge now need explicit confirmation layers.
  • Monitoring and automation that key off event timing should be recalibrated for proposed and voted-stage data.
  • The upgrade is operationally simple at the node layer, but downstream semantics need review.

Sources

Key Takeaways
  • MONAD_NINE mainnet boundary is March 19, 2026 at 14:30 UTC (timestamp 1773930600) per Monad's mainnet changelog.
  • The hard-fork release is v0.13.0, and Monad published v0.13.1 on March 16 as a patch for State Archive RPC issues.
  • RPC semantics changed: latest now returns proposed state, while newHeads and logs surface voted blocks earlier.
  • EVM upgrades include linear memory, reserve balance precompile, and Osaka or CLZ support under MONAD_NINE.
operationsmonadalertpublished-thursdayoperatorsvalidator-opsruntime-upgradechange-management