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: Airgap functionality #31

Closed
evliu opened this issue Jan 6, 2022 · 7 comments
Closed

Feature Request: Airgap functionality #31

evliu opened this issue Jan 6, 2022 · 7 comments

Comments

@evliu
Copy link

evliu commented Jan 6, 2022

Hi, I couldn't find any issues mentioning this, but am wondering if there is a roadmap for this. Bought multiple Jades for airgapped multi-sig based on this Blockstream blogpost:

https://blog.blockstream.com/en-secure-your-bitcoin-and-liquid-assets-with-blockstream-jade/
specifically this paragraph:

Where We’re Going, We Don’t Need Cables
Blockstream Jade also has a few “dormant” features that we’ll be activating through software updates over the course of 2021. Many bitcoiners (especially us!) are looking forward to the ability to properly airgap their hardware wallets. So we’ve equipped Blockstream Jade with an on-board camera.

Once activated, the camera will enable you to complete all incoming and outgoing transactions entirely through QR codes, ensuring that you don’t even need to connect your Blockstream Jade to your device through a cable.

Since 2021 is over, just wanted to see how this is going.

Thank you guys!

@JamieDriver
Copy link
Collaborator

Apologies for the delay.
We are currently working on fully airgapped use of Jade through QR codes.
eg. export xpub using ur:crypto-account QR codes, and tx signing using ur:crypto-psbt QR codes.
This should allow Jade to work fully airpgapped with supporting wallets - eg. BlueWallet, Nunchuk, Sparrow, Specter...

@JamieDriver
Copy link
Collaborator

Initial PSBT signing and receive address validation (singlesig) released in 0.1.41.
Apologies for the delay!

In upcoming releases we hope to improve multisig support (signing currently works, but address validation (including change addresses when signing) does not work for multisig atm), and provide a way to persist the wallet mnemonic/seed on device and decrypt/unlock it using the blind pinserver via QR codes (ie. same as when using usb/ble), thus saving you having to have a QR code of your wallet/seed lying about.

We also hope to provide a site showing a QR code of the current epoch time, to initialise Jade for TOTP use when airgapped (also unsupported atm).

@evliu
Copy link
Author

evliu commented Nov 16, 2022

Awesome! I've been experimenting with it and working w/ Rich on feedback. I proposed creating an app for the blind pin server (was looking at the green iOS repo and seeing if I could simplify it to be an app only with the jade swift lib, but didn't have time). Created a request on this ticket Blockstream/green_ios#45

@JamieDriver
Copy link
Collaborator

Further enhancements, mainly to multisig support, in fw v0.1.42.
'Sign message' should be also be supported in fw v0.1.44

@JamieDriver
Copy link
Collaborator

JamieDriver commented Feb 27, 2023

Unlock with PIN (ie. the pinserver protocol) using QR codes implemented in v0.1.45.
ie. 'airgapped' users can now opt to either (depending on their choice of tradeoffs - eg. whether they prefer to have a QR code of the wallet to hand vs having encrypted wallet data persisted in Jade flash and some/partial encryption-key-data stored on the pinserver) :

a) scan a QR of their seed phrase every time they want to use Jade (and make a CompactSeedQR when initially entering the phrase and recording on these templates).

b) Use the blind pinserver to assist in encrypting the wallet seed, which can then be safely persisted in the Jade flash. Pinserver interaction is then needed to decrypt those keys, using this web application.
(Note: more advanced users can run their own pinserver, and are not constrained to using the blockstream-provided instance).

NOTE: in either case the user can use bip39 passphrases to further protect their wallet.

@bitcoinprecept
Copy link

This request seems to be delivered. Leaving open to track expanded functionality?

@JamieDriver
Copy link
Collaborator

You're probably right, we can probably close this.
As you say there may be ongoing improvements/extensions to what we can do with QRs, but that's (hopefully!) no different to any other existing feature.
Closing as delivered. Thanks.

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

3 participants