> For the complete documentation index, see [llms.txt](https://rocketcpu.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://rocketcpu.gitbook.io/untitled/the-problem.md). # The Problem 3 Resources are required to operate a WAX wallet on the blockchain. CPU (the amount of transactions a wallet can make in a 24hr period), RAM (the amount of data stored on the blockchain) and NET (the speed at which transactions occur). The most important and user-heavy resource however, is CPU. Just imagine the total CPU available throughout the entire blockchain as a large pie chart. Each time a user stakes more WAX to their wallet, the larger the chunk of the pie they have available to them to conduct more transactions. This also goes in the opposite direction though. The more WAX users stake to their wallets, the less everyone else has available Current games rely on performing several transactions daily. Hence, requiring a vast amount of CPU (WAX staked) to play it adequately. Most users don’t have enough resources to stake vast amounts of WAX in order to win playing their favorite game. This affects also the game by itself and its organic growth. With higher amounts of WAX being required over time less users are likely to invest time and money into it. --- # 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://rocketcpu.gitbook.io/untitled/the-problem.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.