-
Notifications
You must be signed in to change notification settings - Fork 30
Fix CIP-82 grants documentation #609
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
5b82783
6366985
eada69d
4f98f9c
e50d818
7622091
e991800
ecafa43
653da51
8b0b6e8
104aef3
b7543c0
00c7e01
931ef38
faec28c
9b3d702
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,22 +4,20 @@ sidebar_position: 4 | |
|
|
||
| # Program Structure | ||
|
|
||
| The CoW Grants Program operates under a structured governance framework as defined in [CIP-63](https://snapshot.org/#/cow.eth/proposal/0xa83e2a3e98e9e4dfb41e54efdb94824a5e0e1ec9a2a381bc978ed46ef8f33a24). | ||
| The CoW Grants Program operates under a structured governance framework as defined in [CIP-82](https://snapshot.box/#/s:cow.eth/proposal/0xe84793f122f1c9faa2bb9194faf71567ffd236df616bd60c300eead541f25304), which renewed the program for 2026. | ||
|
|
||
| ## Committee Composition | ||
|
|
||
| The Grants Committee consists of five members: | ||
| CIP-82 established a five-member committee (three community members and two core team members) with a 3/5 signing threshold, designed to prevent core team veto while maintaining distributed control. Following the departure of [@middleway.eth](https://forum.cow.fi/u/middleway.eth) in March 2026, the committee now consists of four members with a 3/4 threshold: | ||
|
|
||
| - **3 Community Members**: | ||
| - [@Kubesqrt](https://forum.cow.fi/u/kubesqrt) | ||
| - [@Chim9](https://forum.cow.fi/u/chim9) | ||
| - [@mfw78](https://forum.cow.fi/u/mfw78) | ||
| - [@mfw78](https://forum.cow.fi/u/mfw78) (Technical Lead) | ||
| - [@Chim9](https://forum.cow.fi/u/chim9) (Grant Steward) | ||
| - [@Sov](https://forum.cow.fi/u/sov) (Grant Steward) | ||
|
|
||
| - **2 Core Team Members**: | ||
| - [@middleway.eth](https://forum.cow.fi/u/middleway.eth) | ||
| - **1 Core Team Member**: | ||
| - [@Master_CoW](https://forum.cow.fi/u/Master_CoW) | ||
|
|
||
| The committee operates as a Gnosis Safe with a 4/5 quorum required for approving grants. | ||
|
|
||
| ## Committee Roles | ||
|
|
||
| Each committee member may serve in one or more of these roles: | ||
|
|
@@ -42,32 +40,35 @@ Each committee member may serve in one or more of these roles: | |
|
|
||
| ## Safe Structure | ||
|
|
||
| As updated in February 2025, the Grants DAO operates with a streamlined Safe structure: | ||
| As updated in January 2026, the Grants Treasury Safe has been migrated to Ethereum Mainnet to simplify accounting and treasury top-ups: | ||
|
|
||
| - The Grants Committee Safe ([`gno:0xCA1F000D520c21C47E6c634DD31b92b91A6338bD`](https://app.safe.global/home?safe=gno:0xCA1F000D520c21C47E6c634DD31b92b91A6338bD)) ([Gnosisscan](https://gnosisscan.io/address/0xCA1F000D520c21C47E6c634DD31b92b91A6338bD)) directly manages grant disbursements | ||
| - CoW DAO acts as the ultimate beneficial owner (UBO) of the Committee Safe | ||
| - This structure improves operational efficiency while maintaining DAO oversight | ||
| - The Grants Committee Safe ([`eth:0xCA1F000D520c21C47E6c634DD31b92b91A6338bD`](https://app.safe.global/home?safe=eth:0xCA1F000D520c21C47E6c634DD31b92b91A6338bD)) manages grant disbursements | ||
| - To improve capital efficiency, funds are released in quarterly increments (25% of the annual allocation) | ||
| - The committee maintains the authority to return up to 75% of idle assets to the CoW Treasury | ||
| - CoW DAO remains the ultimate beneficial owner (UBO) of the Committee Safe | ||
|
|
||
| ## Decision Making Process | ||
|
|
||
| 1. Grant proposals are submitted on the forum | ||
| 2. The committee assigns a steward and reviewer | ||
| 3. Community discussion and feedback takes place | ||
| 4. The proposal moves to Snapshot for formal voting | ||
| 5. With 4/5 committee approval, the grant is executed | ||
| 5. With 3/4 committee approval, the grant is executed | ||
|
|
||
| ## Grant Lifecycle Management | ||
|
|
||
| For each approved grant: | ||
| - A steward oversees the grant's progress | ||
| - A reviewer (internal or external) evaluates technical milestones | ||
| - Monthly payout cycles process approved milestone payments | ||
| - Regular updates are shared with the community | ||
| - Grantee Feedback Forms are completed upon project conclusion to drive operational improvements | ||
| - Regular updates are shared via the [CoW Grants Hub](https://sovs.notion.site/CoW-Grants-Hub-2a8000c0d59080b18bc3f17b694939b7) | ||
|
|
||
| ## Communication and Resources | ||
|
|
||
| - **Forum**: The [Grants Program Forum Section](https://forum.cow.fi/c/cow-grants-program/10) is the primary communication channel | ||
| - **Discord**: The #grants channel in the CoW Protocol Discord serves as a secondary communication channel | ||
| - **Discord**: The [#grants channel](https://discord.com/channels/869166959739170836/1232280402522275850) in the CoW Protocol Discord serves as a secondary communication channel | ||
| - **Snapshot**: All formal votes happen on the [Grants Program Snapshot Space](https://snapshot.box/#/s:cowgrants.eth) | ||
| - **GitHub**: Grant repositories are hosted on the [CoW DAO Grants](https://github.com/cowdao-grants) organization | ||
|
Comment on lines
+64
to
+72
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Description: Check if the Discord channel URL is accessible/redirects properly
echo "Checking Discord channel URL..."
curl -sI "https://discord.com/channels/869166959739170836/1232280402522275850" | head -5
echo ""
echo "Note: Channel-specific Discord URLs typically require the user to already be a server member."
echo "Consider if this is the intended behavior or if an invite link would be more appropriate."Repository: cowprotocol/docs Length of output: 403 Consider using a public invite link instead of a channel-specific URL. The Discord link uses a channel-specific format ( 🤖 Prompt for AI Agents |
||
|
|
||
| For questions about the program structure, please post in the grants section of the forum. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest re-wording to: Value is measured in consistent effort rather than specific outputs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please supply a suggested edit.