CIP-Draft: Template
CIP-Number: <to be assigned when moved to phase 2>
title: <CIP title>
author: <a list of the author's or authors' name(s) and/or username(s), or name(s) and email(s), e.g. (use with the parentheses or triangular brackets): FirstName LastName (@GitHubUsername), FirstName LastName <foo@bar.com>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)>
status: Draft
created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
This is the suggested template for new CIPs. (EDIT: it was updated 12 December 2024 to reflect Cow DAO approved changed with the successful CIP-56)
Note 
: You can assign as consecutive CIP number when moving it to the second phase (voting on Snapshot).
When creating a topic to submit your CIP, please name accordingly, CIP-draft: title .
Simple Summary
If you can’t explain it simply, you don’t understand it well enough. Provide a simplified and layman-accessible explanation of the CIP.
Motivation
The motivation is critical for gathering support within the community. Please explain how your CIP is intended to advance CowDAO and / or CoW Protocol, and how it’s aligned with CowDAO’s values.
Specification
The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow for it to be reasoned about by participants in the CoW DAO.
Rationale
The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.
Transaction Data
It is recommended to include transactional data to a CIP. This way, there is time for experts, community and voters to review the transaction and comment below, ahead of the voting period.
Execution details in words
The CIP draft must also include a text description of what the transaction should achieve.
Tenderly Simulation
Tenderly simulation are recommended for making sure that it is clear what will be posted to Snapshot. However, at this stage it is a mere indication because the actual transaction data must be verified on Snapshot.
Mandatory reminder to be added
All transaction that can be directly executed by CoW DAO’s Safe, must be put on Snapshot using the oSnap plugin (which allows for automatic execution on-chain after an implemented challenge period of 72 hours).
If your CIP qualifies as such, you must include this statement:
“Transactions will be executed on CoW DAO’s Safe using the oSnap plugin, contingent upon successful passing of this CIP. When voting on Snapshot, participants are encouraged to verify the content, cross-check Tenderly simulations, and confirm alignment with the CIP’s intent. ”
Github PR
It is considered best practice to link the PR that is voted on (as ultimate source of truth). This is especially critical for solver rule changes.
Once it’s posted to Snapshot (after a minimum of 6 days on the forum, please share a link in the comments below.