Procedure status
The final procedure will be published with the official node release. It will specify exact commands, configuration paths, default ports, and hardware requirements.
General prerequisites
- A dedicated 64-bit Linux server or computer with controlled administrator access.
- A stable Internet connection with permitted outbound access to the peer-to-peer network.
- A dedicated, unprivileged system account for the node.
- Backup storage for configuration and sensitive data.
- Basic experience with Linux administration, systemd, and system logs.
Planned procedure
1. Check the release announcement
Check the Downloads page and its corresponding official announcement. Do not use an unannounced release.
2. Download from the official source
Use only files published on this website. Community mirrors and packages are valid only if explicitly listed.
3. Check the checksum and signature
Compare the SHA-256 checksum with the published value, then verify the detached signature using the official public key. Stop if they do not match.
4. Isolate the process
Create a dedicated system user, restrict permissions, and do not run the node as an administrator.
5. Configure the node
The official release will document configuration, the data directory, and network options.
6. Start and monitor
The service will be managed by systemd. Monitor logs, disk space, synchronization, and connection status.
Operational security
- Never expose the node's RPC interface directly to the Internet.
- Restrict server access with a firewall and SSH key authentication.
- Apply operating system security updates.
- Back up configuration and any secrets encrypted and offline.
- Monitor logs and alert on unexpected shutdowns or disk exhaustion.
- Keep nodes separate from wallets: private keys must not be stored on a public server.
Troubleshooting
Troubleshooting guidance will be completed with the official release, covering connection ports, useful logs, desynchronization symptoms, disk management, and updates.