Skip to content
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

[Priority: High] Integrate Segregated Witness #201

Open
nopara73 opened this issue Sep 1, 2017 · 2 comments
Open

[Priority: High] Integrate Segregated Witness #201

nopara73 opened this issue Sep 1, 2017 · 2 comments

Comments

@nopara73
Copy link
Contributor

nopara73 commented Sep 1, 2017

BIP141 - SegWit was introduced as a soft fork to the Bitcoin network. In a nutshell it makes transactions cheaper and fixes transaction malleability.
BIP173 - Bech32 SegWit addresses were introduced lately by Pieter Wuille and they are expected to get widely used in the near future.

Traditional Bitcoin address: 1F1tAaz5x1HUXrCNLbtMDqcw6o5GNn4xqX
SegWit address: bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4
Bech32 SegWit address: lost1qsyq7yqh9gk0szs5

Needed For Integration

Receive

Receive should be enabled for SegWit and Bech32 addresses, optionally traditional addresses, too.

Send

Sending should work on traditional, segwit and bech32 addresses. Optionally p2sh, p2wsh should be supported, too.

Additional Notes

NBitcoin supports for all types.

@nopara73 nopara73 changed the title What is the state of SegWit integration? [Priority: High] Integrate Segregated Witness Sep 1, 2017
@dev0tion
Copy link
Collaborator

This would be great. What needs to be done UI-wise?

@nopara73
Copy link
Contributor Author

Nothing yet.
It's not clear at this point if integrating segwit would mean dropping receiving to traditional addresses or not.
Also we'll have two kind of segwit addresses: P2WPKH and bech32.

So there's three way we can integrate it:

  1. Receive only to bech32
  2. Receive to bech32 and p2wpkh
  3. Receive to bech32, p2wpkh and p2pkh.

The ability of wallets to send to p2wpkh is quickly growing, I'd vote for completely dropping the support for receiving p2pkh. While adding support for sending p2pkh, p2sh, p2wpkh, p2wsh, 2 types of bech32 and even for scriptpubkey in itself.
While ability of wallets to send to bech32 is only slowly growing I'd even vote for not allowing to receive p2wpkh, only to bech32. I'd say Breeze is the wallet of the future, so why not look forward instead of backwards?
Nevertheless these are my preferences, I don't insist to any of those.

@bokobza bokobza added this to the vNext milestone Sep 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants