> For the complete documentation index, see [llms.txt](https://docs.beamable.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beamable.network/project-documentation/readme/staking.md). # Staking You become an active participant in Beamable Network’s decentralized infrastructure by staking $BMB to help power workloads, earn rewards, and shape the future of on-chain compute. When you stake $BMB, you **Earn compensation & yield:** Stakers share directly in network revenue and node incentives. Worker and Checker node participants earn weekly rewards, revenue share from game workloads, and bonus emissions. Rewards can be auto-staked, letting your position grow every week. Locked rewards unlock gradually, helping stabilize token supply and protect long-term holders.\ \ Briefly, staking $BMB aligns incentives between game builders, node operators, and the broader community. It turns passive holders into active contributors who earn compensation & yield, and guide governance in the world’s first gaming-focused DePIN with built-in supply. --- # 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.beamable.network/project-documentation/readme/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.