Lido is a stETH liquidity layer for Ethereum staking

Lido is a liquid staking protocol for Ethereum that turns deposited ETH into stETH, a tokenized claim on staked ether that accrues validator rewards while remaining transferable. A user deposits ETH into the protocol, receives stETH at a one-to-one minting ratio, and keeps exposure to Ethereum staking without running a validator or locking exactly 32 ETH. That stETH then moves through wallets, exchanges, and DeFi markets as usable DeFi collateral.

The stETH receipt that keeps staked ETH moving

The defining idea is simple: staked ether earns rewards on the Beacon Chain, while stETH gives the holder a liquid token that represents the underlying ETH plus the staking rewards assigned to that position. Through Lido, a deposit becomes part of a pooled validator set, and the holder receives a token balance rather than a validator key. That changes the user experience from infrastructure management into normal ERC-20 token handling.

stETH is rebasable. Its balance updates after the protocol receives oracle reports about validator rewards, penalties, and the total pooled ether controlled by the system. When the validator set performs well, stETH balances rise to reflect rewards. If severe validator penalties or slashing occur, the accounting model also allows the token balance to reflect losses.

How deposits become validator balances

Ethereum validators require 32 ETH per validator, client software, reliable uptime, key management, and operational discipline. The protocol pools deposits, routes ETH to node operators, and activates validators under withdrawal credentials controlled by the staking system. Lido DAO governs protocol parameters, node operator onboarding, treasury decisions, and upgrades through the LDO governance token.

Lido assigns validator work to approved node operators rather than asking each depositor to choose a machine, keep it online, and monitor consensus duties. Validators earn consensus layer rewards for attestations, block proposals, and sync committee participation. They also receive execution layer rewards such as priority fees and MEV-related rewards. Those rewards flow into the accounting system and are reflected for token holders after oracle reporting.

A first stake from an Ethereum wallet

A basic stake starts with an Ethereum wallet holding ETH for the deposit and gas. The transaction sends ETH into Lido and mints stETH to the wallet. From there, the holder either keeps stETH, wraps it into wstETH, supplies it to a DeFi market, swaps it, or later requests a withdrawal back to ETH. The amount staked is flexible, so a user does not need to assemble a full validator-sized balance.

Several details matter before signing. Gas is paid in ETH, wallet permissions should match the exact action being taken, and bridged versions of tokens behave differently from mainnet tokens. Direct transfers to helper contracts are the common avoidable mistake; the normal staking, wrapping, and withdrawal flows use contract methods that create the intended token or queue position.

Daily rebases, wstETH, and DeFi accounting

On a practical level, Lido accounting relies on shares behind the visible stETH balance. A wallet sees a stETH balance, but the protocol tracks each holder's share of total pooled ether. When the daily oracle report updates the pooled ether figure, each holder's balance changes while the underlying share ownership remains the accounting anchor.

wstETH solves a separate integration problem. It is a non-rebasing wrapper around stETH, so the token balance stays fixed while the conversion rate to stETH rises as rewards accrue. That design fits protocols and bridges that expect ERC-20 balances to stay stable between transfers. A holder wraps stETH into wstETH, uses it in an application, then unwraps it later to receive the corresponding amount of stETH at the current rate.

What the 10 percent reward fee pays for

That said, Lido applies a protocol fee to staking rewards rather than taking a fee from the principal deposit. The documented Ethereum fee is 10 percent of staking rewards, split between node operators and the protocol treasury. Token holders receive the remaining rewards through the rebasing or wstETH rate mechanism, after the protocol accounts for validator performance and fee minting.

The Lido DAO controls the fee setting through governance, so the percentage is a protocol parameter rather than a fixed rule embedded forever. This fee funds the operators who run validator infrastructure and the treasury that supports audits, maintenance, grants, tooling, and protocol development. The important user-facing distinction is that the fee comes from earned rewards, while deposited ETH remains the base asset represented by stETH.

Redeeming stETH through the withdrawal queue

More broadly, Lido V2 added in-protocol Ethereum withdrawals. A holder submits stETH or wstETH to the withdrawal queue and receives an unstETH NFT that represents the withdrawal request. The queue follows first-in, first-out ordering. After oracle finalization and available ETH matching, the NFT becomes claimable; claiming burns the NFT and returns ETH to the owner of that queue position.

Each withdrawal request has size limits: at least 100 wei in stETH and at most 1,000 stETH per request. Larger exits are split across multiple requests. Once submitted, a request cannot be canceled, though the withdrawal NFT is transferable. The final ETH amount is set at finalization and reflects the protocol's share rate at that point.

Where stETH shows up across DeFi

stETH and wstETH appear across major Ethereum DeFi venues because they represent staked ETH in token form. Curve, Uniswap, and Balancer provide liquidity routes. Aave markets list wstETH or stETH in selected deployments. Maker has used wstETH and stETH-related liquidity positions in collateral systems. Mellow vaults and restaking-adjacent strategies also build around staked ETH liquidity.

Day to day, Lido Multichain extends wstETH to networks such as Arbitrum, Optimism, Base, Scroll, Linea, zkSync Era, Mantle, Polygon PoS, BNB Chain, and others through bridge-based deployments. On most networks, bridged wstETH does not unwrap locally into stETH. The token still represents the wrapped staked ETH position, but applications use rate feeds and bridge-specific mechanics to account for the underlying value.

Validator, oracle, and governance risks to understand

The main technical risks come from smart contracts, validator operations, oracle reporting, bridge design, and governance choices. Slashing and penalties reduce validator balances when operators violate consensus rules or stay offline under conditions that Ethereum penalizes. Oracle delays affect the timing of rebases. Smart contract flaws affect staking, wrapping, withdrawals, or integrations if a bug reaches production.

Market risk is separate from protocol accounting. stETH is designed as a claim on staked ETH through the protocol, but secondary market prices move with liquidity, leverage, and demand. During stressed markets, swaps between stETH and ETH trade at a premium or discount. That price behavior matters most for users who borrow against stETH, build leveraged loops, or need immediate exit liquidity through a market rather than the withdrawal queue.

Alternatives to the pooled stETH route

Solo staking gives the operator full validator control, direct protocol rewards, and responsibility for uptime, keys, hardware, and 32 ETH chunks. Rocket Pool combines liquid staking with a different node operator model and its rETH token. Coinbase Wrapped Staked ETH packages exchange staking exposure into cbETH. Frax Ether uses frxETH and sfrxETH to separate liquid token handling from reward-bearing staking exposure.

Against Lido, those alternatives differ most in custody model, validator control, token mechanics, DeFi liquidity, and governance structure. The best route depends on whether the priority is self-operation, deep stETH liquidity, exchange convenience, a smaller validator set, or specific integrations. The protocol's strongest practical fit is the user who wants Ethereum staking exposure, automatic reward accounting, and a widely integrated token without managing validator infrastructure.