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.

Sign up for GitHub

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

Jump to bottom

SegWit #26

Closed
ruthtern opened this issue Nov 12, 2017 · 6 comments
Closed

SegWit #26

ruthtern opened this issue Nov 12, 2017 · 6 comments

Comments

@ruthtern
Copy link

What is the nature of the work required to add SegWit addresses to bitcoin-tool?
Is it a big job?
@k06a
Copy link

k06a commented May 21, 2018

Same question

@hibiki-sensei
Copy link

Yes, a need it too. Who can add this feature?

@streamofstars
Copy link

I would also appreciate a feature of generating Segwit and Bech32 Segwit addresses.

@streamofstars
Copy link

Recently, there was bech32 option added #36 to --input-format and --output-format so native SegWit addresses (P2WPKH, starting bc1) are now supported. This has not been documented yet, so I have just made a pull req. #39 with appropriate readme changes. I believe that P2SH-wrapped i.e. non-native SegWit addresses (starting 3) are still not supported.

@streamofstars
Copy link

@ruthtern since the bech32 address support is now added, can we assume this issue is resolved? If so, can you please close it?

@ruthtern
Copy link
Author

ruthtern commented Jun 9, 2020

Apologies for the delay. Now closing. Many thanks for this enhancement

@ruthtern ruthtern closed this as completed Jun 9, 2020
@xsoft xsoft mentioned this issue Jun 20, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@k06a @ruthtern @hibiki-sensei @streamofstars