[bisq-network/growth] Add semi-automated DAO reporting to website (#245)

[m52go]

Proper DAO reporting is long-overdue, but probably won't be implemented [as originally envisioned (fully automated)](https://github.com/bisq-network/projects/issues/41) for a while. 

Hence this initiative to add semi-automated reporting, which takes place at intervals (e.g., per-day, per-cycle) instead.

## Mid-term workaround

Reporting BTC+BSQ burning, qualitative issuance, BSQ supply, and more in real-time is not a trivial task.

However, thanks to the cycle results JSON dump provided by Bisq itself, reporting basic DAO voting cycle results in a semi-automated way is quite simple. By "semi-automated" I mean creating a script that parses the JSON dump -- this script will need to be run manually after cycles end, but can write most of the report automatically.

Here's what I'm currently working on to get this done:
- write script to generate YAML markup for a custom Jekyll collection for Bisq DAO cycles (obtain data, create new page, write report)
- redirect old dao cycle reports to new dao cycle reports
  - dao cycle reports are currently blog items (`/blog/cycle-N-results`), but after this change, they will become their own [custom collection type](https://jekyllrb.com/docs/collections/) available at (`/dao/cycle-N`)
- overhaul /dao page
  - remove all existing content except "Want to learn more?" links at the bottom
  - add list of automatically-generated dao cycle reports
- remove /stats page
  - move volume graphs to /markets page
  - move bsq supply graph to top of new /dao page

I'll have the script leave blank spaces for proposal commentary and general commentary, both to be filled in by hand wherever appropriate.

This workflow will make DAO reporting more punctual, as I won't have to spend time getting simple data points such as DAO cycle block numbers, time periods, voting statistics, and other items. Currently these numbers must be obtained from Bisq itself and a bunch of script hacked together over time, which makes doing this by hand tedious and prone to pushing off. 

## Next steps

Once this basic DAO result reporting is completed, the next step will be to add supply dynamics (issuance details, BSQ burn, BTC burn, etc) to help put DAO results into context. 
- issuance details will require GitHub issue parsing ([partly already done](https://github.com/bisq-network/growth/tree/master/reporting/compensation-bot))
- BSQ burn will require BSQ explorer polling
- BTC burn will require BTC address monitoring (method TBD)

Whereas voting cycle results are only released once per cycle and require hand-crafted commentary, fee collection (both BSQ and BTC) happens constantly and needs to be counted in an automated way. Thus this next step will require more technical work and probably some kind of intermediate server that aggregates data on intervals. Details are TBD, and will be addressed in a future issue.

## Future

As mentioned above, the long-term hope is for mempool nodes to entirely take over and provide DAO reporting. They are technically in the best spot to do so since they already have real-time BTC and BSQ data, so implementing this any other way is a compromise. But it's past time to get a handle on DAO reporting, so this compromised approach will have to suffice for now.

I'll have a pull request soon for the items covered in the mid-term workaround section, as I don't see those changes as controversial (they're merely moving around data that's already on the website and changing a behind-the-scenes workflow).

I'm making this issue to outline the approach and background to put that pull request into context and how it could fit within a broader initiative to achieve better overall reporting for the Bisq DAO. 

Please let me know if you have any suggestions or concerns.

-- 
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/growth/issues/245
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210412/7b86af33/attachment.htm>