> For the complete documentation index, see [llms.txt](https://scorum.gitbook.io/scorum-network-2.0-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://scorum.gitbook.io/scorum-network-2.0-whitepaper/scorum-products-overview/validation.md). # Validation Scorum uses a Proof of Stake (PoS) consensus model, ensuring the network’s security and stability through a set of network validators. Anyone can become a validator and receive SCR as a reward while contributing to network security. Network validators are responsible for verifying all user transactions. If all validators reach consensus that a transaction is valid, it is included in the blockchain. Invalid transactions are rejected. Validators receive compensation from a reward pool for their efforts in maintaining network integrity and security. The reward pool for validators is funded by a percentage of the Gross Gaming Revenue (GGR) from the Aviatrix game, which operates on both web2 and web3 versions: * **Web2 Contributions:** 0.25% of the GGR from transactions within the web2 version of Aviatrix contributes to the reward pool. * **Web3 Contributions:** An additional 2.5% of the GGR from the web3 version of Aviatrix is allocated to the reward pool. The distribution of rewards for validating the Scorum Network follows the standard system used in the Cosmos SDK, with rewards distributed with each block and no withdrawal fees for accessing these rewards. If a validator does not participate in creating blocks and signing transactions for a significant amount of time during a validation round, they could potentially be jailed and fined. [Guide on how to become a validator.](https://www.scorum.network/news/validator-guide) --- # 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://scorum.gitbook.io/scorum-network-2.0-whitepaper/scorum-products-overview/validation.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.