MetaMask / MetaMask/metamask-extension

Multilingual SRPs

Open
#27,563 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

external-contributor
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

### What is this about?

This issue is to track internal conversations, user feedback, and potential technical implementation of multilingual SRPs within the MetaMask wallet experience. As we continue to maintain translations of the MetaMask product into 14+ languages, providing capability for multilingual SRPs under BIP-39 would make the wallet more safe, usable, and secure for users whose best language is not English.

Instances of user feedback:
![Portuguese user feedback](https://github.com/user-attachments/assets/d7f72926-65c9-46ab-a05c-8de7aa99087c)

### Scenario

A user who does not read or write English creates a MetaMask wallet, but they struggle to record their SRP accurately. When they go to import their wallet elsewhere, they are unable to because they can't read what they wrote down. Maybe they resort to copying and pasting the SRP, or taking a screenshot instead. If their accounts are hacked, the SRP is easily compromised and their funds are stolen. Providing an SRP in languages other than English means that users are able to record their SRPs accurately and store them securely - which allows them to exercise real self-custody over their assets.

### Design

_No response_

### Technical Details

Other GH issues related to this:

This issue highlights that users have been interested in this for a while: https://github.com/MetaMask/metamask-extension/issues/4837

This was merged: https://github.com/MetaMask/KeyringController/pull/77 , but didn't work?

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [X] Engineering (needed in most cases)
- [X] Design
- [X] Product
- [X] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [X] Security
- [X] Legal
- [X] Marketing
- [X] Management (please specify)
- [ ] Other (please specify)

### References

[Mnemonic Code Converter](https://iancoleman.io/bip39/)
[BIPs - GitHub](https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No implementation files, tests, entry points, design, or acceptance criteria are identified. Start by reviewing the related issue 4837, KeyringController pull request 77, and the BIP-39 references to understand prior work and constraints; the issue does not define a verifiable done state.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, internationalization, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.