Skip to content
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

Extension: Importing private key should also generate shielded accounts #1231

Open
jurevans opened this issue Nov 4, 2024 · 0 comments · May be fixed by #1232
Open

Extension: Importing private key should also generate shielded accounts #1231

jurevans opened this issue Nov 4, 2024 · 0 comments · May be fixed by #1232

Comments

@jurevans
Copy link
Collaborator

jurevans commented Nov 4, 2024

We now have the ability to derive shielded keys from private keys in the SDK package.

When a user imports just a private key:

  • In addition to the imported transparent address/public key, also derive a spending key and default viewing key/payment address
  • Add this to the confirmation UI, as well as View Keys (the shielded key should reference the ID of the transparent SK account as a parent)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant