> For the complete documentation index, see [llms.txt](https://alliance-games.gitbook.io/alliance-games-litepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alliance-games.gitbook.io/alliance-games-litepaper/technical-structure/micro-node/reward-mechanism.md). # Reward Mechanism Alliance Micro Node uses mcWORK as its reward mechanism, incentivizing users to contribute their lightweight processing and verification resources. The reward system is designed to encourage nodes that provide consistent performance, quick response times, and efficient data handling, ensuring that users are rewarded proportionally to their contributions to the network. * **Performance-Based Rewards:** Micro Nodes are compensated based on their overall efficiency in managing network tasks. This includes both data handling and responsiveness. Nodes that consistently demonstrate low latency, high throughput in data processing, and quick response times to network requests earn higher rewards. This incentive structure encourages users to optimize their node's performance, connectivity, and overall contribution to the network's agility and efficiency. --- # 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://alliance-games.gitbook.io/alliance-games-litepaper/technical-structure/micro-node/reward-mechanism.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.