Natural delegation on DAO voting about proposals

[cbeams]

Implied in @ManfredKarrer's text above, but worth calling out explicitly is that voting zero by default allows the voting process to scale up with integrity. For the last nine months we've had basically every contributor voting on every contribution request, and everyone virtually always votes 1 on every request. This suggests that everyone is reviewing everything, and while that might work with our current numbers of 8–10 compensation requests per month, it will break down miserably if those numbers get much larger. The current process is simply not scalable. Some means of delegated voting is a must, and I like the simplicity, elegance and immediate implementability of this approach.

In reality, I doubt that every stakeholder actually reviewed every contribution request in detail every time, and that some degree of "well, everyone else voted 1, so I will too" has been going on. With the approach outlined above, voting becomes much less burdensome on the individual voter. They should at least have a look at each compensation request, but for those they have no familiarity with or expertise or interest in, they can quickly and honestly vote 0 and move on to the next request.

In this way, when a contributor reviews the results of voting for their compensation request and sees, for example, that all or the vast majority of stakeholders voted 0, it may give them pause, and cause themselves to ask, "Is what I'm working on important?", "Am I representing my work clearly?" and so on. And this may cause them to ask questions and get feedback about what they can do differently in the future to get more voting engagement. The status quo of voting 1 by default obscures how stakeholders may really feel about a given compensation request, whereas voting 0 by default allows the reality of stakeholder sentiment to surface naturally.

[sqrrm]

Having just voted for this month, using 0 when I wasn't familiar with the work, I've got a few thoughts.

The delegation of votes must happen somehow or the DAO won't work. I wonder how to judge requests where I only partially know the details. For example, I might know in detail about half of a request but not know anything about the other half. To vote 1 on a request where I only know about half the details I would have to research the other half at time of voting. The nature of how we work is might be that this is the typical case and that's manageable, I can investigate the half I don't know much about. If on the other hand work is spread even more, say I only know about 10% of the request as do others. I would be unlikely to vote 1 and perhaps the remaining collaborators as well since we all know only 10% each. This might be a non-issue, just a thought.

Another thought that struck me is that if the break between proposals and voting phase is short someone can add a request late in proposals phase giving little time to comment before voting starts. Once voting starts it's less likely someone who has already voted would go back to look at a request to see if there are new comments. If 0 is the default someone can ask for compensation for no work and with no comments on the request it would get all 0 except a 1 from the person with the request and the request would be accepted. How do we avoid such cases, it seems like there is quite a big incentive to try to ask for compensation if the likelihood of acceptance is high.

[ManfredKarrer]

@sqrrm There is the quorum to make issuance by self vote only of new contributors hard. We can make the break a day or so, also the voting will take about 3 days. i also assume that there will always be at least one "senior" stake holder who will check the request out. There are diff. areas and all areas should be covered by one who feels more responsible and therefore will look into any request which falls in his/her area.

[ManfredKarrer]

I close that as it had wide consensus and seems most people are following it.