-
Notifications
You must be signed in to change notification settings - Fork 985
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect derivation path for newly generated keypair accounts and theirs derived acccounts #19472
Comments
@ulisesmac - since derivation path flows have been descoped can you unassign this issue and block it for now? |
We must generate a default derivation path for a new derived account in wallet. This issue isn't about the derivation path flow (where you can set a custom one) it's about adding a new account in wallet. Currently, we are stuck, seems Android is not creating a keystore file so maybe there's a bug on Status go side, this issue has become very complex. BTW, @OmarBasem did you replicate the issue we had for new keypairs? If you did, it's time to align with Sale and check what's the problem in Status go. |
Hey @ulisesmac,
I think it works properly on Desktop (?) |
Steps:
Actual result:
The number is incremented at the end for the Derivation path for keypair account and = m/44/60'/0'/0/
<incremented account number>
Expected result:
The derivation path for master (keypair) accounts should not have an incremented number at the end; it should be m/44/60'/0'/0/0. Only accounts that are derived from the master (keypair) accounts should have an incremented path.
For example, if a user has two generated keypairs and two additional accounts derived for each keypair account then derivation path hierarchy should looks so:
discussed in https://discord.com/channels/1210237582470807632/1217175448828514344/1224605345461047326
in the same way it works for Desktop.
The text was updated successfully, but these errors were encountered: