I see now. https://developer.bitcoin.com/tutorials/account-creation/
m / purpose' / coin_type' / account' / change / address_index
Thanks. At the moment, the term "key derivation path" had slipped my mind, so I couldn't search it efficiently.
Topic: BTC vs BCH hardware wallet public address generation (Read 193 times)
Electrum and Electron Cash both use BIP 44 and SLIP 44 for determining the derivation path to use. So Electrum uses m/44'/0'/0'/0/* as that's the one for Bitcoin. Electron Cash uses m/44'/145'/0'/0/* as that is the one for Bitcoin Cash.
I accidentally sent some BTC to a BCH address. It is an insignificant amount, but it made me realize that Electrum (legacy) wallets do not generate addresses in the same order as Electron or perhaps they use a different depths. If I recall correctly there are a few numbers which can be changed when generating a wallet 'x/y/z' where x is the BIP implementation and z is the depth. Presumably, I should be able to see the BTC in Electrum if the client searches the blockchain for transactions.
Electrum: 3.3.6
Electron: 3.3.1
Operating System: Linux
I didn't provide the other specs, because I am more interested in understanding the problem than recovering an insignificant amount of BTC. In Electrum I loaded the transaction from the blockchain via Tools -> Load transaction which did not prompt Electrum to search if it could generate the address which received UTXO in that transaction.
Electrum: 3.3.6
Electron: 3.3.1
Operating System: Linux
I didn't provide the other specs, because I am more interested in understanding the problem than recovering an insignificant amount of BTC. In Electrum I loaded the transaction from the blockchain via Tools -> Load transaction which did not prompt Electrum to search if it could generate the address which received UTXO in that transaction.
Jump to: