Companies and projects covered
Prepared by the Token Metrics Editorial Team using the official sources listed below. Product terms, eligibility, limits, fees, and protocol rules can change; confirm current details before acting.
Who it fits — and who should avoid it
A self-custody user may consider Lido when they want liquid staking without operating validator hardware and can safely sign onchain transactions. The stETH token can be held or used elsewhere, but each added DeFi protocol creates another contract and liquidation path.
Avoid it if you do not understand wallet approvals, token contracts, withdrawal queues, or governance risk. Solo staking may fit an operator who wants direct validator control. A custodial service may feel simpler but replaces protocol complexity with account and counterparty exposure.
Deposit and stETH accounting
The Lido core contract accepts ETH, buffers deposits, mints stETH, and routes funds through protocol components. stETH is a rebasing token whose balances reflect oracle-reported accounting. That is different from a bank balance and from a token with a fixed exchange rate.
Before staking, verify the official contract address from Lido documentation, check the connected network, inspect the transaction, and confirm the received token. A copied token symbol in a wallet is not proof that the contract is genuine.
Node operators and staking modules
Lido does not send every deposit to one validator operator. Its Staking Router allocates stake across modules, which can have different operator admission and risk designs. The curated module and community staking components should be evaluated as part of protocol structure, not treated as background vendor staffing.
A user cannot pick a particular validator through the standard pool workflow. Review module and operator information, concentration, incident processes, and how governance can change routing parameters.
Rewards, protocol fee, and slashing
Lido documentation explains that staking rewards and penalties flow through protocol accounting and that a protocol fee is applied to staking rewards under current DAO parameters. Do not turn that into a fixed net-yield promise. Validator performance, network issuance, MEV, slashing, fee settings, and token use all affect outcomes.
The stETH balance mechanism can reflect negative as well as positive accounting events. If stETH is used as collateral, a price move or protocol event can create a separate liquidation risk even when the underlying staking position remains active.
Withdrawal queue and secondary-market exit
The protocol withdrawal path uses a request queue represented by an NFT before ETH can be claimed. Timing depends on protocol and network conditions. A user can also trade stETH or wrapped stETH on a secondary market, but the available price may differ from the underlying accounting value.
Plan the exit before entry. Decide whether you can wait for the queue and how you will secure the withdrawal NFT. If you use a market exit, set a maximum acceptable difference and account for network and trading costs.
Governance and control surface
LDO governance can change protocol parameters and components. Lido’s Dual Governance system gives stETH holders a veto-signaling and rage-quit path under documented states and timelocks. This adds a user protection mechanism, but it also adds contracts and operational steps.
Monitor proposals and protocol notices when holding a large or long-lived position. Governance documentation can change. Do not rely on a summary when a proposal affects fees, modules, contracts, or exit rights.
Strengths, limitations, and alternatives
Lido’s main differentiator is liquid stETH plus a broad operator and module architecture. The token can be integrated across DeFi, and official docs expose core contracts, routing, withdrawals, and governance.
That same composability is the main source of added risk. Alternatives include solo staking, a staking service with direct validator keys, Rocket Pool pooled staking, or no staking. Rocket Pool also provides a liquid token but has a different node and protocol design.
Decision scenario
Scenario: a self-custody holder wants liquidity while staking but may need ETH within months. Compare the protocol withdrawal queue with a possible market sale before depositing. Use a small transaction, verify stETH receipt, avoid unknown DeFi integrations, and write down the steps needed to request and claim a withdrawal.
Decision checklist
Did you verify the official Lido contract and network? Do you understand rebasing stETH, staking modules, operator routing, oracle reports, protocol fees, and slashing? Is the exit plan a withdrawal request or a market trade? Can you secure a withdrawal NFT? Have you reviewed governance changes and every DeFi contract where stETH or wstETH will be used?
Frequently asked questions
Are returns, execution, availability, or safety guaranteed? No. This profile describes documented workflows and decision checks, not a guarantee or rating.
Why are no fixed fees or limits quoted? Dynamic terms can vary by route, account, market, or protocol state. Use the official pages and a current test.
What should happen before production use? Verify identity and permissions, run normal and failure cases, document support ownership, and keep an exit or migration plan.
Plain-language test plan
Use a fresh wallet for a small test. Check the network first. Get the contract address from Lido docs. Compare every character. Read the wallet call. Deposit only the test amount. Confirm the stETH token contract. Watch how its balance works. Do not call it bank interest. Read the current fee rule. Read the operator and module pages. Note who can change a setting. Test the normal withdrawal path. Keep the request NFT safe. Learn when it can be claimed. Do not promise a wait time. Also check a market exit. Note that its price can differ. Pick one exit before the main deposit. Do not move stETH into a new app at once. Read that app’s own risks first. Avoid wide token approvals. Revoke any approval no longer needed. Watch Lido notices and governance. Write down what would make you leave. Keep tax records for each move. Compare this path with solo staking. Compare it with Rocket Pool. Choose the set of risks you can name and manage.
Release record
Make a Lido position note. Record the wallet. Record the network. Record the token contract. Record the amount sent. Record stETH received. Record the fee rule source. Record the chosen exit. If you request a withdrawal, record the NFT. Keep the NFT in the safe wallet. If you trade out, record the venue and price. Add each later DeFi app. Note what that app can do. Remove an app when use ends. Review the note after a Lido vote. Review it after a contract change. A clear note helps the holder see every added layer. Keep the note near the key plan. Do not put keys in it. Add the last source check. Add the next check date. Mark any open vote. Mark any token approval. Remove an old approval. Test the claim step with care. Read the wallet screen twice. Stop if the contract is wrong. Stop if the network is wrong. A slow check can prevent a hard loss.
Continue your research
Explore Token Metrics research
