Elysium chain ID, RPC URL and network config

Last updated: November 9, 2026

Elysium network identifiers

The chain ID is signed into every transaction (EIP-155); the network ID is what net_version reports. They are separate values that happen to match on most chains — see chain ID vs network ID and the chain ID glossary entry.

Elysium RPC URLs

Public-endpoint limits are as each operator publishes them, checked 23 September 2026.

Plans and per-category rate limits: pricing. Endpoint and plans: Elysium RPC endpoint; method reference: Elysium RPC API reference.

Add Elysium to MetaMask, viem, Hardhat or Foundry

wallet_addEthereumChain (EIP-3085) requires only chainId, as a hex string — 0x1863d, not 99901. The MetaMask block below also fills chainName, nativeCurrency (name, symbol, decimals) and rpcUrls, which a wallet uses to display and reach the network. A wallet cannot send the x-token header, so rpcUrls holds the keyed URL with your API key in the path — paste your key below; the placeholder URL answers 401 until you do.

{
  "method": "wallet_addEthereumChain",
  "params": [{
    "chainId": "0x1863d",
    "chainName": "Elysium",
    "nativeCurrency": { "name": "HYPE", "symbol": "HYPE", "decimals": 18 },
    "rpcUrls": ["https://triport.io/r/<API_KEY>/elysium"]
  }]
}

import { createPublicClient, defineChain, http } from "viem";

export const elysium = defineChain({
  id: 99901,
  name: "Elysium",
  nativeCurrency: { name: "HYPE", symbol: "HYPE", decimals: 18 },
  rpcUrls: { default: { http: ["https://triport.io/r/<API_KEY>/elysium"], webSocket: ["wss://triport.io/ws/elysium/<API_KEY>"] } },
});

export const client = createPublicClient({ chain: elysium, transport: http() });

import { JsonRpcProvider, Network } from "ethers";

const network = Network.from({ name: "elysium", chainId: 99901 });
export const provider = new JsonRpcProvider("https://triport.io/r/<API_KEY>/elysium", network, { staticNetwork: network });

// hardhat.config.ts
export default {
  networks: {
    elysium: { url: "https://triport.io/r/<API_KEY>/elysium", chainId: 99901 },
  },
};

# foundry.toml
[rpc_endpoints]
elysium = "https://triport.io/r/<API_KEY>/elysium"

import { createConfig, http } from "wagmi";
import { elysium } from "./elysium-chain";

export const config = createConfig({
  chains: [elysium],
  transports: { [elysium.id]: http("https://triport.io/r/<API_KEY>/elysium") },
});

curl https://triport.io/rpc/elysium \
  -H "x-token: <API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Keys in URLs vs headers

A keyed URL is the same credential as a header, in a less private place: it lands in shell history, CI logs and screenshots. Use it only where a header is impossible (wallets, hardhat.config, foundry.toml), send x-token from server code, and rotate a key that leaked.

Elysium testnets

Elysium testnet: Kinetiq's public testnet of Elysium. It settles on HyperEVM testnet (chain ID 998) and runs the same stack as mainnet; only endpoints and deployed addresses differ, per Kinetiq's docs. Triport serves mainnet only. These values are for switching your config; they are not Triport endpoints.

Verify you are on Elysium mainnet

Call eth_chainId first. It must return 0x1863d — a client whose configured chain ID disagrees with the reply refuses to connect, which explains most failures when adding a network by hand.

curl https://triport.io/rpc/elysium \
  -H "x-token: <API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Connected to a testnet by mistake? The same call answers 0x185d9 on Elysium testnet.

Sources: the chain's own documentation and the CAIP-2 namespace specs cited in the tables above; EVM chain IDs come from Triport's chain registry and match them.