eth_syncing — Base JSON-RPC
Return node sync progress or false.
- Scope
- base:rpc
Endpoint and plans: Base RPC endpoint.
Parameter limits
| JSON path | Frozen limit | Source |
|---|---|---|
| — | unknown | No numeric parameter ceiling is frozen; enforce the declared schema shape and deny an unknown oversized/range profile. |
Historical block retrieval is not an archive-state guarantee. Selectors must be preserved; do not substitute pending, safe, or finalized with latest.
Rate limits and tier
These are enforced product-policy values, not measured upstream capacity or an SLA. Enterprise is finite, never physical “unlimited” capacity.
| Tier | Limit / access | Category |
|---|---|---|
| Free | 10 RPS sustained · up to 20 burst | base_read_rpc |
| Basic | 20 RPS sustained · up to 40 burst | base_read_rpc |
| Pro | 100 RPS sustained · up to 200 burst | base_read_rpc |
| Business | 250 RPS sustained · up to 500 burst | base_read_rpc |
| Enterprise | 250 RPS sustained · up to 500 burst | base_read_rpc |
See Base limits and Burst capacity. The included buffer refills at sustained RPS; there is no quota on the number of bursts.
Errors
| Code | Meaning here | Client action |
|---|---|---|
-32602 | Parameters fail the declared schema or upstream parser. | Fix the positional parameters; parser acceptance is not execution success. |
Tier and budget rejections are not JSON-RPC errors: the gate decides them before the request reaches the RPC layer and answers with a plain HTTP envelope — 403 tier_insufficient (with an X-Required-Tier header) or 429 rate_limited (honor Retry-After). Both are enforced product policy, not measured capacity or an SLA.
Authentication/transport failures use the shared client error envelope. See Base errors.
Evidence
- Fixture kind:
positive_fixture. - Fixture source:
infra-4-sety/integration-base/research/R04/measurement/FIXTURES.jsonat/fixtures/2. - Fixture SHA-256:
eaef6dd7f176296a03d46f351e0378a8ea073e39d53f9ab49e256f69048b3e66. - Fixture registry:
infra-4-sety/integration-base/research/R04/measurement/FIXTURES.json. - Semantic assertion: false or syncing progress quantities; not freshness
- Source UTC:
2026-09-08T13:27:40.057Z. - Evidence boundary: only the frozen fixture assertion is reusable; it is not blanket provider or deployment evidence.
Limitations
- Availability is the frozen baseline, not deployed readiness. documented is the contract floor; evidence_kind retains unknown/source_summary.