This guide walks you through updating your Nym node to the latest version. The update process involves:
- Understanding the new version changes
- Downloading the latest binary
- Safely replacing the old version
- Verifying the update
1. Version information
a. Latest release: v2026.20-glasgow
Release v2026.20-glasgow ships nym-node v1.42.0, built on 2026-10-13.
- Download: Nym Binaries v2026.20-glasgow
- Changelog: Official Glasgow changelog
b. Node client account balance
The client account is generated when the node is initialized and is separate from your bonding wallet. It pays for on-chain configuration updates and is intended to support bandwidth ticket redemption.
- Check the account balance at your node’s
/api/v2/auxiliary-detailsendpoint, or monitor it throughhttps://validator.nymtech.net/api/v2/nym-nodes/annotation/<NODE_ID>. - Follow the official client account funding guide to fund the correct account. Nym recommends 10 NYM to cover transaction fees while maintaining the minimum balance.
- Allow up to 24 hours for the
nym-apibalance to refresh after funding.
c. Features and fixes
- Key security: Client keys can be encrypted with a passphrase, and pemstore encryption is optional.
- Networking: Network detail defaults and HTTP front/retry policies were added.
- Node reliability: Sphinx key rotation now performs one write with jitter, TLS uses an explicit ring crypto provider, and x86 builds enable AVX2.
- Configuration: The missing credentials request database setting was restored.
- Maintenance: Sphinx was upgraded to v0.8.0 alongside dependency and SQLx updates.
d. Operator maintenance updates
- Server maintenance: The updated
system-maintenance.ymlAnsible playbook is covered in the official maintenance guide. - Self-hosted virtual machines: Operators using KVM and libvirt on dedicated servers can follow the new hypervisor hygiene guide alongside VM maintenance.
2. Update process
a. Download the latest binary
curl -L "https://github.com/nymtech/nym/releases/download/nym-binaries-v2026.20-glasgow/nym-node" -o nym-node && \
chmod +x nym-node b. Stop the Nym node service
systemctl stop nym-node c. Replace the existing binary
- Option 1: Keep Old Version as Backup
mv /usr/local/bin/nym-node /usr/local/bin/nym-node-old - Option 2: Remove Old Version Completely
rm /usr/local/bin/nym-node mv nym-node /usr/local/bin/ d. Re-run the Network Tunnel Manager (if not done since NIP-14)
NIP-14 passed in v2026.15-bydgoszcz and updated the Network Tunnel Manager (NTM) to open additional services for NymVPN users. If you have not re-run NTM since that release, run it on every hosting server now.
curl -L https://raw.githubusercontent.com/nymtech/nym/refs/heads/develop/scripts/nym-node-setup/network-tunnel-manager.sh -o network-tunnel-manager.sh && \
chmod +x network-tunnel-manager.sh ./network-tunnel-manager.sh complete_networking_configuration 3. Restart and verify
a. Restart the service
systemctl daemon-reload && systemctl start nym-node b. Check node status
Confirm the installed binary reports 1.42.0:
nym-node --version Inspect the service logs:
journalctl -fu nym-node c. Verify node operation
- Check service status
systemctl status nym-node - Monitor performance
Visit https://nym.com/explorer to verify node visibility.
- Ensure all ports are accessible
ufw allow 22/tcp # SSH - you're in control of these ports
ufw allow 80/tcp # HTTP
ufw allow 443/tcp # HTTPS
ufw allow 1789/tcp # Nym specific - Mixnet
ufw allow 1790/tcp # Nym specific - Verloc
ufw allow 8080/tcp # Nym specific - nym-node-api
ufw allow 9000/tcp # Nym specific - clients port
ufw allow 9001/tcp # Nym specific - wss port
ufw allow 41264/tcp # Nym specific - Lewes Protocol registration
ufw allow 51264/udp # Nym specific - Lewes Protocol data 4. Resources
- Documentation: https://nymtech.net/docs/
- Explorer: https://nym.com/explorer
- Community: https://discord.gg/nym
- Changelog: https://nym.com/docs/operators/changelog