> 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/incentive-mechanisms.md). # Incentive Mechanisms The following summarizes the incentive mechanisms to be incorporated into the protocol’s design: ### **Incentive Structuring** Beamable’s incentive structure includes staking requirements for nodes, slashing (penalty deductions) for misbehavior, and tiered rewards based on node performance. The model draws inspiration from existing DePIN staking mechanics and a tiered rewards approach. ### **Staking Dynamics** * The system is designed to require a minimum stake of $BMB for the nodes, complemented by delegated staking for broader community participation in network security and governance. * Checker nodes receive rewards to ensure data integrity, with tiered rewards that adjust based on performance, maintaining high standards for service quality. ### **Additional Mechanisms** * Beamable will develop a reputation system for nodes to encourage consistent performance. To this end, it will offers bonuses or higher rewards to nodes with a proven track record. * Reward Vesting and Lockup Periods: To reduce sell pressure initially, Beamable will implement reward vesting for newly minted rewards to delay their distribution. This can be aligned with project milestones or specific compute performance metrics. Introducing early withdrawal penalties similar to Akash's model to discourage selling before rewards mature. ### **Compute credits** Credits are purchased with the project’s native token $BMB, creating continuous demand, as used in similar protocols such as Helium and Akash. --- # 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/incentive-mechanisms.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.