From: Pavol Rusnak <stick@satoshilabs•com>
To: nullius <nullius@nym•zone>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 39: Add language identifier strings for wordlists
Date: Sun, 7 Jan 2018 16:16:47 +0100 [thread overview]
Message-ID: <d05bfa26-4f3d-77d1-5801-9ad59497f334@satoshilabs.com> (raw)
In-Reply-To: <57f5fcd8644c6f6472cd6a91144a6152@nym.zone>
[-- Attachment #1.1: Type: text/plain, Size: 957 bytes --]
On 05/01/18 14:58, nullius via bitcoin-dev wrote:
> I propose and request as an enhancement that the BIP 39 wordlist set
> should specify canonical native language strings to identify each
> wordlist, as well as short ASCII language codes. At present, the
> languages are identified only by their names in English.
I am advising not to use any other language than English for BIP39. I
got persuaded to allow more languages when writing BIP39 spec, but I
learned that it was something I should've been more persistently against.
I am currently drafting a new standard[1] which will allow also Shamir
Secret Scheme Splitting and there we disallow usage of a custom wordlist
in order to eradicate this mess. Will try to push this as BIP too once
we get it to the point we are OK with the contents.
https://github.com/satoshilabs/slips/blob/master/slip-0039.md
--
Best Regards / S pozdravom,
Pavol "stick" Rusnak
CTO, SatoshiLabs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-07 15:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 13:58 nullius
2018-01-05 16:04 ` Sjors Provoost
[not found] ` <CALPhJax=53dLL9+JDKJC7NdEFFRB2kgKiECSh8PUMzrr2KxWuQ@mail.gmail.com>
2018-01-05 17:13 ` Sjors Provoost
2018-01-05 18:08 ` Aymeric Vitte
[not found] ` <CALPhJaxzayykMMxaa421kfu6QQ77JD7bZJk8+dXT4qSqK_eABg@mail.gmail.com>
2018-01-05 19:56 ` Aymeric Vitte
[not found] ` <CALPhJawP7hjucR6X3gpTxCxK+awMT9iArELZYFy_zffCGgVMEw@mail.gmail.com>
[not found] ` <58C8F1BA-B9A1-4525-BCC9-BF4CEDC87E1B@sprovoost.nl>
[not found] ` <a3e10fe7-ed9c-bb58-bf12-d0aeda2827e4@gmail.com>
[not found] ` <a2e8b3e2-b444-039c-c51e-43294a3437c9@gmail.com>
[not found] ` <CALPhJaz1wU8y6KxZipREjus8WbHpwpyYjyMwgj5x-tTodxpjCQ@mail.gmail.com>
2018-01-06 17:40 ` Aymeric Vitte
[not found] ` <CALPhJaw8_wpPCRj58JcZqLnEvOtLoo=U_VBYRLSKTCeN7TFB6A@mail.gmail.com>
2018-01-06 19:46 ` Aymeric Vitte
2018-01-05 18:08 ` nullius
2018-01-07 15:16 ` Pavol Rusnak [this message]
2018-01-08 7:35 ` 木ノ下じょな
2018-01-08 11:13 ` nullius
2018-01-08 14:34 ` Greg Sanders
2018-01-08 14:52 ` Matias Alejo Garcia
2018-01-08 14:54 ` Greg Sanders
2018-01-08 15:23 ` Matias Alejo Garcia
2018-01-08 15:26 ` AJ West
2018-01-08 15:32 ` Greg Sanders
2018-01-08 16:02 ` Aymeric Vitte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d05bfa26-4f3d-77d1-5801-9ad59497f334@satoshilabs.com \
--to=stick@satoshilabs$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=nullius@nym$(echo .)zone \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox