POST
/
evm
eth_syncing
curl --request POST \
  --url https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/evm \
  --header 'Content-Type: application/json' \
  --data '{
  "jsonrpc": "2.0",
  "method": "eth_syncing",
  "params": [],
  "id": 1
}'
{
"jsonrpc": "2.0",
"id": 1,
"result": false
}
Returns the synchronization status of the node. On Hyperliquid, this method always returns false as nodes are always considered synchronized.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

Parameters

This method takes no parameters.

Returns

Returns the synchronization status. On Hyperliquid, this is always false, indicating the node is fully synchronized.
On Hyperliquid, this method always returns false. The network architecture ensures nodes are always synchronized, so there’s no syncing state.

cURL example

curl -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}' \
  https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/evm
Example response:
{"jsonrpc":"2.0","id":1,"result":false}

Use cases

  • EVM compatibility — Maintain compatibility with standard Ethereum JSON-RPC interface
  • Application initialization — Check node readiness (always ready on Hyperliquid)
  • Health monitoring — Verify node status in monitoring systems
  • Cross-chain compatibility — Support applications that check sync status across different networks

Body

application/json
jsonrpc
enum<string>
default:2.0
required

JSON-RPC version

Available options:
2.0
method
enum<string>
default:eth_syncing
required

The RPC method name

Available options:
eth_syncing
params
any[]
required

No parameters required

id
integer
default:1
required

Request identifier

Response

200 - application/json

Successful response with synchronization status

jsonrpc
string

JSON-RPC version

id
integer

Request identifier

result

false if the node is fully synchronized