Verify who can disable an Avalanche L1 validator and who receives its balance
An L1 validator registration carries separate P-Chain ownership conditions for emergency disablement and for its remaining AVAX. These roles can be controlled by different keys.
Inspect the validation record before an incident
Use /ext/bc/P and the validation ID, which identifies a particular registration. Inspect the disable owner and remaining balance owner including their thresholds and full address lists. Compare both against the signed registration or conversion data and your custody inventory.
{"jsonrpc":"2.0","id":1,"method":"platform.getL1Validator","params":{"validationID":"VALIDATION_ID"}}
Simulate role separation on paper
A two-of-three operations group may be allowed to disable while a separate treasury address receives residual AVAX. Possessing the operations threshold therefore does not establish entitlement to treasury funds. Preserve the old validation ID when tracking the refund UTXO, and distinguish a disable action from manager-driven removal by zero weight.