BTCPAY SERVER ADDS WABISABI COINJOIN PLUGIN, GIVING OPTION FOR INCREASED PRIVACY \ stacker news ~bitcoin

pull down to refresh

BTCPAY SERVER ADDS WABISABI COINJOIN PLUGIN, GIVING OPTION FOR INCREASED PRIVACY bitcoinmagazine.com/business/btcpay-server-adds-coinjoin-plugin

900 sats \ 16 comments \ @Fezzy 27 Feb 2023 bitcoin

view all related items

20 sats \ 0 replies \ @cryptocoin 27 Feb 2023

Here's the Tweet by Kukks, a BTCPay Server developer, that kicked off the Twitter thread where this was announced:

Today, I'm announcing the beta release of the Coinjoin plugin for @BtcpayServer. After many months of hard but exciting work, this opt-in plugin makes BTCPay Server one of the most extensive privacy-oriented Bitcoin tools around.

https://i.postimg.cc/s3kjV0yw/image.jpg

https://twitter.com/MrKukks/status/1630221270246719489 [Nitter]

1 sat \ 9 replies \ @And1 27 Feb 2023

Does anyone know why they chose Wasabi over Whirpool or JoinMarket?

218 sats \ 5 replies \ @benthecarman 27 Feb 2023

Wasabi's mixes are a million times better, the coordinator just sucks. They aren't using Wasabi's coordinator so you can get all the benefits with none of the downside

1 sat \ 4 replies \ @bitgould 27 Feb 2023

Better in what quality / quantity? Wasabi mixes have "it's private, trust us!" privacy guarantees. As far as I gather, the "anonymity score" is a bunch of ad hoc assumptions that are easy to thwart, especially for the largest participants.

At least whirlpool has a straight forward fungibility model anyone can understand.

426 sats \ 1 reply \ @chytrik 28 Feb 2023

One issue with Samurai is that whirlpool has a low participant count in each mix, and the wallet's default mode of operation dox's a user's addresses to the samurai servers.

So even if you are running dojo (ie, to not dox yourself to their server), the chance of the other mix participants also running dojo isn't that great, and thus your addresses can be doxx'd (by the samurai server) by a simple process of elimination. Running through repeated mixes doesn't do much to fix this.

For a 'privacy wallet', this is pretty egregious imo. There are known ways to fix this issue, that Samurai hasn't implemented for.. some reason?

1 sat \ 0 replies \ @bitgould 28 Feb 2023

agreed

11 sats \ 1 reply \ @benthecarman 27 Feb 2023

No un mixed change is the biggest thing. Removes the biggest foot gun that exists

1 sat \ 0 replies \ @bitgould 27 Feb 2023

if the mix isn't quantified it's all un mixed change. transfers might change this

1 sat \ 2 replies \ @demitasse 27 Feb 2023

nicolas dorier and adam ficsor are friends. i am not a fan of wasabi since they became cucked, even before when they were reusing addresses to be honest

1 sat \ 1 reply \ @Kukks 27 Feb 2023

Neither of them worked on this plugin.

1 sat \ 0 replies \ @demitasse 27 Feb 2023

out of curiosity, why didn't you use a better coinjoin implementation, like one that doesn't work with blockchain surveillance companies to blacklist addresses??

1 sat \ 0 replies \ @ncryppt 27 Feb 2023

based, love it

1 sat \ 3 replies \ @nerd2ninja 27 Feb 2023

Should be payjoin.

446 sats \ 0 replies \ @kristapsk 27 Feb 2023

BTCPay Server supports payjoin for both sending and receiving for a very long time. They were authors of BIP78 payjoin spec.