I am providing a
FREE coinjoin coordination service using the WabiSabi protocol. A coinjoin is a privacy enhancing Bitcoin transaction that combines inputs from multiple users. The more users that participate in the coinjoin, the greater privacy all participants receive.
Wasabi Wallet and
BTCPay Server both support the WabiSabi coinjoin protocol and use Tor by default so the coordinator is not trusted with any information.
Of course! Here is the adapted message for posting in the forum thread, addressed to the topic starter and participants:
---
Hello everyone,
We previously used the zkSNACKs coordinator for executing CoinJoin rounds. We use WasabiWallet in Headless Wasabi Daemon mode along with our own round manager, which controls CoinJoin rounds via RPC.
We decided to connect to your coordinator, but we see in the wallet logs that it cannot connect to your backend, reporting that your server returns a 307 (redirect to kruw.io)
We start the wallet daemon with the following parameters:
'--wallet:HotWallet',
'--wallet:ColdWallet',
'--jsonrpcserverenabled=true',
'--dustthreshold=0.00002',
'--network=main',
'--enablegpu=false',
'--usetor=true',
'--datadir=/wasabi/data',
'--downloadnewversion=false',
'--mainnetbackenduri=https://btcpay.kruw.io/plugins/wabisabi-coordinator/',
'--maxcoordinationfeerate 0.003',
The wallet (daemon) is built from the latest source code, commit 569d20ce5a70b90e2a6b6ef3c259ea8cc87e5bf9 from June 28, 2024.
Could you please advise what might be the issue and how we can start using your coordinator?
Thank you!