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
A concern raised by @jaekwon, after the implementation of minimum self-delegation, is that it is advantageous to allow new (non-genesis) validators to be created at mainnet launch under the context of disabled transfers. Such reasons include comprised operator keys or validators who did not participate in GoS or the fundraiser that wish to be validators at launch.
Since transfers are disabled, we desire the ability to create new accounts (validator operators) with some small amount of uatoms (to meet their min self-delegation). Various solutions have been discussed offline and the main candidate proposal seems to be to allow MultiSend transfers where 90% of the tokens are burned. Further discussion should occur here.
Thanks for the summary. Given a 90% burn fraction, crippled transfers being used for other purposes seems unlikely, although we could further opt to only allow such transfers if the destination account is empty.
Summary
A concern raised by @jaekwon, after the implementation of minimum self-delegation, is that it is advantageous to allow new (non-genesis) validators to be created at mainnet launch under the context of disabled transfers. Such reasons include comprised operator keys or validators who did not participate in GoS or the fundraiser that wish to be validators at launch.
Since transfers are disabled, we desire the ability to create new accounts (validator operators) with some small amount of uatoms (to meet their min self-delegation). Various solutions have been discussed offline and the main candidate proposal seems to be to allow MultiSend transfers where 90% of the tokens are burned. Further discussion should occur here.
/cc @cosmos/cosmossdk @ebuchman @zmanian @jaekwon
For Admin Use
The text was updated successfully, but these errors were encountered: