Skip to content

Conversation

@bram-vdberg
Copy link
Contributor

@bram-vdberg bram-vdberg commented Dec 3, 2025

Description

This PR updates the documentation reference to bonding pools to include all networks CoW Protocol is currently active on.

Changes

  • Add missing networks
  • Minor language changes

Summary by CodeRabbit

  • Documentation
    • Clarified bonding pool setup timeline — reduced pool size now progresses over the following year.
    • Minor wording and grammar improvements for clarity.
    • Expanded vouching contracts list to include Avalanche, Polygon, Lens, BNB, and Linea.

✏️ Tip: You can customize this high-level summary in your review settings.

@bram-vdberg bram-vdberg requested a review from fhenneke December 3, 2025 09:52
@bram-vdberg bram-vdberg requested a review from a team as a code owner December 3, 2025 09:52
@vercel
Copy link

vercel bot commented Dec 3, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
docs Ready Ready Preview Dec 3, 2025 10:53am

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 3, 2025

Walkthrough

Updated documentation for bonding pools: clarified that the reduced-bonding-pool size progression occurs over the following year, adjusted wording from "the solver" to "a solver with a reduced bonding pool," and expanded the Vouching contracts list with Avalanche, Polygon, Lens, BNB, and Linea (Lens URL formatting corrected).

Changes

Cohort / File(s) Summary
Documentation update
docs/cow-protocol/reference/core/auctions/bonding_pools.md
Specify that reduced bonding pool size progression spans the following year; change wording to "a solver with a reduced bonding pool"; add Vouching contracts entries for Avalanche, Polygon, Lens, BNB, and Linea; correct Lens URL formatting.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Simple documentation edits and list additions.
  • Attention points:
    • Verify Lens URL now renders correctly.
    • Confirm the timeframe phrasing ("following year") matches project style.

Poem

🐰 I hop through docs with nimble paws,

Chains added, timelines set with laws,
Grammar trimmed and links made bright,
Bonding pools now step by step, in sight —
A joyful nibble, docs take flight! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Update documentation reference to bonding pools' directly matches the main change—updating the bonding pools documentation to include all networks.
Description check ✅ Passed The description follows the template with both required sections (Description and Changes) completed, explaining the purpose and listing the specific changes made.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch Update-Bonding-Pools

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d33d693 and 6d0cdec.

📒 Files selected for processing (1)
  • docs/cow-protocol/reference/core/auctions/bonding_pools.md (2 hunks)
🔇 Additional comments (3)
docs/cow-protocol/reference/core/auctions/bonding_pools.md (3)

13-13: Previous grammar issues resolved.

The hyphenation of "yield-bearing" has been correctly applied in both occurrences, and the time-frame clarification ("over the course of the following year") improves the documentation's clarity.


15-15: Wording improvement enhances generality.

Changing "the solver" to "a solver" appropriately generalizes the statement to apply to any solver setting up a reduced bonding pool, rather than implying a single specific solver.


25-29: Verify network support and contract addresses.

Five new networks have been added with vouching contracts. The previous issue with the Lens address checksum format has been resolved (now showing 0xAAA4De096D02AE21729aA31D967E148D4e3Ae501 consistently). However, please verify:

  1. That CoW Protocol is indeed active on all five newly added networks (Avalanche, Polygon, Lens, BNB, Linea)
  2. That the contract address 0xAAA4De096D02AE21729aA31D967E148D4e3Ae501 is the correct VouchRegister contract for each of these networks
  3. That the explorer URLs are correct and currently functional

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between db62143 and d33d693.

📒 Files selected for processing (1)
  • docs/cow-protocol/reference/core/auctions/bonding_pools.md (2 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/cow-protocol/reference/core/auctions/bonding_pools.md

[grammar] ~13-~13: Use a hyphen to join words.
Context: ...lver needs to deposit $50,000 in (yield bearing) stable coins or ETH, and 500,00...

(QB_NEW_EN_HYPHEN)


[grammar] ~13-~13: Use a hyphen to join words.
Context: ... year all the way to $100,000 in (yield bearing) stable coins or ETH, and 1,000,...

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (2)
docs/cow-protocol/reference/core/auctions/bonding_pools.md (2)

15-15: Grammar improvement is well-applied.

The change from "the solver with a reduced bonding pool" to "a solver with a reduced bonding pool" reads more naturally and is grammatically sound.


13-15: Documentation updates enhance clarity and network coverage.

The narrative clarification specifying that reduced bonding pools are built "over the course of the following year" provides better expectation setting. The expansion to five additional networks (Avalanche, Polygon, Lens, BNB, Linea) appropriately reflects CoW Protocol's expanded deployment footprint.

Also applies to: 25-29

Copy link
Contributor

@fhenneke fhenneke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

The AI comments make sense to me, so you can include their suggestions.

bram-vdberg and others added 2 commits December 3, 2025 11:52
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Assuming that the core team approves the creation of a reduced bonding pool, the first step for setting up a reduced bonding pool is to deploy a Gnosis safe on Mainnet that has only one signer (the CoW DAO Solver Payouts safe, that is, eth:0xA03be496e67Ec29bC62F01a428683D7F9c204930). After this is done and has been confirmed by the CoW DAO team, the solver needs to deposit \$50,000 in (yield-bearing) stable coins or ETH, and 500,000 COW tokens to the newly created safe, and gradually build the pool's size over the course of the following year all the way to \$100,000 in (yield-bearing) stable coins or ETH, and 1,000,000 COW tokens.

We stress that the reduced bonding pool setup is just an arrangement within the CoW DAO bonding pool; meaning that the solver with a reduced bonding pool is still formally vouched under the CoW DAO bonding pool.
We stress that the reduced bonding pool setup is just an arrangement within the CoW DAO bonding pool; meaning that a solver with a reduced bonding pool is still formally vouched under the CoW DAO bonding pool.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pool is still formally vouched --> pool is still formally vouched for

Copy link
Contributor

@pretf00d pretf00d left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one small correction

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants