Adam Ficsor had a donation address for a few years while he was working alone on Wasabi. It's not the case anymore. Though it's most likely not an issue to accept Bitcoin donations, zkSNACKs team discontinued accepting donations because they don't want to get into accidental legal gray areas. Wasabi has a coordination fee that is capped at 0.3% for every CoinJoin and it became zkSNACKs' main income. To help Wasabi development, just CoinJoin your bitcoins via Wasabi! If you want to read more about fees here is a nice explanation: What are the fees for the CoinJoin.
There are many Wasabikas working with great effort and care to manifest this powerful tool of self-defense. Over 50 peers have already contributed to the repository. Four of the main contributors are Ádám Ficsor [co-founder and former CTO of zkSNACKs Ltd, co-author of the zero link Bitcoin fungibility framework], Lucas Ontivero [lead engineer of zkSNACKs Ltd], Dávid Molnár [CTO of zkSNACKs Ltd], and Dan Walmsley [co-maintainer of Avalonia UI Framework].
As the Wasabi code is libre and open-source, anyone has access to review the latest contributions and browse the open pull requests. The review of any Wasabika is not just deeply appreciated, but desperately needed! Wasabi is cutting-edge, high security software, and there can never be enough eyes seeking and squashing bugs. Especially review by experienced C# developers are vitally important, yet even typo and grammar fixes are necessary.
There are four developers who have the ability to merge code into master branch. Per default, they require at least one approving review by one of the other maintainers before a pull request can be merged. However, since all four are administrators, they can still force the merge without the approval of others, but this will be noticed by many contributors.
- Ádám Ficsor, co-founder and former CTO of zkSNACKs Ltd, co-author of the zero link Bitcoin fungibility framework.
- Lucas Ontivero, lead engineer of zkSNACKs Ltd.
- Dávid Molnár, CTO of zkSNACKs Ltd.
- Dan Walmsley, co-maintainer of Avalonia.
Wasabi is far from complete, there are many Wasabikas contributing every day to make this tool of self-defense even more powerful. Because Wasabi is libre and open-source software, anyone can support the project without asking for permission. Thus it is relatively tricky to give a precise roadmap with what will be implemented in the near and distant future.
Thank you for considering to support this beautiful libre and open-source project! It is the responsibility of everyone using the software to contribute to its growth. Your help is deeply appreciated, and very much needed! First please read the contribution checklist to get introduced to the project and to start out in the right direction. Join our Slack and check out our GitHub repository, so that you can stay up-to-date with the latest contributions.
Yes! The beauty of Wasabi is that it's not just a very awesome wallet by default, but it has the additional opt-in CoinJoin service. This is provided by zkSNACKs Ltd., and in exchange for this service, the user pays a coordination fee. In return, zkSNACKs is supporting several developers to dedicate their full time to contribute to this open-source project. There are also contribution games where a bounty is paid out to any contributor worthy the prize.
Code is speech, and can never be perfect. Thus it is expected that there are many known and unknown bugs, quirks and issues in Wasabi. Such a complex software requires constant and rigorous review by the developers and the users, this is everyone's responsibility working with Wasabi.
When you stumble upon an issue that needs fixing, please first check the open issues and pull requests if there is already someone working on it. If yes, then you can comment your situation and bug report under the open issue. If no, then please consider to open a new issue and give a detailed report on the problem. It is especially helpful when you provide a step-by-step guide on how to reproduce what you have found. There is constantly a lot of work done to the code base, thus it's good to know which version of Wasabi, and what operating system you are using. In some cases it might be useful to see your logs, though please consider your privacy and encrypt this data properly in direct communication with the developers.
If you find a bug that puts users' privacy or security at serious risk, please take great care with responsible disclosure! Send an email to [email protected], preferably using PGP encryption 21D7 CA45 565D BCCE BE45 115D B4B7 2266 C47E 075E.
Wasabi is a quite beautiful piece of software already. Yet there are also 1001 things that could be just a little better, or even quite substantially superior. The beauty and bane of libre and open-source software is that it is never complete, there is always more work to be done.
Regardless if you are a new user of Wasabi, or a veteran black belt Wasabika, any suggestions on how to improve are very welcome. Please first check the existing issues and pull requests if someone has the same feature request as you. If yes, then you can comment your desired improvement under the open issue. If no, then please consider to open a new issue and give a detailed request. It makes sense to first explain the problem you have in the incumbent version of Wasabi, this is the place to express your frustrations and annoyances. Then describe the solution that you have envisioned, with all the nuances and details of how this would fix your problem. To flesh our your argument, please consider alternatives and different approaches to this feature request.
You are already on the right track by first checking this documentation for the knowledge you are seeking. It's likely that you are not the first person who has an issue or a question, and hopefully someone has curated the answer in here already. You can use the search function in the top navbar to look for a specific topic, and the sidebar menu as a table of content. You can also use our GitHub Discussions to find solutions to different issues and to ask questions if necessary. If your trouble is specific to the code, then it might also be suitable to check the existing GitHub issues and open a new one.
Wasabi is libre and open-source software, thus it relies on the support of several contributors on all fronts. Of course, this includes coding new features, bug fixes and stability improvements. Yet just equally important is the review of the commits of all other Wasabikas. It's not just the contributions to the code, but also to the documentation and the effort to educate peers using Wasabi. This includes education in meatspace tribe gatherings, but also in cyberspace peer support. So basically, we need help with building and shilling Wasabi!