CIP-0: Template

CIP-Draft: Template

CIP: <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 <>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)>
status: Draft
created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
requires (*optional): <CIP number(s)>
replaces (*optional): <CIP number(s)>

This is the suggested template for new CIPs.

Note :trumpet:: CIP number will be assigned by a forum moderator when the proposal is moved to the second phase.
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.


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.


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 CowDAO.


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.

Safe Transaction Data

Mandatory for every proposal that requires transaction from CowDAO.


Tenderly Simulation

Mandatory for every proposal that requires transaction from CowDAO.
Link to Tenderly simulation


Phase 2 Proposal: Add a link to the corresponding CowDAO Snapshot poll you’ve created.