Version 3

[dcousens]

• [ ] Isolation of wordlists from primary export (https://github.com/bitcoinjs/bip39/issues/71)
• [ ] Remove mnemonicToSeedHex, remove implicit hex support, Buffer only
• [x] safe-buffer
• [ ] Removal of mnemonicToEntropy and entropyToMnemonic from the public API
• [ ] Change to async pbkdf2, aka, an async API (https://github.com/bitcoinjs/bip39/issues/72)

Thoughts any/everyone?

[prayerslayer]

I don't know what your goals are, so it's a bit hard to assess these proposals. From top of my head:

Buffer APIs only

There is no Buffer in the browser, only ArrayBuffer and typed arrays (views on ArrayBuffers). Could be that it can be shimmed cheaply, I'm not sure.

safe-buffer

Depends on the Node versions you want to support. Personally I'd not use it.

Removal of mnemonicToEntropy and entropyToMnemonic from the public API

What is the reasoning behind this?

[dcousens]

Could be that it can be shimmed cheaply, I'm not sure.

Buffer is ArrayBuffer/UInt8Array in the browser. It simply has a few methods tacked on for encoding, decoding, serialization and other Buffer operations.

Depends on the Node versions you want to support. Personally I'd not use it.

I suppose we could drop node <4.5.0... probably simplest.

What is the reasoning behind [Removal of mnemonicToEntropy and entropyToMnemonic]

Simplification - I don't know if they are being used - if anyone feels otherwise we can keep them.

[prayerslayer]

Buffer is ArrayBuffer/UInt8Array in the browser

Sure, I'm just saying that you can't expect new Buffer() to work in the browser, unless you include shims. Typed arrays however are supported on both platforms and you could use them directly.

I suppose we could drop node <4.5.0... probably simplest.

0.x is EOL and in between there was iojs :) So yeah, definitely drop everything < 4 https://github.com/nodejs/LTS

Simplification - I don't know if they are being used - if anyone feels otherwise we can keep them.

My company has a use case for mnemonic -> entropy, so I'd be happy if you keep it around :grin:

[dcousens]

My company has a use case for mnemonic -> entropy, so I'd be happy if you keep it around

@prayerslayer you probably should be using mnemonicToSeed, not mnemonicToEntropy?

0.x is EOL and in between there was iojs :) So yeah, definitely drop everything < 4 https://github.com/nodejs/LTS

4.5.0 isn't < 4, specifically

@prayerslayer could you elaborate on why you use mnemonicToEntropy?

@fanatid I think we need to specify \u300 in the Japanese WORDLIST as the default delimiter for us to be able to drop the wordlists from the default export

[fanatid]

@dcousens sorry, I do not understand, what's wrong with Japanese wordlist?

[dcousens]

@fanatid it requires the \u300 separator instead of ' '.

[fanatid]

agrh, I see... we can store seprator with wordlist...

[dcousens]

@prayerslayer could you elaborate on why you use mnemonicToEntropy?

Added a checkbox that we should change to an async API to support high performance pbkdf2, as recommended in https://github.com/crypto-browserify/pbkdf2/pull/75

AFAIK, only mnemonicToSeed would need to be async...

@fanatid

agrh, I see... we can store seprator with wordlist...

Any thoughts on how we should?

[dcousens]

@fanatid

agrh, I see... we can store seprator with wordlist...

Any thoughts on how we should?

[fanatid]

Any thoughts on how we should?

{
  separator: '...',
  words: [...]
}

?

[dcousens]

@fanatid we will need to re-write the download script

[dcousens]

ping @prayerslayer ?

[dcousens]

@jkandzi @oed I noticed you use mnemonicToEntropy, can you elaborate on why it was required compared to using the seed bytes?

[oed]

@dcousens seed bytes is double the size which annoying if you want to keep size down. Last time I played around with it mnemonicToSeed behaved weirdly when going back and forth between seed and mnemonic.

[dcousens]

@oed was truncating the seed not an option?

[oed]

Right, now I remeber. There is no way to go from seed -> mnemonic. The reason I want this is because I want to split the entropy into multiple parts using shamirs secret sharing. Then I can give these parts to some delegates. When I recreate the entropy I want to be able to get the mnemonic again.

[dcousens]

@oed do you ever need mnemonicToEntropy? Or only entropyToMnemonic?

(thanks for this information btw)

[oed]

I need both. In case a user want's to recover with mnemonic and then split this and give to delegates. Thank you for asking for feedback! :+1:

[dcousens]

See https://github.com/bitcoinjs/bip39/pull/74