Skip to content

Update rewards.md#528

Merged
harisang merged 4 commits intomainfrom
blacktieaccountant-patch-2
Aug 27, 2025
Merged

Update rewards.md#528
harisang merged 4 commits intomainfrom
blacktieaccountant-patch-2

Conversation

@blacktieaccountant
Copy link
Contributor

@blacktieaccountant blacktieaccountant commented Aug 19, 2025

Added context on CIP-72 and the new CAPs for rewards.

Description

Changes

  • ...
  • ...

Summary by CodeRabbit

  • Documentation
    • Documented new gating criteria for price-estimation quote rewards (CIP-72-style) with four explicit conditions.
    • Updated per-chain reward amounts: Ethereum (0.0007 ETH), Arbitrum (0.00024 ETH), Base (0.00024 ETH), Gnosis (0.15 xDAI).
    • Added rewards for Avalanche-C (0.006 AVAX) and Polygon (0.6 POL).
    • Clarified currency wording to “Native Token/xDAI” for COW conversions using 24h Dune averages.
    • Aligned terminology and reward figures across price-estimation sections (CIPs 27, 57).

Added context on CIP-72 and the new CAPs for rewards.
@blacktieaccountant blacktieaccountant requested a review from a team as a code owner August 19, 2025 12:59
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 19, 2025

Walkthrough

Documentation updates to price-estimation rewards: adds explicit CIP-72-style gating criteria, updates per-chain reward amounts (including new Avalanche and Polygon entries), standardizes currency wording to “Native Token/xDAI,” and aligns figures and terminology across CIP-27 and CIP-57 sections in the rewards reference.

Changes

Cohort / File(s) Summary
Documentation: Rewards and Gating
docs/cow-protocol/reference/core/auctions/rewards.md
Documents CIP-72-style gating for winning quotes (market FOK, autopilot verification, executed order, solver’s proposal ≥ quote and passes fairness filter). Updates per-chain rewards: Ethereum 0.0007 ETH; Arbitrum/Base 0.00024 ETH; Gnosis 0.15 xDAI; adds Avalanche 0.006 AVAX, Polygon 0.6 POL. Standardizes “Native Token/xDAI” wording and aligns across CIP-27/57 sections.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    actor User as User
    participant PE as Price Estimator
    participant Sim as Autopilot Simulator
    participant FCAA as Fair Comb. Auction
    participant Solver as Solver
    participant Exec as Settlement
    participant Reward as Reward Engine

    User->>PE: Submit market FOK order
    PE->>PE: Produce price-estimation quote
    PE->>Sim: Submit quote for verification
    Sim-->>PE: Verification result (pass/fail)

    alt Quote verified
        Solver->>FCAA: Propose execution
        FCAA-->>Solver: Fairness filtering result
        alt Pass fairness filter
            Solver->>Exec: Execute order
            Exec-->>User: Order executed
            Note over Reward: Gating check (all 4 conditions)
            PE->>Reward: Winning quote + context
            Reward-->>PE: Reward granted if all conditions met
        else Filtered out
            Reward-->>PE: No reward (fails fairness filter)
        end
    else Verification failed
        Reward-->>PE: No reward (verification failed)
    end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

  • pretf00d

Poem

A hop, a bop, a quote well-tuned,
Four little gates and the carrot’s soon! 🥕
Mainnet sprinkles, Arbi hums,
Base and Gnosis thump their drums—
New trails on Polygon, AVAX snow,
Rewards align—off we go!
— Signed, a jubilant code rabbit 🐇

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch blacktieaccountant-patch-2

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@vercel
Copy link

vercel bot commented Aug 19, 2025

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

Project Deployment Preview Updated (UTC)
docs Ready Ready Preview Aug 27, 2025 6:16am

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: 0

🧹 Nitpick comments (6)
docs/cow-protocol/reference/core/auctions/rewards.md (6)

72-72: Tighten phrasing; minor grammar polish.

Streamline “used in order to” and “all of the following,” keep content unchanged.

-As specified in [CIP-27](https://snapshot.org/#/cow.eth/proposal/0x64e061568e86e8d2eec344d4a892e4126172b992cabe59a0b24c51c4c7e6cc33), [CIP-36](https://snapshot.org/#/cow.eth/proposal/0x4e58f9c1208121c0e06282b5541b458bc8c8b76090263e25448848f3194df986) and [CIP-57](https://snapshot.box/#/s:cow.eth/proposal/0x46d4fea1492207cf400fcb7a01141a7d4c730791d658cc77236941fc9eb7dccb), solvers that participate in the price estimation competition are rewarded for each order that is within the market price, is associated with a quote that was computed as part of the price estimation competition, and was used in order to compute the limit price of the order. [CIP-72](https://snapshot.box/#/s:cow.eth/proposal/0xc1b1252f0c99126b4e09730022faa31a7bb58073a3dc064c19b74d44164c39a7) has imposed additional constraints on the quotes that are rewarded. Specifically, if a solver provides the winning quote that results in an order being created, then the quote is rewarded only if all of the following conditions are satisfied:
+As specified in [CIP-27](https://snapshot.org/#/cow.eth/proposal/0x64e061568e86e8d2eec344d4a892e4126172b992cabe59a0b24c51c4c7e6cc33), [CIP-36](https://snapshot.org/#/cow.eth/proposal/0x4e58f9c1208121c0e06282b5541b458bc8c8b76090263e25448848f3194df986) and [CIP-57](https://snapshot.box/#/s:cow.eth/proposal/0x46d4fea1492207cf400fcb7a01141a7d4c730791d658cc77236941fc9eb7dccb), solvers that participate in the price estimation competition are rewarded for each order that is within the market price, is associated with a quote that was computed as part of the price estimation competition, and was used to compute the limit price of the order. [CIP-72](https://snapshot.box/#/s:cow.eth/proposal/0xc1b1252f0c99126b4e09730022faa31a7bb58073a3dc064c19b74d44164c39a7) has imposed additional constraints on the quotes that are rewarded. Specifically, if a solver provides the winning quote that results in an order being created, then the quote is rewarded only if all the following conditions are satisfied:

74-77: Minor copyedits: add FOK acronym; capitalize Autopilot; improve clause.

Small clarity tweaks without changing meaning.

-1. The order is a fill-or-kill market order;
-2. The quote is verified (i.e., its calldata successfully simulated in the autopilot);
+1. The order is a fill-or-kill (FOK) market order;
+2. The quote is verified (i.e., its calldata was successfully simulated by Autopilot);
 3. The order was executed (not necessarily by the quoting solver);
 4. The solver that provided the winning quote during order creation proposed an execution of the order (in at least one auction) that is at least as good as the quote, and that execution was not filtered out by the fairness filtering of the fair combinatorial auction mechanism.

79-79: Fix typo: “eligble” → “eligible”.

-The current rewards for eligble quotes are as follows:
+The current rewards for eligible quotes are as follows:

84-86: Normalize chain names for consistency.

Use commonly accepted names: “Base”, “Avalanche C-Chain”, “Polygon”.

-- Base Chain: $$\min\{0.00024 ~\textrm{ETH}, 6 ~\textrm{COW}\}$$,
-- Avalanche-C Chain: $$\min\{0.006 ~\textrm{AVAX}, 6 ~\textrm{COW}\}$$,
-- Polygon Chain: $$\min\{0.6 ~\textrm{POL}, 6 ~\textrm{COW}\}$$
+- Base: $$\min\{0.00024 ~\textrm{ETH}, 6 ~\textrm{COW}\}$$,
+- Avalanche C-Chain: $$\min\{0.006 ~\textrm{AVAX}, 6 ~\textrm{COW}\}$$,
+- Polygon: $$\min\{0.6 ~\textrm{POL}, 6 ~\textrm{COW}\}$$

Note: If other sections use “Base chain” or “Polygon Chain,” consider harmonizing globally in a follow-up sweep for consistency.


88-88: Clarify conversion sentence to cover xDAI explicitly.

Make it explicit that either Native Token/COW or xDAI/COW pairs are used.

-where, again, the conversion from Native Token and xDAI to COW is done by using an up-to-date price (specifically, the average Native Token/COW Dune prices of the past 24h before the payout are used to determine these exchange rates).
+where, again, conversion from the Native Token (or xDAI) to COW uses an up-to-date price — specifically, the average 24h Dune price of Native Token/COW (or xDAI/COW) observed before the payout to determine these exchange rates.

72-72: Standardize all CIP links to snapshot.org

Both snapshot.org and snapshot.box resolve (HEAD on snapshot.org returns 301 due to fragment-only paths, snapshot.box returns 200), but we should use the canonical snapshot.org domain for consistency.

• File: docs/cow-protocol/reference/core/auctions/rewards.md
Replace the two snapshot.box URLs with snapshot.org:

 As specified in [CIP-27](https://snapshot.org/#/cow.eth/proposal/0x64e061568e86e8d2eec344d4a892e4126172b992cabe59a0b24c51c4c7e6cc33),
 [CIP-36](https://snapshot.org/#/cow.eth/proposal/0x4e58f9c1208121c0e06282b5541b458bc8c8b76090263e25448848f3194df986)
-  and [CIP-57](https://snapshot.box/#/s:cow.eth/proposal/0x46d4fea1492207cf400fcb7a01141a7d4c730791d658cc77236941fc9eb7dccb),
-  [CIP-72](https://snapshot.box/#/s:cow.eth/proposal/0xc1b1252f0c99126b4e09730022faa31a7bb58073a3dc064c19b74d44164c39a7)
+  and [CIP-57](https://snapshot.org/#/s:cow.eth/proposal/0x46d4fea1492207cf400fcb7a01141a7d4c730791d658cc77236941fc9eb7dccb),
+  [CIP-72](https://snapshot.org/#/s:cow.eth/proposal/0xc1b1252f0c99126b4e09730022faa31a7bb58073a3dc064c19b74d44164c39a7)
 , solvers that…  

Optional refactor: switch all four links to snapshot.org for a unified canonical domain.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 47bbea0 and 4b5d232.

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

[style] ~72-~72: Consider a more concise word here.
Context: ...ce estimation competition, and was used in order to compute the limit price of the order. [...

(IN_ORDER_TO_PREMIUM)


[grammar] ~72-~72: There might be a mistake here.
Context: ...sed in order to compute the limit price of the order. [CIP-72](https://snapshot.box/#/s:cow.e...

(QB_NEW_EN)


[style] ~72-~72: Consider removing “of” to be more concise
Context: ...ted, then the quote is rewarded only if all of the following conditions are satisfied: 1....

(ALL_OF_THE)


[grammar] ~79-~79: Ensure spelling is correct
Context: ...ion mechanism. The current rewards for eligble quotes are as follows: - Ethereum main...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~81-~81: There might be a mistake here.
Context: ...0007 ~\textrm{ETH}, 6 ~\textrm{COW}}$$, - Gnosis Chain: $$\min{0.15 ~\textrm{xDAI...

(QB_NEW_EN)


[grammar] ~82-~82: There might be a mistake here.
Context: ....15 ~\textrm{xDAI}, 6 ~\textrm{COW}}$$, - Arbitrum: $$\min{0.00024 ~\textrm{ETH},...

(QB_NEW_EN)


[grammar] ~83-~83: There might be a mistake here.
Context: ...0024 ~\textrm{ETH}, 6 ~\textrm{COW}}$$, - Base Chain: $$\min{0.00024 ~\textrm{ETH...

(QB_NEW_EN)


[grammar] ~84-~84: There might be a mistake here.
Context: ...0024 ~\textrm{ETH}, 6 ~\textrm{COW}}$$, - Avalanche-C Chain: $$\min{0.006 ~\textr...

(QB_NEW_EN)


[grammar] ~85-~85: There might be a mistake here.
Context: ...006 ~\textrm{AVAX}, 6 ~\textrm{COW}}$$, - Polygon Chain: $$\min{0.6 ~\textrm{POL}...

(QB_NEW_EN)

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.

Just added two nit comments. Feel free to disregard.

Co-authored-by: Felix Henneke <felix.henneke@protonmail.com>
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: 1

♻️ Duplicate comments (1)
docs/cow-protocol/reference/core/auctions/rewards.md (1)

88-88: LGTM — incorporates prior reviewer suggestion about conversion wording.

This matches the earlier recommendation to clarify Native Token→COW conversion via 24h average Dune prices.

🧹 Nitpick comments (4)
docs/cow-protocol/reference/core/auctions/rewards.md (4)

72-78: Tighten wording; keep logic unchanged.

Polish for concision and clarity; no semantic change.

-As specified in [CIP-27](https://snapshot.org/#/cow.eth/proposal/0x64e061568e86e8d2eec344d4a892e4126172b992cabe59a0b24c51c4c7e6cc33), [CIP-36](https://snapshot.org/#/cow.eth/proposal/0x4e58f9c1208121c0e06282b5541b458bc8c8b76090263e25448848f3194df986) and [CIP-57](https://snapshot.box/#/s:cow.eth/proposal/0x46d4fea1492207cf400fcb7a01141a7d4c730791d658cc77236941fc9eb7dccb), solvers that participate in the price estimation competition are rewarded for each order that is within the market price, is associated with a quote that was computed as part of the price estimation competition, and was used in order to compute the limit price of the order. [CIP-72](https://snapshot.box/#/s:cow.eth/proposal/0xc1b1252f0c99126b4e09730022faa31a7bb58073a3dc064c19b74d44164c39a7) has imposed additional constraints on the quotes that are rewarded. Specifically, if a solver provides the winning quote that results in an order being created, then the quote is rewarded if and only if all of the following conditions are satisfied:
+As specified in [CIP-27](https://snapshot.org/#/cow.eth/proposal/0x64e061568e86e8d2eec344d4a892e4126172b992cabe59a0b24c51c4c7e6cc33), [CIP-36](https://snapshot.org/#/cow.eth/proposal/0x4e58f9c1208121c0e06282b5541b458bc8c8b76090263e25448848f3194df986) and [CIP-57](https://snapshot.box/#/s:cow.eth/proposal/0x46d4fea1492207cf400fcb7a01141a7d4c730791d658cc77236941fc9eb7dccb), solvers that participate in the price estimation competition are rewarded for each order that is within the market price, is associated with a quote computed as part of the price estimation competition, and was used to compute the order’s limit price. [CIP-72](https://snapshot.box/#/s:cow.eth/proposal/0xc1b1252f0c99126b4e09730022faa31a7bb58073a3dc064c19b74d44164c39a7) imposes additional constraints on rewarded quotes. Specifically, if a solver provides the winning quote that results in an order being created, the quote is rewarded if and only if the following conditions are all satisfied:
@@
-2. The quote is verified (i.e., its calldata successfully simulated in the autopilot);
+2. The quote is verified (its calldata successfully simulates in the autopilot);
@@
-4. The solver that provided the winning quote during order creation proposed an execution of the order (in at least one auction) that is at least as good as the quote, and that execution was not filtered out by the fairness filtering of the fair combinatorial auction mechanism.
+4. The solver that provided the winning quote during order creation proposed, in at least one auction, an execution that is at least as good as the quote, and that execution was not filtered out by the fairness filtering of the fair combinatorial auction mechanism.

72-72: Standardize Snapshot link domains.

You mix snapshot.org and snapshot.box. Pick one canonical domain used elsewhere in the docs and apply consistently.


81-86: Confirm chain naming and style consistency.

Names vary across the docs/ecosystem (“Base” vs “Base Chain”, “Avalanche C-Chain”, “Polygon/Polygon PoS/Polygon Chain”). Align with your style guide before merging.


79-88: Add “last updated” note to reduce drift risk.

These values change over time. Add an as-of date and a pointer to the source of truth.

 - The current rewards for eligible quotes are as follows:
+The current rewards for eligible quotes are as follows:
@@
 - Polygon Chain: $$\min\{0.6 ~\textrm{POL}, 6 ~\textrm{COW}\}$$
+:::note
+As of August 27, 2025. See the [Dune dashboard](https://dune.com/cowprotocol/cow-solver-rewards) and relevant CIPs for the latest parameters.
+:::
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 4b5d232 and 48212ad.

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

[style] ~72-~72: Consider a more concise word here.
Context: ...ce estimation competition, and was used in order to compute the limit price of the order. [...

(IN_ORDER_TO_PREMIUM)


[grammar] ~72-~72: There might be a mistake here.
Context: ...sed in order to compute the limit price of the order. [CIP-72](https://snapshot.box/#/s:cow.e...

(QB_NEW_EN)


[style] ~72-~72: Consider removing “of” to be more concise
Context: ...en the quote is rewarded if and only if all of the following conditions are satisfied: 1....

(ALL_OF_THE)


[grammar] ~79-~79: Ensure spelling is correct
Context: ...ion mechanism. The current rewards for eligble quotes are as follows: - Ethereum main...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~81-~81: There might be a mistake here.
Context: ...0007 ~\textrm{ETH}, 6 ~\textrm{COW}}$$, - Gnosis Chain: $$\min{0.15 ~\textrm{xDAI...

(QB_NEW_EN)


[grammar] ~82-~82: There might be a mistake here.
Context: ....15 ~\textrm{xDAI}, 6 ~\textrm{COW}}$$, - Arbitrum: $$\min{0.00024 ~\textrm{ETH},...

(QB_NEW_EN)


[grammar] ~83-~83: There might be a mistake here.
Context: ...0024 ~\textrm{ETH}, 6 ~\textrm{COW}}$$, - Base Chain: $$\min{0.00024 ~\textrm{ETH...

(QB_NEW_EN)


[grammar] ~84-~84: There might be a mistake here.
Context: ...0024 ~\textrm{ETH}, 6 ~\textrm{COW}}$$, - Avalanche-C Chain: $$\min{0.006 ~\textr...

(QB_NEW_EN)


[grammar] ~85-~85: There might be a mistake here.
Context: ...006 ~\textrm{AVAX}, 6 ~\textrm{COW}}$$, - Polygon Chain: $$\min{0.6 ~\textrm{POL}...

(QB_NEW_EN)

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: 0

🧹 Nitpick comments (4)
docs/cow-protocol/reference/core/auctions/rewards.md (4)

72-72: Tighten wording; consider Snapshot link domain consistency.

  • Style: replace “used in order to” with “used to,” and prefer “order’s limit price.”
  • Consider standardizing Snapshot links (snapshot.org vs snapshot.box) across the doc for consistency.

Apply this minimal edit:

-As specified in [CIP-27](...), [CIP-36](...) and [CIP-57](...), solvers that participate in the price estimation competition are rewarded for each order that is within the market price, is associated with a quote that was computed as part of the price estimation competition, and was used in order to compute the limit price of the order. [CIP-72](...) has imposed additional constraints on the quotes that are rewarded. Specifically, if a solver provides the winning quote that results in an order being created, then the quote is rewarded if and only if all of the following conditions are satisfied:
+As specified in [CIP-27](...), [CIP-36](...) and [CIP-57](...), solvers that participate in the price estimation competition are rewarded for each order that is within the market price, is associated with a quote computed as part of the price estimation competition, and was used to compute the order’s limit price. [CIP-72](...) imposes additional constraints on which quotes are rewarded. Specifically, if a solver provides the winning quote that results in an order being created, then the quote is rewarded if and only if all the following conditions are satisfied:

74-77: Link “autopilot,” or briefly define it on first mention.

Readers may not know “autopilot.” Link to its docs or add a one-liner parenthetical.

I can insert the correct relative link if you point me to the canonical Autopilot doc path.


81-86: Normalize chain names and list punctuation; keep style consistent.

  • Names: “Base” (not “Base Chain”), “Avalanche C-Chain” (not “Avalanche-C Chain”), “Polygon” (or “Polygon PoS,” pick one style and use it everywhere).
  • Punctuation: avoid trailing commas on bullets; end the last item with a period (or convert all to semicolons and end with a period).

Apply this edit:

-- Ethereum mainnet: $$\min\{0.0007 ~\textrm{ETH}, 6 ~\textrm{COW}\}$$,
-- Gnosis Chain: $$\min\{0.15 ~\textrm{xDAI}, 6 ~\textrm{COW}\}$$,
-- Arbitrum: $$\min\{0.00024 ~\textrm{ETH}, 6 ~\textrm{COW}\}$$,
-- Base Chain: $$\min\{0.00024 ~\textrm{ETH}, 6 ~\textrm{COW}\}$$,
-- Avalanche-C Chain: $$\min\{0.006 ~\textrm{AVAX}, 6 ~\textrm{COW}\}$$,
-- Polygon Chain: $$\min\{0.6 ~\textrm{POL}, 6 ~\textrm{COW}\}$$
+- Ethereum mainnet: $$\min\{0.0007 ~\textrm{ETH}, 6 ~\textrm{COW}\}$$
+- Gnosis Chain: $$\min\{0.15 ~\textrm{xDAI}, 6 ~\textrm{COW}\}$$
+- Arbitrum: $$\min\{0.00024 ~\textrm{ETH}, 6 ~\textrm{COW}\}$$
+- Base: $$\min\{0.00024 ~\textrm{ETH}, 6 ~\textrm{COW}\}$$
+- Avalanche C-Chain: $$\min\{0.006 ~\textrm{AVAX}, 6 ~\textrm{COW}\}$$
+- Polygon: $$\min\{0.6 ~\textrm{POL}, 6 ~\textrm{COW}\}$$.

88-88: Trim verbosity and remove “again.”

Concise and neutral tone reads better in reference docs.

-where, again, the conversion from native token to COW is done by using an up-to-date price (specifically, the average native token/COW Dune prices of the past 24h before the payout are used to determine these exchange rates).
+where the native-token-to-COW conversion uses the 24h pre‑payout average native token/COW price on Dune to determine these exchange rates.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 48212ad and 8ab2a88.

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

[style] ~72-~72: Consider a more concise word here.
Context: ...ce estimation competition, and was used in order to compute the limit price of the order. [...

(IN_ORDER_TO_PREMIUM)


[grammar] ~72-~72: There might be a mistake here.
Context: ...sed in order to compute the limit price of the order. [CIP-72](https://snapshot.box/#/s:cow.e...

(QB_NEW_EN)


[style] ~72-~72: Consider removing “of” to be more concise
Context: ...en the quote is rewarded if and only if all of the following conditions are satisfied: 1....

(ALL_OF_THE)


[grammar] ~81-~81: There might be a mistake here.
Context: ...0007 ~\textrm{ETH}, 6 ~\textrm{COW}}$$, - Gnosis Chain: $$\min{0.15 ~\textrm{xDAI...

(QB_NEW_EN)


[grammar] ~82-~82: There might be a mistake here.
Context: ....15 ~\textrm{xDAI}, 6 ~\textrm{COW}}$$, - Arbitrum: $$\min{0.00024 ~\textrm{ETH},...

(QB_NEW_EN)


[grammar] ~83-~83: There might be a mistake here.
Context: ...0024 ~\textrm{ETH}, 6 ~\textrm{COW}}$$, - Base Chain: $$\min{0.00024 ~\textrm{ETH...

(QB_NEW_EN)


[grammar] ~84-~84: There might be a mistake here.
Context: ...0024 ~\textrm{ETH}, 6 ~\textrm{COW}}$$, - Avalanche-C Chain: $$\min{0.006 ~\textr...

(QB_NEW_EN)


[grammar] ~85-~85: There might be a mistake here.
Context: ...006 ~\textrm{AVAX}, 6 ~\textrm{COW}}$$, - Polygon Chain: $$\min{0.6 ~\textrm{POL}...

(QB_NEW_EN)

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

72-78: Good addition: CIP-72 gating criteria are clearly enumerated.

The logical “if and only if” phrasing removes ambiguity, and the 4-item checklist reads clearly.


79-86: Action: Annotate quote-reward table with “as of” date and governance references

Please update the “current rewards for eligible quotes” section as follows:

• Prepend an introductory sentence:
“As of July 8 2025 (accounting week July 8–15, 2025), per CIP-72, the per-quote rewards are:”

• For each network, append the governing CIP (or core-team decision) that set the cap:

  • Ethereum mainnet: min{0.0007 ETH, 6 COW} – (set by CIP-36, Jan 19 2024)
  • Gnosis Chain: min{0.15 xDAI, 6 COW} – (set by CIP-57, Nov 11 2024)
  • Arbitrum: min{0.00024 ETH, 6 COW} – (set by CIP-57, Nov 11 2024)
  • Base chain: min{0.00024 ETH, 6 COW} – (inherited under CIP-57 new-chain policy)
  • Avalanche chain: min{0.006 AVAX, 6 COW} – (live since July 1 2025 via core-team adjustment under CIP-57 new-chain policy)
  • Polygon chain: min{0.6 POL, 6 COW} – (support pending launch; first payout week after chain deployment)

• Confirm naming matches the rest of the docs: use “Base chain”, “Avalanche chain”, “Polygon chain” (lowercase “chain” per style guide).

• Verify Avalanche rewards are already live (from the week of July 1–8 2025) and that Polygon support is pending, and specify the first payout week for Polygon once live.

@harisang harisang merged commit 4c9d6b8 into main Aug 27, 2025
6 checks passed
@harisang harisang deleted the blacktieaccountant-patch-2 branch August 27, 2025 06:39
@github-actions github-actions bot locked and limited conversation to collaborators Aug 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants