Critical bugs

This page explains what critical bugs are and covers the workflow for devs willing to solve them.

What are critical bugs?

Starting with our dev budget, we will focus in a first step on our most critical core use cases. A core use case is any set of actions that a user must be able to complete in order to successfully trade and/or manage funds using Bisq.

A critical bug is any bug or other issue that:

• impedes users from completing a core use case in Bisq, and/or
• repeatedly lands users in support, and/or
• puts user funds or privacy at risk

Bisq maintainers will scan every day the issues within the Bisq repository and apply the label is:critical bug to all issues that fit the description above. Afterwards they are move to the critical bugs board and sorted by priority.

I want to work on a critical bug

If you want to tackle one of this important issues please leave a comment that you want to work on it to get officially assigned.

We do want to prevent that people are working on the same problem at the same time. When you start working please also to post status updates in our #standup channel on Keybase and do post update comments on your investigations within the issue. This enables other devs to help out if there is need be. Also it is additional documentation on your progress and efforts when you want to post your compensation request.

Do I get compensated by the DAO?

Delivered work on critical bugs is up for compensation. In this case delivered work could mean one of the following:

• the bug was solved and the fix is merged into master
• the bug was investigated and solution is documented, but can't be fixed right now because of an external dependency (e.g. JDK/OpenJFX update required)