expose per-reason slash point breakdown on node queries
Summary
Adds a slash_points_by_reason field to the /thorchain/node/{addr} and /thorchain/nodes query responses. Operators can now see why their node accumulated slash points - failed observation vs. failed keysign vs. missed block signing, etc. - instead of just an opaque total.
Example response shape:
{
"node_address": "thor1...",
"slash_points": 17,
"slash_points_by_reason": [
{ "reason": "failed_keysign", "points": 4 },
{ "reason": "failed_observe_txin", "points": 8 },
{ "reason": "miss_block_sign", "points": 5 }
]
}Design
The aggregate slash_points counter is untouched all the consensus paths (e.g. payNodeAccountBondAward, findBadActors, markActor...) continue to read the same value, with no behavioural change.
A second store under prefix slashr/{addr}/{reason} rides alongside,
maintained in lockstep by the keeper. The reason is pulled from
CtxMetricLabels — every existing slash call site already sets a
reason label there for telemetry, so no call sites needed to change.
This is Consensus-breaking — introduces a new KV store prefix (slashr/). So needs gating behind a chain upgrade. No explicit migration needed: existing aggregate counters keep working, and the per-reason breakdown populates organically as nodes accrue slash points after the upgrade. Any residual pre-upgrade aggregate drains at the next churn via the existing ResetNodeAccountSlashPoints call.