Rob Thijssen
bbe29caafe
deploy / fetch (push) Successful in 17s
deploy / deploy-node (bob.hanzalova.internal, 0x134e73f06fa9bdb1dbfa909e149c563f5860ceb71a0e7307918f7033970edf59, benjy.hanzalova.internal, --public-addr /dns4/nh.thgttg.com/tcp/30333) (push) Successful in 31s
deploy / deploy-miner (1, benjy.hanzalova.internal, bob.hanzalova.internal) (push) Successful in 41s
deploy / deploy-metrics (push) Successful in 9s
Adds a Mining efficiency row: mining rounds started per minute, hashes per mining round, and active jobs over time. These are proxies, not the answer. Neither binary exports what the question actually needs -- quantus-node has no difficulty metric and no authored-block counter (substrate_proposer_block_constructed counts proposals constructed, not rounds won), and quantus-miner has no solutions-found counter. So authored-blocks-vs-expected-share cannot be plotted, and a panel implying otherwise would be worse than none. A text panel on the row states that plainly rather than leaving someone to infer a conclusion the data does not support. lair/quantus#1 tracks closing the gap -- a chain-query exporter counting blocks credited to the reward address is the cheapest route -- and the experiments that depend on it.