Skip to main content
Monad needs an x86_64 host on a bare-metal Agent — upstream publishes its packages for amd64 only, so an Agent on an aarch64 host doesn’t advertise Monad and the wizard won’t offer it for that executor.
Monad is a high-throughput, EVM-compatible chain. Every Monad node runs three roles — more than any other chain Novacula manages — deployed and managed together:
  • consensus — the BFT consensus role, run by the monad-node client.
  • execution — the execution-layer state engine, run by the monad client.
  • rpc — the Ethereum-compatible JSON-RPC front-end, run by the monad-rpc client.
Monad runs only on a bare-metal executor (Agent). It is not available on the Kubernetes (Operator) backend — the host needs hugepages, a dedicated monad user, and a metrics collector that the Agent sets up for you during install. To provision a host, see Provision on bare metal. To deploy a node, open Deploy node, pick Monad, then choose a network. The three roles are deployed as one unit on a single version — you pick one version and all three roles use it. The wizard offers exactly the networks and versions your target executor declares; if a version isn’t listed, that executor can’t run it.

​
Networks and resources

Defaults are pre-filled in the deploy wizard. A Monad node is heavy, and the execution role dominates. CPU and RAM are sized per role; disk is one shared data volume — the three roles’ defaults are summed into a single total you size in one input. Lower the defaults only if you know your workload fits. The shared data volume defaults to 2600 GiB on both networks (500 + 2000 + 100); the execution role drives most of it. Size it correctly — it matters more than for any other chain.

​
Clients

All three roles use a single client version. The roles are versioned in lock-step — there is no “upgrade execution without consensus” path. New nodes deploy on 0.16.4 (mainnet) or 0.16.3 (testnet) — the wizard no longer offers the older versions. Nodes already on them keep running, and testnet nodes follow the update path below. On testnet, in-place update steps run 0.15.0 → 0.15.2 → 0.16.0 → 0.16.3, all three roles together; the step to 0.16.0 is security-urgent. See Update a node’s version.
A mainnet node on 0.15.1 diverged from the network when MONAD_TEN activated and can’t be updated — the step to 0.16.4 shows as Update blocked. Delete the node and redeploy it on 0.16.4.

​
Ports

Only monad-rpc serves HTTP; the consensus and execution roles have no public endpoint and are observed through metrics.

​
Configuration overrides

The console offers no config-override step in this release; the keys below describe what Monad reads, for reference. The toggles you’ll commonly set: Settings the platform owns — chain selection, ports, identity paths, and the metrics endpoint — are protected: typing one flags the row as managed by Novacula and blocks the save until you remove it.

​
Monitoring

The node page surfaces per-role status, block height, peers, sync progress, disk usage, and Monad-specific consensus and sync counters. See Node monitoring.

​
What you can build

  • Public RPC node — accept the defaults and expose :8080 (HTTP) behind your own proxy.