Seed and public key for eth/btc(Ledger)

[egetrorx]

Maybe stupid question but i am not sure.If I have public address for bitcoin and public address for ethereum,can i know if these public addresses belong to same seed even if I dont have seed?

[bitmover]

Maybe stupid question but i am not sure.If I have public address for bitcoin and public address for ethereum,can i know if these public addresses belong to same seed even if I dont have seed?

They are different blockchain, but They could share the same mnemonic phrase, which is somehow a way to sahre their seed.

If you create a wallet in coinomi or ledger nano for example, your keys and addresses of these two blockchain will share the same mnemonic phrase, i.e. seed.

[pooya87]

the BIP32 derivation path that Ledger uses for each cryptocurrency is different so your bitcoin keys are on an entirely different branch than your ETH keys and your other coins. bitcoin uses m/44'/0'/0' and ETH uses m/44'/60'/0' paths and then they use /0 or /1 or/.... for each account and derive the keys that way.

[egetrorx]

Maybe stupid question but i am not sure.If I have public address for bitcoin and public address for ethereum,can i know if these public addresses belong to same seed even if I dont have seed?

They are different blockchain, but They could share the same mnemonic phrase, which is somehow a way to sahre their seed.

If you create a wallet in coinomi or ledger nano for example, your keys and addresses of these two blockchain will share the same mnemonic phrase, i.e. seed.

yeah so I have public eth and public bitcoin address which should be from same seed,but no seed to confirm

[bob123]

yeah so I have public eth and public bitcoin address which should be from same seed,but no seed to confirm

If you don't have access to your seed, you should IMMEDIATELY move all of your coins away from your ledger.

There are a lot of scenarios where you can't access your nano s anymore (e.g. after update, firmware buggy, nano s breaks, someone enters the pin wrong 3 times, etc...).
Without the seed, there is NO WAY to recover your coins anymore.

If you really don't have your seed (which does seem so from your statement), create a temporary wallet to move all your funds to, reinitialize your nano s with a new seed, MAKE A BACKUP OF IT, and move your funds to your nano s again.
Also, note that you shouldn't store your seed on your PC. Write it on a sheet of paper.


It is extremely risky to leave your coins on your nano s without having the seed to restore it in case of it being non-accessible.

[HCP]

Maybe stupid question but i am not sure.If I have public address for bitcoin and public address for ethereum,can i know if these public addresses belong to same seed even if I dont have seed?

In a word, No.

There is no way to link a BTC address to an ETH address unless you know what the common starting point is. In this case, it would be the BIP32 root key (which is derived from the BIP39 seed).

Go here: https://iancoleman.io/bip39/
Generate a random mnemonic, change the coin from BTC to ETH... ETH to BTC... the only constants are the mnemonic, BIP39 seed and BIP39 root key... all the other data used for private key/public address derivation changes.

[pooya87]

Maybe stupid question but i am not sure.If I have public address for bitcoin and public address for ethereum,can i know if these public addresses belong to same seed even if I dont have seed?

In a word, No.

There is no way to link a BTC address to an ETH address unless you know what the common starting point is. In this case, it would be the BIP32 root key (which is derived from the BIP39 seed).

Go here: https://iancoleman.io/bip39/
Generate a random mnemonic, change the coin from BTC to ETH... ETH to BTC... the only constants are the mnemonic, BIP39 seed and BIP39 root key... all the other data used for private key/public address derivation changes.

this is not by design or by force though. this is by choice. in other words you can technically use one seed and then derive the same exact keys for every coin that supports BIP32 and use those keys. but the "choice" is that tools like Ledger use a different derivation path with a hardened key so that they resulting key pairs will be different.
otherwise the technique is the same, during your second depth key extension, instead of using index 2,147,483,649 (0') you use index 2,147,483,709 (60') and you get ETH keys