Author

Topic: BIP39 bug? Is Electrum affected? (Read 401 times)

legendary
Activity: 910
Merit: 1000
February 26, 2017, 08:06:51 AM
#6
Electrum is not affected by that, it's a bug in the bitcore library used by Copay.

Even if you can use BIP39 seeds in Electrum, we do not recommend to do so.
It is safer to create an Electrum seed. For explanation see http://docs.electrum.org/en/latest/seedphrase.html

so if i use a seed generated by electrum itself. even if i moved devices several times and resync the wallet on the new device. no problem.. correct?



Yes. As long as you have the correct seed generated by electrum you can restore and resync your electrum wallet on any new device you like.
full member
Activity: 235
Merit: 100
February 23, 2017, 07:51:34 AM
#5
Electrum is not affected by that, it's a bug in the bitcore library used by Copay.

Even if you can use BIP39 seeds in Electrum, we do not recommend to do so.
It is safer to create an Electrum seed. For explanation see http://docs.electrum.org/en/latest/seedphrase.html

so if i use a seed generated by electrum itself. even if i moved devices several times and resync the wallet on the new device. no problem.. correct?

legendary
Activity: 1896
Merit: 1353
February 23, 2017, 05:28:16 AM
#4
Electrum is not affected by that, it's a bug in the bitcore library used by Copay.

Even if you can use BIP39 seeds in Electrum, we do not recommend to do so.
It is safer to create an Electrum seed. For explanation see http://docs.electrum.org/en/latest/seedphrase.html
copper member
Activity: 2996
Merit: 2374
February 23, 2017, 05:07:33 AM
#3
Electrum will calculate addresses correctly.

The bug seems to affect Copay and BitPay wallets, not electrum.
full member
Activity: 235
Merit: 100
February 23, 2017, 03:05:19 AM
#2
i just read that on reddit. came here for clarifications and steps to take. anyone?
legendary
Activity: 3808
Merit: 1723
February 23, 2017, 02:38:47 AM
#1
I assumed Electrum wasn't BIP39.

Its referring to this bug

https://github.com/iancoleman/bip39/issues/58#issuecomment-281897788
Jump to: