Hi everyone, I’ve been following this conversation and I’m impressed by the depth and breadth of thought that’s been invested into this proposal. I have a few thoughts I shared in the Governance Discord call that I’m posting here for good measure:
On the topic of delegates being actively involved in governance, I wholeheartedly agree. I believe that further steps could be taken to incentivize and ensure active participation of delegates and generate more interest in SafeDAO governance. See 1inch’s Recognized Delegate Program and Aave DAO’s Incentivized Delegate Campaign for examples of delegate compensation models and its effects. This could actually work in conjunction with The Guardians program, wherein a next version could potentially be comprised of the most active existing delegates, and would be a great addition to a SafeDAO Resource Allocation Model. A further step could be, as a community member mentioned in the thread, implementing measures to mitigate the risk of sticky delegation, such as regular delegate re-election or re-delegation campaigns. See Uniswap Foundation’s Delegate Race and Optimism’s Delegate Discovery Initiatives for inspiration.
Regarding the statement that “SafeDAO is stewarded by the Safe Ecosystem Foundation, consistent with the SafeDAO Constitution and the Safe Ecosystem Foundation Charter”, and that “the Foundation acts as a legal wrapper of the SafeDAO treasury, facilitates and administers the governance procedures and implements passed governance proposals if necessary”, I understand the need for a legal entity like the Safe Ecosystem Foundation. However, I agree with other community members who have suggested that the wording here might unintentionally communicate a top-down governance model. Perhaps we could revise the phrasing to better relay the stewardship role of the Foundation, and the agency of SafeDAO and its members.
The concept of “Seasons”, where SafeDAO will change its decision-making process over a specified time frame and run several governance experiments, is pretty interesting, and I see its potential for allowing ongoing iterations and improvements in the governance process. However, further explanation on how a Season is defined and what it encompasses would be beneficial for clarity. A dedicated Glossary or Definitions section in the proposal could serve to delineate such concepts. Maybe we can actually add “Definition of Terms” as a section in the proposal template, encouraging proposal authors to provide additional context and meanings for terms they use.
Lastly, on the points about delegate and token holder participation, this highlights an important aspect of delegate-token holder relationship dynamics. To further clarify and formalize this relationship, I propose we design a “Delegation Agreement”. Delegates could adopt this agreement to define their commitment and decision-making processes in permissionless delegation or state their preferred terms. This, coupled with clear delegate statements, can help provide more transparency in this dynamic.
Some other things I think could be nice to include in a final version of this prop:
- An org chart depicting stakeholder groups within SafeDAO & showing how their responsibilities will overlap or diverge
- Clarify what happens if there isn’t sufficient participation in a voting sprint
- Share how the specifics of voting systems for proposals are decided or could be. Case study examples maybe?
Overall great work, and look forward to seeing the next version of this!