Quote from: nc50lc on Today at 02:44:30 AM

Quote from: Husna QA on August 27, 2024, 02:19:16 PM

-snip- and vice versa; the BIP39 seed phrase generated from the Electrum wallet can be restored to Trezor T.

Electrum doesn't generate BIP39 seed phrase, it's just using the same word list by default, although it will work with any word list.
Electrum seed may look the same but if tested to BIP39 wallets, it wont pass the checksum test since it doesn't have a checksum but a reserved number.

Old Electrum seed isn't BIP39 standard compliant either.

Thanks for the correction.
I forgot that Electrum doesn't generate BIP39 seed phrases but uses its seed type even if you generate it using the console (https://bitcointalk.org/index.php?topic=5338687.msg57048278#msg57048278). However, Electrum can still import BIP39 seed phrases.

Quote from: Husna QA on April 18, 2024, 02:34:48 AM

-snip-
However, Electrum does not generate BIP39 seed phrases. Here are some of the reasons mentioned at: https://electrum.readthedocs.io/en/latest/seedphrase.html#motivation

Quote from: https://electrum.readthedocs.io/en/latest/seedphrase.html#motivation

Early versions of Electrum (before 2.0) used a bidirectional encoding between seed phrase and entropy. This type of encoding requires a fixed wordlist. This means that future versions of Electrum must ship with the exact same wordlist, in order to be able to read old seed phrases.

BIP39 was introduced two years after Electrum. BIP39 seeds include a checksum, in order to help users figure out typing errors. However, BIP39 suffers the same shortcomings as early Electrum seed phrases:

• A fixed wordlist is still required. Following our recommendation, BIP39 authors decided to derive keys and addresses in a way that does not depend on the wordlist. However, BIP39 still requires the wordlist in order to compute its checksum, which is plainly inconsistent, and defeats the purpose of our recommendation. This problem is exacerbated by the fact that BIP39 proposes to create one wordlist per language. This threatens the portability of BIP39 seed phrases.

• BIP39 seed phrases do not include a version number. This means that software should always know how to generate keys and addresses. BIP43 suggests that wallet software will try various existing derivation schemes within the BIP32 framework. This is extremely inefficient and rests on the assumption that future wallets will support all previously accepted derivation methods. If, in the future, a wallet developer decides not to implement a particular derivation method because it is deprecated, then the software will not be able to detect that the corresponding seed phrases are not supported, and it will return an empty wallet instead. This threatens users funds.

For these reasons, Electrum does not generate BIP39 seeds. Starting with version 2.0, Electrum uses the following Seed Version System, which addresses these issues.

Electrum 2.0 derives keys and addresses from a hash of the UTF8 normalized seed phrase with no dependency on a fixed wordlist. This means that the wordlist can differ between wallets while the seed remains portable, and that future wallet implementations will not need today’s wordlists in order to be able to decode the seeds created today. This reduces the cost of forward compatibility.