Node Operations
Run sudo d9-manager to open the management menu tailored to your host’s current state. If your Node Admin is set to your D9 Wallet address, you can also rotate keys, update the reward destination, and set the display name directly from D9 Wallet.
On-chain management
Section titled “On-chain management”| Action | Description |
|---|---|
| Check Node Status | View registration state, Node Admin, reward destination, service status, and sync progress. |
| Rotate Session Keys | Generate new session keys on the host and update them on chain in one step without changing the Node ID. |
| Change Reward Destination | Set a new reward address (requires the self-transfer ownership check). |
| Set Display Name | Assign a network-unique display name to your validator. |
| Change Node Admin | Replace the operator management address (requires the Node ID seed phrase). |
| Leave Candidacy | Withdraw from the validator candidate pool. |
Node maintenance
Section titled “Node maintenance”| Action | Description |
|---|---|
| Update Node Binary | Download and verify the latest release defined in the network profile, then restart the service. |
| Check Service Status | Display d9-v2-node service health and recent log output. |
| Restart Node Service | Restart the d9-v2-node service. |
Recovery
Section titled “Recovery”Interrupted registration: Re-run sudo d9-manager. It loads your saved progress and resumes based on current on-chain state.
Rebuilt or migrated server: Restore your existing node identity on the new host, then rotate session keys:
sudo d9-manager restore-node-account <NODE_ID_ADDRESS> --confirmSecurity
Section titled “Security”The validator node’s local RPC is strictly for local management. Never expose it to the public internet, bind it to an external interface, or forward it through a reverse proxy or tunnel.
Common issues
Section titled “Common issues”| Symptom | Resolution |
|---|---|
Another d9-manager session is already running |
Close the existing session before starting a new one. |
| Network profile mismatch or invalid config | Verify network.json, and confirm the host was not initialized on a different network. |
| Local node RPC unreachable or timed out | Check service health with sudo systemctl status d9-v2-node and wait for the node to finish starting before retrying. |
Node remains in ValidationPending |
Wait for chain synchronization to complete. On a rebuilt host, run restore-node-account and rotate session keys. |
| Registration not yet reflected on chain | Wait for block sync and finalization, then re-run sudo d9-manager. |
| Interrupted during key rotation | Keep all state files and the keystore intact, check current on-chain status with Check Node Status, then retry if needed. |
