TriportRPC

eth_syncing

POSThttps://triport.io/rpc/tron

Reports whether the selected Tron node exposes active synchronization progress.

Tron mainnettron:rpcfree+; tron_read_rpc: 15 / 20 / 100 / 250 RPS (free / basic / pro / business; default, unmeasured)

eth_syncing returns false when the selected upstream does not report active synchronization. The OpenRPC result also permits an implementation-defined object when a node reports progress.

Use the method as a node-state hint, not as a finality or freshness guarantee. For a chain height that applications can compare over time, call eth_blockNumber.

Parameters

JSON-RPC params must be an empty array.

paramsarrayrequired
Empty array; this method accepts no positional parameters.

Response

Response fields

FieldTypeDescription
jsonrpcstringJSON-RPC protocol version.
idnumberCorrelates the response with the request.
resultboolean or objectfalse, or implementation-defined synchronization progress.

Errors

See Tron errors for the shared envelope.

CodeMeaningWhen it happens
-32602Invalid paramsAn unexpected positional parameter is supplied.
-32601Method not foundThe method is outside the published catalog.
401UnauthorizedThe API key is missing or invalid.
429Rate limitedThe tron_read_rpc budget is exceeded.

Examples

const response = await fetch("https://triport.io/rpc/tron", {
  method: "POST",
  headers: { "x-token": process.env.TRIPORT_API_KEY, "Content-Type": "application/json" },
  body: JSON.stringify({ jsonrpc: "2.0", id: 1, method: "eth_syncing", params: [] }),
});
const { result } = await response.json();

Notes

  • false means the node did not report active synchronization; it does not independently prove that the node is at the newest network head.
  • Progress-object fields are deliberately not documented because the schema leaves them implementation-defined and the captured example is boolean.
  • Related: getnodeinfo exposes native node status.