[bisq-network/bisq] Show changes in BSQ Supply over time (PR #6106)

[Christoph Atteneder]

I don't t hink it is a good idea to also hardcode the values post-DAO as well. Doing it like this someone needs to update the values for each release (we have this issue already on the website, where it is stuck at cycle 29 - @m52go is there someone who is aware of doing this instead of you?). As total issued and total burned BSQ are already calculated for this graph it would be better IMO to use those than to hardcode the values. Also it would make the graph more correct post-DAO as ATM the total cycle values (not monthly) are shown, no matter if yearly, monthly or daily is selected.

![Bildschirmfoto 2022-03-21 um 12 38 19](https://user-images.githubusercontent.com/170962/159253902-1f8aed08-f939-4fac-b797-f4d38f27894a.png)
![Bildschirmfoto 2022-03-21 um 12 38 24](https://user-images.githubusercontent.com/170962/159253907-fd879d5f-baa6-4ef3-a3e0-abfca9133304.png)
![Bildschirmfoto 2022-03-21 um 12 38 31](https://user-images.githubusercontent.com/170962/159253911-5b132411-9fec-41d2-b4d6-b35cb1cbf174.png)
![Bildschirmfoto 2022-03-21 um 12 38 44](https://user-images.githubusercontent.com/170962/159253912-9869358d-2756-4911-8064-9dbdcadcec23.png)


-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/6106#issuecomment-1073793582
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/bisq/pull/6106/c1073793582 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220321/1bdab9f7/attachment-0001.htm>