Rob Thijssen
ca94e3a6c0
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) (push) Successful in 31s
deploy / deploy-miner (1, benjy.hanzalova.internal, bob.hanzalova.internal) (push) Successful in 41s
deploy / deploy-miner (1, quadbrat.hanzalova.internal, bob.hanzalova.internal) (push) Successful in 40s
deploy / deploy-metrics (push) Successful in 8s
quantus-node has no balance subcommand, and the faucet_getAccountInfo RPC that MINING.md documents is absent from this build -- rpc_methods returns only account_nextIndex and system_accountNextIndex. So the exporter builds the System.Account storage key itself: twox128(System) ++ twox128(Account) ++ blake2_128_concat(account). XXH64 is inlined because python3-xxhash is not installed on the node hosts and this exporter stays dependency-free. It asserts the two universally-known prefixes at import, so a broken implementation fails loudly instead of silently querying the wrong key. The reward address is Poseidon2(inner_hash). Rather than reimplement Poseidon2 over Goldilocks, the deploy lifts it from the node's own startup log; empty is tolerated and the exporter simply omits balance metrics, which is what a genuinely first deploy will see. Verified live: 158.153404340522 PLK, 12 decimals, zero RPC errors. Also: str.replace fails silently on a missing anchor, which is how the first attempt shipped an exporter calling a method that was never inserted. Edits to this file now assert their anchors.