What Actually Happens When You Stake ETH

Most explanations of Ethereum staking stop at “lock up your ETH, earn rewards.” That’s technically true, and it’s also the least useful part of the story. The interesting part (the one that actually matters if you’re deciding whether to stake, how to stake, or who to stake with) happens in between: the validator queue, the consensus mechanics, the reward sources, the penalties, and the exit process that determines how quickly you can get your ETH back when you need it.

This post walks through what actually happens when you stake ETH, technically and economically, from the moment it’s deposited to the moment it’s withdrawn; and why the details in between are exactly what separates a retail staking decision from an institutional one.

Staking ETH, in One Paragraph

When you stake ETH, you’re depositing it as collateral to help run Ethereum’s proof-of-stake consensus mechanism. In exchange for locking that capital and running (or delegating) validator software, you earn a share of the ETH the protocol issues to secure the network, plus a portion of transaction fees and MEV (maximal extractable value) captured when your validator proposes a block. The system replaced Ethereum’s old energy-intensive mining model in 2022, and validators now do the same job miners used to do: proposing blocks and confirming other validators’ work, using economic stake instead of computational power as the deterrent against bad behavior.

That’s the summary version of what happens when you stake ETH. Here’s what’s actually happening underneath it.

Step One: The Deposit and the Validator

Every Ethereum validator is backed by exactly 32 ETH. That number isn’t arbitrary; it’s calibrated to keep the total number of validators (and the messages they need to exchange to reach consensus) within a range the network can handle, while keeping the cost of running a validator low enough that solo staking stays accessible to individuals, not just large institutions.

Once 32 ETH is deposited and the validator key is generated, the validator doesn’t go live immediately. It enters an activation queue, and how long it waits depends on how many other validators are trying to join at the same time. During periods of high demand, that queue has stretched to weeks. This is the first thing many new stakers don’t expect: staking isn’t instant, in either direction.

Once active, the validator’s job is straightforward but constant. It needs to be online, correctly attest to which blocks it believes are valid, and occasionally propose a new block itself. It needs to do this reliably, because both the rewards and the penalties are built around uptime and correctness, not just participation.

Step Two: Where the Rewards Actually Come From

“Staking rewards” sounds like a single number, but it’s actually three separate revenue streams stacked together:

• Consensus layer (protocol) rewards: new ETH issued directly by the protocol to validators for attesting to blocks and proposing them correctly. This is the base layer of staking yield, and it scales down as more ETH is staked network-wide, since the same issuance is split across more validators.
• Priority fees: the optional tips users attach to transactions to get faster inclusion. These go to whichever validator proposes the block.
• MEV: additional value validators can capture from how transactions within a block are ordered. This has become a meaningful and fairly consistent component of total yield, though it varies block to block.

Combined, these currently put ETH staking yield in the neighborhood of 2.5-3% annually, though the exact figure moves with total ETH staked network-wide and network activity. Ethereum.org’s staking page is a good primary source for current network-wide participation and APR figures, since both shift over time.

One detail worth sitting with: the more ETH that gets staked across the network, the lower the individual reward rate goes, because issuance is shared across a larger validator set. That’s a deliberate design choice; the protocol doesn’t want an unbounded incentive to stake everything, since that would also mean more ETH sitting in exit queues at any given time. It’s a small mechanical detail with a large downstream consequence for how institutions size their staking allocation, which we’ll come back to.

Step Three: What Can Go Wrong

This is the part that gets glossed over in most “staking 101” content, and it’s the part that matters most if you’re staking anything beyond pocket change.

Downtime penalties. If a validator goes offline, it stops earning and starts incurring small penalties for the attestations it misses. This isn’t catastrophic on its own, but it’s a direct hit to net yield, and it’s the reason infrastructure reliability -not just staking mechanics- determines actual realized returns. 

Slashing. This is the serious one: a validator that behaves maliciously or makes specific protocol violations (like signing conflicting attestations) can be slashed; forcibly ejected from the network with a meaningful portion of its stake burned. In practice, slashing events are rare. Historical uptime across the validator set has stayed above 99.7%, and slashing incidents have affected a small fraction of a percent of validators since withdrawals were enabled. But “rare” isn’t “zero,” and slashing risk is entirely a function of the operator’s infrastructure quality and key management, which is exactly why validator operator selection matters as much as the staking decision itself.

Exit and withdrawal delays. This is the risk that surprises people most, because it has nothing to do with the validator doing anything wrong. Ethereum limits how many validators can exit and how much ETH can be withdrawn per unit of time, to protect network stability. Under normal conditions, that means withdrawal waits of a few days. Under stress, it’s much longer. When a major operator, Kiln, unstaked a large volume of ETH in 2024, the network’s exit queue backed up so severely that withdrawal times stretched from roughly 20 days to more than 45 days, the longest delays in the network’s history at that point. That’s not a hypothetical edge case; it’s a documented data point about how the queue behaves when a lot of ETH tries to exit at once.

Counterparty and smart contract risk. Anyone staking through a pooled service, liquid staking protocol, or exchange is also taking on trust in that provider: their key management, their smart contracts (if applicable), and their operational security. This is a fundamentally different risk profile than solo staking, where the only party you’re trusting is yourself.

None of these risks are evenly distributed across ways to stake ETH. Downtime penalties and slashing are almost entirely a function of the operator’s infrastructure discipline: redundant systems, tested failover, and rigorous key management materially lower the odds of either. Liquidity risk, on the other hand, is a network-level constraint that no individual operator can fully engineer around, which is exactly why it has to be managed at the portfolio level rather than assumed away. Understanding which category a given risk falls into is a useful filter for evaluating any staking provider’s claims: infrastructure risk is something a provider can genuinely reduce, while queue-driven liquidity risk is something a provider can only help you plan for.

The Four Ways to Actually Stake ETH

Each of these trades off differently across custody, decentralization, fees, and critically for anyone staking meaningful volume liquidity. Exchanges like Kraken and Coinbase have made custodial staking essentially frictionless for retail users: Coinbase, for example, lets ETH staked directly from an account balance start earning rewards immediately, with no minimum, though standard unstaking still runs through the network’s normal wait period (Coinbase also offers an instant-unstake option for a fee, and a liquid wrapped token, cbETH, for users who want to stay staked while retaining tradeable liquidity). Kraken’s explainer walks through the reward-rate mechanics from a similar retail-first angle.

That convenience is the right tradeoff for a lot of individual holders. It’s a materially different calculation for an institution.

Why This Looks Completely Different at Institutional Scale

Everything above is true regardless of who’s staking. What changes at institutional scale isn’t the underlying mechanics; it’s which risks become operationally unacceptable.

Take the exit queue. A retail staker who has to wait 45 days for a withdrawal during network congestion is inconvenienced. A fund, an ETP issuer, or a treasury desk that has to meet daily redemptions and can’t access staked ETH fast enough has a real liquidity mismatch on its hands. iShares’ guide to Ethereum staking is explicit about this, noting that withdrawal delays that stretch from days to weeks ,or longer under stress, are a core structural risk institutional products have to design around, not an inconvenience they can absorb after the fact.

That’s precisely why 21Shares has been public about deliberately not staking 100% of the ETH behind its products. Their own explanation is worth reading in full, but the core logic is simple: staking over roughly 90% of assets creates redemption risk, because meeting investor withdrawals during a queue backlog like the one triggered by Kiln’s mass unstaking isn’t optional. Their answer is a dynamic staking strategy, adjusting the staked percentage based on market conditions and redemption flows, and keeping unstaked reserves on hand deliberately, even at the cost of some yield.

This is the piece that gets lost when staking is explained purely as a rewards mechanism. For an institution, the staking decision isn’t “how do I maximize APR.” It’s a liquidity management problem, a counterparty due-diligence problem, and, increasingly, as frameworks like MiCA mature in Europe, a compliance and reporting problem, all layered on top of the base protocol mechanics.

That’s also why the operational track record of whoever is running the validator infrastructure matters more at scale than at the retail level. When an institution decides to stake ETH, it isn’t just choosing a yield; it’s choosing a counterparty whose uptime, key management, and incident history become part of its own risk profile. Independent verification of controls, through audit frameworks like SOC 2 Type II and the Cryptocurrency Security Standard (CCSS), stops being a nice-to-have and starts being the actual basis for a due diligence decision, the same way it would be for any other piece of critical financial infrastructure. Regulatory frameworks maturing around staking (MiCA in Europe being the clearest example) are pushing in the same direction: toward operators who can document their controls, not just advertise a rate.

There’s a related, less-discussed variable too: where and how validator infrastructure is run. Geographic and client diversity across an operator’s validator set reduces the odds that a single regional outage, cloud provider incident, or software bug takes down a large share of stake at once, which matters just as much for realized uptime as raw hardware quality does. Energy sourcing has become part of that same conversation, as institutional allocators increasingly factor sustainability commitments into vendor selection alongside security and compliance.

This is the layer GlobalStake was built around: treating staking infrastructure and transparency as the product, rather than an operational afterthought bolted onto a token. If you’re evaluating how to size and structure an institutional staking allocation, our approach to institutional staking infrastructure and our security and compliance standards go into more detail on how we think about the exact tradeoffs described above, because the honest answer to “what happens when you stake ETH” changes considerably once due diligence, not just yield, is part of the question.

What Actually Happens, Step by Step

To bring it all together, here’s the full lifecycle of staked ETH, start to finish:

1. Deposit: 32 ETH (or a fractional pooled equivalent) is committed and a validator key is generated.
2. Activation queue: the validator waits to join the active set; wait time depends on network-wide demand.
3. Active validation: the validator attests to blocks and periodically proposes them, earning consensus rewards, priority fees, and MEV.
4. Ongoing risk exposure: uptime determines realized yield; malicious or faulty behavior risks slashing.
5. Exit request: the validator (or the staker, via a pooled/liquid provider) requests to unstake.
6. Exit queue: the validator waits its turn to leave the active set, a wait time that’s protocol-throttled and can extend significantly under network stress.
7. Withdrawal: ETH becomes liquid and available again.

Every step in that chain has a real-world precedent for taking longer, costing more, or behaving worse than the simplified version suggests — which is exactly why “what happens when you stake ETH” is a more useful question to answer honestly than “how much can I earn.”

Common Questions About Staking ETH

Is staking ETH the same as locking it up forever? No. Staked ETH can be withdrawn once you initiate an exit, but the timeline isn’t instant, it depends on the protocol-level exit queue described above, which can range from a few days to several weeks depending on how many other validators are exiting at the same time.

How much do you need to stake ETH? Solo staking requires exactly 32 ETH per validator. Staking-as-a-service typically has the same requirement while letting a third party run the infrastructure. Pooled and liquid staking, along with most exchange staking options, let you stake ETH with far smaller amounts, sometimes fractions of a single ETH.

What’s the actual risk when you stake ETH? Three categories: downtime penalties (small, tied to validator uptime), slashing (rare, but tied to operator error or misconduct), and liquidity risk (the exit queue, which is a network-level constraint rather than a provider-specific one). None of these are unique to any single platform:  they’re properties of the protocol itself, which is why operator quality is what actually differentiates one staking option from another.

Do staking rewards change over time? Yes. Reward rates move inversely with total ETH staked network-wide, more ETH staked across the network means the same issuance gets split more ways, which lowers the rate for each individual validator. Priority fees and MEV add variable upside on top of that base rate.

Why would an institution not stake all of its ETH? Because staking 100% removes the liquidity needed to meet redemptions or rebalance quickly. As 21Shares has explained, keeping a portion of holdings unstaked is a deliberate liquidity management decision, not a missed opportunity, particularly after real-world exit queue congestion events showed how long withdrawals can actually take under stress.

The Takeaway

Staking ETH is not complicated to describe, but it’s genuinely complicated to do well, especially once the amount involved is large enough that liquidity timing, operator due diligence, and compliance reporting become part of the decision rather than footnotes to it. The protocol mechanics (deposits, activation, rewards, slashing, exit queues) are the same for everyone, whether you stake ETH through an exchange, a pool, or dedicated institutional infrastructure. What differs is how much those mechanics can hurt you if the operational layer underneath them isn’t built to handle scale, stress, and scrutiny.

Understanding what actually happens when you stake ETH and not just the advertised yield is the first step toward staking it responsibly.