> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/learn/glossary/staking.md). # Staking Staking glossary for Chiliz Chain: delegation logic, CHZ locking, validator/delegator roles, Parlia compatibility, and decentralized staking platform overview. ## Overview Staking is a contract created to manage an active validator set. It implements delegation logic that allows users to vote for the best validators. It brings decentralisation into blockchain and allows users to gain rewards by voting for the most honest and stable validators. This is because the Annual Percentage Rate (APR) primarily depends on the stability of the validator. ### Compatibility The staking contract is fully compatible with the original Parlia’s validator set contract. ## **Decentralised Staking Platform** Staking is an integral part of the consensus mechanism. Likewise, the Chiliz Chain depends on a robust structure of validators that help in reducing gas fees and shorten block time. A common consensus mechanism used by blockchains is based on Proof of Stake (PoS). Staking allows CHZ holders to contribute to the network by locking their assets on the chain. There are two different roles in staking, namely Validators and Delegators. They are also the participants in the Chiliz Chain staking model. **Validators** must run a node and stake a large amount of native tokens to create and validate blocks. **Delegators** are able to contribute to a validator's staking pool with a much lower amount of tokens, allowing communities with fewer CHZs to participate in the network. ### **Rewards** The reward for each block comes from the gas fees spent on all transactions in the block. These rewards are then split between three entities: * The validators who created the block, * The delegators of the same validator's pool, * and the network. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chiliz.com/learn/glossary/staking.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.