Electrum does not store imported BIP39 seeds in the wallet file... Only the generated xprv, thus it is unable to show the seed and the menu is greyed out.
I believe this is done to avoid users thinking they have an Electrum seed, when it was originally a BIP39 seed... (Electrum seeds are not BIP39 compatible)
Topic: Segwit addresses on Electrum (Read 2538 times)
Hi
I followed the instructions, I created a wallet at the mentioned site (https://iancoleman.io/bip39/ )and then I imported it into Electrum (24 seed words). It worked. But I noticed another difference from the standard wallet: the wallet no longer allows the display of the seed words. It's normal? (I wrote down the words, but this struck me as odd.) Thanks.
I followed the instructions, I created a wallet at the mentioned site (https://iancoleman.io/bip39/ )and then I imported it into Electrum (24 seed words). It worked. But I noticed another difference from the standard wallet: the wallet no longer allows the display of the seed words. It's normal? (I wrote down the words, but this struck me as odd.) Thanks.
Why is it that when trying to create a segwit address, Electrum is providing me a receiving address starting with bc1 and not 39 like my Trezor does? Reading the rest of this thread it looks like I have to create a segwit address somewhere else and then import it into Electrum?
Electrum only supports the creation of bech32 Segwit Addresses (the one starting with bc1) and Legacy Addresses (starting with a 1). For now, the bech32 addresses aren't supported in many places, which means that most services won't allow you to withdraw to this kind of address - which is why it's not recommended to use this kind of address until people start supporting them.Read the previous posts to know how to create and import a Segwit wallet that generate addresses starting with a 3 (not 39) in Electrum;
And will that be view only? Thanks!
If you import with the seed, you will be able to spend the coins.yes, right..
to have segwit addresses starting with a 3 in Electrum just follow these simple steps:
1) generate a bip39, 12 words seed on https://iancoleman.io/bip39/ (use it offline for more security)
2) on electrum choose, File -> New/Restore -> Standard Wallet -> I already have a seed -> click on "options" and choose bip39, write the seed then click next
3) on derivation path path use: m/49'/0'/0'/0
that's all. Remember to save in a safe place the seed as electrum will not show it (read below)
Thank you!
Why is it that when trying to create a segwit address, Electrum is providing me a receiving address starting with bc1 and not 39 like my Trezor does? Reading the rest of this thread it looks like I have to create a segwit address somewhere else and then import it into Electrum?
Electrum only supports the creation of bech32 Segwit Addresses (the one starting with bc1) and Legacy Addresses (starting with a 1). For now, the bech32 addresses aren't supported in many places, which means that most services won't allow you to withdraw to this kind of address - which is why it's not recommended to use this kind of address until people start supporting them.Read the previous posts to know how to create and import a Segwit wallet that generate addresses starting with a 3 (not 39) in Electrum;
And will that be view only? Thanks!
If you import with the seed, you will be able to spend the coins.
Why is it that when trying to create a segwit address, Electrum is providing me a receiving address starting with bc1 and not 39 like my Trezor does? Reading the rest of this thread it looks like I have to create a segwit address somewhere else and then import it into Electrum? And will that be view only? Thanks!
yes. You can have a segwit addresses starting with 3 on electrum (better then the one starting by bc1 used by default as segwit on electrum).
1) generate a bip39, 12 words seed on https://iancoleman.io/bip39/ (use it offline for more security)
2) on electrum choose, create new wallet, I already have a seed, then on "options" choose bip39, paste the seed then click next
3) on derivation path path use: m/49'/0'/0'/0
that's all
You might want to double check the Private keys that Electrum is generating using this method. I just tried this, and the public address and public key are the same as the BIP39 Mnemonic Code Converter... but the private keys are different??!? 1) generate a bip39, 12 words seed on https://iancoleman.io/bip39/ (use it offline for more security)
2) on electrum choose, create new wallet, I already have a seed, then on "options" choose bip39, paste the seed then click next
3) on derivation path path use: m/49'/0'/0'/0
that's all
Electrum private key: LLCKoLPeE5sfCn79kUe9eqWFN32UYip2CjdmsJ48UgbHqxMcBxyD
BIP39 private key: L334f1fqsn3PFk5ceKrN4VKGsAdAstGZsrPWkPMwVj5sHHv9mebd
Pubkey: 02f5bd4fab452b5b850d6131175d5d9ac64079fa230e6e68f6660d1ede80b02dd5
Address: 39tWyTGX4K75Z1Bni9nR2qHWVJjRU5wZRQ
I tried putting the private key generated by Electrum into bitaddress.org and it says "Invalid, version 130 not supported"...
if you check, the addressed generated by electrum using the specific BIP39 seed (derivation path m/49'/0'/0'/0) are the same listed under BIP49 on page https://iancoleman.io/bip39/
so everything is fine. Actually I am using the electrum segwit wallet with "3" addresses with no problems.
here you can find a discussion about this method.
https://pay.reddit.com/r/Bitcoin/comments/7a7i69/electrum_30_release/dp8njgs/
Besides, you can see that when electrum generates a private key of a segwit address, it alerts you that it is not compatible with other wallets (warning: the format of private keys associated to segwit addresses may not be compatible with other wallets). In particular you cannot use a segwit private key on bitaddress.org who generates legacy addresses
yes. You can have a segwit addresses starting with 3 on electrum (better then the one starting by bc1 used by default as segwit on electrum).
1) generate a bip39, 12 words seed on https://iancoleman.io/bip39/ (use it offline for more security)
2) on electrum choose, create new wallet, I already have a seed, then on "options" choose bip39, paste the seed then click next
3) on derivation path path use: m/49'/0'/0'/0
that's all
You might want to double check the Private keys that Electrum is generating using this method. I just tried this, and the public address and public key are the same as the BIP39 Mnemonic Code Converter... but the private keys are different??!? 1) generate a bip39, 12 words seed on https://iancoleman.io/bip39/ (use it offline for more security)
2) on electrum choose, create new wallet, I already have a seed, then on "options" choose bip39, paste the seed then click next
3) on derivation path path use: m/49'/0'/0'/0
that's all
Electrum private key: LLCKoLPeE5sfCn79kUe9eqWFN32UYip2CjdmsJ48UgbHqxMcBxyD
BIP39 private key: L334f1fqsn3PFk5ceKrN4VKGsAdAstGZsrPWkPMwVj5sHHv9mebd
Pubkey: 02f5bd4fab452b5b850d6131175d5d9ac64079fa230e6e68f6660d1ede80b02dd5
Address: 39tWyTGX4K75Z1Bni9nR2qHWVJjRU5wZRQ
I tried putting the private key generated by Electrum into bitaddress.org and it says "Invalid, version 130 not supported"...
Are the segwit addresses available on Electrum wallets ?
yes. You can have a segwit addresses starting with 3 on electrum (better then the one starting by bc1 used by default as segwit on electrum).
1) generate a bip39, 12 words seed on https://iancoleman.io/bip39/ (use it offline for more security)
2) on electrum choose, create new wallet, I already have a seed, then on "options" choose bip39, paste the seed then click next
3) on derivation path path use: m/49'/0'/0'/0
that's all. Remember to save in a safe place the seed as electrum will not show it (read below)
electrum v3.0 changelog:
Quote
# Release 3.0 - Uncanny Valley (not released yet)
* The project was migrated to Python3. Python2 is no longer
supported. If you cloned the source directory, you will need to
run "python3 setup.py install" in order to install the new
dependencies.
* Segwit support:
- P2SH-segwit scripts are supported and can be used with hardware
wallets. To create a segwit wallet, trezor/ledger users will
need to provide a BIP49 derivation path.
- Native segwit scripts are supported with Electrum software
wallets, using a new type of seed. Segwit seeds have version
0x100. Note that the wizard will not create Segwit seeds by
default; users must opt-in with the segwit option.
- Native segwit scripts are represented using bech32 addresses,
following BIP173. Please note that BIP173 is still in draft
status, and that other wallets/websites may not support
it. Thus, you should keep a non-segwit wallet in order to be
able to receive bitcoins during the transition period. If BIP173
ends up being rejected or substantially modified, bech32 wallets
may have to be restored from seed. This will not affect funds
sent to bech32 addresses, and it will not affect the capacity of
Electrum to spend these funds.
- The BIP32 master keys of segwit wallets are serialized using new
version numbers. Version numbers are user visible, with the
following prefixes:
* xpub/xprv : non-segwit wallet
* ypub/yprv : segwit-p2sh wallet
* zpub/zprv : native segwit wallet
* A new version of the Electrum protocol is required by the client
(version 1.1). Servers using older versions of the protocol will
not be visible in the GUI.
* The project was migrated to Python3. Python2 is no longer
supported. If you cloned the source directory, you will need to
run "python3 setup.py install" in order to install the new
dependencies.
* Segwit support:
- P2SH-segwit scripts are supported and can be used with hardware
wallets. To create a segwit wallet, trezor/ledger users will
need to provide a BIP49 derivation path.
- Native segwit scripts are supported with Electrum software
wallets, using a new type of seed. Segwit seeds have version
0x100. Note that the wizard will not create Segwit seeds by
default; users must opt-in with the segwit option.
- Native segwit scripts are represented using bech32 addresses,
following BIP173. Please note that BIP173 is still in draft
status, and that other wallets/websites may not support
it. Thus, you should keep a non-segwit wallet in order to be
able to receive bitcoins during the transition period. If BIP173
ends up being rejected or substantially modified, bech32 wallets
may have to be restored from seed. This will not affect funds
sent to bech32 addresses, and it will not affect the capacity of
Electrum to spend these funds.
- The BIP32 master keys of segwit wallets are serialized using new
version numbers. Version numbers are user visible, with the
following prefixes:
* xpub/xprv : non-segwit wallet
* ypub/yprv : segwit-p2sh wallet
* zpub/zprv : native segwit wallet
* A new version of the Electrum protocol is required by the client
(version 1.1). Servers using older versions of the protocol will
not be visible in the GUI.
There hasnt been an update in quite some time on Electrum - although never change a running team is probably a prudent approach, as the software is very stable and secure IMO.
Are the segwit addresses available on Electrum wallets ?
No, not yet as far as I know. This will likely come in one of the next Electrum updates. I've seem a number of segwit related fixes on the GitHub lately.
Are the segwit addresses available on Electrum wallets ?
Jump to: