Appearance
RPC surface
Only https://rpc2.testnet.empooriochain.com (and wss://) has a valid certificate. rpc.testnet.empooriochain.com does not serve the chain (nginx CN=invalid, return 444). Cleartext 9944 / 9946 are closed.
Identify the chain with chain_getBlockHash(0), not with system_chain.
0xe973931eb0041952249c6a5f6d66537ced5acfe7e1334c44b531ddbbffeae7aaMethod groups
Last inventory against the live node (2026-11-20): 163 methods. rpc_methods is the live list.
| Space | Count | Role |
|---|---|---|
eth_ | 45 | Frontier EVM |
state_ | 23 | Storage and metadata |
system_ | 20 | Node and network identity |
chain_ | 19 | Blocks and headers |
author_ | 9 | Submit extrinsics (key methods gated on public RPC) |
chainHead_ | 9 | Follow API v1 |
childstate_ | 7 | Child storage |
debug_ | 5 | EVM traces |
emp_ | 5 | Chain-specific |
chainSpec_, net_, offchain_ | 3 each | |
payment_, transaction_, transactionWatch_, web3_ | 2 each | payment_queryInfo is the fee quote |
account_, rpc_, subscribe_, unsubscribe_ | 1 each |
system_health on 2026-11-20: 2 peers, not syncing. system_syncState.currentBlock around 1,166,534.
SS58: you cannot even ask for a nonce with vx…
system_properties declares ss58Format: 2026. The deployed binary does not parse that format on any RPC that takes an address — emp_* and stock Substrate alike.
Same account, three encodings, system_accountNextIndex:
| Encoding | Result |
|---|---|
SS58 2026 (vx…) | Unknown SS58 address format 2026 |
| SS58 42 | nonce |
hex 0x… | nonce |
Without a nonce you cannot sign. A client that encodes 2026 because system_properties said so cannot transact.
Two fixes exist in source and neither is on the VPS:
| Where | Since | Covers |
|---|---|---|
node/src/main.rs set_default_ss58_version(2026) | 2026-09-14 | stock RPCs including system_accountNextIndex |
node/src/rpc/emp_rpc.rs a_ss58 | 2026-09-05 | the five emp_* |
Both live in the node binary. set_code does not carry them. Proof of deploy: system_accountNextIndex accepts a vx… address. Until then, use prefix 42 or hex.
The five emp_* methods
Defined in node/src/rpc/emp_rpc.rs. Same SS58 bug. Extra: prefix 0 (Polkadot) is accepted and the 32 bytes are reinterpreted as a local account.
| Address | Prefix | Live validators | New binary |
|---|---|---|---|
vx… | 2026 (this chain) | REJECTED | accepted |
5… | 42 (generic) | accepted | accepted |
12… | 0 (Polkadot) | ACCEPTED, returns a score | rejected as other network |
emp_getDomainOwner("aephoron") returns the owner in prefix 42 while storage gives prefix 2026. Same public key 0x40a65bf2…, two strings. String equality lies.
For integrators:
- Do not pass
vx…intoemp_*on this testnet. - Compare 32-byte public keys, never SS58 strings.
- An accepted address is not proof it belongs to this network. The five methods are read-only.
emp_getDomainOwner(name)
Name without .emp. target is decoded text. Storage holds raw bytes (0x6874747073 = "https").
emp_getTrackInfo(track_id: u32)
cid is not an IPFS CID. It is JSON embedded as a string; parse it again. bps are basis points (1000 = 10 %).
emp_getAiModelStatus(model_id: u32)
Owner, endpoint, active, version. A missing model is not a chain outage.
emp_getValidatorScore(account)
SS58 or hex. { "score": 0, "tier": "Bronze" } is an account with no history, not an error.
emp_getBlobData(blob_id)
Unknown id → null.
Unsafe methods
Public RPC runs in Safe mode. author_rotateKeys / author_insertKey are rejected there. Generate session keys on localhost with --rpc-methods unsafe. See Session keys.
CORS
The public RPC answers browser OPTIONS with access-control-allow-origin: *. The marketing hero reads it from the page. That is intentional.
Single public door
A cut on validator 2 (the only TLS RPC) leaves the chain producing blocks with no public door. Closing that is nginx server_name + Let’s Encrypt for rpc.testnet.empooriochain.com, not a runtime upgrade. See TLS and reverse proxy.
