This is a great proposal and needed. Calendar works the best, but as pointed out decide on one country holiday list and lay down the proposals schedule, helping each one to ensure they participate actively.
15 Likes
Thanks for this proposal very useful and must need.
14 Likes
Why ranked choice vote?
13 Likes
For this proposal. This will bring structure and organized approach for participation. Thanks for your work.
10 Likes
From our experience at other DAOs and time, we think that predicting the timeframe of votes is most important and are excited to see this hopefully come into fruition. However, we are not in favor of a delegate approval process at this time as we don’t think things are too overwhelming. Introducing this only introduces a level of extra politics and lobbying that we think is unneeded for a project or vote to be snapshot held.
5 Likes
gm
I don’t have a strong preference on this, I generally don’t feel the need to structure the proposal process further. A vote lasts 1 week so delegates have any day of the week available to vote.
The risk is that people miss the posting day for whatever reason (the delegate that was supposed to submit it can’t do it that day) and the submission is delayed by 1 week.
In favor of a break between the end of December and early Jan.
Instead, I am against a minimal threshold of comments/endorsements.
It’s always and understandably recommended that proposers gather early feedback from delegates, but we should not enforce it.
Also I second this:
7 Likes
This will bring great value and reduce premature proposals coming on snapshot. There was 100 proposals at one time in snapshot which created fatigue and disinterest. Also there were voting for the sake of it. I hope this wont repeat again with this approach.
6 Likes
I support this proposal and voted accordingly. I think it makes sense to have a fixed date for the DAO on votings and it would be great to have it tracked similiar to how Optimism does it with their calendar.
And I want to echo @GFXlabs comment on the addition to Tally to help enforce it better.
1 Like
I agree , with you , in this batch . You are correct.
Start all votes (Snapshot and Tally) on Thursdays to improve predictability and reduce delegate fatigue.
Introduce a holiday break from December 20 to January 6 to ensure delegates have a regular rest period and return refreshed.
Strongly consider adopting the optional delegate approval process, as it can significantly improve the quality of proposals reaching the voting stage and prevent premature submissions.
The guidelines for emergency proposals to maintain the integrity of the governance process while allowing for necessary flexibility in exceptional circumstances.
This comprehensive communication plan to ensure all delegates and community members are well-informed about the new guidelines and processes. Updating the Ground Rules Topic and making the information easily accessible to new members.
With establish a monitoring and feedback mechanism to assess the effectiveness of the implemented changes and gather insights from delegates. The resulting feedback loop ,continuously refine and improve the governance processes. Consensus can be reach around ,
the proposed timeline:
- Conduct the feedback period from June 24 to July 11
- Hold the Snapshot vote from July 11 to 18
- Begin the first implementation on August 1
Leverage the fact that these changes can be implemented without additional costs to the DAO, and emphasize the potential benefits of increased predictability, reduced delegate fatigue, and improved proposal quality.
1 Like
Voted for Predictability #1 and Predictability + Delegate Approval #2
Reasoning being Predictability is super low hanging fruit and organization should be a priority while I believe Delegate Approval is important but not something that will have as much impact.
1 Like
Voting in favour of predicability only.
We need a way for people to know when they will have to do their job (yes, doing this has the responsibilities of a job knowing the consequence of certain votes; and also has for some compensation attached).
I don’t currently fancy having delegates having to approve it to go to snapshot, because I don’t think we are at a point in which votes are spread enough in enough active delegates. While the numbers might seems to point so, we already have a good amount of non active ones. Likely this will translate in pinging some high vote and usually very active candidates to push for the publication.
Would like to see this option (approval), if fails, to be reconsidered in 6 months, after a) we have more data on this b) we have had redelegation weeks and other initiatives that might help toward this goal c) other initiatives that could further reinforce the governance strength we have in arbi.
Cheers!
1 Like
Proposal Summary
This proposal aims to improve predictability in Arbitrum DAO operations by setting guidelines for voting. Key measures include starting all votes on Thursdays and implementing a holiday break from December 20 to January 6. These changes intend to reduce delegate fatigue and enhance governance efficiency without altering the DAO Constitution.
Supportive Points
- Predictability: Fixed voting dates allow better planning and reduce delegate fatigue.
- Holiday Break: Provides delegates time to rest and maintain long-term engagement.
Discussion Points
- Feasibility of Automation: Can automated voting adjustments be effectively implemented?
- User Acceptance: How will users perceive these changes, and will it affect participation?
- Handling Emergency Proposals: Ensuring efficient processing of urgent proposals.
2 Likes
We are voting in favor of predictability. It is essential for people to know when they need to act, as this role carries job-like responsibilities and compensation. We also agree with JOJO’s point that more information is needed before implementing delegate approval for Snapshot.
On behalf of the UADP, we think the predictability component is the most important. Knowing and having a set timeline for when votes will be posted is the only way we can properly scale DAO votes into the future in our opinion. The piece around having delegates submit approvals we think for now is not needed, but could be revisited very soon. Maybe we can have some sort of “approval” team that just sanity checks proposals before they make it to the forums, or anything else in this regards without requiring an intensive 4 approvals.
1 Like
I really like this proposal, however I’d like to point out a potential vulnerability:
Nothing prevents a user from putting a proposal onchain outside of “acceptable” time frames. If we normalize the practice of, for example, not posting proposals onchain during holidays, or certain time frames, it creates an opportunity for an attacker to create a proposal that might be missed.
Maybe it would be worthwhile to consider entrusting the security council to veto proposals that are created outside of “acceptable” times? Or perhaps encourage the DAO members to always vote “no” on proposals that aren’t at acceptable times?
1 Like
I don’t like Optional: Delegate Approval Process
Thus we are adding too much bureaucracy to a proposal that should help all delegates and the community become more clear. Bureaucracy only complicates processes, and forcing delegates to simply submit to procedures that limit them is a bad idea.
But otherwise, the idea is good.
I am voting in support of predictability only on Snapshot. Having a more structured schedule for voting would definitely allow more efficiency and better planning for delegates. Concerning the delegate approval process, I don’t think it’s necessary as the current system is still working well without major problems or without being too overwhelming. Introducing this threshold would only push for more lobbying and add unneeded steps in the process. I don’t think that it is necessary for the moment.
My highest rank vote was to “Improve predictability”, as that will help all delegates and the ecosystem as whole to enhance the processes within the DAO. The Delegate approval can be added in a later stage, but it does not feel necessary at the moment.
Another great proposal from @entropy - building more structure around proposals and communications (strong agree with @GFXlabs here). I’m less convinced about the 4 delegate threshold given the existing concentration and the fact that proposers already have to find a delegate to post their proposal, which can be a disincentive for people coming to the DAO for the first time. So with that said, I’m voting for aligning incentives (top ranking) but not for the delegate approval.
Blockworks Research will vote FOR the option of Improving Predictability (No Approval Process) on Snapshot.
The proposal addresses an emerging issue within the community. Although Arbitrum communications are somewhat organized, the governance proposal-to-voting pipeline lacks structure. Starting on Thursday is ideal because people tend to be busier toward the end of the week. This timing allows ample time early in the week for deliberation and provides sufficient time in the following period for voting. At Blockworks, we believe that improving the predictability of voting schedules will help reduce delegate fatigue and bring better consistency into the DAO.
However, we would like to caution against a delegate approval process as structured in this proposal because while we understand it is to encourage delegate cooperation outside of the forums, implementing an incentive like this without more structure may inadvertently lead to more politics. We would like to revisit this at a later date though, as we believe that this would be a worthy idea of pursuing in reference to specific proposals, such as highly technical proposals (i.e., posting the block hash to the L1, BoLD upgrades, etc).
1 Like