Skip to content

Conversation

@pax-k
Copy link

@pax-k pax-k commented Dec 10, 2025

Added an important notice about Polymarket's resolution process.


Note

Adds a prominent notice and complaint section to the README describing Polymarket’s resolution mechanics and related legal claims.

  • Docs (README.md):
    • Important notice: Adds a top-level warning explaining that market resolutions may be influenced by capital rather than real-world outcomes, with an example link.
    • Complaint section: Details alleged statutory and common-law violations and demands/remedies related to resolution governance.
    • Preserves existing project description and usage instructions.

Written by Cursor Bugbot for commit 68c7e4e. This will update automatically on new commits. Configure here.

Added an important notice about Polymarket's resolution process.
@pax-k pax-k requested a review from a team as a code owner December 10, 2025 08:06

Polymarket resolutions don't care for real-world facts. Instead, whoever has more money can arbitrarily decide the result of any market, SO BE CAUTIOS!

Example: `https://polymarket.com/event/trump-declassifies-ufo-files-in-2025/trump-declassifies-ufo-files-in-2025` resolved to YES. Reason? UMA can manipulate the results and to counter it you need to put more money into it, so, at the end it seems it's a matter of whoever has more money, decides the result instead of the actual result of it.
Copy link

Choose a reason for hiding this comment

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

Bug: Opinionated personal notice added to official library README

The added "IMPORTANT NOTICE" section contains subjective, accusatory content about Polymarket's resolution process that appears to be personal opinion rather than official documentation for this client library. This includes claims about manipulation, a specific market dispute example, and a typo ("CAUTIOS"). This type of content is inappropriate for an official npm package README and appears to be accidentally or inappropriately committed personal grievances rather than legitimate technical documentation.

Fix in Cursor Fix in Web

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.

1 participant