Appearance
Validators
Today: two validators. GRANDPA needs 2/3, so losing one stops finality. Aura and GRANDPA cap authorities at 32 (MaxAuthorities). Staking allows 100 (MaxValidators). Bonding extra validators does not pay if staking economics are not running.
Both machines sit in IONOS AS8560, Logroño. That is 100 % infrastructure concentration.
What a validator is taking on
Keys, session keys, disk, and the social cost of missing a slot on a two-node set. Read docs/nodos/01_LO_QUE_ARRIESGA_UN_VALIDADOR.md in the repository before generating anything. This page does not walk a production bond on a chain that still has two authorities and unpaid extra bonds.
Testnet bond figure in that guide: 50,000 DRACMA. Genesis endowment of ordinary accounts was 10,000. An external operator cannot bond from genesis dust alone.
Public door versus authoring
Authoring and GRANDPA can keep producing while the public RPC is down. Since 2026-10-27 there is one public RPC (rpc2). Validator 1 has no HTTP/WSS name with a valid certificate. A cut on validator 2 hides the chain from the outside without stopping block production.
Closing that is nginx server_name + Let’s Encrypt for rpc.testnet.empooriochain.com, not a runtime upgrade. See TLS.
Binary versus runtime
The live validators run a node binary from before 2026-09-05. That is why SS58 2026 is rejected on RPC. Shipping specVersion 255 did not fix it. A validator operator who rebuilds from current source gets the SS58 fix locally; the public RPC stays broken until both VPS binaries are replaced.
Session keys
Aura (sr25519) + GRANDPA (ed25519) = 64 bytes public. Rotate on localhost with --rpc-methods unsafe. Register with session.setKeys. They enter next session (2,400 blocks, 4 hours). Step-by-step: Session keys.
