privateExtendedKey error handling
See original GitHub issueCalling privateExtendedKey
on a public node will result in the following exception: TypeError: Cannot read property 'length' of null
I think it would be nice either adding an assert into the function with a proper message or to return null.
In comparison privateKey
just returns null if it is not available, perhaps that should be followed.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
WoeOm/ethereumjs-wallet-react-native - GitHub
Utilities for handling Ethereum keys ethereumjs-wallet - GitHub ... privateExtendedKey() - return a BIP32 extended private key (xprv); publicExtendedKey() ...
Read more >Extended private key vs private key - Ethereum Stack Exchange
When trying to sign I am getting an error that the private key is invalid. Waht private key I need to use to...
Read more >hdkey-wasm - UNPKG
20, - fix bug when `privateKey` is `null`, `privateExtendedKey` should not throw, and return `null` [#7][#7] ... "privateExtendedKey error handling".
Read more >BIP32 Mechanism Support and Implementation - Thales Docs
The handle of the unwrapped key is stored in hUnwrappedKey if there were no errors. Exporting a private extended key. CK_MECHANISM mechanism =...
Read more >EthereumJS library not providing me with correct address ...
toChecksumAddress(addr); and I seem to get the error : error to seed Error: This ... .catch(err => { console.error('error to seed', err) })....
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 Free
Top 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
Fixed. Published. Sorry about the delay!
Thanks!