[bisq-network/proposals] Implement budgeting and improve reporting (#158)

[MwithM]

This is a very difficult task for a DAO, but a very important one.

I am not able to imagine the whole process, but I'm open to changes that I think are mandatory.

Regarding this:
>What is the maximum amount of BSQ the network should issue in the next cycle, based on how much BSQ was burned in the last cycle? Trading volume is too volatile to make projections so these figures probably need to be backward-looking for now.

I would consider the possibility of not taking into account burned BSQ (which can be seen as a kind of revenue) and create a certain fixed (or at least, rigid) amount of BSQ in a certain period. This way all DAO participants would know from advance what is the maximum rate of inflation to expect, even if is a high one at the beginning. I like this feature for BTC (it doesn't matter its demand, the creation of coins is fixed) and I think it would be good for BSQ too.
Another possibility is to calulate total BSQ burned in the last 4 cycles and not exceed this amount divided by 4 on the next cycle, in a similar way we are calculating BSQ/USD [rate for compensation requests](https://github.com/bisq-network/compensation/issues/114). Reading again the proposal, I guess this option, or a similar one, is what @m52go means by backward looking.

I think that chosing a conservative approach on inflation rate (creating the same amount of burned BSQ)  is the best for Bisq. It could look like this way we are limiting possible growth of the project, but it's the best way of making it  long term sustainable from the beginning and something valuable that contributors want to hold and not sell it as soon as they earn.

-- 
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/158#issuecomment-568290727
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191222/4849a923/attachment.html>