RPC Infrastructure: Two Public Nodes, No Third-Party Providers, Run Your Own

What exists


`rpc.testnet.empooriochain.org`	HTTPS + WSS, node 1 (also validator 1), nginx → 9944, own TLS
`rpc2.testnet.empooriochain.org`	HTTPS + WSS, node 2 (also validator 2)
Rate limit	~10 req/s per IP, one-hour ban (fail2ban)
Namespaces	Substrate (`chain_`, `state_`, `author_`, `system_`), Ethereum (`eth_`, `net_`, `web3_`), custom `emp_` (unpublished)
Operator	Empoorio, both nodes, one hosting provider

That is the entire RPC tier. It doubles as the validators' own RPC, which is why it is rate-limited so bluntly: a misbehaving client can degrade consensus.

What does not exist

Decentralised RPC networks. None supports EmpoorioChain. The previous version of this page announced such an integration for another chain.
Commercial RPC providers. None. An older /rpc page on the official site listed sixteen providers from another ecosystem; it is being rewritten.
A separate RPC tier distinct from validators.
Archive nodes publicly available.
Uptime measurement over 30 days (a mainnet-gate item; not yet published).

Run your own

A full node (not a validator) needs no node key ceremony, no bond and no stake:

./scripts/restaurar_sdk_vendorizado.sh
cargo build --release -p empoorio-node
./target/release/empoorio-node --chain chainspec.raw.json --base-path /var/lib/empooriochain \
  --name my-rpc --rpc-external --rpc-cors all --rpc-methods safe --port 30333

Use the repository's chainspec.raw.json — never build-spec, which creates a new chain. Confirm header-hash: 0xe973…e7aa and peers. Sync from genesis takes minutes at the testnet's current size. Put nginx and TLS in front if it is public; keep --rpc-methods safe unless you trust every caller.

An indexer, a CI pipeline, a load test or a production dApp should each have its own node. The public pair is for wallets and casual development.

What a healthy tier looks like

The decentralization and mainnet gates imply it: RPC nodes separate from validators; more than one operator; public uptime above 99.5 % over 30 days; archive nodes for explorers; and — eventually — third-party providers, which arrive when there is a mainnet worth serving. Each is listed as not done.

`emp_*`

The custom namespace (emp_getAiModelStatus, emp_getBlobData, emp_getDomainOwner, emp_getTrackInfo, emp_getValidatorScore, …) is exposed and unpublished. Treat it as unstable until the reference exists.

Based on RED.json (hosts), VALIDATOR_IN_30_MINUTES.md, MAINNET_GATE.md Gate 2 and the RPC rate-limit finding.