BitCtrl logoBitCtrl
← Back to Pulse
Monad logoOperationsMonadBlockchainWatch

Monad Testnet Release v0.14.0 - Incremental Update Following MONAD_NINE

New testnet release introduces post-fork RPC and node-ops refinements; operators should upgrade to stay aligned with the latest client behavior.

BitCtrl Pulse•Node Operations Desk•Apr 2, 2026•3 min read
Monad v0.14.0 upgrade banner

Monad Testnet Release v0.14.0 - Incremental Update Following MONAD_NINE

Overview

Written on April 2, 2026. Monad's v0.14.0 release continues the post-MONAD_NINE iteration cycle on testnet. Unlike v0.13.0, the official release notes do not describe a new hard-fork boundary or revision activation for this version, so the operator focus is not fork timing but staying aligned with the latest RPC and node behavior.

What Changed

The biggest user-facing changes are on the RPC side. Monad's changelog says v0.14.0 makes transaction receipt queries roughly 400ms faster by tracking receipts in the chainstate buffer, adds a new eth_fillTransaction endpoint for fully populating unsigned transactions, and moves websocket newHeads and logs notifications from voted blocks to proposed blocks for lower-latency updates.

Node Ops Changes

Context

The release also includes several operator-relevant implementation changes:

  • auth UDP fields in node.toml are now required
  • monad-ledger-tail --node-config-path is renamed to --peers-path
  • packaged systemd units move from Restart=no to Restart=always

If you run custom units, custom wrappers, or manual ledger-tail commands, these are the changes most likely to require follow-up.

Why It Matters

Operational Impact

Under the hood, v0.14.0 also bundles robustness and performance work: triedb sync fixes, stricter decoding cleanup, weighted fair queueing for transaction ingestion, gas-based peer scoring, and several archive and execution bug fixes. None of those create a fork boundary by themselves, but together they make the release operationally relevant for validators, full nodes, and RPC-dependent tooling.

Operator Notes

  • Upgrade testnet nodes to v0.14.0 and restart the standard services.
  • Recheck sync, receipt queries, websocket consumers, and any dashboards or bots that assume older block-notification timing.
  • Review custom systemd units and any manual monad-ledger-tail usage for the renamed flag and new restart defaults.
  • Treat this as a recommended compatibility checkpoint during Monad's rapid post-fork iteration phase.

Sources

Key Takeaways
  • v0.14.0 continues Monad's post-MONAD_NINE testnet iteration without a new fork boundary in the official release notes.
  • The release adds faster receipt queries, a new `eth_fillTransaction` endpoint, and websocket notifications on proposed blocks.
  • Operators using custom units or scripts should review required auth UDP fields, the `monad-ledger-tail` flag rename, and the systemd restart policy change.
  • Validators and RPC consumers should treat this as a recommended upgrade and a validation point for downstream tooling.
operationsmonadwatchpublished-thursdayvalidator-opsoperatorstoolingchange-management