From: Aymeric Vitte <vitteaymeric@gmail•com>
To: Pavol Rusnak <stick@satoshilabs•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] License for BIP39 word lists
Date: Tue, 9 Apr 2019 18:19:40 +0200 [thread overview]
Message-ID: <788850e2-f361-4f06-43b4-0a21050de0d2@gmail.com> (raw)
In-Reply-To: <CAF90Avk1EdXTgCXx7xZHEekd8n=3EbR+L-bHsRRkj+-ZZbhODg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2290 bytes --]
What is not final finally and when do you expect it to be?
Le 09/04/2019 à 11:49, Pavol Rusnak a écrit :
> We are in process of finalizing it, so it is not live in Trezor yet.
> It will be soon, though. I suppose every wallet that uses BIP39 will
> adopt this one as well.
>
> On Tue, Apr 9, 2019, 11:46 Aymeric Vitte <vitteaymeric@gmail•com
> <mailto:vitteaymeric@gmail•com>> wrote:
>
> Is it final now and live in Trezor? Do you know who else will
> adopt it?
>
> Regards
>
> Aymeric
>
> Le 03/04/2019 à 11:19, Pavol Rusnak via bitcoin-dev a écrit :
>> I am the author of the wordlist. Feel free to use it without any
>> restrictions.
>>
>> However, we are finalizing SLIP39 standard for splitting shares
>> which uses a different wordlist with better properties. It might
>> be more suitable for your project.
>>
>> See https://github.com/satoshilabs/slips/blob/master/slip-0039.md
>> and https://github.com/satoshilabs/slips/blob/master/slip-0039/wordlist.txt
>>
>>
>>
>> On Wed, Apr 3, 2019, 09:32 Elia via bitcoin-dev
>> <bitcoin-dev@lists•linuxfoundation.org
>> <mailto:bitcoin-dev@lists•linuxfoundation.org>> wrote:
>>
>> I would like to use the BIP39 word lists posted in the Github
>> BIP repo
>> for my own project.
>>
>>
>> Unfortunately there is no license associated with the lists
>> provided on
>> Github so I am not sure whether usage for other projects is
>> permitted. I
>> am not able to file issues on the repo either to suggest
>> adding a license.
>>
>> Does anybody know under which license these lists are published?
>>
>>
>> Best regards,
>>
>> Elia
>>
>>
>>
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> <mailto:bitcoin-dev@lists•linuxfoundation.org>
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org <mailto:bitcoin-dev@lists•linuxfoundation.org>
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 5845 bytes --]
prev parent reply other threads:[~2019-04-09 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <iKDdEbi-0Ihe0gNPYsIN_nkg2X8t9FK7RRUoTb6fz9rF4mRReXjpKDjIOsZkpGYKG1UXtCHdMdKzXNgk2iihosaWg-8HqYIa9JDoGdJv9Kw=@dl1ye.com>
[not found] ` <pgnG4aynAMLF_fvTKASzXWqV9OMAQFghcNTGmwRA9Dvo6JKD6vN7kcfyMNyIgXz-ONUWYq5AjA8G1fUVqPrMbeWiXicnkczqDlerjSiDZB8=@dl1ye.com>
2019-04-03 5:53 ` Elia
2019-04-03 9:19 ` Pavol Rusnak
2019-04-09 9:46 ` Aymeric Vitte
2019-04-09 9:49 ` Pavol Rusnak
2019-04-09 16:19 ` Aymeric Vitte [this message]
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=788850e2-f361-4f06-43b4-0a21050de0d2@gmail.com \
--to=vitteaymeric@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=stick@satoshilabs$(echo .)com \
/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