Allow users to update the public keys for their existing accounts #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
eosio-toppings
is using theupdate-auth
branch otherwise this branch will not be usable, or you can wait until that branch has been merged intodevelop
Changes
active
permission's key pair, orowner
permission's key pair, or both at the same timeupdateauth
in the Push Action page, the permission which got changed will have the private key reset. You will need to import the missing key in this case, but the permission which did not get updated will still be usable🔎 Please note, importing private keys to accounts with no private keys in the local storage remains unchanged compared to previous updates