Interesting to see the original guide request by @timcliff, this could have large implications on the Steem blockchain.
Overall your coverage of the topic is well detailed.
Appreciate you making edits to include alternative approach using beempy, makes the tutorial more elaborate.
Good use of screenshots and output results. Gists are quite helpful too! Few additional comments there would have been more helpful.
Also loved your additional thoughts on the whole concept overall.
Good luck winning the bounty :)
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
I really wanted to write pretty much this exact tutorial for a few months, but sadly I couldn't motivate myself to tinker around with that stuff. Sadly school is too demanding this year, and if I technically have free time (like right now for example), I either want to do nothing, or have other more important things to do :(((
But looking at your post, I know that it's better than my post would've been. For sure ;-)
Let's hope I can finally get myself to write that post about me taking away those delegations D:
haha, I know that state, I find myself in that position often enough as well :) The contest was a good "kick" to actually give it a try. Looking forward to your delegation removal post! I noticed your recent PR in the irredeemables list and you had plenty of them in the past - make the post, some rewards for your work would be well deserved ;)
I basically did exactly this but was too slow about it, so I'm pretty sure it works.
The first part can be done much, much more easily with beempy's allow command.
allow -a targetaccount --permission active --weight 10 signingaccount
and then when you get to the last one add --threshold 40 after the weight. (Don't do it before or you won't be able to add new ones without the owner key or building a multisig transaction to do it.)
(Don't do it before or you won't be able to add new ones without the owner key or building a multisig transaction to do it.)
For changing the active authority, this actually doesn't matter since you need the owner key for anyway. You can't chance the active authority with an active key. It doesn't matter if there is an intermediate situation where none of the active keys can reach the active threshold.
edit: You are right, it is possible to change the active auth with active keys - using the owner key in the first place is an easy workaround.
It makes a difference though, if the owner authority is changed. But in that case it's probably better to use a script like mine and set them all at once unless you're OK with waiting one hour after each change.
Thank you so much for participating the Partiko Delegation Plan Round 1! We really appreciate your support! As part of the delegation benefits, we just gave you a 3.00% upvote! Together, let’s change the world!
Even with a multi-sig active authority, transfers can still be done with the owner authority (currently requiring only one sig with the example account).
However, the exact same concept can be applied to the owner authority as well. This has to be done carefully, since a mistake there could render the account unusable and the funds locked.
In looking for an easy way to get my test account usable again, I discovered that a master password reset will automatically change the weight of all that account's native keys to the Threshold weight, presumably including the owner key, though I didn't test for it. I don't know that there's any way to prevent that.
I would presume account recovery behaves similarly.
The account recovery on its own only affects the owner authority, all other authorities are not touched. In the Request_account_recovery operation, you can specify how the new authority should look like, including any account_auths, key_auths, weights and the threshold - see for example here. Changing any lower-priviledged keys is then possible from the new owner authority.
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your UA account score is currently 5.006 which ranks you at #1086 across all Steem accounts.
Your rank has improved 1 places in the last three days (old rank 1087).
In our last Algorithmic Curation Round, consisting of 207 contributions, your post is ranked at #8.
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).
Thank you for your contribution.
Good luck winning the bounty :)
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
Thanks for your review, @mcfarhat!
Thank you for your review, @mcfarhat! Keep up the good work!
I really wanted to write pretty much this exact tutorial for a few months, but sadly I couldn't motivate myself to tinker around with that stuff. Sadly school is too demanding this year, and if I technically have free time (like right now for example), I either want to do nothing, or have other more important things to do :(((
But looking at your post, I know that it's better than my post would've been. For sure ;-)
Let's hope I can finally get myself to write that post about me taking away those delegations D:
Thanks for your post, it's neat :P
haha, I know that state, I find myself in that position often enough as well :) The contest was a good "kick" to actually give it a try. Looking forward to your delegation removal post! I noticed your recent PR in the irredeemables list and you had plenty of them in the past - make the post, some rewards for your work would be well deserved ;)
I basically did exactly this but was too slow about it, so I'm pretty sure it works.
The first part can be done much, much more easily with beempy's allow command.
and then when you get to the last one add --threshold 40 after the weight. (Don't do it before or you won't be able to add new ones without the owner key or building a multisig transaction to do it.)
For changing the active authority, this actually doesn't matter since you need the owner key for anyway. You can't chance the active authority with an active key. It doesn't matter if there is an intermediate situation where none of the active keys can reach the active threshold.edit: You are right, it is possible to change the active auth with active keys - using the owner key in the first place is an easy workaround.
It makes a difference though, if the owner authority is changed. But in that case it's probably better to use a script like mine and set them all at once unless you're OK with waiting one hour after each change.
In fact I haven't been able to do it with the owner key; beempy crashes out with "Unnecessary signature(s) detected."
Thank you so much for participating the Partiko Delegation Plan Round 1! We really appreciate your support! As part of the delegation benefits, we just gave you a 3.00% upvote! Together, let’s change the world!
In looking for an easy way to get my test account usable again, I discovered that a master password reset will automatically change the weight of all that account's native keys to the Threshold weight, presumably including the owner key, though I didn't test for it. I don't know that there's any way to prevent that.
I would presume account recovery behaves similarly.
The account recovery on its own only affects the owner authority, all other authorities are not touched. In the
Request_account_recoveryoperation, you can specify how the new authority should look like, including any account_auths, key_auths, weights and the threshold - see for example here. Changing any lower-priviledged keys is then possible from the new owner authority.Hi @crokkon!
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your UA account score is currently 5.006 which ranks you at #1086 across all Steem accounts.
Your rank has improved 1 places in the last three days (old rank 1087).
In our last Algorithmic Curation Round, consisting of 207 contributions, your post is ranked at #8.
Evaluation of your UA score:
Feel free to join our @steem-ua Discord server
This post has been included in today's SOS Daily News - a digest of all you need to know about the State of Steem.
Editor of the The State of Steem SoS Daily News.
Promoter of The State of Steem SoS Weekly Forums.
Editor of the weekly listing of steem radio shows, podcasts & social broadcasts.
Founder of the A Dollar A Day charitable giving project.
Hey, @crokkon!
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!