EmpoorioChain

Appearance

Public testnet & nodes ​

This page lists public network information for developers. Validator setup, bootnodes, and production runbooks live in the EmpoorioChain operator documentation in the repository — not here.

Network status ​

NetworkStatusNotes
TestnetLiveUse the endpoints below
MainnetPlanned / inactiveNo public mainnet RPC published in README

Published testnet endpoints ​

From projects/EmpoorioChain/README.md:

RPC (HTTPS):  https://testnet.empooriochain.org
WebSocket:    wss://testnet.empooriochain.org
Explorer:     https://testnet.explorer.empooriochain.org
Chain name:   empoorio-testnet-1

Local development defaults ​

When you run a node on your own machine:

RPC:       http://localhost:9933
WebSocket: ws://localhost:9944
Explorer:  http://localhost:3000  (if you run the local explorer stack)

These are local ports — they are not Empoorio public infrastructure.

Consensus (summary) ​

Production testnet nodes use Aura + GRANDPA with BEEFY support, per docs/CAPABILITY_STATUS.md.

Experimental consensus research (e.g. HotStuff/Bullshark) is not described as production-ready on this site.

What developers should do ​

  • Connect SDKs and wallets to testnet URLs only.
  • Inspect transactions in the public explorer.
  • Do not hard-code private IPs, unpublished bootnodes, or validator keys in apps or docs.
  • Treat mainnet as unavailable until an official launch announcement with audited releases.

What belongs in operator docs ​

The following are intentionally out of scope for this marketing site:

  • Validator keystore paths and session keys
  • Private bootnode peer IDs and internal IPs
  • Slashing runbooks and on-call procedures
  • Unreleased mainnet genesis parameters

See docs/04_DEPLOYMENT_AND_INFRA/NODE_OPERATOR_GUIDE.md in the EmpoorioChain repository if you operate infrastructure.