Elysium mainnet is in the docs, for Premium and Enterprise
We serve Elysium mainnet on rpc.ankr.com/elysium to Premium and Enterprise users, over HTTPS and WSS. The chain is now in the chain list, with its own API reference.
Docs
- Elysium is in the chain list. Elysium, the Kinetiq Layer 2 for Hyperliquid that settles to HyperEVM, carries the HTTPS and WSS endpoints, the MetaMask settings (chain ID
99901,HYPE), and the supported and unsupported method lists. The API reference documents 31 methods, includingdebug_traceBlockByHash,debug_traceBlockByNumber,debug_traceBlock,debug_traceTransactionanddebug_traceCall. - Every example on those pages except the
eth_sendRawTransactionplaceholder was run against mainnet, and the response shown is the one it returned.
Worth checking on your side
- Premium and Enterprise only. The chain is not on the Freemium or Public plans. A request without an API key returns
-32052. - WSS. Connect to
wss://rpc.ankr.com/elysium/ws/YOUR_ANKR_API_KEY;eth_subscribeworks, for examplenewHeads. See the WebSocket limits. - Blocks arrive about every 100 ms. The
eth_getLogswindow is capped at 10,000 blocks per call, which on this chain is under 17 minutes of history; a larger range returns-32062. Filter byaddressortopics: an unfiltered 10,000-block range on this chain returns tens of megabytes of logs. Page through long ranges, or subscribe tonewHeadsover WSS instead of polling. - There is no
trace_*,arbtrace_*orarb_*. The node exposes thedebug,eth,net,rpcandweb3modules. Use thedebug_trace*methods withcallTracerfor call traces. - Filter methods are blocked.
eth_newFilter,eth_newBlockFilter,eth_newPendingTransactionFilter,eth_getFilterChanges,eth_getFilterLogsandeth_uninstallFilterreturn-32075. Useeth_getLogs, oreth_subscribeover WSS. - No RPC method limits, error codes, batch caps or range caps changed on any other chain.