You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thus, the question if and how we can make the upcoming WabiSabi CoinJoin protocol a modular library that Wasabi and other wallets can call?
as far as I understand the initial rational of ZeroLink, it was that many different wallets can use this CoinJoin protocol to reclaim the privacy of their users. Sure, Wasabi is tailor made for privacy in all aspects, and thus it might be the most suitable wallet for using WabiSabi. However, other wallets [especially non xpub leaking full nodes] might want to use WabiSabi too, and there might be no privacy concern with this. This even breaks the assumption that every WabiSabi user is a Wasabi user.
So, this issue is to discuss further on how Wabisabi can / should be compartmentalized.
The text was updated successfully, but these errors were encountered:
If there was an nuget release that handles a lot of the coinjoin internal heavy lifting i'd love to integrate that as a feature in to the blockcore node.
based on #77, @nopara73 says that we should separate the conversation for each module.
Thus, the question if and how we can make the upcoming WabiSabi CoinJoin protocol a modular library that Wasabi and other wallets can call?
as far as I understand the initial rational of ZeroLink, it was that many different wallets can use this CoinJoin protocol to reclaim the privacy of their users. Sure, Wasabi is tailor made for privacy in all aspects, and thus it might be the most suitable wallet for using WabiSabi. However, other wallets [especially non xpub leaking full nodes] might want to use WabiSabi too, and there might be no privacy concern with this. This even breaks the assumption that every WabiSabi user is a Wasabi user.
So, this issue is to discuss further on how Wabisabi can / should be compartmentalized.
The text was updated successfully, but these errors were encountered: