`mnemonicToEntropy` not returning correct entropy about bip39

[dcousens]

Interesting, but, this actually isn't our fault!

let buffer = Buffer.from('ea9d80e70b08bbfb6b7f2bca56c88ddb2c2d003e675a855779d81e11f3009346a', 'hex')
// <Buffer ea 9d 80 e7 0b 08 bb fb 6b 7f 2b ca 56 c8 8d db 2c 2d 00 3e 67 5a 85 57 79 d8 1e 11 f3 00 93 46>

You passed a 65-byte hex string, and a 32-byte Buffer is parsed.
Why does Node not throw? Ask them, but, alas.

[dcousens]

Keeping open for now, as I'd like to hear your opinion, this is certainly a confusing (and unfortunate) result.

[cgcardona]

Looking back through my console I see the issue. TLDR adding the a on the end was a typo in my test suite.

Both the 64 and 65 char entropy strings produce the same mnemonic

let a = bip39.entropyToMnemonic('ea9d80e70b08bbfb6b7f2bca56c88ddb2c2d003e675a855779d81e11f3009346')
// 'tunnel ugly degree bid merry world pupil tornado ski rent casino rent security length wet twice luxury rookie invite destroy busy leopard escape shoe'

let b = bip39.entropyToMnemonic('ea9d80e70b08bbfb6b7f2bca56c88ddb2c2d003e675a855779d81e11f3009346a')
// 'tunnel ugly degree bid merry world pupil tornado ski rent casino rent security length wet twice luxury rookie invite destroy busy leopard escape shoe'

Node's Crypto.randomBytes correctly returned a 64 character hex encoded string but when I manually copied the 64 char string to my fixtures JSON I added an a due to my vim workflow.

So my entropyToMnemonic tests passed but the mnemonicToEntropy tests failed because my assertion was for the 65 character string.

Apologies for the false flag. Again, thanks for a great lib. 🎩

[lp12ucw]

What’s this ?

…

Sent from my iPhone On 16 Mar 2018, at 11:03, Daniel Cousens <[email protected]> wrote: Closed #70. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.