Hi Blockstream team,
I recently purchased a Jade Core, which does not have a built-in camera. I would like to use its OTP/2FA functionality, but under Options > Authentication > OTP > New OTP, my device only offers “Enter URI”.
Manually entering a full otpauth:// URI using the device buttons is very tedious and easy to get wrong, especially when it contains a long secret and additional parameters.
Could you please add an option in the Blockstream mobile app to scan an OTP setup QR code using the phone’s camera and import it into the connected Jade Core?
The proposed flow would be:
- Connect and unlock Jade Core through the mobile app.
- Scan the service’s OTP setup QR code with the phone.
- Send the decoded OTP details to Jade over the supported USB or Bluetooth connection.
- Review and confirm the account details on Jade before saving the record and generating OTP codes.
Pasting an OTP URI into the mobile app would also be a useful alternative.
Jade already appears to expose a register_otp RPC accepting an otpauth URI. Could the app reuse this capability while keeping the existing on-device confirmation?
Since the phone would handle the OTP secret during import, please avoid saving it to photos, logs, analytics, or cloud services.
This would make OTP setup much more practical for Jade Core owners. If an existing supported workflow already allows this, please point me to it.
Thank you!
Hi Blockstream team,
I recently purchased a Jade Core, which does not have a built-in camera. I would like to use its OTP/2FA functionality, but under Options > Authentication > OTP > New OTP, my device only offers “Enter URI”.
Manually entering a full otpauth:// URI using the device buttons is very tedious and easy to get wrong, especially when it contains a long secret and additional parameters.
Could you please add an option in the Blockstream mobile app to scan an OTP setup QR code using the phone’s camera and import it into the connected Jade Core?
The proposed flow would be:
Pasting an OTP URI into the mobile app would also be a useful alternative.
Jade already appears to expose a register_otp RPC accepting an otpauth URI. Could the app reuse this capability while keeping the existing on-device confirmation?
Since the phone would handle the OTP secret during import, please avoid saving it to photos, logs, analytics, or cloud services.
This would make OTP setup much more practical for Jade Core owners. If an existing supported workflow already allows this, please point me to it.
Thank you!