eth_getUncleByBlockNumberAndIndex — Elysium JSON-RPC
Return an uncle by block and index.
https://triport.io/rpc/elysium- Network
- Elysium mainnet (chain ID 99901)
- Scope
- elysium:rpc
- Auth
- X-API-Key: $TRIPORT_API_KEY
- Rate limit
- elysium_read_rpc - 5 / 10 / 25 / 40 / 40 RPS sustained (Free / Basic / Pro / Business / Enterprise; BE5, 2026-11-08); Limits
Endpoint and plans: Elysium RPC endpoint.
eth_getUncleByBlockNumberAndIndex — return an uncle by block and index. Elysium is an Arbitrum Orbit L2 (chain ID 99901) that pays gas in HYPE; the signature and response shape come from the Elysium OpenRPC contract.
Behaviour follows the standard EVM JSON-RPC semantics for this method.
Parameters
JSON-RPC params is a positional array.
blockNumberBlockTagrequiredlatest.indexQuantityrequiredResponse
Measured 2026-11-08 on Elysium mainnet; captured values in a reconstructed JSON-RPC envelope, not a captured Triport response.
On Elysium
The result on Elysium is null for any index. Because no block has uncles, there is no ommer header at position 0x0 or anywhere else; the capture for block 0x270775 returned null, which is the correct, successful answer and not an error.
Treat null as "nothing at this position". It is not a signal to retry and not a sign that the node is lagging. Code ported from Ethereum mainnet sometimes loops from index 0 until it sees null; on Elysium that loop ends immediately, which is harmless but costs one request per block.
If you are migrating an explorer, you can hide the uncles panel for chain ID 99901 instead of querying it. The reward model also differs from proof-of-work chains: there is no uncle reward to display.
Errors
See Elysium errors. Inspect the code and message together.
| Code | Meaning | Action |
|---|---|---|
| -32601 | Method unavailable | Check the documented method set. A method outside it is rejected earlier with HTTP 403 method_unknown. |
| -32602 | Invalid parameters | Correct the request. |
| -32005 | Request limit exceeded | Arrives with HTTP 429: back off and honor Retry-After; see Limits. |
| -32000 | Upstream unavailable | Retry reads with bounded backoff. |
HTTP 429 rate_limited | Plan RPS exceeded (plain HTTP error, not JSON-RPC) | Honor Retry-After; see Limits. |
Examples
const response = await fetch("https://triport.io/rpc/elysium", {
method: "POST",
headers: { "X-API-Key": process.env.TRIPORT_API_KEY, "Content-Type": "application/json" },
body: JSON.stringify({"jsonrpc":"2.0","id":1,"method":"eth_getUncleByBlockNumberAndIndex","params":["0x270775","0x0"]}),
});
const payload = await response.json();Notes
- The result is the view of the healthy node that answered; adjacent calls are not pinned to one node.
- For transaction submission, see eth_sendRawTransaction (live). The Triport contract excludes
net_listening,net_peerCount,txpool_*,debug_*andtrace_*: they are rejected with HTTP 403method_unknown; see unsupported methods.