CIP-Draft: Change CoW DAO's (cow.eth) Snapshot space settings

CIP: <to be assigned when moved to phase 2>
title: Change CoW DAO's (cow.eth) Snapshot space settings
author: @middleway.eth
status: Draft
created: 2023-09-08

Simple Summary

This proposal aims to remove admins and authors from CoW DAO’s Snapshot space, add community moderators, and introduce a token threshold for submitting new proposals.
In order for the DAO to better handle Snapshot space setting in the future, it is proposed to change the snapshot text record on cow.eth where the snapshot space settings are defined. Replacing the IPNS record link, to an IPFS record link pointing to a JSON file with the full space settings will make cow.eth the sole owner that is able to change the snapshot settings.
In addition it is proposed to extend cow.eth domain registration by 6 years securing it until 2030. This will cost roughly 2.4 ETH to be requested from the trasury management safe.

Motivation

Following the successful implementation of CIP-30, it became clear that CoW DAO’s snapshot settings have a more critical role in the proposal execution process as they represent the source of truth of proposal validity for oSnap execution. Therefore it’d make sense to reomove all admins making CoW DAO’s Safe the sole admin that can change the cow.eth snapshot space settings. This will remove the risk of snapshot setting being changed by a single admin which might change execution validation on oSnap.

This change will lead the community to not be able to easily assign authors ad hoc according to ongoing governance process needs. Therefore it is proposed to pick a COW token holdings amount (10k COW as a placeholder, but open for discussion) that will allow anyone holding that amount to post new proposals in the snapshot space. This is also positive as it makes the technical governance process more inclusive and open.

As seen in other Snapshot spaces (for example gnosis.eth) this approach sometimes results in spam proposals or proposals that do not comply with the governance precess requirements. In order to mitigate this problem, it is proposed to community moderators who will have the power to filter such proposals as needed, mitigating spam or non-complying proposals who might be submitted by any COW holder with the required holding threshold.

Specification

The snapshot text record on cow.eth will be changed to an IPFS record which includes the proposed snapshot space settings.

In addition, a call will be made to extend cow.eth registration by 6 years.

  • It is still pending to nominate a list of addresses to become Snapshot space proposals moderators.

Rationale

Using an IPFS record makes it easier for the DAO to make changes to the snapshot space settings using an onchain transaction by the DAO through oSnap proposal or by Safe signers if needed.
Extending registration of cow.eth will help avoiding a situation the DAO losing access to this domain.

Execution

  • Repo (link) including the JSON file copied from CoW DAO’s existing settings (link)
  • JSON file hosted on IPFS (link)
  • Testing space (cowtesting.eth) configured with the above IPFS file in its snapshot ENS text record (link)

Safe Transaction Data

TBD

<payload>

Tenderly Simulation

TBD

Snapshot

TBD

3 Likes

what permissions do moderators hold besides removing proposals?

I agree this is a good way forward. The 10k COW threshold sounds like a fair barrier to entry to prevent spam. We need to define what is considered a non-complying proposal, and this should be shared with the community to ensure future compliance.