Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modularize WabiSabi #78

Open
MaxHillebrand opened this issue May 1, 2020 · 1 comment
Open

Modularize WabiSabi #78

MaxHillebrand opened this issue May 1, 2020 · 1 comment

Comments

@MaxHillebrand
Copy link
Member

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.

@dangershony
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants