> For the complete documentation index, see [llms.txt](https://up-protocol.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://up-protocol.gitbook.io/untitled/gameplay.md).

# Gameplay

#### Overview:

TallyUP's core player loop can be understood in the following way:

1. **Player Staking:** TallyUP stakes players with a small but[ real financial value ](/untitled/gameplay/player-staking.md)in the system, and then allows them to compete for prizes in various modes of play and tournaments. Some modes involve risking the free value that has been staked by the system, in order to win more.
2. **Competitive Gameplay:** Through various [modes of gameplay](/untitled/gameplay/modes-of-gameplay.md), players compete against one another to increase their balances and eventually "cash out" or redeem prizes from the system once a minimum threshold has been reached. Some forms of competition allow players to multiply their balances exponentially for large, potentially life-changing rewards. 
3. **Revenue Generation:** As players compete, numerous forms of revenue are generated by the system (e.g. ad revenue, in-app purchases and more), which [powers the economy](/untitled/up-tokens-usdup/core-economic-model.md) and allows even larger tournament stakes to be offered to players.

Players continuously earn small amounts of rewards / stake in the system through daily games and practice, which they can choose to risk to multiply their winnings. Players may always be re-staked in the economy with the value of their attention and engagement.

For players, this provides a simple gameplay narrative that does not require any spending, advanced skill or knowledge or complicated set up to begin playing, winning and earning free cryptocurrencies. Players simply download the app and start competing in the tournament economy.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://up-protocol.gitbook.io/untitled/gameplay.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.