[bisq-network/proposals] Require the Burning Man and Refund Agent roles to maintain a Google Docs spreadsheet (#263)

[wiz]

> _This is a Bisq Network proposal. Please familiarize yourself with the [submission and review process](https://docs.bisq.network/proposals.html)._

It is currently very difficult to track or audit the financials of the Bisq DAO. For example, I can see the [Bisq donation address](https://mempool.space/address/3A8Zc1XioE2HRzYfbb5P8iemCS72M6vRJV) has now received over 50 BTC, which also contains user funds that got refunded, but where is the accounting of that 50 BTC? How much of it was actual BTC revenue from trading fees, and how much of it was trading capital donated to Bisq? How much of it was refunded by the Refund Agent? Can anyone answer these questions at all? Is anyone tracking the DAO's financials?

AFAIK this data only exists scattered among random GitHub comments in a long thread that's not easy to follow or verify. In the past while trying to follow the money, I found an obvious mistake where 2.14 BTC was accidentally paid out twice and lost by the Refund Agent. As he said in [his reimbursement request to the DAO for the lost 2.14 BTC](https://github.com/bisq-network/support/issues/461#issue-661744919), it's not entirely his fault, the "system" is just really bad.

I propose that the BM and RA simply collaborate on a simple Google Docs spreadsheet. It does not need to be fancy, but the numbers should absolutely add up, and my questions at the top of this proposal should be able to be answered with a quick glance. Simple mistakes like the ones would likely have been avoided by using a simple spreadsheet, and users should be able to easily verify the data contained in it by clicking on blockchain explorer links.

If the BM and RA do not want to create the spreadsheet themselves, perhaps we can make a BSQ bounty for someone who is good with spreadsheets for this very critical task of auditing the DAO financials.

cc @burningman3 @refundagent

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/263
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201018/c5d66f3f/attachment.html>