From 2e6a4e9ad3539fc81d843d2a7320017340a3c12f Mon Sep 17 00:00:00 2001 From: ayaanoncrypto <1.06945712e+08+ayaanoncrypto@users.noreply.github.com> Date: Thu, 20 Aug 2026 00:38:14 +0000 Subject: [PATCH] docs: clarify eth_blockNumber verification --- docs/running-an-arc-node.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/running-an-arc-node.md b/docs/running-an-arc-node.md index 93f04f9d..73afa4d0 100644 --- a/docs/running-an-arc-node.md +++ b/docs/running-an-arc-node.md @@ -218,8 +218,8 @@ curl -s -X POST http://localhost:8545 \ ``` The produced output is in JSON format. -The `result` field represents the next block height, in hexadecimal -(you can use `printf "%0d"` to translate it into decimal). +The `result` field represents the latest block number known to the node, +encoded as a hexadecimal quantity (you can use `printf "%d\n" ` to convert it to decimal). It should increase over time. If it remains `0x0`, check the logs of the consensus layer for errors. Common causes are a missing or incomplete snapshot, mismatched `$ARC_RUN`