Useful commands

---

Node Backup and Restore

Caution

If there are more than one nodes running on the network which have the same Node ID, other nodes will randomly communicate with one of these nodes. If this NodeID is that of a validator node, its uptime calculation will be negatively effected which may result in loss of staked rewards. Please make sure that only one node is running with your NodeID.

The NodeID is identified by two files:

• staker.crt
• staker.key

You will be able to find these files in the juneogo installation, specifically in ~/.juneogo/staking.

This folder contains a third file:

• signer.key

Caution

In order to backup our node, all we need to do is bootstrap a new one which contains these three files in the staking directory. If we were to remove these files and restart our node, a new version of these files would be created and our node would be assigned a new nodeID.

Check your node

curl -X POST --data '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"info.isBootstrapped",
    "params": {
        "chain":"JUNE"
    }
}' -H 'content-type:application/json;' 127.0.0.1:9650/ext/info

Get your node informations

curl -X POST --data '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"info.getNodeID"
}' -H 'content-type:application/json' 127.0.0.1:9650/ext/info

Check the health of your node

curl -H 'Content-Type: application/json' --data '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"health.health",
    "params": {
        "tags": ["11111111111111111111111111111111LpoYY"]
    }
}' 'http://127.0.0.1:9650/ext/health'

Delete Node

Danger

Make sure you save everything you need before deleting the node. Check here Node Backup and Restore

sudo systemctl stop juneod
sudo systemctl disable juneod
rm /etc/systemd/system/juneod.service
rm -rf juneogo-binaries .juneogo