Skip to main content

Go-Zenon Node Status

When running a Node in Zenon Network, it’s important to check its status to ensure it’s operational and in sync with the network. This guide explains how to use the curl command to query the sync status of your Node. Instructions are provided for both Windows and Linux/macOS users.

Understanding Sync Status​

The JSON-RPC response includes a State field with three possible values:

  1. "State":1: Not synced. The node is behind in block height and still catching up.
  2. "State":2: Fully synced. The node is synced to the latest block and has sufficient peers.
  3. "State":3: Synced but has low peers. The node is synced to the latest block but has insufficient peers to operate optimally.

Instructions for Linux and macOS Users​

  1. Open Terminal:
  • Linux: Open your preferred terminal application
  • macOS: Press Command + Space, type Terminal, and hit Enter
  1. Run the Command:
curl -X POST https://my.hc1node.com:35997 \
-H "Content-Type: application/json" \
-d '{"jsonrpc": "2.0", "id": 40, "method": "stats.syncInfo", "params": []}'

Note: Replace https://my.hc1node.com:35997 with the address of node being tested.

Instructions for Windows Users​

  1. Open Command Prompt:
  • Press Win + R, type cmd, and press Enter
  1. Run the Command:
curl -X POST https://my.hc1node.com:35997 ^
-H "Content-Type: application/json" ^
-d "{\"jsonrpc\": \"2.0\", \"id\": 40, \"method\": \"stats.syncInfo\", \"params\": []}"

Note: Replace https://my.hc1node.com:35997 with the address of node being tested.

Understanding the Response​

The node will respond with a JSON object similar to this:

{
    "jsonrpc": "2.0",
    "id": 40,
    "result": {
        "state": 2,
        "currentHeight": 9177763,
        "targetHeight": 9177763
    }
}

Check the state field:

  • 1: Not synced
  • 2: Fully synced
  • 3: Synced but low peers

Troubleshooting Sync Issues​

  • State 1 (Not Synced): The node is still catching up. Verify your node's network connectivity and block processing.
  • State 2 (Fully Synced): The node is fully operational.
  • State 3 (Synced but Low Peers): Ensure your node is connected to enough peers. Check your node configuration to add more peers if necessary.
  • No Response: Verify the API URL and ensure the node's API port is open and reachable.