You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Operator identity keys: script payouts and the returning operator's BLS key #5840
Two follow-ups from #5775 (operator payouts follow Dash Core at protocol 15), both deferred out of that PR.
1. Script (P2SH) payouts become withdrawal keys nobody can sign
Platform turns owner and operator payouts into identity TRANSFER keys of type ECDSA_HASH160. For a P2SH payout the 20 bytes hash a redeem script, so the key can never sign. On the owner side this has been so since protocol 1; from protocol 15 the operator side follows Core's payout too, so an operator who switches to a P2SH payout loses a working key. Mainnet had 0 P2SH owner or operator payouts on 2026-11-06.
Needs dashpay/rust-dashcore#1385 (keep the payout destination type), then a protocol version that refuses or handles script payouts for both sides. Planned with the V24 payout work in 5.2.
2. A returning operator identity's BLS key stays disabled
update_operator_identity (generations 0 and 1) disables the operator identity's BLS key when the masternode moves to another operator key, and never re-enables it when it switches back. After A -> B -> A the current operator's BLS key is disabled, so a document key reference to it is refused (validate_referenced_identity_key_v1 rejects disabled keys). Re-enable the BLS key matching the returning operator key in the next generation, with an A -> B -> A test that also references the key from a document. The protocol 15 upgrade block reads this state as it is before activation, so changing later generations does not affect it.
Activity