What is Lido?

Introduction

Lido is a liquid staking protocol, best known on Ethereum for letting users stake ETH without giving up liquidity. That solves a real friction in native staking: staking is supposed to earn yield for helping secure the network, but the act of staking usually makes capital less usable. Lido’s answer is to separate the economic position of staking from the operational work of running validators.

If you stake ETH directly, you are opting into validator operations, activation queues, withdrawal mechanics, and infrastructure risk. If you stake through Lido, you deposit ETH into a pooled protocol and receive stETH, a token that represents your share of the pooled staked ETH. The important shift is that stETH is transferable. Your stake is still exposed to Ethereum staking rewards and validator performance, but the claim on that stake becomes something you can hold, move, trade, or use in other onchain applications.

That is why Lido is useful to a broad set of users. It is for people who want staking exposure without personally running validator infrastructure, and for users who want their staked ETH to remain usable inside the wider Ethereum and DeFi ecosystem. The protocol is also built to serve more demanding participants (such as integrators, institutions, and node operators) but the core idea starts with a very simple user problem: how do I stake without turning my ETH into a dead asset?

What problems does Lido solve for ETH stakers?

Native staking on Ethereum has two jobs bundled together. The first is financial: you lock ETH and earn rewards. The second is operational: validators must be run correctly, kept online, and managed through deposits, exits, and reward collection. For many users, the second job is the obstacle. They want the returns from staking, but not the infrastructure burden.

There is a second problem layered on top. Even if you are comfortable staking, staked ETH is not as flexible as unstaked ETH. It is committed to validator balances and subject to Ethereum’s withdrawal process. That means staking can create an opportunity cost: you earn staking rewards, but you lose flexibility exactly when liquidity might matter.

Lido’s core design is to pool user deposits, route them to validator operators, and issue a liquid token against the pooled position. In effect, it turns staking from an all-or-nothing operational commitment into a tokenized financial position. That is the main idea that makes the protocol click. Lido is not mainly “a website for staking.” It is a system for transforming illiquid staked ETH into a liquid, standardized onchain asset.

How do I stake ETH with Lido and receive stETH?

A user-facing example makes the mechanism concrete. Suppose you hold ETH and want staking rewards, but you also want the option to use that position elsewhere later. You deposit ETH into Lido. In return, the protocol mints stETH to your wallet. That stETH represents your share of the total ETH pooled and staked through the protocol.

From your point of view, two things now happen in parallel. Operationally, the protocol buffers deposits, assigns stake across staking modules and node operators, and manages validator-side processes behind the scenes. Economically, your wallet now holds stETH, which can serve as the liquid representation of your stake.

Lido describes stETH as a rebasing token. In plain language, that means your token balance is updated to reflect staking rewards and protocol accounting, typically via oracle reports. The protocol’s accounting model is share-based: a holder’s balance is derived from their share of total pooled ether rather than from a fixed principal plus separately paid coupons. The consequence is that rewards show up as balance changes, rather than as a separate reward token.

This is where newcomers often get confused. stETH is not just a receipt with a fixed 1:1 value forever. It is a claim on a pooled staking position whose value depends on the total pooled ETH and the total shares outstanding. Because the pooled position earns rewards (and can also, in adverse conditions, be affected by penalties or slashing) the backing changes over time.

Lido says users begin receiving staking rewards within 24 hours of deposit, without waiting for their specific deposit to move through validator activation. That works because rewards are socialized across the pool. You are joining an existing staking system rather than waiting for a single isolated validator tied only to your deposit.

What components power Lido: pools, node operators, oracles, and withdrawals?

At the protocol level, Lido has a few moving parts, and each exists for a specific reason. The staking pool accepts user ETH, mints stETH, tracks pooled balances, and handles withdrawals. Node operators run validator infrastructure on behalf of the protocol. Governance decides key protocol parameters and operator arrangements. Oracles deliver the offchain validator and Execution Layer accounting data needed to keep the onchain state accurate.

The oracles matter because Ethereum staking rewards and validator balances do not live entirely inside one simple smart-contract balance on Ethereum mainnet. Lido’s accounting needs information about beacon-chain balances, execution-layer rewards, withdrawals, and related validator events. Lido’s AccountingOracle submits reports, usually daily though not guaranteed on a fixed schedule, and those reports drive updates to pooled accounting and stETH balances.

Withdrawals now have two practical paths. If a user wants out, they can either use Lido’s withdrawal flow to redeem stETH for ETH through the protocol’s withdrawal queue, or they can sell stETH on a secondary market. The protocol path is the direct redemption route. The market route is often faster, because it relies on available liquidity rather than withdrawal processing. The trade-off is obvious once stated: protocol redemption targets ETH withdrawal mechanics, while market exit depends on the market price of stETH at that moment.

When should I use wstETH instead of stETH?

A subtle but important part of Lido is wstETH, or wrapped stETH. This exists because rebasing tokens are not equally convenient for every application. Some DeFi protocols, Bridge, and layer-2 systems work better with tokens whose balances stay fixed.

wstETH solves that compatibility problem by wrapping stETH into a non-rebasing ERC-20 form. Your wstETH balance does not increase every time Lido updates accounting. Instead, each unit of wstETH becomes redeemable for more stETH over time. The reward accrual is still there; it is expressed through the conversion rate rather than the wallet balance.

This distinction sounds cosmetic, but it is operationally important. For users staying on Ethereum mainnet and simply holding the token, stETH is intuitive because the balance itself grows. For integrations, bridges, and many DeFi systems, wstETH is easier to support because token balances remain stable in the ERC-20 sense. That is why Lido’s ecosystem presence often revolves around both assets rather than only one.

How does Lido manage validators and what governance protections exist?

Lido is non-custodial in the sense the protocol is designed so no single party can simply take user funds. But non-custodial does not mean riskless, and the mechanism matters. Users are trusting a smart-contract system, an oracle system, governance, and a distributed validator-operator set rather than one centralized custodian.

Lido states that it works with 800+ operators globally across multiple modules, including the Curated module, Simple DVT, and Community Staking. This matters because pooled staking concentrates operational responsibility unless the validator set is itself diversified. Lido’s architecture tries to spread that responsibility across many operators rather than relying on one infrastructure provider.

Governance sits above that system through the Lido DAO, where key decisions are made by LDO token holders. Those decisions can include things like protocol parameters and operator-related choices. Lido’s governance also includes Dual Governance, which gives stETH holders a safeguard against certain onchain actions by introducing a dynamic delay and opposition mechanism. The broad purpose is clear even if a typical staker never interacts with it directly: upgrades and control changes are not supposed to happen as a one-sided, frictionless administrative act.

This is part of who Lido is for. Most users will never vote, run a validator, or inspect oracle reports. But advanced users, institutions, and integrators care that the protocol is open source, audited, and governed through visible processes rather than private operator discretion. Lido explicitly highlights audits, bug bounties, and open-source code as part of that trust model.

What returns, fees, and trade-offs come with staking via Lido?

Lido’s staking APR for Ethereum is described as Protocol APR * (1 - Protocol fee). The protocol fee is currently 10% of staking rewards, split between node operators and the DAO treasury, and governance can change it through a vote. So the user is not getting the raw gross validator return; they are getting the pooled return net of protocol fees.

That fee is the price of outsourcing validator operations, pooling risk, and gaining liquidity. For many users, that trade is attractive precisely because the alternative is not “free yield.” The alternative is either running validators yourself or accepting that native staking keeps capital less flexible. Lido is aimed at users who prefer a liquid, delegated staking position even after fees.

The trade-offs become clearer when you look at what can go wrong. Smart-contract bugs are a protocol risk. Oracle failures or delays can affect accounting timeliness. Validator underperformance, penalties, or slashing can reduce pooled returns. Secondary-market prices for stETH can diverge from ETH, especially when liquidity conditions are stressed, even though the token represents staked ETH. None of these risks are incidental; they are the costs of turning staking into a liquid, composable asset.

There are also product-level constraints that matter in practice. APR figures are estimates based on recent conditions, not guarantees. stETH is rebasing, which some integrations handle poorly, hence the importance of wstETH. And while protocol withdrawals exist, secondary-market exits may be faster or cheaper depending on conditions. In other words, Lido improves flexibility, but it does not erase the underlying mechanics of Ethereum staking or DeFi market structure.

What is Lido V3 and how do stVaults change staking?

Lido’s newer technical direction, described in its V3 materials, points toward stVaults: isolated, non-custodial staking positions with user-defined validator setups and optional stETH liquidity layered on top. The basic motivation is to relax an old trade-off inside staking itself. Historically, you could either have standardized pooled liquidity or more direct control over validator setup. Lido V3 is trying to support more of both.

For most readers, the important takeaway is not every implementation detail. It is that Lido is evolving from a single pooled liquid-staking product into a broader staking infrastructure stack. The familiar pooled stETH model remains central, but the protocol is also trying to support more tailored staking arrangements for sophisticated users without giving up the liquidity layer that made Lido important in the first place.

Conclusion

Lido is best understood as a protocol that turns staked ETH into a liquid onchain asset. You deposit ETH, the protocol handles pooled staking through a distributed operator set, and you receive stETH (or often wstETH for compatibility) as the usable representation of that position.

The simple version to remember is this: Lido lets you earn Ethereum staking rewards without having to hold your position in an unusable form.

Everything else exists to make that trade-off workable at scale.

• the oracle system
• the governance
• the operator modules
• the wrapped token format
• the withdrawal design