FAQ - Validators
How do I check my node status?
Once your node is running, you can run
curl -s localhost:8888/status | jq .last_added_block_info to query your local server's synchronization status. The output will look similar to:
curl -s http://localhost:8888/status | jq .last_added_block_info
What ports are required for casper-node?
Casper-node requires the following ports:
- 35000 - Required for external visibility
- 7777 - RPC endpoint for interaction with casper-client
- 8888 - REST endpoint for status and metrics (This port allows your node to be part of the network status)
- 9999 - SSE endpoint for event stream
What '--node-address' do I use for making requests?
If you are running a node, you can use
localhost:7777 for RPC requests like deploys. For node-health queries, use
How can I move my node to another machine?
- Stop the node.
- Copy all data.
- Change the mountpoint.
- Start the node.
- Create another node in parallel.
- Once it is up to date, stop the nodes.
- Swap the associated keys.
- Restart the new node.
Note: Use the following command to copy your node's data:
rsync -av --inplace --sparse /var/lib/casper/ /new_mount
Does Casper run on ARM?
Casper-node does not work with ARM type servers. You can see our hardware specifications here.
What operating systems are supported for casper-node?
Casper is currently tested and packaged for Ubuntu 18.04 or 20.04.
Do I have to run a node 24/7?
Validators must be online 24/7. Otherwise, they face ejection and loss of rewards as a result of liveness failure. Failure to participate in consensus for one era results in ejection.
If you cannot run a node 24/7, you can delegate your tokens to a healthy validator node with good uptime.