are you sure about this?
Nope!
Hmmmm maybe it is just the SegWit "xprv" (actually a zprv) that I saw doing odd things...
From the Electrum SegWit seed:
"keystore": {
"pw_hash_version": 1,
"seed": "wine comfort off fat pudding initial wash they tennis fashion never nuclear",
"type": "bip32",
"xprv": "zprvAYvZpviDe8FvV1uHrqohakCtZ3M4Cv6pcZYqcvzHb1Ujh8s1c3J3cMzza2bCcK91iyik8dZJU3LSiMFkBtppQNSdmcpq3sxtBiT7ojnHq45",
"xpub": "zpub6muvESF7UVpDhVykxsLhwt9d75BYcNpfynUSRKPu9M1iZwCA9acJAAKURHHq8bPcLS3X2p39SJHW45WYmWcsXzPdBTf5f8cPSf7tgUSipez"
You can see the stored zprv... it produces this address:
But, when we put the seed into the converter... we get this:
So, to see the same "xprv" (as stored in the wallet) in BIP39 converter... you need to use a derivation path of: m/0'
But... then addresses shown are NOT the ones in the wallet!!
To see the correct address you need the extra "0" (path= m/0'/0), which gives the correct addresses, but shows the wrong xprv:
Meanwhile, in Legacyland...
"keystore": {
"pw_hash_version": 1,
"seed": "resist flee ginger seminar pretty walnut basic shift you reason trigger battle",
"type": "bip32",
"xprv": "xprv9s21ZrQH143K3jnoRp5JYq2zjuw1d6rAUmkMT2has1wFujr5SPQdDDma3jwjMRV1rT8xS7ZdeQywSdhzc7SHVncCEQH4FjK9DUKM7ip6WBU",
"xpub": "xpub661MyMwAqRbcGDsGXqcJuxyjHwmW2Za1qzfxFR7CRMUEnYBDyvism263tzxQZLdm8Z2q44HbmjRKk3A28nMJMgM57fBdpnmEMmPSo8rSM7S"
},
Which generates this:
The "xprv" stored in the wallet, is the same as you get if you put the seed into the converter... (so path=m):
but again, does not show the correct addresses until you add a 0 (path = m/0):
It all seems a bit confusing and somewhat inconsistent... but seems to be because the old BIP44 stuff only had:
m / purpose' / coin_type' / account' / change / address_index
whereas the newer stuff apparently uses:
m / purpose' / coin_type' / account' /
script_type' / change / address_index
But the "xprvs" we have stored in the wallets, are actually at m (legacy) and m/0' (SegWit) ??!?
This stuff does my head in sometimes!