Endpoints
| Type | URL | Use |
|---|---|---|
| RPC (HTTPS) | https://zenx.network/rpc | Recommended. Browser apps and wallets (HTTPS required by MetaMask). |
| RPC (direct) | http://194.31.55.222:8545 | CLI tools, servers, private infra (no TLS). |
| WebSocket | ws://194.31.55.222:8546 | Subscriptions: eth_subscribe (newHeads, logs). Not browser-usable over HTTPS pages. |
All endpoints are standard JSON-RPC 2.0, POST-only, returning JSON. Full method reference: API Documentation.
Quick start
Test the endpoint from any terminal:
curl -X POST https://zenx.network/rpc \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
Chain facts for config files:
| Key | Value |
|---|---|
| chainId | 88911 (0x15B4F) |
| network | zenx / "ZENX Smart Chain" |
| native currency | ZENX, 18 decimals |
| explorer | https://zenx.network/explorer/ |
| supports EIP-1559 | yes (London activated from genesis) |
MetaMask / wallets
RPC https://zenx.network/rpc · Chain ID 88911 · Symbol ZENX · Block explorer https://zenx.network/explorer/. Use the site's Connect Wallet for one-click add.
Node.js (web3.js)
new Web3('https://zenx.network/rpc') — works like any EVM RPC.
Hardhat / Foundry
Point the network at the HTTPS RPC and set chainId: 88911; gas price ~1 gwei.
MetaMask-add JSON (dApps)
Use wallet_addEthereumChain with the HTTPS rpcUrl above inside try/catch.
Public RPC rate-limiting plan
The public RPC is shared infrastructure. The following fair-use policy keeps the endpoint healthy for wallets and explorers while protecting it from accidental or abusive load. Enforcement is applied at the reverse proxy on /rpc.
| Dimension | Public default | Notes |
|---|---|---|
| Request rate (HTTPS) | 100 requests / 15 s per IP | Bursts above ~30 req/s are rate-limited with HTTP 429 |
| Response header | Retry-After on 429 | Clients should back off and retry |
| WebSocket connections | 5 concurrent / IP | For eth_subscribe users |
| Historical / archive reads | Allowed (archive node) | Large eth_getLogs windows are the #1 source of abuse; cap ~10k blocks per query |
| Payload size | ~1 MB per request | Batch carefully; split big batches |
Plan status. Limits above are the published policy. Rate limiting goes live on the public HTTPS endpoint in the same deployment as this page; the raw IP endpoint (
:8545) remains open for operators and private infrastructure. If you operate an indexer, relayer, or high-volume service, contact us for a dedicated allowance or a private node instead of hammering the shared endpoint.Fair-use best practices
- Prefer batch JSON-RPC calls over many single requests where the API supports it.
- Poll blocks, not transactions: subscribe to
newHeads(WS) or polleth_blockNumberevery ~2 s at most. - Bound
eth_getLogsranges (≤ ~10k blocks) and use address/topic filters. - Cache reads that don't change (chainId, contract metadata, token decimals).
- Honor HTTP 429 +
Retry-Afterwith exponential backoff.