Avatar
Kruw
0b9de7c5e82d26c285690a13cd164149a5a0ee3131b9912e1c0bb36c66b471ab
Taxes are a scam. Inflation is a stealth tax. Bitcoin fixes this.

It depends on the settings the user chooses. Each individual decides which coordinators they connect to and whether they want to cross mix.

You can choose any WabiSabi coordinator with either BTCPay Server's coinjoin plugin or Wasabi Wallet.

Did you install the coinjoin plugin? The discover coordinators and publish coordinator buttons are right there on the first menu:

#m=image%2Fjpeg&dim=507x531&blurhash=%7C24Lq8%3F0.QR7R%25X4R7XgIB%3F%40v%3At%24MzbYoyj0kmMf%25yZ%3AtiR7R%25bEaMtja5J4H%5Bb%3Bj0tQoyaOtPj0I-Dkbrn%2CoybFRQoynm9YD%25RjoMt6ayWBoft7DjInRQt6t7j%5Ba%7BafoyR8braNtQj%5DafbYaMoyMeXfR8o%7BjcjboxV%5BkU&x=93e1bca399c420bb6402f04377863f960aa600b7914e0845a35f35a282420870

#m=image%2Fjpeg&dim=502x311&blurhash=r442%3Bb-%3Bx%5B*ERjM%7BpXV%5BVuw6.j%25_Q%3DpCk%2BR7oxoyyUZ-Vbt%24R7RRo%7BjIjbZpnTa4MNRQV%5BVukBoyijnAZ.Q%3DR8VuVuaybFf%7EQ%3BVbtQi%25aOoxV%5BWB&x=fd1af524de0319308a7a2569054c492558f0d619b0943cad18d295635c6ab3d2

That's like saying no one should use Nostr because a single relay censors notes. Anyone can run a WabiSabi coordinator just like anyone can run a Nostr relay, stop blaming the protocol for the actions of a single user of that protocol.

Yes, it's a very important detail that WabiSabi does not incentivize free Sybil attacks like Whirlpool does: In Whirlpool, the victims of Sybil attacks pay for the block space used by an attacker, who remixes for completely free. WabiSabi is more resilient to Sybil attacks because the attacker has to pay for the block space they use.

Yes, the list of WabiSabi coordinators is published to Nostr so anyone can discover and add them. And yes, BTCPay Server's coinjoin plugin has cross mixing between coordinators built in as a feature.

I think that project has long been deprecated. I use BTCPay Server's coinjoin plugin to run my WabiSabi coordinator, you can enable it with 1 click.

While the naive per round privacy expectations from Whirlpool are objectively smaller than WabiSabi (5 input minimum in Whirlpool compared to 150 input minimum in WabiSabi), that's just an implementation detail. There's no coordinator fee charged for remixing using zkSNACKs' WabiSabi coordinator either.

The advancement that makes the WabiSabi coinjoin protocol so much better is that you gain COMPLETE privacy on your coins, whereas Whirlpool links your transactions together due to common input ownership being revealed and toxic change being created during the premix transaction.

WabiSabi coinjoins gives the same privacy UX to Bitcoin as Monero does to Monero 🎭 The only exception is if you are the largest whale in your coinjoin round - since Bitcoin does not have confidential transactions, a whale's coins might require multiple remixes before gaining full privacy.

You can read more from the mailing list post if you enjoy the technical details: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020202.html

...why would you pay more in fees to get worse privacy using Whirlpool?

WabiSabi coinjoins cost far less in mining fees and provide superior privacy compared to Whirlpool since there's no toxic change created and no common input ownership revealed. You can participate in WabiSabi coinjoins with BTCPay Server's coinjoin plugin, Trezor's coinjoin account, or Wasabi Wallet for desktop.

Replying to Avatar Clark Moody

Dashboard v2 beta test: https://dashboard.clarkmoody.com/

Sign in with nostr to:

- Unlock a couple new modules

- Choose a theme

Not tested on mobile yet. No Whirlpool stats yet. Lots of other stuff missing. Lots of new stuff coming S👀N

Needs WabiSabi coinjoin stats!

That's fine to include a new UTXO if you use coinjoin to turn all the UTXOs in your wallet private.

Huntingsats.com

There's another wallet cracking bounty going out soon 😏

"Tx0 is not a waste"

PLEASE JUST LOOK AT THE CHART, YOU LOSE POTENTIAL ANONSET GAINS AND CONSUME MORE BLOCK SPACE BY PREMIXING:

#m=image%2Fjpeg&dim=1544x1491&blurhash=%7C8SF%40R%25M%7EqMy%25hgLogt8wgtRM_D%25xvR%24xv-qV%40oNxbbakCoLR*aejZWUj%5Bxuj%5D%25MWURQWANFoMW-%3FcMxIU%25gNFWExuRjRkM%7BX7xbnQR%2BbEWBX7spf%2CxakBIonjazWBxHNssEt7kCRPtQV%5BM%7BxuRjIUof%25LRkV%40oeWCWAog&x=3226e49be19cf5640fddfd6ca3bccf5b980d5202c66abdcbe16ee69572319df1

Try BTCPay Server's coinjoin plugin instead of Whirlpool. It's uses an upgraded protocol that's MASSIVELY cheaper, and you can make EVERY spend a coinjoin, without revealing common input ownership or creating toxic change -

nostr:nevent1qqs2lypcwr8d2rjcawh5a534pfq3marffrt5eqawdlurcgt0cqqh27gppamhxue69uhkummnw3ezumt0d5pzpywf5hs6jazpznr0uttp4ex7sf3fa24qldf0fq5gpy78ulsrd7pjqvzqqqqqqyvu22vn

A DISCUSSION ABOUT BITCOIN PRIVACY IS NEVER "NOT WORTH CONTINUING".

YOU'VE SPENT 20 POSTS ARGUING ABOUT SYBIL ATTACKS (that don't apply whatsoever if the coordinator is part of your threat model) WITHOUT EVER ADDRESSING HOW TX0 PREMIXING WASTES BLOCK SPACE AND HARMS PRIVACY COMPARED TO DOING A CUTHROUGH TRANSACTION:

#m=image%2Fjpeg&dim=1544x1491&blurhash=%7C8SF%40R%25M%7EqMy%25hgLogt8wgtRM_D%25xvR%24xv-qV%40oNxbbakCoLR*aejZWUj%5Bxuj%5D%25MWURQWANFoMW-%3FcMxIU%25gNFWExuRjRkM%7BX7xbnQR%2BbEWBX7spf%2CxakBIonjazWBxHNssEt7kCRPtQV%5BM%7BxuRjIUof%25LRkV%40oeWCWAog&x=3226e49be19cf5640fddfd6ca3bccf5b980d5202c66abdcbe16ee69572319df1

A Sybil attacker is not limited to using a single client, they can tx0 with multiple clients in order to participate in the same round. YOU APPARENTLY DO NOT FUNDAMENTALLY UNDERSTAND HOW IT WORKS SINCE YOU THOUGHT FLOODING PAYS LESS IN COORDINATOR FEES COMPARED TO CONSOLIDATING.

I've never "advocated for a coordinator", I'm pointing out technical flaws that waste block space and harm privacy and create unbalanced incentives that subsidize Sybil attacks and all you do is VIRTUE SIGNAL TO DEFLECT FROM REAL ARGUMENTS. If you really gave a shit about "censorship", you would just check the "run coordinator" box on your BTCPay Server coinjoin plugin. Do you have the balls?

Let's talk about dust grinding! Whirlpool is paying 369 sats in fees to create a non private output for 305 sats??? https://mempool.space/address/bc1qp25y8kfywz88myuh7ed3dmx3vv2z2dwuxhjnlv