> For the complete documentation index, see [llms.txt](https://docs.gysr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gysr.io/concepts/pools.md). # Pools ### What are they Each Pool is a standalone staking contract and incentive mechanism. These contracts allow users to deposit tokens as a stake and earn reward tokens in return over time. ### **Architecture** There are two parts to every Pool, staking and rewards. GYSR v2 is built with a modular architecture that separates these two concepts to add more flexibility and make future development more efficient. ![Modular pool architecture](/files/mjXOCzLOTvoqK0gdODqk) Each individual Pool will have a specific staking module and a reward module associated with it. During the configuration of a new Pool, different modules can be attached, resulting in a variety of incentive mechanics. The Pool contract is the end user’s primary point of interaction. It handles all information flow and manages interactions with the underlying modules. The contract only exposes a few simple methods that the end user needs to be aware of. ### --- # 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://docs.gysr.io/concepts/pools.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.