To reach the goal to remove the role of the Burningman we propose the distribution of trade fees (https://github.com/bisq-network/proposals/issues/383) and the distribution of the funds from the delayed payout transactions of trades ending up in arbitration (proposal not published yet) to contributors based on their contribution requests. This require that the traders have the DAO data available.
Currently users can choose to deactivate the DAO in the Settings and therefore would not have any DAO data.
If we permit that, we still need a fallback solution for such traders, making the complete removal of the BM role impossible.
This proposal suggests to remove the option to deactivate the DAO in the settings as well as from the program arguments.
Users who have disabled it would switch automatically to the enabled state.
If users would still manage to deactivate it (e.g. by changing the code) their trades would fail.
This change might increase also the chances that users use BSQ for paying the trade fee as a positive side effect.
The downside is that users might need a bit more bandwidth for syncing the DAO data but even if that data sync fails due bad connectivity the app is still usable and as long the user has the data of the last or second last DAO cycle a trade can be completed (details will follow in a future proposal about the delayed payout transactions).
To reach the goal to remove the role of the Burningman we propose the distribution of trade fees (https://github.com/bisq-network/proposals/issues/383) and the distribution of the funds from the delayed payout transactions of trades ending up in arbitration (proposal not published yet) to contributors based on their contribution requests. This require that the traders have the DAO data available. Currently users can choose to deactivate the DAO in the Settings and therefore would not have any DAO data. If we permit that, we still need a fallback solution for such traders, making the complete removal of the BM role impossible.
This proposal suggests to remove the option to deactivate the DAO in the settings as well as from the program arguments. Users who have disabled it would switch automatically to the enabled state. If users would still manage to deactivate it (e.g. by changing the code) their trades would fail.
This change might increase also the chances that users use BSQ for paying the trade fee as a positive side effect. The downside is that users might need a bit more bandwidth for syncing the DAO data but even if that data sync fails due bad connectivity the app is still usable and as long the user has the data of the last or second last DAO cycle a trade can be completed (details will follow in a future proposal about the delayed payout transactions).