> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/xyo-layer-one/staking/slashing.md). # Slashing Slashing is a security measure in the XYO Layer One blockchain that holds node operators accountable. Through slashing, bad actors are penalized financially, for example by losing their staked $XYO. Ultimately, slashing discourages bad actions to preserve the integrity of the network. ### Purpose Slashing exists to prevent bad actors from doing negative actions on-chain. If a node submits invalid data, approves bad blocks, or interferes with the chain, it can harm other users' interactions and lower the trust in the blockchain. ### Conditions for Slashing [Node Stakers](/xyo-layer-one/staking/types-of-staking.md#node-staking) ([Block Producers](/xyo-layer-one/architecture/node-structure.md#block-producer-nodes) and [Validators](/xyo-layer-one/architecture/node-structure.md#validator-nodes)) put their $XYO tokens at risk when joining consensus. A stake may be slashed if a node: * Produces or approves an invalid block * Submits false or poor-quality data * Performs actions that break consensus rules [System Stakers](/xyo-layer-one/staking/types-of-staking.md#system-staking), who contribute through the pooled staking option, do not face slashing risk because they do not have nodes that can commit bad actions and threaten 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.xyo.network/xyo-layer-one/staking/slashing.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.