New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What do users of electrum have to do to take advantage of segwit? #2791
Comments
The current release (2.9.3), or the master branch, does not yet have segwit ready to be used on mainnet. It can only be used on testnet at the moment (as evident in the commits you referenced, such as af54ba0). I believe p2sh-p2wpkh type addresses (the successor of p2pkh, the current '1' type addresses) are fully implemented, but p2sh-p2wsh addresses (which would be needed for e.g. multisig) are not. Hence, most users will need to wait for a new release of Electrum that at least enabled the currently implemented functionality on mainnet, and then create new "segwit" type wallets (to clarify, this means a wallet with new "seed words", as the current code implies that a wallet having segwit addresses is a property of the seed). |
@SomberNight Thanks for the information! Mind if I add that info to the readme for this project? If that's not the right place for it, where can I add it? Any idea when a version of electrum that supports segwit type wallets might be released? |
soon |
@ecdsa Cool, but many users (myself included before this thread) are probably assuming Electrum supports Segwit today, since there's been so much time (over a year) to upgrade. I think users should have the info, about how segwit will be dealt with, now (ie regardless of how soon support might happen). How can I help make that happen? I'm actually surprised p2sh-p2wpkh addresses weren't made the default like a year ago - my understanding is that its been about that long since we've known users will need updated addresses to use Segwit. Had that been done, most people now might not even have had to switch to a new wallet. Electrum is a popular client and getting users on Segwit is important to get people on segwit and lower fees so the community will stop yelling about how they can't buy coffee or whatever. |
Coins sent to a p2sh-p2wpkh address, before SegWit activation, are spendable upon presenting the redeemscript without a valid signature. They are only protected by the hash algorithm of p2sh. That is, anyone that can present a script that has So that is why
|
Ahh, I didn't know that. Thanks again for the helpful info @SomberNight ! Still wondering how I can help get this information out there : ) |
Hello, I do realize that this are noob questions but I can not find too many straight answers... |
@bainsmit Your addresses starting with 1 will remain fully functional in the foreseeable future. You can send between segwit and non-segwit addresses in both directions. |
Trezor now supports segwit. If I create a hardware wallet type in Electrum using the Trezor, will Electrum automatically see and support the segwit addresses? |
@Engelberg Its not quite automatic, but not difficult. Here's the guide I used to setup my Trezor through electrum: https://blog.trezor.io/using-trezor-with-electrum-v3-a0b9bcffe26e?gi=96884803f8fc |
Segwit is coming out tomorrow. I've heard (from here) that wallets must generate P2SH addresses (that start with a '3') in order to use segwit. But all the addresses I see generated in my Electrum start with '1'. Is there anything users have to do to start using segwit? Could something be added to the readme or website to clarify to users what they need to do, if anything, for segwit?
I've checked through a bunch of commits, but nothing makes it clear to me how segwit will be usable:
The text was updated successfully, but these errors were encountered: