Ethereum proof-of-stake secures the chain with money at risk instead of mining work. Validators each lock up 32 ETH, the beacon chain coordinates them in 12-second slots, and a block becomes final, meaning it cannot be reversed, once two-thirds of all staked ETH agrees. That takes roughly 13 minutes.
What is Ethereum proof-of-stake, and how does it secure the chain?
Proof-of-stake is the system Ethereum uses to agree on which transactions are real. People called validators put up 32 ETH as a deposit. Honest work earns them small rewards. Cheating destroys part of that deposit. The money at risk is what keeps everyone honest.
Think of it like a deposit you leave at a busy market stall. If you play fair, you get your goods and a small bonus for showing up. If you try to cheat the stall, you lose the deposit you left behind. Nobody has to police you closely. The deposit does the work, because losing it hurts more than cheating could ever pay.
That is the heart of proof-of-stake, often shortened to PoS. The network does not trust validators because they are nice. It trusts them because misbehaving is expensive. The more ETH staked across the whole network, the harder and costlier it becomes for any attacker to take control (source: Ethereum consensus mechanisms overview).
Ethereum has not always worked this way. It switched to proof-of-stake at an event called the Merge on September 15, 2022, moving away from the energy-heavy mining model it used before. The full story of that switch is its own topic, covered in our companion guide on the Merge.
Before proof-of-stake, Ethereum used proof-of-work, where computers raced to solve puzzles and spent huge amounts of electricity to secure the chain. Proof-of-stake replaces that race with staked capital. We will not unpack the full mining-versus-staking debate here. For a side-by-side comparison of the two systems, see our guide on proof of work versus proof of stake. Bitcoin still runs on mining, and how the two networks differ is covered in Bitcoin versus Ethereum.
The one idea to carry forward is simple. Proof-of-stake turns honesty into the cheapest option. Everything else in this guide, the validators, the voting, the finality, is just the machinery that makes that bet pay off.
What is a validator, and what does staking 32 ETH actually do?
A validator is a piece of software that runs with a 32 ETH deposit behind it. That deposit, called the stake, is what lets it join in. A validator does two jobs. When chosen, it proposes a new block of transactions. The rest of the time, it attests, meaning it votes that other blocks look correct.
The 32 ETH stake is not a fee. It is collateral, money held as a promise of good behavior. As long as the validator does its jobs honestly, the stake stays safe and earns small rewards over time. If the validator tries to cheat the network in a provable way, the protocol takes part of that stake away. We will look at exactly how later.
Here is what a validator actually spends its day doing:
Job | What it means | Reward or risk |
|---|---|---|
Propose | When randomly chosen, bundle transactions into a new block and broadcast it | Earns a reward for a valid block on time |
Attest | Vote that a proposed block is valid and on the right chain | Earns small rewards for honest, on-time votes |
Stay online | Keep running so it can vote when needed | Small penalties if offline, not a destroyed stake |
Stay honest | Never sign two conflicting things | Loses part of the stake if it cheats provably |
Attesting is the job a validator does most. Proposing happens rarely, because only one validator proposes per slot and there are many validators. Most of the time, a validator is simply voting on the work of others. Those votes are how the network reaches agreement without any central referee.
You do not need to picture special hardware here. The deep details of how a validator is set up, run, and retired are a separate subject, covered in our future guide on Ethereum validators. For this guide, the point is the role: 32 ETH at stake, two jobs, and rewards or penalties that depend entirely on doing those jobs honestly (source: Ethereum proof-of-stake documentation).
What is the beacon chain, and how does it coordinate validators?
The beacon chain is Ethereum's consensus layer, the part that manages agreement among validators. It keeps a record of every validator, picks who proposes each block, tallies the votes, and decides which blocks are final. Without it, the validators would be a crowd with no way to agree.
A good way to picture the beacon chain is a control tower at an airport. The planes, our validators, do the flying. But the tower decides who takes off and when, watches every aircraft, and confirms each landing as official. No plane lands itself on the record. The tower signs off. The beacon chain plays that role for Ethereum (source: Ethereum beacon chain overview).
So what does the beacon chain actually store and track? A few things stand out:
The validator registry. A list of every active validator, its stake, and its current status. This is how the network knows who is allowed to vote.
The schedule. Which validator proposes in each upcoming slot, and which validators are grouped together to vote on each block.
The votes. Every attestation, the votes validators cast, gets collected and counted here.
Finality. The beacon chain is where the network decides a block is locked in for good.
The beacon chain runs on a strict clock, which is what makes coordination possible across thousands of validators scattered around the world. That clock is built from slots and epochs, and they are the next piece to understand. They are the reason every validator knows exactly when it is its turn to act and when it should vote.
One note on names. The beacon chain started as a separate chain before proof-of-stake and later merged with Ethereum's main chain. Today it is simply Ethereum's consensus layer, working underneath the transactions you actually send. You never interact with it directly, but it is running every second your ETH sits on the network.
How do slots and epochs schedule the work?
Ethereum runs on a steady clock. Time is split into slots, each lasting 12 seconds, and one validator is randomly chosen to propose a block in each slot. Slots are grouped into epochs of 32 slots, which works out to 6.4 minutes. Epochs are the unit the network uses to measure finality.
In each 12-second slot, one validator gets the proposer job, and a group of others, called a committee, attests. A committee is just a batch of validators assigned to vote in that slot. The proposer builds the block; the committee votes on whether it looks right. Twelve seconds later, a new slot begins with a new proposer and new voters. A clear walk-through of how slots and epochs fit together is laid out in an independent technical explainer (source: Ethos.dev beacon chain primer).
The choice of who proposes is random and decided in advance by the beacon chain. No validator can buy or grab the proposer slot. This randomness matters, because if an attacker could pick when to propose, they could line up to do damage. Spreading the job randomly across many validators keeps any single one from gaining too much sway.
Here is how the timing stacks up, from the smallest unit to the point a block is locked in:
Unit | How long | What happens |
|---|---|---|
Slot | 12 seconds | One validator proposes; a committee attests |
Epoch | 32 slots, about 6.4 minutes | A full round of slots; a checkpoint forms at the boundary |
Finality | About 2 epochs, roughly 13 minutes | A block becomes irreversible once enough stake agrees |
A checkpoint is simply a block at the boundary of an epoch that the network uses as a marker when measuring finality. Think of checkpoints as the mileposts the network counts to decide a block is permanent. We will see exactly how that count works next.
The takeaway is rhythm. Every 12 seconds, a block. Every 6.4 minutes, an epoch closes. And after about two epochs, the work done earlier is locked in for good. That steady beat is what lets thousands of validators stay in step without anyone giving orders.
What is finality, and how does a block become irreversible?
Finality means a block can no longer be reversed or removed. On Ethereum, a block becomes final when a two-thirds supermajority, that is 66 percent, of all staked ETH votes to agree on it across two consecutive checkpoints. That takes about two epochs, or roughly 13 minutes. After that, the block is permanent.
Here is why two checkpoints are needed. At the first epoch boundary, the network sees that two-thirds of the staked ETH supports a checkpoint, and it marks that checkpoint as justified, meaning strongly supported but not yet locked. When the next checkpoint also earns two-thirds support, the earlier one becomes finalized, meaning permanent. Two rounds of agreement, not one, are what make it safe. The precise voting rules that govern this two-checkpoint process are defined in Ethereum's open consensus specifications (source: Ethereum consensus specifications).
Let us walk one deposit through the process. Say your ETH transfer lands in a block at slot 5 of an epoch:
Proposed. A validator includes your transaction in its block. The block exists, but it is not yet safe.
Attested. Committees across the next slots vote that the block is valid. Support builds.
Justified. At the epoch boundary, two-thirds of staked ETH backs the checkpoint above your block. It is now strongly supported.
Finalized. At the next epoch boundary, another two-thirds vote locks the earlier checkpoint in place. About 13 minutes after your transaction, the block holding it is irreversible.
From Blofin's operational perspective, finality is why our deposit crediting waits a set number of confirmations. Once the network finalizes the block your deposit is in, the transaction cannot be reorganized away, and that is the point at which our systems safely credit your balance. We are not running validators or voting on blocks; we are simply watching the same public finality signal every Ethereum user can see, and waiting for it before we treat your funds as settled.
What makes finality strong is the cost of breaking it. To revert a block that is already finalized, an attacker would need to control and then lose at least one-third of all the staked ETH on Ethereum. As of 2026, that is tens of millions of ETH, an enormous sum to put at risk. Reversing finalized history is not just hard; it is designed to be financially ruinous for whoever tries. That is the guarantee finality rests on, and it is verified against the protocol's own rules rather than any single company's word.
What stops a validator from cheating? Slashing and the inactivity leak
Two protections keep validators in line, and they handle different problems. Slashing destroys part of a validator's stake and removes it from the network for provably malicious acts. The inactivity leak slowly bleeds stake from validators that go silent when the chain is struggling to reach finality. One punishes cheating; the other punishes absence at the worst possible time.
Slashing is the serious one. It fires only for actions the protocol can prove are malicious, not for honest mistakes. The two clearest examples are double-proposing, where a validator signs two different blocks for the same slot, and contradictory attestations, where a validator votes for two conflicting versions of history. Both are things an honest validator simply never does. When the network catches one, it destroys part of the validator's 32 ETH stake and ejects it (source: Ethereum solo staking guide).
It helps to keep two very different penalties straight, because beginners often blur them:
Situation | What triggers it | What it costs |
|---|---|---|
Slashing | Provably malicious acts, like double-proposing or contradictory votes | Part of the stake destroyed, validator ejected |
Being offline | Simply not voting because the validator is down | Small penalties, roughly the rewards it would have earned |
Inactivity leak | The chain fails to finalize for more than 4 epochs and a validator stays silent | Stake steadily bleeds away until finality returns |
Being merely offline is not slashing. If a validator's software goes down, it loses small amounts, roughly the rewards it missed. That is a minor cost, not a destroyed stake. Slashing is reserved for the provably bad behavior described above. This separation matters: it means an honest validator that has a bad day is treated very differently from one that tries to attack the chain.
The inactivity leak is a clever safety valve. If the chain cannot reach finality for more than four epochs, perhaps because too many validators are offline at once, the network starts draining stake from the silent ones. As their share shrinks, the validators still online eventually make up two-thirds of the active stake again, and finality can resume. The leak is how Ethereum heals itself even if a large group disappears.
From Blofin's operational perspective, the economic security of proof-of-stake, that an attacker would have to put up and then lose enormous staked value to rewrite finalized history, is exactly why we treat a finalized Ethereum deposit as settled and irreversible, the same standard we apply across the networks we support. We do not stake user ETH or run validators; we observe the guarantee the protocol enforces and build our deposit handling on top of it.
What do validators earn, and how much ETH is staked in 2026?
Validators earn newly issued ETH plus a share of transaction fees for doing their jobs honestly. That reward is usually described as a yield, a percentage return on the staked ETH. As of 2026, the base yield runs roughly 2.7 to 3.5 percent a year. It is protocol issuance, not a promised return.
The yield is not a fixed rate that someone pays out. It comes from the protocol issuing small amounts of new ETH to reward honest work, plus the tips from transactions a proposer includes. When more ETH is staked across the network, each validator's slice of the rewards gets a little thinner. When less is staked, each slice grows. The rate moves on its own as participation changes.
Here is a snapshot of Ethereum's staking scale, framed as ranges because these figures move and should be treated as a guide. All values are as of 2026 and shift with network participation:
Measure | As of 2026 (approximate range) |
|---|---|
Active validators | About 0.9 to 1 million |
Share of ETH supply staked | About 30 to 33 percent (roughly 36 to 40 million ETH) |
Base staking yield | About 2.7 to 3.5 percent a year |
Custodial product yield | About 2.1 to 2.3 percent |
Solo validator yield | About 3.2 to 3.8 percent |
These figures come from public staking trackers and shift constantly, so treat them as a picture of 2026, not a quote (source: Beaconcha.in validator dashboard). The protocol rules behind staking rewards are set out in Ethereum's own staking documentation (source: Ethereum staking documentation). The yield also depends on the method. A custodial product, where a company runs the validator for you, tends to pay a little less because the company keeps a cut. A solo validator, where you run everything yourself, tends to keep more. Some validators also earn an extra slice, roughly 0.5 to 1 percent, from a practice called MEV, which is its own subject and covered in our future guide on Ethereum MEV.
None of this is a recommendation. The numbers describe how the protocol issues rewards, not advice on whether to stake. If you want to understand staking as an investor, including how to actually do it and what the trade-offs are, that lives in our guide on staking in a crypto portfolio. The point here is just the mechanism: honest work earns issuance plus fees, and the headline rate drifts with total participation.
Can you stake without running a validator? Liquid staking, briefly
Yes. You do not need 32 ETH or your own validator to stake. With liquid staking, you put your ETH into a protocol like Lido, which pools it with other people's ETH and runs the validators for the group. In return, you receive a token that represents your staked ETH and keeps the ETH usable while it stays staked.
That token is the clever part. Normally, staked ETH is locked and cannot be moved. A liquid staking token gets around this by standing in for your staked position, so you can hold it, trade it, or use it elsewhere while your underlying ETH keeps earning. The mechanics of how those tokens work as an investment, the yields involved, and the risks to weigh are covered in our guides on liquid staking in a crypto portfolio and the Blofin staking earn guide. For this protocol-level guide, the one idea to keep is that liquid staking lets you join in without the 32 ETH bond or the validator software.
Frequently asked questions
How long does it take for an Ethereum block to become final?
About 13 minutes. A block becomes final once a two-thirds supermajority of all staked ETH agrees on it across two consecutive checkpoints, which are markers at the boundaries of epochs. Since each epoch is roughly 6.4 minutes and finality needs two of them, the full process takes around two epochs, or about 13 minutes. After that, the block cannot be reversed.
Do you need 32 ETH to take part in Ethereum staking?
To run your own validator, yes, you need 32 ETH as the stake. But you do not need that much to stake at all. Through liquid staking, you can put in any amount with a protocol like Lido, which pools your ETH with others and runs the validators for the group. You receive a token representing your share, and that token keeps your ETH usable while it earns.
What is the difference between slashing and being offline?
They are very different penalties. Being offline simply means a validator is not voting because its software is down, and it costs only small penalties, roughly the rewards it would have earned. Slashing is far harsher: it destroys part of the validator's stake and removes it from the network. Slashing fires only for provably malicious acts, like signing two conflicting blocks, not for honest downtime.
What does the beacon chain do?
The beacon chain is Ethereum's consensus layer, the part that manages agreement among validators. It keeps a record of every validator and its stake, randomly picks who proposes each block, collects and counts the votes called attestations, and decides which blocks are finalized. You never interact with it directly, but it runs underneath every transaction, coordinating thousands of validators on a strict 12-second clock.
How hard is it to attack Ethereum proof-of-stake?
Extremely hard, and extremely expensive by design. To reverse a block that has already been finalized, an attacker would need to control and then lose at least one-third of all the ETH staked on the network. As of 2026, that is tens of millions of ETH. The whole system is built so that attacking it costs far more than any attacker could gain, which is what makes finalized history safe to treat as permanent.
Researched and written by the Blofin Academy editorial team with AI-assisted drafting. Primary sources include the Ethereum proof-of-stake documentation, the Ethereum beacon chain overview, and the Ethereum staking documentation, with 2026 staking figures drawn from public network trackers. All facts independently verified against cited documentation current as of June 2026.
This article is for informational purposes only and does not constitute financial advice, investment guidance, or a recommendation to buy, sell, or hold any digital asset. Staking yields are protocol issuance that varies by method and over time, not a promised return. Cryptocurrency markets involve significant risk and you should conduct your own research and consult qualified professionals before making decisions. Blofin Academy content reflects the state of public information at time of publication; validator counts, staking levels, and yields change frequently.