Skip to content

Network identity ​

Do not trust the name. Anyone can return a chain called EmpoorioChain. The network is the genesis hash.

Measured against https://rpc2.testnet.empooriochain.com (2026-11-20):

CallResult
chain_getBlockHash(0)0xe973931eb0041952249c6a5f6d66537ced5acfe7e1334c44b531ddbbffeae7aa
system_chainEmpoorioChain Public Testnet
system_chainTypeLive
specNameempoorio-chain
specVersion255 (rises without invalidating signatures)
transactionVersion12 (rises → signed extrinsics die)
eth_chainId0x7ea = 2026
SS582026, prefix emp / addresses vx…
TokenDRACMA, 18 decimals
Head (approx.)block 1,166,534, 2 peers, not syncing
bash
curl -s https://rpc2.testnet.empooriochain.com \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"chain_getBlockHash","params":[0]}'

Endpoints ​

TLSServes the chain
https://rpc2.testnet.empooriochain.comLet’s Encryptyes — HTTP JSON-RPC and wss://
rpc.testnet.empooriochain.comno (nginx CN=invalid, return 444)no

There is one public RPC. A cut on validator 2 leaves the chain producing blocks with no public door. Cleartext ports 9944 / 9946 are closed.

Explorer: empooscan.com.

Facts that waste weeks if unsaid ​

  1. SS58 prefix does not isolate networks. What stops a testnet signature from being valid elsewhere is genesis hash (native) and EIP-155 chain ID (EVM), not the number 2026 in SS58.
  2. transactionVersion breaks clients. specVersion does not. A runtime upgrade that only bumps spec keeps signatures valid.
  3. The live binary rejects SS58 2026 on any RPC that parses an address, including system_accountNextIndex. Use 42 or hex. Accounts and SS58.

Validators and finality ​

Two validators, both IONOS AS8560, Logroño. P2P ports are 8443 and 8447, not the Substrate default 30333.

GRANDPA requires 2/3. Losing one validator stops finality. Fault tolerance today is zero. That is the operating reality of this testnet, not a footnote.

Full constant table: Network constants.

English technical docs. Marketing lives at empooriochain.com.