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
As in the rec. Creating a new account will create a new record on the list, but it will be the same exact account. It's not only a displaying issue, the exported account files are also exactly the same. (as discussed - the reason behind it is that the account creation does not automatically create a new key for the account, it uses the existing key)
Screen.Recording.2024-09-10.at.12.41.37.mov
I noticed the same while testing the deleting keys/accounts.
Delete Key- create a new key pair, you will get the exact same key over and over again.
I thought that it could be the cache issue? To be checked, I could easily reproduce it
cached.key.mov
The text was updated successfully, but these errors were encountered:
As we discussed on the call, I'll add "Create a new key" option to the dropdown and make it default (for SingleSig for sure).
Also I think that showing a message is still actual. So I'll add it as well.
Then I think it will be enough UX tweaks to not have confusion anymore. :)
brusherru
changed the title
Create New Account or Key is generating the same addresses
Add "Create new key" option to key selection drop down in Create/Edit Account popup
Sep 16, 2024
As in the rec. Creating a new account will create a new record on the list, but it will be the same exact account. It's not only a displaying issue, the exported account files are also exactly the same. (as discussed - the reason behind it is that the account creation does not automatically create a new key for the account, it uses the existing key)
Screen.Recording.2024-09-10.at.12.41.37.mov
I noticed the same while testing the deleting keys/accounts.
Delete Key- create a new key pair, you will get the exact same key over and over again.
I thought that it could be the cache issue? To be checked, I could easily reproduce it
cached.key.mov
The text was updated successfully, but these errors were encountered: