Limiting owner key's role to only changing keys
What happens to the people who have the same key set for everything? A quick hivesql query(SELECT * FROM Accounts WHERE owner=posting AND owner=active;) shows that there are 18080 accounts like that. A lot of them were threespeak related, and changing the query to skip those(SELECT * FROM Accounts WHERE owner=posting AND owner=active AND owner NOT LIKE '%threespeak%';) still results in 15606 accounts like that. Will they be forced to change their keys? I'm sure that some people are actively doing that to use the same key. Checking accounts created in the last year(SELECT * FROM Accounts WHERE owner=posting AND owner=active AND owner NOT LIKE '%threespeak%' AND created > '2020-04-01';) results in 24 accounts. While thats not a lot(less than 2 per month on average), leaving the option for advanced users(I saw that marky and deathwing made a few of the accounts that have the same keys) to have more control over their keys would be best would it not?
They can use their owner key to generate new keys and continue on.
afaik the threespeak accounts actually don't have keys, everything is done via authorities, and they generate the keys only if the user asks for it.
That's a good point though ! I'll bring it up when we start working on it.
Yes and if peakd jumps into simplified custodial accounts for users who want a simple experience we would do the same thing and not even generate keys for those accounts until the user is ready to take on responsibilities themselves
I think the best solution here would be just UI changes. Just don't let users use the owner key to sign in and that should solve it. If they aren't used to using it, they might think twice about putting it in new places.