EmpoorioChain

Appearance

API reference ​

EmpoorioChain nodes expose a Substrate-compatible JSON-RPC API over HTTP and WebSocket.

Public testnet ​

No RPC/WebSocket URL is published here yet — testnet genesis has not been relaunched and no single, stable, publicly-peered endpoint is confirmed live. See Public testnet notes for status. Once published, use the announced URL in SDKs and tools — do not embed private validator or internal IPs, and do not reuse an old or third-party endpoint.

Common JSON-RPC methods ​

These are standard Substrate JSON-RPC methods — once you have a verified endpoint, they work the same way against it:

Chain metadata ​

bash
curl -s -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"system_chain","params":[]}' \
  <verified-rpc-endpoint>
bash
curl -s -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"system_properties","params":[]}' \
  <verified-rpc-endpoint>

system_properties returns token symbol and decimals (DMS, 18 decimals per runtime source).

Latest block height ​

bash
curl -s -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"chain_getHeader","params":[]}' \
  <verified-rpc-endpoint>

SDK-first integration ​

Most applications should use:

  • TypeScript: @empoorio/sdk (Polkadot.js-based)
  • Rust: empoorio-sdk + subxt
  • CLI: emp for operator and protocol commands

The SDKs wrap RPC calls, signing, and subscriptions — prefer them over raw RPC when possible.

EVM (Frontier) ​

Solidity tooling can target the Frontier EVM layer. Testnet EVM chain ID: 27777 in current runtime source — this is provisional; other project docs have cited different numbers for the same network at different times, so verify with a live eth_chainId call before deploying.

Local EVM JSON-RPC in dev setups may use port 8545 on your machine — that is not a public Empoorio endpoint.

REST / EmpProtocols ​

The repository describes additional REST-style protocol surfaces in docs/03_DEVELOPMENT/API_AND_SDK_REFERENCE.md. Only use base URLs that are officially announced for your environment — this marketing site does not publish a testnet RPC/WebSocket base URL until one is confirmed live (see above).