> For the complete documentation index, see [llms.txt](https://docs.upshot.cards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.upshot.cards/contests/contest-points-gold-points.md). # Contest Points (Gold Points) ## Card Contest Points & Scoring Model Each contest card pays out gold points based on how likely it is to come true. By locking cards into a contest, players score points based on their Gold Points found on individual cards. Lower-risk cards pay fewer points, while higher-risk cards pay more points. This creates a balanced contest experience where users can choose between safer predictions and bigger potential rewards. Upshot Contest Cards are gamified cards that are minted with a probability at the time they are created and published. This probability helps determine the potential points a card can earn if the outcome comes true. Because real-world events are constantly changing, probabilities may shift after a card has been minted. This means the probability shown on a card may not always reflect the current real-time likelihood of that outcome occurring. Users are encouraged to follow real-world events, review the prize potential of each card, and make their own judgement before entering contests. Some users may choose to keep collecting specific cards, some may use them in contests, and others may decide to sell them on the marketplace for Gold Points. ## Prize Formula The formula is: ``` Points = 113 / p ``` Where: ``` p = the probability that the card comes true ``` For example, a card with a 50% chance: ``` 113 / 0.50 = 226 points ``` A card with a 25% chance pays: ``` 113 / 0.25 = 452 points ``` A card with a 10% chance pays: ``` 113 / 0.10 = 1,130 points ``` Every card begins with the same expected prize: ``` Probability × Payout = 113 ``` Example: ``` 0.25 × 452 = 113 ``` Users are rewarded for balancing risk versus reward. *** ## Example Prize Table | Card Probability | Odds Style | Points if True | | ---------------: | ----------------- | -------------: | | 90% | Very safe | 126 | | 75% | Safe | 151 | | 60% | Likely | 188 | | 50% | Toss-up | 226 | | 40% | Risky | 283 | | 30% | Hard | 377 | | 25% | Long shot | 452 | | 20% | Very hard | 565 | | 10% | Massive long shot | 1,130 | *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.upshot.cards/contests/contest-points-gold-points.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.