Skip to main content
Please do not proceed until Monad Foundation provides notice.

​
Instructions for node operators

​
1. SSH into the node as root user

​
2. Update configuration file

Add the ping_rate_limit_per_second parameter to the [peer_discovery] section in your configuration file: 
nano /home/monad/monad-bft/config/node.toml
Add the following line to the [peer_discovery] section: 
[peer_discovery]
self_address = "YOUR_IP:8000"
self_record_seq_num = 0 # This remains the same as your current self_record_seq_num
self_name_record_sig = "YOUR_SIGNATURE"
refresh_period = 20
request_timeout = 5
unresponsive_prune_threshold = 3
last_participation_prune_threshold = 1000
min_num_peers = 1
max_num_peers = 450
ping_rate_limit_per_second = 100  # This is new to 0.12.6

​
3. Check systemctl overrides (if applicable)

This release adds --persisted-peers-path /home/monad/monad-bft/config/peers.toml to the monad-bft service startup. If you have existing systemctl overrides for monad-bft, you must ensure this flag is included in your override configuration.
To check if you have overrides: 
systemctl cat monad-bft | grep -A 10 "override"
If you have an existing override, edit it to include the persisted peers path: 
sudo systemctl edit monad-bft
Ensure your override includes: 
--persisted-peers-path /home/monad/monad-bft/config/peers.toml

​
4. Upgrade monad package

sudo apt update && sudo apt install --reinstall monad=0.12.6 -y --allow-downgrades --allow-change-held-packages

​
5. Restart the services and verify

sudo systemctl restart monad-bft monad-execution monad-rpc
sudo systemctl status monad-bft monad-execution monad-rpc --no-pager -l
Expected output: All services should show Active: active (running)

​
6. Verify the correct version is running

monad-rpc --version
Expected output: 
monad-rpc {"commit":"cced63c687c6ab67846c94bc9fd6d6ae60272cd4","tag":"v0.12.6","branch":"","modified":true}
Sidecars need their own CPU cores and cannot share cores with monad processes. Monad uses all 16 cores on a standard setup (cores 0-15), so running a sidecar on the same cores will cause performance issues.

​
Patch notes

Please refer to the public changelog for v0.12.6.

​
Important updates for node operators

  • [Node ops / Peer Discovery] Add ping rate limiting configuration
    • New required parameter: ping_rate_limit_per_second = 100 in [peer_discovery] section
    • Prevents excessive ping traffic and improves network stability