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

[Feature Request] Encrypted seed back up #195

Open
takeshi117 opened this issue Jan 7, 2025 · 0 comments
Open

[Feature Request] Encrypted seed back up #195

takeshi117 opened this issue Jan 7, 2025 · 0 comments

Comments

@takeshi117
Copy link

Stateless mode is a great functionality for long term hold and reduce the risk of physical attack on the device, since there is no valuable data on it at rest.
However, there are some risks when the user has to scan the SeedQr in order to sign a transaction or to verify a receiving adresse :

  • The user has to access to his physical seed, so it is unpractical when the opsec involves using tamper evident bag to store physical seed back up
  • There could be camera during the scanning of the Seed Qr (webcam/phone)

Existing solutions in order to eliminate these risks :

  • use the blind oracle : need to trust the feature
  • use a passphrase : unpractical and risky for multisig setup (because of complexity)

Feature request
It could be great to be able to :

  • back up the seed on micro sd for the jade plus, where to back up is encrypted using AES 256. The decryption key could be 40 digits code or 12 words from BIP39 for example
  • Encrypted SeedQr back up using the same principle as above. Could be compatible with Jade Classic and Plus

Benefits

  • Eliminate the risks involved in stateless mode by adding a 2 FA methods (encrypted seed + decryption key)
  • No need to trust blind oracle
  • Able to store encrypted seed on micro sd or in seed qr in untrustworthy places

Thank you in advance for your answers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant