> 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/player-staking.md). # Player Staking When a player first enters TallyUP or has zero-balance in their account, they are staked with a small but real financial value in the system. This initial value is carefully calculated based on the expected value of a player's time, attention and engagement on the platform. Numerous factors are taken into account, including player metadata (device, location, and more). In this way, players essentially *buy-into* the economy with the value of their attention and engagement. **Players can be staked in a variety of different system currencies and rewards, including:** * USD * $UP Tokens * In-game items (e.g. basic or mega spins that can be used to be staked with variable prizes) * Bananas (social, non-financial in-game currency) * Unique, One-off rewards (e.g. Entry to special VIP Tournaments) * Other cryptos Calculating the rate and type of staking for a given set of players is one of the many functions of the game economy that has been carefully designed and optimized both for maximum global engagement and economic sustainability . No matter where players are based, TallyUP is designed to be equally winnable for all players and to never incorporate pay-to-win mechanics that put any specific set of players at a disadvantage. The [goals of TallyUP](/untitled/core-values.md) include all humans having a real and equivalent shot at highly impactful financial outcomes. While there may be different forms of staking players and rewards, all players can eventually compete in live games for USD and other prizes. --- # 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/player-staking.md?ask=&goal= ``` `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.