[bisq-network/proposals] Separate compensation request submission and voting periods (#40)

sqrrm notifications at github.com
Mon Oct 8 21:32:15 UTC 2018


Sorry to mix the terms @cbeams, I hadn't made a real distinction in my mind if this should be for all proposals or only compensation requests (which are a subset of proposals). I think it should be the same for all proposals though, easier to code (fewer bugs) and they all have the same issue of review comments not pertaining to what's being voted on.

I do indeed want to lock any proposal from being modified for three days to give the community time to comment on it. The fact that it can't be modified means all the comments during the review period are relevant for the proposal being voted on and they can be used to base a judgement on how to vote.

If the proposal could be changed during the review period there could be good discussion and approval from the community. At the last moment the proposal could however be changed and once it's time for vote there would be no comment and review of the actual proposal. I see this as a possible way to sneak through malicious proposals.

### Example in case of modifiable proposals during review period
I create a compensation request for 2000 BSQ. After discussion during the review period it's concluded that I should ask for 3000 BSQ and I update my request. At the last moment I update it again to request 30000 BSQ.

As a voter I would read the comments and conclude that there is nothing contentious about this proposal. The only way to actually figure out that I want to vote `-1` is to go through all the comments, read the details and conclude that the value should be 3000 and not 30000. Even the people that commented on this request need to read through in detail rather than relying on the decision how to vote that was taken during the review period.

## Words
The word review might be a bad name for this, and in the code the phase is called `BREAK1`. I also want there to be proper review with a chance to adapt the proposals to something that has rough consensus before actually publishing the proposal through the bisq software. Maybe we should refer to the last three days of the proposal phase as the review period and just refer to `BREAK1` for the time when a proposal can neither be created/modified nor voted on.

-- 
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/40#issuecomment-427985895
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20181008/cca04927/attachment.html>


More information about the bisq-github mailing list