Skip to content

Update the_problem.md #497

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update the_problem.md #497

wants to merge 1 commit into from

Conversation

acanidio-econ
Copy link
Contributor

@acanidio-econ acanidio-econ commented May 26, 2025

Changed UCP rule to "directional"

Changed the description of the auction to better fit the "Fair combinatorial auction"

Summary by CodeRabbit

  • Documentation
    • Clarified the price uniformity condition to specify "uniform directional clearing prices" for token pairs, allowing for price differences between trading directions.
    • Updated the scoring formula for buy orders to correct a mathematical error.
    • Enhanced explanations around pricing and scoring to improve clarity for end-users.

Changed UCP rule to "directional"

Changed the description of the auction to better fit the "Fair combinatorial auction"
@acanidio-econ acanidio-econ requested a review from a team as a code owner May 26, 2025 08:59
Copy link

coderabbitai bot commented May 26, 2025

Walkthrough

The documentation update refines the auction protocol's price uniformity constraint from a global to a directional scope, specifying that users trading the same token pair in the same direction receive identical prices. It also corrects the scoring formula for buy orders and clarifies the treatment of gas costs and order hooks.

Changes

File(s) Change Summary
docs/cow-protocol/reference/core/auctions/the_problem.md Refined price uniformity constraint to be directional; corrected buy order scoring formula; clarified gas cost handling.

Poem

In the warren of auctions, prices realign,
Directional fairness—now clearly defined!
Scoring gets fixed, with π in its place,
Each rabbit-trader finds their own pace.
With tokens and hops, the rules now precise,
We celebrate clarity—oh, isn’t that nice?
🐇✨


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.
    • Explain this complex logic.
    • 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. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

Documentation and Community

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

Copy link

@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 (1)
docs/cow-protocol/reference/core/auctions/the_problem.md (1)

84-84: Minor grammar and clarity adjustment.

To improve readability, consider adding a comma in the compound clause and making the article usage more explicit. For example:

- From the protocol viewpoint, each solution that satisfies the above constraints has a _score_ that is given by the total surplus generated and the fees paid to the protocol, all aggregated and denominated in some numéraire.
+ From the protocol viewpoint, each solution that satisfies the above constraints has a _score_ that is given by the total surplus generated, the fees paid to the protocol, and any additional components, all aggregated and denominated in some numéraire.

- the score of a solution is equal to the sum of scores of the orders the solution proposes to execute
+ the score of a solution is equal to the sum of the scores of the orders that the solution proposes to execute
🧰 Tools
🪛 LanguageTool

[grammar] ~84-~84: It looks like you are using the wrong form of the noun or the verb. Did you mean “constraint has” or “constraints have”?
Context: ... each solution that satisfies the above constraints has a score that is given by the total su...

(NOUN_PLURAL_HAS)


[uncategorized] ~84-~84: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ... is given by the total surplus generated and the fees paid to the protocol, all aggr...

(COMMA_COMPOUND_SENTENCE_2)


[uncategorized] ~84-~84: You might be missing the article “the” here.
Context: ...re of a solution is equal to the sum of scores of the orders the solution proposes to ...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 97265be and 983c25b.

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

[grammar] ~84-~84: It looks like you are using the wrong form of the noun or the verb. Did you mean “constraint has” or “constraints have”?
Context: ... each solution that satisfies the above constraints has a score that is given by the total su...

(NOUN_PLURAL_HAS)


[uncategorized] ~84-~84: Use a comma before “and” if it connects two independent clauses (unless they are closely connected and short).
Context: ... is given by the total surplus generated and the fees paid to the protocol, all aggr...

(COMMA_COMPOUND_SENTENCE_2)


[uncategorized] ~84-~84: You might be missing the article “the” here.
Context: ...re of a solution is equal to the sum of scores of the orders the solution proposes to ...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)


[misspelling] ~89-~89: Did you mean “for sale”?
Context: ...en of the order (i.e., in the buy token for sell orders and in the sell token for buy or...

(FOR_SELL)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: cla
🔇 Additional comments (2)
docs/cow-protocol/reference/core/auctions/the_problem.md (2)

74-74: Directional price uniformity clarified.

The updated bullet correctly narrows the uniform price constraint to a per-pair, per-direction basis and mentions gas‐cost deviations. This aligns precisely with the PR objective to define “Uniform directional clearing prices.”


87-87: Corrected buy-order scoring formula.

Switching from division by π to multiplication by π accurately reflects the intended economic interpretation for buy orders and matches the PR’s specification.

Copy link

vercel bot commented May 26, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
docs ❌ Failed (Inspect) May 26, 2025 9:32am

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.

looks good

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