Fix CIP-82 grants documentation#609
Conversation
Update the Grants Program documentation to align with CIP-82
Update the Grants Program documentation to align with CIP-82 * Added Volume Grants * Added Partnership Incentives to Bonus section
Update the Grants Program documentation to align with CIP-82 * Updated committee composition and treshold * Updated Safe structure details * Updated Grant Lifecycle section * Added direct link to the #grants channel on Discord
Update the Grants Program documentation to align with CIP-82 * Added emphasis on outcome-based results * Added mention of feedback form for After Approval
Update the Grants Program documentation to align with CIP-82
Update the Grants Program documentation to align with CIP-82
Update the Grants Program documentation to align with CIP-82
- Fixed truncated snapshot proposal hash (was missing 'a2bb9194') - Added forum discussion link for CIP-82 - Fixed typo: 'focusses' → 'focuses'
Removed chatbot-style "Key Updates for 2026" section that was accidentally left in the document by the author.
The Grant Agreement link was changed to a non-public GitHub repo URL. Restored the original IPFS link consistent with how-to-apply.md.
Added link to https://github.com/cowdao-grants in both how-to-apply.md and program-structure.md resource sections.
The linked Process Guide and Grant Agreement predate CIP-82 and still reference Gnosis Chain payouts. Added a notice directing applicants to follow CIP-82 / Ethereum Mainnet guidance where there are discrepancies.
CIP-82 defines 4 focus areas, not 5. Removed fabricated 'Ecosystem Growth' and 'Integrations' areas. Added 'Volume Incentive Program' which is a CIP-82 focus area. Updated descriptions to match CIP text.
CIP-82 defines committee performance bonuses as a quarterly pool of up to 1,500 xDAI per member per month via peer review, not 10k per grant. Added cash-on-cash clarification for partnership incentives.
CIP-82 established a 5-member committee with 3/5 threshold to prevent core team veto. Document middleway.eth's March 2026 departure and the resulting 3/4 threshold adjustment for transparency.
Consistent with program-structure.md - note original 5-member design with anti-veto rationale and current 4-member state.
|
@mfw78 is attempting to deploy a commit to the cow Team on Vercel. A member of the Team first needs to authorize it. |
|
All contributors have signed the CLA ✍️ ✅ |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe PR updates CoW Grants governance docs from CIP-63 (Jan 2025) to CIP-82 (Jan 2026), revising budgets, grant types, incentive structures, committee composition/thresholds, treasury network (Gnosis → Ethereum), quarterly release mechanics, evaluation criteria, and post‑grant reporting across four grant docs. ChangesGrants mandate, budgets, and strategic focus
Grant types and incentives
Application process, evaluation and post‑approval steps
Committee composition, Safe mechanics, and operational rules
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/governance/grants/program-structure.md (1)
50-56: Consider hyphenating "Decision Making" for grammatical correctness.The heading "Decision Making Process" would be more grammatically correct as "Decision-Making Process" when used as a compound adjective.
📝 Suggested fix
-## Decision Making Process +## Decision-Making Process🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/governance/grants/program-structure.md` around lines 50 - 56, Change the heading "Decision Making Process" to the hyphenated form "Decision-Making Process" by updating the header text (the string "Decision Making Process") in the markdown so the compound adjective is grammatically correct.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/governance/grants/program-structure.md`:
- Around line 64-72: Replace the channel-specific Discord URL used in the
"**Discord**: The [`#grants` channel]" line with a public invite link (or a
permanent invite) so external users can access the server without needing prior
membership; update the markdown link target for the "#grants channel" anchor to
the invite URL and keep the visible text unchanged so the entry still reads
"**Discord**: The [`#grants` channel]".
---
Nitpick comments:
In `@docs/governance/grants/program-structure.md`:
- Around line 50-56: Change the heading "Decision Making Process" to the
hyphenated form "Decision-Making Process" by updating the header text (the
string "Decision Making Process") in the markdown so the compound adjective is
grammatically correct.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 32ca2f3e-89b2-4ebc-a09e-73232a1f21b5
📒 Files selected for processing (4)
docs/governance/grants/README.mdxdocs/governance/grants/grant-types.mddocs/governance/grants/how-to-apply.mddocs/governance/grants/program-structure.md
| - 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 |
There was a problem hiding this comment.
🧩 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 (https://discord.com/channels/869166959739170836/1232280402522275850). While this URL is valid, users who aren't already members of the CoW Protocol Discord server won't be able to access it directly and will see a "page not found" or "private" message. For documentation, a public server invite link would provide better accessibility.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/governance/grants/program-structure.md` around lines 64 - 72, Replace
the channel-specific Discord URL used in the "**Discord**: The [`#grants`
channel]" line with a public invite link (or a permanent invite) so external
users can access the server without needing prior membership; update the
markdown link target for the "#grants channel" anchor to the invite URL and keep
the visible text unchanged so the entry still reads "**Discord**: The [`#grants`
channel]".
|
I have read the CLA Document and I hereby sign the CLA |
|
recheck |
| - Your role requires flexibility in addressing emerging needs | ||
| **When to choose:** | ||
| * Your contribution involves ongoing work or maintenance | ||
| * The value is in consistent effort rather than specific outputs |
There was a problem hiding this comment.
Suggest re-wording to: Value is measured in consistent effort rather than specific outputs
There was a problem hiding this comment.
Suggest re-wording to: Value is measured in consistent effort rather than specific outputs
Can you please supply a suggested edit.
There was a problem hiding this comment.
I did! See above. It's not the same as the original copy.
There was a problem hiding this comment.
Applied in 8207ebc.
Quick note for next time — your re-wording was written as plain prose rather than in a GitHub '```suggestion' block, so I had to copy-paste it in manually instead of using the one-click "Commit suggestion" button. Wrapping the new line in a suggestion block makes adopting these tweaks a single click rather than a round-trip.
pretf00d
left a comment
pretf00d
left a comment
There was a problem hiding this comment.
left comment in response to my comment.
| - Your role requires flexibility in addressing emerging needs | ||
| **When to choose:** | ||
| * Your contribution involves ongoing work or maintenance | ||
| * The value is in consistent effort rather than specific outputs |
There was a problem hiding this comment.
I did! See above. It's not the same as the original copy.
3 participants
Summary
Builds on the work from #604 by @theChim9 with the following corrections:
Test plan
:::noteadmonition renders correctlySupersedes #604.
Summary by CodeRabbit
Documentation