Error: Range consisting of offset and length are out of bounds
See original GitHub issueHey,
I’m getting this error “Range consisting of offset and length are out of bounds”, when calling the method bip39.mnemonicToSeed
const mnemonic = "butter top unaware common define punch about merge animal sniff give climb";
const password = "";
const seed = await bip39.mnemonicToSeed(mnemonic, password);
I tried to debug seems like error is thrown from pbkdf2
lib, not sure why this is happening.
but If I use 24 words mnemonic it works, then this method gives same error
const root = bitcoin.bip32.fromSeed(seed, config.bitcoinNetwork);
Version
"bip39": "3.0.2",
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
I'm getting error [RangeError: Range consisting of offset and ...
I'm getting error [RangeError: Range consisting of offset and length are out of bounds] #30. Open. vtn-dev2016 opened this issue on Nov 2, ......
Read more >c# - Offset and length were out of bounds for the array
You provided us a function which takes a binary reader (whatever position it's already at, if it's new, then position 0), it reads...
Read more >Offset and length were out of bounds for... on serialport - MSDN
Question. Hi. Message=Offset and length were out of bounds for the array or count is greater than the number of elements from index...
Read more >"Offset and length were out of bounds for the array" error when ...
'Offset and length were out of bounds for the array or count is greater than the number of elements from index to the...
Read more >Issue 5733 in v8: Out of bound array from BufferArray error ...
Can we make a new error message such as "The offset is out of range of the buffer" for this? This error occurs...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It looks like the root cause is the following: https://github.com/feross/buffer/issues/272
Issue has been fixed, update to latest buffer version
buffer