A validator is a participant in a proof-of-stake network who runs node software, locks up a bond of the network’s native token, and participates in the consensus process by proposing and attesting to new blocks. The validator role is the PoS equivalent of a miner in proof-of-work: it is the entity that gets paid for helping the network reach agreement on which transactions to include and in what order. On Ethereum, the minimum stake is 32 ETH and there are roughly a million active validators as of 2026. On Solana, Avalanche, Cardano, Cosmos, and other major PoS chains, the validator set is smaller — typically hundreds to thousands — but the role is conceptually similar.
A validator’s job on Ethereum consists of two main responsibilities. First, proposing blocks: every 12 seconds, one validator is pseudo-randomly selected to propose the next block, which means they collect transactions from the mempool, execute them, build a new block with the results, and broadcast it to the network. Second, attesting: every validator is assigned to a committee that votes on whether each proposed block is valid and should be included in the chain. Honest validators vote on every block they are assigned to, and they are rewarded for doing so correctly and on time. Dishonest or offline validators miss attestations or produce conflicting ones, and they are penalised.
How Validators Earn and Lose Money
Validator rewards come from three sources on Ethereum: newly-issued ETH for attestations and block proposals (the “issuance” portion), priority fees paid by users whose transactions are included (the “tip” portion), and MEV extraction (the “MEV” portion, paid indirectly through block builders who compete to assemble the most profitable blocks). In normal conditions, the total yield for a validator is around 3-4 percent per year on the staked amount, though the exact figure varies with network activity, total validator count, and MEV conditions.
Losses come from two sources. Inactivity penalties apply when a validator fails to attest correctly or on time, typically because the node is offline or misconfigured. These are small — a validator losing 0.01-0.1 ETH over a few days of downtime — and are designed to gently encourage reliability without being catastrophic. Slashing applies when a validator commits a provably dishonest action: proposing two conflicting blocks at the same height, or attesting to conflicting checkpoints. Slashing takes away 1 ETH minimum and can rise sharply if many validators are slashed together as part of a coordinated attack. After slashing, the validator is forcibly ejected from the active set and has to wait out an exit queue before getting the remainder of its stake back.
The slashing penalties are the thing that makes PoS economically secure. Running a validator honestly has a well-defined expected reward. Running one dishonestly risks losing the entire bond, and the only rational reason to do so would be if the attack produced more profit than the cost of the slashing — which is designed to be impossible for realistic attack sizes.
Running a Validator at Home vs Through a Pool
Solo validating is the ideological ideal for Ethereum decentralisation. You run your own hardware, control your own keys, and contribute directly to the validator set without depending on any intermediary. The practical requirements are modest — a mid-range computer, a reliable internet connection, and some technical willingness to keep the software updated — but the 32 ETH minimum (currently around $100,000 at typical prices) is a high financial bar for most people.
Pooled staking addresses the capital requirement by aggregating smaller deposits. Lido is the largest, using a model where depositors receive stETH that can be freely used in DeFi while the underlying ETH is staked across a curated set of professional node operators. Rocket Pool is a more decentralised alternative where individuals can run validators with a smaller ETH requirement (8 or 16 ETH, topped up with pooled ETH from other users). Coinbase, Binance, Kraken, and other exchanges offer staking-as-a-service where they run validators on your behalf and pay you a share of the rewards minus a fee.
The tradeoff is between decentralisation (solo validating is best for the network) and convenience (pools are much easier). The market has overwhelmingly chosen convenience, which has produced a situation where a small number of pooled staking services run a large percentage of all validators. This is the main centralisation concern for Ethereum PoS, and the Ethereum Foundation has been pushing initiatives like “distributed validator technology” (DVT), staking hardware appliances, and solo-staker outreach to try to shift the balance back toward solo participation.
The Validator as a Unit of Stake
Ethereum’s protocol distinguishes validators by their deposit rather than by their operator, which creates some quirks. The 32 ETH minimum is per validator, not per operator, so a staking service with $3.2 million in deposits runs 100 validators even though they are all operated by the same entity. The “million validators” figure you see in statistics is a count of validator keys, not a count of independent operators — the real operator count is much smaller, in the high hundreds or low thousands depending on how you count.
EIP-7251, shipped in the Pectra upgrade in 2025, allowed validators to effectively bundle up to 2,048 ETH into a single validator, which reduces the artificial inflation of validator counts and simplifies operations for large stakers. This is one of several ongoing changes aimed at making the validator architecture more flexible and closer to what actual validator operations look like in practice.
The validator role is both the most important economic function on Ethereum and one of the least-understood parts of the system for ordinary users. Most ETH holders never interact with validators directly; they just see their staking yield show up in whatever service they use. But the fact that there are real people running real nodes, following specific protocol rules, and being economically incentivised to do so correctly is what the security of the entire network depends on, and it is worth understanding even if you never run one yourself.