eth_syncing - Arbitrum

Example code for the eth_syncing JSON RPC method. Сomplete guide on how to use eth_syncing JSON RPC in GetBlock Web3 documentation.

This method returns the node's syncing status. If the node is fully synced, it returns false. If syncing is in progress, it returns an object describing the current sync state such as starting block, current block, highest block, and related fields. This method helps developers understand whether the node is caught up with the blockchain.

Parameters

  • none

Request

curl --location 'https://go.getblock.us/<ACCESS_TOKEN>' \
--header 'Content-Type: application/json' \
--data '{
   "jsonrpc": "2.0",
    "method": "eth_signTransaction",
    "params": [],
    "id": "getblock.io"
}

Response

{
    "jsonrpc": "2.0",
    "id": "getblock.io",
    "result": false
}

Response Parameter Definition

Field
Type
Description

result

boolean or object

false if node is fully synced. Otherwise, an object with sync progress.

startingBlock

string

Block number where syncing started.

currentBlock

string

Block that the node is currently processing.

highestBlock

string

The latest block known to the network.

warpChunksAmount

string

Total warp sync chunks required for full sync.

warpChunksProcessed

string

Number of warp chunks processed so far.

pulledStates

string

Number of state entries downloaded.

knownStates

string

Total expected state entries.

Error handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid ACCESS_TOKEN.

Integration with Web3

The eth_syncing helps developers to:

  • Detect if a provider or RPC endpoint is still catching up with the chain.

  • Pause transaction execution or contract event listeners until the node is synced.

  • Build intelligent dashboards that show syncing progress in real time.

  • Improve user experience by avoiding stale reads or outdated contract state.

  • Implement logic in wallets, bots and dApps to switch RPC endpoints when one is behind.

Last updated

Was this helpful?