> 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/types-of-staking.md). # Types of Staking Staking with $XYO in the XYO Layer One Blockchain is integral to securing the blockchain, and users have more than one option for participating in the staking ecosystem. ### Node Staking There are two types of Node Staking: Block Producer Node and Validator Node Staking. Staking a Node should only ever be done by the Node owner, and not a multitude of parties. Node Staking includes risk of slashing, but gives returns higher rewards than System Staking. ### System Staking Sometimes referred to as "Nodeless" Staking, this version allows a user to stake the system itself, rather than an individual node. System Stakers earn rewards from the [Step Reward Pool](/xyo-layer-one/rewards/step-rewards.md). By locking up $XYO to System Stake, the "risk" a user incurs stems from the inability to quickly move the stake, but **this stake cannot be slashed inside the network itself.** --- # 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/types-of-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.