From: Ronald van der Meer <ronald@vandermeer•frl>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Suggestion to remove word from BIP39 English wordlist
Date: Tue, 23 Jan 2018 19:40:42 +0000 [thread overview]
Message-ID: <HE1PR0301MB1915391234785F1963D11A49A3E30@HE1PR0301MB1915.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <CALPhJayvtBra2GhAXAJkrCBtQeXu-+jj-uUtQB4zWYmbcuS4gA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]
I’m new to this so what is the next step?
--
Ronald van der Meer
E: ronald@vandermeer.frl<mailto:ronald@vandermeer•frl> | W: https://www.vandermeer.frl
S: https://twitter.com/truly_secure
GPG: 8203 CE3E 064D C462 1D22 F635 A1EC 45F9 645F 878D
From: bitcoin-dev-bounces@lists•linuxfoundation.org [mailto:bitcoin-dev-bounces@lists•linuxfoundation.org] On Behalf Of Alan Evans via bitcoin-dev
Sent: donderdag 18 januari 2018 22:29
To: Matthew Clancy <matthewpclancy@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Suggestion to remove word from BIP39 English wordlist
> and then agree that by convention, the words 'satoshi' or the alternative word will represent the same number on the list
That convention would be the alternative to BIP0039 I am referring to.
On Thu, Jan 18, 2018 at 4:49 PM, Matthew Clancy <matthewpclancy@gmail.com<mailto:matthewpclancy@gmail•com>> wrote:
I would disagree here:
>But most of all:
>7. Removing a word or changing a list *is impossible* as verification of an
>existing mnemonic requires the list. To change one word, you would need to
>provide an alternative to BIP0039 to cope with alternative words, or change
>all the words to a completely new set of 2048 English words so that it is
>clear which wordlist is in use.
All that really would need to be done is select another word that is not on the 2048 list, and then agree that by convention, the words 'satoshi' or the alternative word will represent the same number on the list. It seems to be to be a fairly simple thing to implement.
[-- Attachment #2: Type: text/html, Size: 6325 bytes --]
next prev parent reply other threads:[~2018-01-23 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 20:49 Matthew Clancy
2018-01-18 21:29 ` Alan Evans
2018-01-23 19:40 ` Ronald van der Meer [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-09 11:20 Ronald van der Meer
2018-01-18 1:07 ` Weiwu Zhang
2018-01-18 1:14 ` CryptAxe
2018-01-18 6:55 ` Jonathan Sterling
2018-01-18 19:50 ` Alan Evans
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=HE1PR0301MB1915391234785F1963D11A49A3E30@HE1PR0301MB1915.eurprd03.prod.outlook.com \
--to=ronald@vandermeer$(echo .)frl \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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