867a71f514
All checks were successful
deploy / fetch (push) Successful in 16s
deploy / deploy-node (bob.hanzalova.internal, 0x134e73f06fa9bdb1dbfa909e149c563f5860ceb71a0e7307918f7033970edf59, benjy.hanzalova.internal quadbrat.hanzalova.internal, --public-addr /dns4/nh.thgttg.com/tcp/30333, --unsafe-rpc-external --rpc-methods safe --rpc-c… (push) Successful in 34s
deploy / deploy-miner (1, quadbrat.hanzalova.internal, bob.hanzalova.internal) (push) Successful in 40s
deploy / deploy-miner (1, benjy.hanzalova.internal, bob.hanzalova.internal) (push) Successful in 42s
deploy / deploy-metrics (push) Successful in 9s
The chain can only see miners that WIN blocks. A miner too small to take a block in any given window is invisible in the authorship leaderboard while still being connected and still burning electricity. Telemetry sees every node, so the two series together answer a question neither can alone: nodes flat while distinct authors falls means small miners are being out-competed, not quitting. Measured on the live feed: 32 nodes against 9-21 distinct authors, 229 aggregate CPU cores, 15 VMs, and five client versions in the wild -- half the network is still on 0.6.x/0.7.x/0.8.x, which is a fork risk at a runtime upgrade and worth knowing before 2026-09-09. python3-websockets is a SOFT dependency, packaged not pip: without it the exporter serves every chain metric and reports quantus_telemetry_up 0, so a missing package degrades rather than breaks. infra-setup.sh installs it and treats failure as non-fatal. The genesis hash is discovered from the node rather than configured -- one less value to get wrong when the chain changes for mainnet.