Feature request: Use the phone camera to scan OTP QR codes for Jade Core
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- authentication, mobile-dev, security
Research direction
Start by locating the existing register_otp RPC and the mobile app's Jade connection path, then trace how OTP URIs and on-device confirmation are handled. Check the USB and Bluetooth paths mentioned in the issue before determining where camera scanning or URI pasting belongs. Done means an OTP QR code can be imported through the app, reviewed on Jade, and saved without exposing the secret to photos, logs, analytics, or cloud services.
Written by the indexing model from the issue text.
Description
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!
- Dominant language
- C
- Stars
- 497
- Forks
- 131
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Blockstream/Jade
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Blockstream/Jade#329 · 4 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Blockstream/Jade#317 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Blockstream/Jade#315 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Blockstream/Jade#313 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Blockstream/Jade#345 · 4 comments ·
All issues in Blockstream/Jade
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·