Allow unwhitelisting of zero-bond providers while Active
There has been interest expressed in this Issue's topic, most recently in this Discord conversation:
Hope this get fixed soon, kind of sad to submit a leave and churn out, make BP lose rewards, just to change whitelist list
🙂
I have previously been hesitant about the idea as a lot of handler_unbond.go
(the usual way of unwhitelisting bond providers with an Unbond memo)
is rejecting an unbond message for many possible reasons and keeping it away from the refundBond
call.
Trying to do a bond-provider-removal-specific exception to these checks makes me wary.
However, bond memos are allowed while Active, and they also have a field for bond provider address;
a bond memo is how a bond provider is added in the first place.
(Granted, unlike unbond memos, they require a non-zero RUNE amount to pass ValidateBasic
.)
My current suggestion for this then, if desired, is that the bond memo whitelisting be used as a toggle:
one whitelist message whitelists a provider, and another (if still bondless) unwhitelists it.
Specifically: !3209
'Toggle zero-bond BondProvider whitelisting with Bond memo'.
2024-06-27 update:
Noting here the similarly-themed #2002 (closed)
'Allow bond provider removal of active/inactive nodes with < 0.02 rune'.