This page covers full/RPC nodes. Validator operators should consider the Slow & Safe Upgrade (rolling replacement with key rotation) described in the official guide.
Before you start
- Check the latest version and release notes on the GitHub Releases page.
- Plan a maintenance window if you expose RPC to users.
- The procedure is identical for Mainnet and Turing; your
--chainflag selects the network.
A) Upgrade — Pre-built binary
Replace the existingavail-node binary with the latest release, then restart the service.
data-avail. If that’s your case, replace avail-node in the commands above with data-avail.
B) Upgrade — Docker
C) Upgrade — Build from source
Verify the upgrade
- Logs show the new version near startup (e.g.,
version 2.x.x-<git-hash>). - Telemetry: find your node by
--nameon the correct network tab and confirm the reported version. - RPC (if enabled):
curl http://127.0.0.1:9944 -H 'Content-Type: application/json' -d '{"id":1,"jsonrpc":"2.0","method":"system_version","params":[]}'
After protocol/runtime upgrades, nodes running an outdated client may fail to sync or build blocks. Keep up with release announcements and upgrade promptly.