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

update why-does-wasabi-only-use-segwit-bech32-addresses #1462

Open
MarnixCroes opened this issue Mar 7, 2023 · 1 comment
Open

update why-does-wasabi-only-use-segwit-bech32-addresses #1462

MarnixCroes opened this issue Mar 7, 2023 · 1 comment

Comments

@MarnixCroes
Copy link
Collaborator

https://docs.wasabiwallet.io/FAQ/FAQ-UseWasabi.html#why-does-wasabi-only-use-segwit-bech32-addresses

change title and add taproot?

@yahiheb
Copy link
Collaborator

yahiheb commented Mar 7, 2023

I wouldn't do it until we can generate taproot addresses.
Maybe I wouldn't change the title, I would just edit the answer mentioning that it is no longer the case and point to another question where we mention support of both segwit v0 and segwit v1 addresses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants