> For the complete documentation index, see [llms.txt](https://docs.memusic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.memusic.io/waves/waves-nodes/validator-rewards.md). # Validator Rewards On MeMusic's native blockchain, Station Nodes play a crucial role in validating the blockchain. There will be two types of validators on the blockchain (primary and secondary validators). **Primary Validator** * In the initial phase of the blockchain's launch, there will be primary validators ranging between 21 and 32. These validators are to receive * Primary Validators are required to provide computing power for the blockchain. A high-end computing device with a minimum of 32GB RAM and 1TB HDD will be required. * After meeting the hardware requirements, primary validators are selected based on the number of Station Nodes held. The more nodes a validator hold, they will have a higher priority of being selected as a primary validator. **Secondary Validator** * Secondary Validators are to share the network rewards. Any Station Node Holder can be a secondary validator by staking $MMT and delegating its voting power to a primary validator. --- # 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://docs.memusic.io/waves/waves-nodes/validator-rewards.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.