eth_syncing
eth_syncing JSON-RPC reference for MegaETH.
Summary
Returns whether the node is currently syncing.
The public MegaETH endpoint supports this method. The standard, node, and gateway layers below identify behavior that differs from a generic Ethereum endpoint.
Parameters
None.
Result
false when the node is fully synced. When syncing, a SyncProgress object:
startingBlockQuantitySync start point.
currentBlockQuantityCurrent progress.
highestBlockQuantityTarget block.
Comparison with Ethereum Standard JSON-RPC
Ethereum Standard
The canonical Ethereum method uses the parameter and result contract documented above, including the stated null, false, or zero-value semantics where applicable.
MegaETH Node Behavior
The node returns false when caught up and a progress object while synchronizing. This reports node synchronization, not L1 finality.
MegaETH Public Gateway
The gateway forwards this dynamic status without response caching in the simple read tier.
Errors
The | Scope | column distinguishes method failures from gateway policy errors.
No method-specific errors were observed.
-32005
Transport/policy
Rate limit exceeded
The caller exceeds the public gateway's simple read budget.
-32099
Transport/policy
Payload too large
The request body exceeds the 128 KiB public endpoint limit.
See also Error Codes.
Examples
Endpoint: https://mainnet.megaeth.com/rpc
Capture date: July 24, 2026
Outcome: success
Sources
Spec:
[email protected]:ethereum/execution-apis.git @ d24f58b56dcd16ab0f0c70ec609bcc1c42750b51: src/eth/client.yamlCode:
[email protected]:megaeth-labs/mega-reth.git @ ab60376631228edab3a6df180f295280bad26e93: crates/rpc/rpc/src/eth/core.rsCode:
[email protected]:megaeth-labs/mega-rpc.git @ 06aa35aa95d569c227cc25d2aa12834eb0458aa0: workers/src/spec/methods.tsProbe: MegaETH Mainnet public endpoint, July 24, 2026
Last updated