[bisq-network/proposals] Propose DOA phase periods and fees (#46)

Manfred Karrer notifications at github.com
Wed Oct 10 17:11:09 UTC 2018


As discussed in #45 I will propose here the periods for the DAO phases. Additionally I would use that for suggesting BSQ fees for proposal and voting.

Phase duration is initially hard coded but can be changed via DAO voting. I would prefer though to use that option only if really required and to get it right from the beginning. We collected some experience with the manual process over the last year so we can assume that a months cycle is reasonable.

Note that 1 day is roughly 150 blocks (real average time is about [9.35 min](https://data.bitcoinity.org/bitcoin/block_time/all?f=m10&t=l)). We cannot sync with calendar dates but if we use even numbers and start the genesis block on a even number (if we get it mined, but with high fees that should be doable) we stay in a grid with migth be easier to remember.
The breaks are required to avoid problems with re-orgs and should be at least 10 blocks. I think the longest re-org in Bitcoin was 4 blocks. The BREAK1 might be longer as it can serve as a review/discussion buffer for voters (proposal cannot be changed anymore.

## Phase durations

1. PHASE_PROPOSAL:
Here proposals can be submitted and removed. Editing is not supported but removing and re-sumbitting has the same effect.
Suggested duration: 3600 blocks (about 24 day)

2. PHASE_BREAK1:
As said that break can be longer to add some buffer for discussions/reviews.
Suggested duration: 150 blocks (about 1 day)

3. PHASE_BLIND_VOTE:
As said that break can be longer to add some buffer for discussions/reviews.
Suggested duration: 600 blocks (about 4 days)

4. PHASE_BREAK2:
For reorg protection.
Suggested duration: 10 blocks (about 100 min)

5. PHASE_VOTE_REVEAL:
Here the voter need to be online so that his app can publish the reveal transactions which reveals the secret key for the previously published encrypted votes.
Suggested duration: 300 blocks (about 2 days)

6. PHASE_BREAK3:
For reorg protection.
Suggested duration: 10 blocks (about 100 min)

7. PHASE_RESULT:
This triggers the result calculation. We don't need more then 1 block as it is just a trigger but to stick with even number I suggest 10 blocks. There are no re-org issues here as no new transactions have been created.
Suggested duration: 10 blocks (about 100 min)


The total cycle would be then 4680 blocks which would be about 9.36 min/block if we use the [minutes of a average year](https://www.quora.com/How-many-minutes-are-there-in-a-year) (525 949 minutes / 12 month = 43829 minutes -> 43829/4680=9,365 min/block which fits nicely to the rough [average](https://data.bitcoinity.org/bitcoin/block_time/all?f=m10&t=l)). But as said above we should not intend to stick with calendar months otherwise we will end up to be always slightly off which is probably worse than having our independent cycle.

## Fees

1. Proposal fee: 
To avoid spam we use a fee for submitting a proposal. If a proposal is removed the fee is lost and by re-sumbitting it it need to be paid again. The fee can be changed by DAO voting.
As the fee is defined in BSQ it is subject to BSQ volatility and might require adjustment over time.
As we want to incentivize also small contributions we try to keep the fee low. 
Suggested fee: 2 BSQ

2. Vote fee:
Again as spam protection and to have a regulatory elemente to make voting more expensive if we get too many voters who are not well informed but see voting as "fun" we use a fee here as well. As it can be expected that we will not have both of the mentioned problems we can start also with a rather low fee.
Suggested fee: 2 BSQ

Note: In case of changes by voting there will be a max. ration for the allowed change. It is not defined yet but might be max 4 times in both directions. E.g. a 4 BSQ fee can be changed in one cycle only to max. 1 BSQ or 16 BSQ. But it can be repeated so next cycle it could be 0.25 BSQ or 64 BSQ.



-- 
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/46
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20181010/6399e5d4/attachment-0001.html>


More information about the bisq-github mailing list