-
Notifications
You must be signed in to change notification settings - Fork 19
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
Promote support of multi-language recovery phrases #291
Comments
I will expand this list as I make issues, feel free to copy + paste my message and use it with other wallets. |
olawalethefirst created a mnemonic translator to easily convert recovery phrases from one language to another. This could be helpful in reducing the chicken-and-egg problem. |
Afromnemonics is another project from bolt.fun that is creating a wordlist in Swahili. |
Phoenix just merged support for importing seed phrases in 3 extra languages (spanish, french, czech). Cool to see progress on this. |
Recovery phrases are usually in English, which does not work well for people not proficient in the language. Wallets should support multiple languages during wallet generation and import. This should make it easier for people around the world to adopt and protect their bitcoin, fitting our tagline of "Design bitcoin for everyone".
BIP39 includes word lists in 10 languages, and there's a separate repo to collaborate around creating more. Not much activity there at the moment.
One of the problems right now is that there's little support, so if a user generates a wallet in another language, they may not be able to recover it in any other software. So first step would be to work with different wallet teams to support multi-language import. Then, once there is decent support for this, we can promote wallet creation in multiple languages.
This effort evolved from this issue.
We can also consider updating the Manual backup and Wallet recovery pages with relevant info.
Wallets working on this:
Issues filed for:
What are some other wallets to talk to about implementing this?
The text was updated successfully, but these errors were encountered: