Overview: RPC requests are an application's gateway to EmpoorioChain. The public testnet exposes two nodes over HTTPS and WebSocket; both also serve the Ethereum JSON-RPC (eth_*) of the Frontier EVM on chain id 2026 (0x7ea). From a user's perspective poor RPC performance is indistinguishable from poor chain performance, so an application that goes public should run its own node.
Development: Run a local node during development. The EmpoorioChain node binary starts a single-authority dev chain with --dev; use it for unoptimized early iterations and for tests that would otherwise hit the public rate limit. Once the application is stable, point it at the public testnet.
Like all optimization, with RPC less is more. Avoid repeated calls for the same data; subscribe (chain_subscribeFinalizedHeads, state_subscribeStorage) instead of polling; cache what you can. "Backend-less dApps" are a myth — a client that calls the public RPC directly is pummelling shared infrastructure, and the public nodes ban the source IP for one hour above 10 requests per second.
The only hosts that exist. Anything else you may find in older documentation — rpc.empooriochain.org, ws., api., explorer. — never resolved and must not be cited.
Testnet
https://rpc.testnet.empooriochain.org — node 1, HTTP JSON-RPC and wss:// on the same host (217.160.88.153)https://rpc2.testnet.empooriochain.org — node 2 (212.227.108.41)Both serve Substrate JSON-RPC (chain_*, state_*, author_*, system_*) and Ethereum JSON-RPC (eth_chainId → 0x7ea, eth_blockNumber, eth_gasPrice → 1 gwei since runtime 220). Rate limit: 10 requests per second per IP, one-hour ban. No SLA.
Mainnet
There is no mainnet. Any configuration that points to one is inventing it.
Explorer
https://empooscan.com — EmpooScan. Its indexer is being repaired to decode the runtime 220 metadata; block and extrinsic lookups by hash work through the RPC directly.For anything beyond a demo, run a node. The binary is built from the EmpoorioChain repository; a full node needs the chain spec of the live genesis (0xe973931e…eae7aa) and the bootnodes on the non-default p2p ports (8443 on node 1, 8447 on node 2). Compile with CARGO_INCREMENTAL=0: the target directory reaches 50 GB and a full disk disguises itself as a compilation error. Validators are not open to external operators yet; that is a mainnet-gate item.
20262026 (0x7ea)Chain ids 1337, 9911 and 27777 that circulated in older material do not belong to this chain; a signature made for them is not valid here.
The extrinsic envelope carries two custom signed extensions: CheckPqcPolicy (2 bytes, first in SignedExtra) and CheckDormantAccount (zero-size). Generic Substrate libraries that build the envelope from the live metadata handle them; libraries that hardcode the envelope (an older substrate-interface did) produce signatures the node rejects. Regenerate SDK metadata after every runtime upgrade — the spec version lives inside it.