-
Notifications
You must be signed in to change notification settings - Fork 170
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
Allow Stonewall(x2) when spending to non bech32 address #1177
Comments
The way Sparrow presents StonewallX2 though is an upgrade path from Stonewall. The UX of disallowing a Stonewall but allowing a StonewallX2 feels like it may be confusing.
They are always sent to 2 different people in a StonewallX2? Not sure I follow. |
Apologies I was not clear in my explanation. I meant allow both stonewall and stonewallx2 transactions when spending to a non bech32 address. Despite the decoy change output being obvious when not sending to a bech32 address, there is still a privacy benefit allow stonewall and stonewallx2 since an observer does not know if it is a 2 person coinjoin or a fake 2 person coinjoin, therefore:
EDIT: Since Sparrow does not have like-type change output functionality (for obvious UX and UI reasons) like Samourai does, some users who have the same wallet loaded in both Samourai and Sparrow disable that option in Samourai so that their wallet balance is exactly the same in both wallets. |
This is possible with Samourai, and while the true spend is indeed easily identifiable there are still benefits to making a Stonewall(x2) spend here:
The text was updated successfully, but these errors were encountered: