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
| Network | Status | Notes |
|---|---|---|
| Testnet | Pre-launch — connection details not published | Genesis relaunch and operational hardening in progress |
| Mainnet | Planned / inactive | No public mainnet RPC published |
Connection details
We are not publishing a specific RPC, WebSocket, explorer, or faucet URL as safe to use today. Testnet genesis has not been relaunched, so any address published before that work lands could point developers at an insecure or unstable network.
Once the network is confirmed live on a single, relaunched genesis with a stable public RPC, we will publish:
- RPC (HTTPS) and WebSocket endpoint
- Public block explorer URL
- Faucet URL for test DMS
- Confirmed chain name, SS58 format, and EVM chain ID
Until then, follow the EmpoorioChain repository release notes for the launch announcement, or build and run a node locally against the published source.
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)
Testnet nodes run 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
- Do not hard-code any RPC/WS/explorer URL from third-party docs, old release notes, or unofficial sources — several candidate endpoints found across project documentation resolve to the wrong chain or don't resolve at all.
- Wait for an official "testnet live" announcement referencing a relaunched genesis before connecting production tooling.
- 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.