Live Nodes

Public Exfer JSON-RPC endpoints surfaced by this site. Health is polled every 30 seconds from a background task running on the proxy server.

Use these endpoints for read-only testing and exploration. For production integrations (exchanges, wallets, explorers, settlement services), run your own node — see Run Your Own Node.

How health is determined

Every 30 seconds the proxy issues a get_block_height call to each listed node with a 5-second timeout. A node is reported as online if it returns a well-formed JSON-RPC result; otherwise the error field on the card contains the failure reason (HTTP status, timeout, decode failure, etc.).

The height you see on each card is the tip reported at the last probe. A node falling more than a handful of blocks behind the others is likely syncing slowly, partitioned, or otherwise unhealthy — pick a different one for your tests.

Why a CORS proxy

The Exfer node's RPC server is plain JSON-RPC and does not emit Access-Control-Allow-Origin headers, so browsers refuse direct fetch() calls from a third-party origin. This site exposes a thin proxy at POST /rpc/<node_id> that forwards your request body unchanged to the chosen upstream node and returns the JSON-RPC response with permissive CORS headers added. The proxy does not parse, cache, or rewrite the payload; it caps body size at 2 MB and times out at 15 s.

For terminal use, you can call the upstream nodes directly with curl — the CORS restriction does not apply outside the browser.