Lido is Ethereum staking with a transferable stETH balance

Lido is a way to earn Ethereum staking rewards while holding a transferable token that represents deposited ETH. The protocol pools deposits, routes ETH through staking modules to validators, and issues stETH, whose wallet balance reflects pooled staking results. This removes the 32 ETH solo-validator entry threshold for depositors and keeps the position usable across decentralized finance. It adds layers beyond native staking: smart contracts, oracle reporting, node-operator performance, DAO governance, and secondary-market pricing. The sections below explain fees, risk checks, entry and exit paths, DeFi uses, accounting mechanics, and credible alternatives.

In short: A one-third share of staked ETH is enough to delay Ethereum finality, even without controlling two-thirds.

The 10% reward fee and changing transaction costs

Core Lido staking charges a 10% protocol fee on Ethereum staking rewards. That fee comes from rewards, rather than the ETH initially submitted. The remaining 90% increases the pooled value represented by holders' stETH. StakingRouter records module and treasury shares in basis points: a 500-basis-point operator allocation, or 5%, plus a 500-basis-point treasury allocation equals the full 10%. Operator shares differ across staking modules, and LDO governance can change these parameters.

Network costs sit outside that fee. A direct ETH transfer has an intrinsic 21 000-gas requirement, while calling Lido's staking, wrapping, or withdrawal contracts consumes more gas because contract logic executes. Under EIP-1559, the base fee moves by at most 12.5% between adjacent blocks at the extremes, and the sender also sets a priority fee. A decentralized exchange route adds the fee that the pool charges plus price impact. Comparing direct staking with a Curve or Uniswap swap therefore requires the quoted token amount, pool liquidity, and total gas.

Lido charges no separate protocol withdrawal fee; requesting and claiming still require Ethereum transactions.

Smart contracts, validators, and market pricing

By contrast, Lido exposure combines smart-contract execution, validator performance, oracle reporting, governance, and stETH liquidity (more in Lido guide use cases ).

Smart-contract risk covers the Core Pool, StakingRouter, AccountingOracle, WithdrawalQueueERC721, wstETH wrapper, and every DeFi protocol added afterward. Validator downtime reduces rewards, while slashable consensus faults create penalties that pooled accounting distributes across holders. Oracle reports turn consensus-layer balances and execution-layer rewards into a rebase. A delayed report postpones the balance update; a negative pool result reduces it. Lido V3 also introduces stVaults whose external stETH shares are minted against overcollateralized vault positions, adding reserve-ratio and forced-rebalancing mechanics beyond the simpler Core Pool path.

stETH has both a protocol accounting value and a secondary-market price. The market price moves with buyers, sellers, available liquidity, and confidence in redemption. A protocol withdrawal follows queue accounting, whereas an immediate exchange uses the available market quote. Depositing wstETH into Aave adds collateral and liquidation risk; supplying stETH or wstETH to Curve, Uniswap, or Balancer adds the rules and price exposure of that pool. Each additional contract expands the position's dependency chain.

Validator concentration and Ethereum finality

Validator concentration matters because pooled stake carries voting weight in Ethereum's proof-of-stake consensus.

Ethereum finality needs votes representing at least two-thirds of total staked ETH, while one-third can delay finalization. That threshold does not grant arbitrary control over balances or protocol rules. It creates a network-liveness concern when too much voting weight shares one coordination system, governance process, or operational dependency.

Ethereum divides time into 12-second slots, and 32 slots form a 6.4-minute epoch. Finality links checkpoints across two epochs, with user-facing finality commonly arriving in about 15 minutes. EIP-7251 keeps the minimum validator activation balance at 32 ETH and permits compounding validators up to 2 048 ETH. Larger effective balances reduce validator-count overhead, but stake weight remains concentrated wherever ownership and coordination remain concentrated.

On the same footing, Lido's StakingRouter separates validator groups into modules, including the Curated Module, Simple DVT, and Community Staking Module. Modules diversify entry rules and operator sets, while the DAO still controls key protocol parameters. The relevant decision is not a live market-share snapshot; it is how much coordinated stake, oracle dependence, and governance exposure the user accepts.

stETH and wstETH across DeFi

stETH suits applications that correctly account for rebasing balances, while wstETH supplies fixed-balance compatibility.

Both tokens use 18 decimal places, but their accounting looks different. stETH balances normally change when the daily oracle report applies, without an ERC-20 Transfer event for each holder. wstETH keeps its token count fixed and changes the amount of stETH represented by each unit. Curve and some Yearn strategies support rebasing stETH, while Aave V3 markets, Uniswap, and Balancer commonly integrate wstETH for predictable balance accounting.

wstETH is also the practical form for bridges and Layer 2 networks because token counts remain stable between reports. Established deployments include OP Mainnet, chain ID 10, and Arbitrum One, chain ID 42161; contract addresses differ by network. Lending, liquidity provision, and collateral use remain separate positions with their own interest, liquidation, pool, and bridge mechanics. The chosen application must explicitly support the exact token and network.

A deliberate path from ETH to stETH

Entering Lido directly requires ETH, an Ethereum wallet, and enough ETH for execution gas.

The Core Pool mints stETH against submitted ETH at a 1:1 accounting ratio, subject to protocol rate limits. Depositors do not need 32 ETH, validator keys, an execution client, or a consensus client. MetaMask, Ledger, and WalletConnect-compatible interfaces can sign the transaction, but the signer must remain on Ethereum Mainnet, chain ID 1. Buying stETH through Curve or Uniswap reaches the same transferable token through market liquidity, so the received amount follows the quoted trade.

The decision turns on five concrete checks, as set out in Using Lido.

• Confirm that the wallet shows Ethereum Mainnet, chain ID 1, and reserve ETH for gas.
• Choose direct minting for protocol-issued stETH, or compare the full decentralized exchange quote before buying.
• Select stETH for rebase-aware use, or wstETH when the application expects a fixed token count.
• Read the submitted amount, destination contract, and maximum transaction fee before signing.
• Plan either a queued protocol withdrawal or a market exchange, because timing and exchange value differ.

Direct staking takes one contract transaction. Wrapping existing stETH normally requires an allowance and a wrapping call, while a dedicated ETH-to-wstETH route can combine the economic steps. The wallet retains the liquid token, not individual validator keys or a claim on one named operator. Future rewards follow whoever holds the token or the DeFi position that accounts for it.

The withdrawal NFT and exit path back to ETH

Broadly, Lido withdrawals use a first-in, first-out queue that separates requesting from claiming ETH.

Each request accepts at least 100 wei of stETH, equivalent to 0.0000000000000001 stETH, and at most 1 000 stETH. Larger amounts are divided into multiple requests. Submitting stETH or wstETH mints one unstETH NFT under the ERC-721 standard for each request; wstETH is converted into its stETH amount for queue accounting. The NFT owner can transfer the request or claim its ETH after finalization. Claiming burns the NFT, so the same request cannot be collected twice.

Queue time is not fixed. Available ETH in the protocol buffer, new deposits, pooled rewards, the amount already waiting, Beacon Chain exit capacity, validator performance, and the protocol's operating mode determine finalization. A decentralized exchange settles within one transaction after inclusion, yet it uses the available market price and liquidity rather than withdrawal-queue accounting.

Once a request enters the queue, its submitted stETH stops receiving later rebases.

Shares, oracle frames, and daily rebases

For a first attempt, Lido records ownership as shares, then derives each stETH balance from pooled ether.

An account's stETH balance equals its shares multiplied by total pooled ether and divided by total shares. The token exposes 18 decimals, and integer division can leave a 1-wei remainder in edge-case transfers. Shares remain stable through a normal rebase; the pooled-ether numerator changes. This design updates every holder economically without iterating over every address or emitting millions of transfer events.

AccountingOracle normally reports once per frame. A frame spans 225 Ethereum epochs; at 32 slots per epoch and 12 seconds per slot, that equals 86 400 seconds, or 24 hours. The report updates validator balances, execution-layer rewards, withdrawal funding, penalties, and fees. If a report misses its frame, the next successful report covers the accumulated accounting period, so wallet balance changes need not land at an identical clock time every day.

wstETH converts that share ownership into a fixed-balance ERC-20 wrapper. Its stETH-per-wstETH rate carries pool changes. Under Lido V3, total stETH supply includes Core Pool shares and external shares from eligible stVaults. Those external shares face reserve ratios and configured caps, making their backing path distinct from a direct Core Pool deposit.

Solo validation, rETH, cbETH, and osETH

Alternatives differ mainly in validator control, custody, reward accounting, liquidity, redemption, and governance.

Solo Ethereum validation preserves direct control of keys and protocol rewards, but it requires at least 32 ETH, an execution client, a consensus client, a validator client, reliable hardware, and continuous operations. A compounding validator using 0x02 withdrawal credentials has a maximum effective balance of 2 048 ETH after EIP-7251; that upper bound does not lower the activation minimum. Staking as a service retains the full-validator capital requirement while outsourcing operations.

Rocket Pool issues rETH, whose token count remains fixed while its ETH exchange rate reflects pooled performance. Coinbase issues cbETH for ETH staked through its custodial service, coupling the token to Coinbase eligibility and account processes. StakeWise issues osETH against overcollateralized staking-vault positions. These alternatives change who selects operators, how rewards appear, and which redemption and governance systems apply. Choosing among Lido, rETH, cbETH, and osETH requires comparing operator entry, token liquidity, contract dependencies, reward accounting, and exit mechanics. Solo staking removes the liquid-token and shared-oracle layers, then transfers uptime, client selection, key management, and maintenance to the operator. Greater control carries greater operational responsibility.