Contributions to Wasabi
How to donate to Wasabi Wallet?
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 coordinator 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.
The Wasabikas of the dojo
Who is contributing to Wasabi already?
There are many Wasabikas working with great effort and care to manifest this powerful tool of self defense. Over 35 peers have already contributed to the repository, and more and more supporters are joining the dojo. Four of the main contributors are Ádám Ficsor [co-founder and CTO of zkSnacks Ltd, co-author of the zero link Bitcoin fungibility framework], Lucas Ontivero [lead engineer of zkSnacks Ltd], Dávid Molnár [zkSnacks Ltd employee], and Dan Walmsley [maintainer of Avalonia UI Framework]. For an inclusive list of all the Wasabikas, not just the code developers, please visit the dojo.
Who reviews and merges the pull requests?
As the Wasabi code is libre and open source, anyone has access to review the latest contritions 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 three developers who have the ability to merge code into master branch.
- Ádám Ficsor [co-founder and CTO of zkSnacks Ltd, co-author of the zero link Bitcoin fungibility framework] is the admin of the GitHub repository and has full write access to everything in it, he has the ability to merge any code that he wants.
- Lucas Ontivero [lead engineer of zkSnacks Ltd] is co-maintainer of the GitHub repository, he can merge a pull request, but only when both Ádám and Dávid have reviewed and acknowledged the changes.
- Dávid Molnár is co-maintainer of the GitHub repository, he can merge a pull request, but only when both Ádám and Lucas have reviewed and acknowledged the changes.
What is on the future roadmap of Wasabi development?
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. You can check the ToDo list for a somewhat up-to-date summary of the short term priorities of the next #twoweeks, and what might be implemented in the distant future.
You can become a Wasabika
How should I start contributing to Wasabi?
Thank you for considering to support this beautiful libre and open source project! Nobody owns this software, and thus it is the responsibility of everyone using it to contribute to its growth. Thus 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. You can also see the ToDo list for inspiration of what other Wasabikas are tinkering on. Join our Slack, Telegram or Sub-Reddit, and check out the GitHub, so that you can stay up-to-date with the latest contributions.
Is there a bounty program?
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 serivce. This is provided by zkSnacks Ltd., and in exchange for this additional service the user pays a coordinator fee. In return, zkSnacks is supporting several developers to dedicate their full time to contribute to this open source project. There are also projects like the contribution game where a bounty is paid out to any contributor worthy the praise. Specifically for the documentation, there is a monthly budget of 1.000 USD to cover for the maintenance and expansion of this knowledge archive.
How can I report a bug?
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.
How can I request a feature?
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 bain 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 desperately needed and very welcome. Please first check the existing issues and pull requests if some one 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.
How can I get help and support?
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 peer who has an issue and question, and hopefully one 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. Though often times it is quite useful to start a conversation with other Wasabikas about a specific problem. It is useful to reach out to the contributors on Twitter, Reddit, and Telegram. 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.
What does the Wasabi project need help with?
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!