JSON RPC API

Xone Chain is an L1 public chain based on Ethereum, fully compatible with Ethereum JSON-RPC API, and supports interaction with mainstream libraries such as Web3.js and Ethers.js. Developers can use JSON-RPC to access Xone Chain for account management, transaction sending, smart contract calling, and other operations.

Endpoint

Xone Chain provides multiple RPC endpoints for developers to connect to the main network or test network. All requests use the POST method.

Quick start

Query the latest block (cURL)

curl -X POST https://rpc.xone.org \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Connect with Ethers v6

import { JsonRpcProvider } from "ethers";
 
const provider = new JsonRpcProvider("https://rpc.xone.org");
const block = await provider.getBlockNumber();
console.log(`Current block: ${block}`);

Connect with Web3.js v1

import Web3 from "web3";
 
const web3 = new Web3("wss://rpc-wss.xone.org");
const accounts = await web3.eth.getAccounts();

Tip: For production applications we recommend using a WebSocket endpoint for real‑time subscriptions (eth_subscribe).

Rate limits & best practices

• Public quota: 10 000 requests per IP per day (soft limit). If you need more throughput, consider hosting your own node or applying for an increased quota.
• Use batching: Group multiple calls in a single request to reduce latency (eth_call & eth_estimateGas are good candidates).
• Prefer WebSocket for subscriptions: Event‑driven apps (price feeds, dashboards) should use eth_subscribe over a WebSocket endpoint instead of long‑polling eth_getLogs.
• Handle retries & back‑off: Transient network errors can occur; implement exponential back‑off and idempotent logic on retries.

Common error codes

Troubleshooting

We ❤️ Feedback!

If you have any feedback or questions about this documentation, let us know We'd love to hear from you!