TriportRPC
DashboardDocs

eth_syncing

Polygon / https://triport.io/polygon

Minimum tier: Free

Polygon method guide

Last updated:

eth_syncing returns the synchronization status of the backend node. If the node is at the chain head and not importing historical blocks, it returns the boolean false. If the node is still catching up, it returns a sync-progress object describing how far along it is: { startingBlock, currentBlock, highestBlock }.

Use it as a lightweight health indicator before relying on a node for freshness-sensitive reads — for example, to confirm a backend is at the tip before trusting its eth_blockNumber or balance results. It takes no parameters and is one of the cheapest calls on the standard EVM read surface.

In practice, Triport fronts a pool of upstream Polygon providers and steers traffic away from any node that is not at the head, so on this surface eth_syncing almost always returns false. Treat a non-false response as the exception — a backend that briefly fell behind — rather than the normal case. Do not use eth_syncing as your sole liveness check: a CDN-fronted backend can return false even when it is stale, so pair it with a tip-freshness check (compare eth_blockNumber against expected block time, ~2s on Polygon).

Parameters

This method takes no parameters.

Returns

eth_syncing return value
FieldType
resultobject

Examples

curl https://triport.io/polygon \
  -X POST -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <api-key>' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_syncing","params":[]}'
const res = await fetch("https://triport.io/polygon", {
  method: "POST",
  headers: { "Content-Type": "application/json", Authorization: "Bearer <api-key>" },
  body: JSON.stringify({
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_syncing",
  "params": []
}),
});
const data = await res.json();
import requests
resp = requests.post(
    "https://triport.io/polygon",
    headers={"Authorization": "Bearer <api-key>"},
    json={"jsonrpc":"2.0","id":1,"method":"eth_syncing","params":[]},
)
print(resp.json())

Usage

  1. Transport: HTTP (JSON-RPC).
  2. Chain: Polygon.
  3. Clusters: mainnet.
  4. Credit cost: 1 per call.

FAQ

What does eth_syncing do?
Reports whether the Polygon node serving your request is still catching up to the chain head, or fully synced.
How many credits does eth_syncing cost?
eth_syncing costs 1 credit(s) per call on Triport by default.
Is eth_syncing available over WebSocket?
eth_syncing is an HTTP JSON-RPC method.