Is bip32 safe with electrum?

[Menealo]

I have generated a seed to see how it works in different clients and when I import it into electrum a warning message appears telling me that the seed has been created with bip32 and that they do not guarantee the security of the wallet because it does not follow the electrum standard.

It tells me that by not keeping track of the version, they do not ensure compatibility in the future.

my question is:

Is the creation of the seed with bip32 completely safe??

What standard are you referring to that is not contemplated in bip32?


thanks in advance.

[1714106912]

1714106912

[1714106912]

1714106912

[1714106912]

1714106912

[hosseinimr93]

The seed phrase you are talking about is called BIP39, not BIP32.

A 12 word BIP39 seed phrase provides 128 bits of entropy and is secure enough. Do not worry about the safety of your seed phrase.
Even if electrum doesn't support BIP39 seed phrases in the future updates, there won't be anything to worry about. There are many other tools that can be used to derive the private keys from a BIP39 seed phrase.

[Charles-Tim]

It is safe, but these are the remaining standard deviation paths:

Old, BIP 32: m/0'/0/0
Legacy, BIP 44: m/44'/0'/0'/0/0
Nested segwit BIP 49: m/49'/0'/0'/0/0
Native segwit, BIP 84: m/84'/0'/0'/0/0
P2TR, BIP 86: m/86'/0'/0'/0/0

BIP32 is the derivation path that determines the HD wallet, then later followed by the rest mentioned, but BIP39 standard wallets now uses Legacy, nested segwit, native segwit and pay-to-tap-root derivation paths, but BIP32 defines the path.

I expect you to use native segwit or pay-to-tap-root which are the latest, to pay less as transaction fee each time you make transaction.

[BlackHatCoiner]

Yes. Normal behavior, Electrum developers are responsible for the Electrum standard, and not for the rest, that's why they don't guarantee their security. In fact, the software won't allow you generate any seed that doesn't follow the Electrum standard.

You can read more about it here: https://electrum.readthedocs.io/en/latest/seedphrase.html

[Abdussamad]

bip39 seeds don't include the derivation path and the script type so they are not idiot proof. the onus is on the user to figure out the correct derivation path and the script type. electrum seeds include a version number and electrum can use that to figure out the correct derivation path and script type automatically.

[pooya87]

The warning is also telling you that the software you are using (ie. Electrum) can not know or guarantee the security of what you have created elsewhere. In other words it is saying the seed phrase you have may or may not be secure and it is your responsibility. If you want ensured secure seed you should use Electrum itself.

[Menealo]

I need study more about how work derivation path.

Thanks!!!!

[o_e_l_e_o]

I need study more about how work derivation path.

First place to start would be here: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki. This BIP explains how you can use the information at one level of the derivation path to derive the necessary information at the next level.
If you find that too technical, then you could try here instead: https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch05.asciidoc#private-child-key-derivation

Once you understand how child key derivation works, then the next thing to read is this: https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki. This BIP explains the standard for generating derivation paths.

Here's another less technical resource: https://learnmeabitcoin.com/technical/derivation-paths

[hosseinimr93]

It is safe, but these are the remaining standard deviation paths:

The common derivation path which is usually used is m/x'/0'/0' not m/x'/0'/0'/0/0.
For example, m/44'/0'/0' is derivation path used for deriving legacy addresses and refers to the whole wallet while m/44'/0'/0'/0/0 refers to the first legacy receiving address and m/44'/0'/0'/1/0 refers to the first legacy change address.