> For the complete documentation index, see [llms.txt](https://docs.emoney.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emoney.network/validating-on-e-money-network/validator-nodes.md). # Validator nodes The E Money Network is secured by a Proof-Of-Stake consensus algorithm. Validators in the E Money Network can install E Money Network clients on their AWS/GCP or other cloud nodes or in-house nodes. ### Key Responsibilities of Validator Nodes in E Money Network: * Securing the Network: Validator nodes are responsible for maintaining consensus, validating transactions, and adding new blocks to the blockchain, ensuring its integrity and security. * Staking: To become a validator, a node must stake a significant amount of the blockchain's native cryptocurrency. This stake serves as a financial incentive to act honestly and disincentivizes malicious behaviour. * Block Proposal: Validators take turns proposing new blocks containing valid transactions. The selection process often prioritises nodes with higher stakes and longer uptime. * Block Validation: Upon receiving a proposed block, validators verify its legitimacy, including transaction validity, signatures, and compliance with consensus rules. * Voting: Validators vote on the proposed blocks, either agreeing or disagreeing with their validity. A block is added to the blockchain only if a majority of validators reach consensus. * Rewards: Validators who participate honestly and successfully in the consensus process earn rewards in the form of transaction fees and newly minted coins, proportional to their stake. * Slashing: Validators who act maliciously, such as attempting to create invalid blocks or double-spend, can be penalised by having a portion of their stake slashed (forfeited). This mechanism further incentivizes honest behaviour. --- # 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.emoney.network/validating-on-e-money-network/validator-nodes.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.