> For the complete documentation index, see [llms.txt](https://docs.crescent.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crescent.network/introduction/liquid-staking/liquid-staking-validator.md). # Liquid Staking Validator ### **Liquid Staking Validator** Crescent Network’s liquid staking utility consists of whitelisted validators that receive delegation directly from the liquid staking module. When a user stakes their CRE, the delegated amount is distributed equally among the set of whitelisted validators that can be changed by governance, led by the Crescent Foundation. Validator addition conditions: * Maximum of 1 validator added each month to existing group when no performance issues exist on the network * The validator’s performance and potential contribution to Crescent Network must be provided and addition must be agreed on by governance Grounds of expulsion from group: * Potential significant network performance drag caused by the validator * Commission rate set differently than the commission rate decided by signal governance * Statistical evidence of VEV(validator extractable value) The Crescent Foundation can monitor the statistical differences between mempools in multiple full-nodes and the transactions in each proposed block to prevent VEV. When there exists very strong statistical evidence that a significant number of blocks are proposed by a certain validator, the below punishment on the validator can be executed via governance process: * Expulsion of the validator from the liquid staking validator group * Slash proportion of delegations towards the validator * Tombstone the validator --- # 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.crescent.network/introduction/liquid-staking/liquid-staking-validator.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.