# Becoming a Validator ## Considerations As much as we wish that staking were accessible and risk-free to everyone, this is not a reality. There are some practical and serious considerations to consider before deciding to become a validator and stake your KUB. ### Technical Knowledge Node setup requires reasonable technical knowledge when working with computers, although new tools make this easier over time. Understanding the command-line interface is helpful, but no longer strictly required. It also requires a basic hardware setup and an understanding of the minimum recommended specs. ### Secure Key Management Similar to private keys that secure your wallet address, you will need to generate keys specifically for your validator. You must understand how to keep any seed phrases or private keys safe and secure. ### Maintenance Hardware occasionally fails, network connections error out, and client software occasionally needs upgrading. Node maintenance is inevitable and will occasionally require your attention. You'll want to be sure you stay aware of any anticipated network upgrades or other critical client upgrades. ### Reliable Uptime Your rewards are proportional to the time your validator is online and properly attested. Downtime incurs penalties that are proportional to how many other validators are offline simultaneously, but does not result in [slashing](/run-a-kub-node/run-a-validator-node/slashing.md). Bandwidth also matters, as rewards are decreased for attestations that are not received in time. You must keep your validator online and up to date. This is your responsibility, and your account will be penalized if it goes offline. The penalties for being offline are roughly equal to the rewards for actively participating. ## Become a Validator | Resource | Description | | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | | [Run a Validator Node](/run-a-kub-node/run-a-validator-node.md) | Propose new blocks and verify transactions following the KUB Proof-of-Stake mechanism | | [Run a Full Node](/run-a-kub-node/run-a-full-node.md) | Run the latest part of the blockchain state to ensure the stability and operation of the network | | [Run an Archive Node](/run-a-kub-node/run-an-archive-node.md) | Run a node that retains the complete block history of the KUB network | --- # Agent Instructions: 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: ``` GET https://docs.kubchain.com/run-a-kub-node/becoming-a-validator.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.