Replies: 1 comment
-
Sorry for the long delay getting this question answered. Unfortunately, the BIP-32 extended key does not encode the path in any way; it is designed to be of fixed length (which is a medium-to-hard requirement for encoding data using Base58), which doesn't allow for variable-length data to be encoded. Sorry this likely doesn't help, but long story short is that the specification doesn't allow for it. :( |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Ethers Version
6.0.8
Search Terms
fromExtendedKey, extendedKey, derivePath, path null
Describe the Problem
I'm playing with https://iancoleman.io/bip39/ utility and ethers library.
I'm trying to get what is BIP32 Root Key. As I understand I can use BIP32 Root Key to generate all derived keys instead of mnemonic phrase.
And I did it. But the main issue is null value in
path
property. Please look to the complete example below.root.path
which I got from mnemonic equalsm
as I expected.But when I create
restoredRoot
usingHDNodeWallet.fromExtendedKey
method,restoredRoot.path
equalsnull
and there is no way to override it.When I derive
m/44'/60'/0'/0/0
andm/44'/60'/0'/0/1
fromrestoredRoot
I get nulls in theirpath
s too.So the question: is there any way to restore wallets with right paths from extended private key?
Code Snippet
Contract ABI
No response
Errors
No response
Environment
node.js (v12 or newer)
Environment (Other)
No response
Beta Was this translation helpful? Give feedback.
All reactions