Pages:
Author

Topic: BTCPayServer adds CoinJoin plugin, but there's a catch - page 2. (Read 386 times)

sr. member
Activity: 406
Merit: 443

Here is the rub, however: they will use Wasabi coordinator as their default coordinator.
When you say default coordinator, it means that there is an option for the user to choose other coordinators, or at least there will be.

Quote
The main coordinator run by ZKSnacks submits inputs to a chain surveillance firm.
Are these claims true? How can a privacy-enhancing service provide data to parties trying to reveal identity?
legendary
Activity: 3458
Merit: 6231
Crypto Swap Exchange
From the docs it looks like a simple switch to a different coordinator.

From my PoV the other thing is that even though the Wasabi coordinator has gone full monitoring, they do have support.

In theory, it's a it's works or it does not thing.

In reality, we know that there can be dozens of little things that may not work that need to be dealt with now and then deepening on the way someone tweaked their BTCPay server or some other changes they made. Having a 'default' implementation can help troubleshooting.

Beyond that, use a different coordinator.

-Dave
legendary
Activity: 2310
Merit: 4313
🔐BitcoinMessage.Tools🔑
Great news for those who value their rights to transact privately and protect their financial affairs from prying eyes of undesirable actors. BTCPayServer, free open source software that allows merchants as well as individuals accept bitcoin payments without additional fees or intermediaries, adds a CoinJoin plugin for obfuscation of history of transactions.

What I can say about this news is that it is fascinating to witness how such well-known and widely used services adopt privacy-enhancing technologies  thereby contributing to their development and dissemination among ordinary people. Such additions make people more interested in protecting their privacy, and if it is available out-of-the-box, it is more likely to be used by default. Thus, more people will be making confidential transactions without fuss or muss with the help of convenient tools like that.

Here is the rub, however: they will use Wasabi coordinator as their default coordinator.

According to https://www.nobsbitcoin.com/coinjoin-plugin-btcpay-server/

Quote
The main coordinator run by ZKSnacks submits inputs to a chain surveillance firm.

If this is true then we won't achieve nothing with this plugin; if it is used with default coordinator, we just exchange one type of surveillance for another.

I'd like to see the adoption of privacy-protecting techniques but without Wasabi coordinator who only do the opposite and attacks yhe privacy of users instead.
Pages:
Jump to: