Topic: Wasabi Wallet - Open Source, Noncustodial Coinjoin Software - page 15. (Read 8597 times)
I have one running on my own hardware, yes.
any wallet with zerolink protocol still working with coinjoin ?
I don't know of any. The WabiSabi protocol supercedes Zerolink, so wallets integrating coinjoins have been implementing the new version.
what do you think about payjoin ?
It's cool. Wasabi, BTCPay Server, and JoinMarket all support payjoin.
any wallet with zerolink protocol still working with coinjoin ?
what do you think about payjoin ?
what do you think about payjoin ?
the graph in #256 and #270 message shows some unspent capacity for wasabi 1.0 but it doesn't mean coinjoin is working ?
so wasabi 1.0 wallet can no longer be used for coinjoin operation, is that correct ?
so wasabi 1.0 wallet can no longer be used for coinjoin operation, is that correct ?
Correct, the unspent capacity of Wasabi 1.0 is all the coinjoin outputs from years ago that still haven't moved at all. So this number will not increase any more, it will only decrease.
the graph in #256 and #270 message shows some unspent capacity for wasabi 1.0 but it doesn't mean coinjoin is working ?
so wasabi 1.0 wallet can no longer be used for coinjoin operation, is that correct ?
so wasabi 1.0 wallet can no longer be used for coinjoin operation, is that correct ?
is wasabi wallet 1.0 coinjoin feature still usable ?
No, only Wasabi 2.0 coinjoins have rounds available.
is wasabi wallet 1.0 coinjoin feature still usable ?
Wasabi 2.0.8.1 is out with precise fee controls for coinjoins available directly in the GUI: https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.0.8.1
"FreeSabi" is a bot that tracks the liquidity of 0% fee WabiSabi coinjoin coordinators:
https://x.com/FreeSabiBot
npub1u4rl3zlfa2efxslhypf4v6r8va5e0c9smxyr5676pxkyk0chn33s0teswa
https://x.com/FreeSabiBot
npub1u4rl3zlfa2efxslhypf4v6r8va5e0c9smxyr5676pxkyk0chn33s0teswa
Wasabi v2.0.8 "Hydra" is out! Release notes: https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.0.8
After so many years, Wasabi Wallet finally provide GUI method to choose/change WabiSabi coordinator. Although i briefly tried it and it require me to enter the coordinator link. So i wonder how many user bother search for WabiSabi coordinator run by someone else.
I believe if an individual truly needs to CoinJoin their outputs, what choice would he/she have? And as a community, users should teach and help each other/give others the information they need.
Plus in the Bitcoin community, we are using Open Source Software. It's part of its fundamental philosophy for its more senior members to be some sort of technical support, like the forums in the Linux community.
After so many years, Wasabi Wallet finally provide GUI method to choose/change WabiSabi coordinator. Although i briefly tried it and it require me to enter the coordinator link. So i wonder how many user bother search for WabiSabi coordinator run by someone else.
They have to, otherwise there is no coordinator for them to use and therefore no additional privacy to gain from this wallet.
Wasabi v2.0.8 "Hydra" is out! Release notes: https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.0.8
After so many years, Wasabi Wallet finally provide GUI method to choose/change WabiSabi coordinator. Although i briefly tried it and it require me to enter the coordinator link. So i wonder how many user bother search for WabiSabi coordinator run by someone else.
Personally, I don't have a problem with coordinators that decide to filter what goes through them. But - I have posted about it before - the problem is how accurate are those filters, and how do we dispute their findings if they got it wrong?
As I posted before, I don't know how accurate these filters are. But, Ginger Wallet is a complete fork of Wasabi's client in addition to its coordinator, so it's best to discuss their blacklisting policy in the thread for their wallet instead.
I say it sincerely that that's the list that everyone needed to have, especially during the criticism in the topic about zkSNACKS' decision to filter inputs. Haha.
On the ridiculous petition topic, I repeated over and over that Nostr is the decentralized discovery layer for coordinators. It's been this way the whole time.
Hahaha, I remember that. But we already know that Cobra would do no such thing unless the app/wallet is truly damaging on what Bitcoin stands for. Accepting the trade-offs and different models should be OK.
I believe any of those coordinators are not "working with" on-chain analysts, no?
Ginger Wallet is marketing themselves as actively blocking criminal activity:
Plus were those coordinators already online before zkSNACKS' decision to stop their own coordinator?
Yes, there were several people who had coordinators running prior to this.
Personally, I don't have a problem with coordinators that decide to filter what goes through them. But - I have posted about it before - the problem is how accurate are those filters, and how do we dispute their findings if they got it wrong?
I say it sincerely that that's the list that everyone needed to have, especially during the criticism in the topic about zkSNACKS' decision to filter inputs. Haha.
On the ridiculous petition topic, I repeated over and over that Nostr is the decentralized discovery layer for coordinators. It's been this way the whole time.
I believe any of those coordinators are not "working with" on-chain analysts, no?
Ginger Wallet is marketing themselves as actively blocking criminal activity:
Plus were those coordinators already online before zkSNACKS' decision to stop their own coordinator?
Yes, there were several people who had coordinators running prior to this.
Find new coinjoin coordinators using Nostr:
https://wabisator.com/
https://github.com/Kukks/wasabinostr
https://wabisator.com/
https://github.com/Kukks/wasabinostr
I say it sincerely that that's the list that everyone needed to have, especially during the criticism in the topic about zkSNACKS' decision to filter inputs. Haha. I believe any of those coordinators are not "working with" on-chain analysts, no?
Thank you for posting.
Plus were those coordinators already online before zkSNACKS' decision to stop their own coordinator?
Wasabi v2.0.8 "Hydra" is out! Release notes: https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.0.8
Find new coinjoin coordinators using Nostr:
https://wabisator.com/
https://github.com/Kukks/wasabinostr
Mod note: Consecutive posts merged
Find new coinjoin coordinators using Nostr:
https://wabisator.com/
https://github.com/Kukks/wasabinostr
Mod note: Consecutive posts merged
Does that mean there are default round parameters hardcoded in the client?
The way it works is that each round has a "MaxSuggestedAmount" and clients have a "LiquidityClue". You can read more about the code here: https://github.com/WalletWasabi/WalletWasabi/issues/12500
Here's what round splitting looks like in practice - All 3 of these coinjoins were created at the ~same time with a total of 626 inputs and confirmed in block 845572:
https://mempool.space/tx/4a8fc729fb6aa879db47af7a3b3e34743888650da7bd6f9812c10950634c1189
https://mempool.space/tx/94ab6e19edc63bf29dc586a9c5447a3eb6f00100301212c199837f4d5b20ff84
https://mempool.space/tx/1d423480f59c27d8136f8a1d022461317fa1227860547e62ef5b212dd972f2da
You can see the first tx has 65 BTC while the other two have 10 BTC, so the whales mostly managed to get into the same round as one another. This sorting is a result of the "MaxSuggestedAmount" being set lower in one round than another.
Theoretically, it would might be recommended to avoid them, but practically, there is no internal function within the client that would let me know they're running rounds in parallel, AFAIU. That's something I need to manually check. For example, I need to notice that my coins belong to different coinjoins. Isn't that correct?
Your wallet won't register inputs to two different rounds at once, it only registers inputs for the same round.
Choosing the round isn't manual when there's multiple, it's done automatically based on the round parameters.
Does that mean there are default round parameters hardcoded in the client?If a coordinator is running many rounds in parallel with low minimum input counts/fast input registration timeouts, you should already be avoiding them altogether since their config isn't making good use of scarce block space.
Theoretically, it would might be recommended to avoid them, but practically, there is no internal function within the client that would let me know they're running rounds in parallel, AFAIU. That's something I need to manually check. For example, I need to notice that my coins belong to different coinjoins. Isn't that correct? Jump to: