[bisq-network/bisq] Running the numbers on Bisq DAO revenues (#5171)

m52go notifications at github.com
Fri Feb 19 06:30:27 CET 2021


We can talk about metrics and models all day long but the main issue, as I said in [my very first comment above](https://github.com/bisq-network/bisq/discussions/5171#discussioncomment-351961), is implementation. The practical process of collecting, manipulating, and reporting this data is a critical consideration that should not be overlooked.

I do some of this work on a regular basis already, so let me give you an idea of how it works right now.

Currently done on regular basis:
- get issuance data broken down by user and team (with a script; budget spreadsheet updated by hand)
- get bsq burned (with a script; entire tx history needs to first be downloaded from mempool since the software no longer outputs bsq tx json dumps)
- get bsq supply at specific points in time, like end of cycle (with a script)

In order to compose meaningful public reports on DAO financials, we would also need to:
- get btc trading fees (just became feasible with separate btc addresses -- not automated yet)
- get qualitative issuance data (e.g., compensation line items -- not automated yet)
- get volume data (somewhat automated already, but will probably need more work based on what metrics we want to show)
- distinguish between compensation issuance and reimbursement issuance (not automated yet)
- determine miscellaneous data points like cycle dates, block starts and ends, number of proposals, votes cast, etc (some of this is trivial, and some of it needs access to a bsq explorer)

It would be nice to:
- distinguish between different types of proposals to show governance decisions in each cycle
- track some of the other metrics discussed above

Is the suggestion in this thread to expand this rickety error-prone workflow, build a **public** front end on top of it (whether spreadsheet or website or whatever), and then assign someone to manually keep it all updated every month?

@pazza83 I would love to work with you on this but I would not love to work on a process that's becoming increasingly tedious, unmaintainable, and inefficient.

-- 
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/bisq/discussions/5171#discussioncomment-383158
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210218/3b057105/attachment.htm>


More information about the bisq-github mailing list