MetaMask / MetaMask/metamask-extension

Enable import of private key via QR code

Open
#20,629 0 comments 0 reactions 0 assignees View on GitHub
area-UI external-contributor INVALID-ISSUE-TEMPLATE team-accounts-framework type-enhancement ux-enhancement
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

**Describe the bug**

Today we support scanning QR for the send flow, I would like to request an enhancement to add the QR scanning capability into the private key import field. This would help reduce user transcription errors and would bring extension client into parity with mobile.

**Steps to reproduce**

1. Tap accounts drop-down
2. Select `Import account`
3. Observe lack of ability to scan a QR

**Version**

10.34.5

**Build type**

None

**Browser**

Chrome, Firefox

**Operating system**

MacOS

**Additional context**

QR scanning in send flow:
![Screenshot 2023-08-28 at 11 33 58 AM](https://github.com/MetaMask/metamask-extension/assets/32695229/2d72d640-8f2c-426e-a937-91742495a8d2)

Place where it would be nice to have QR scanning button in private key import:
![Screenshot 2023-08-28 at 11 33 47 AM](https://github.com/MetaMask/metamask-extension/assets/32695229/3ff331b5-814a-40a3-8ca0-24213a7c662c)

Contributor guide

Open the contributing guide

Research direction

Start from the Accounts > Import account flow and compare it with the existing QR scanning behavior in the send flow. Check the result in Chrome and Firefox; done means a user can scan a private key QR code during import instead of transcribing it, bringing the extension flow toward mobile parity.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.