Introduction
Lido V3 is an update that adds a layer for choosing risk and yield to ETH liquid staking — the practice of depositing ETH, receiving a liquid receipt token, and earning staking rewards. Under the previous Lido, staking rewards from the entire pool of validators managed by Lido were averaged together and reflected in the yield of stETH, the receipt token that represents a holder’s share of the deposited ETH plus accrued rewards. With V3, users and operators can choose risk and yield individually through the Lido protocol. According to Lido’s official blog, V3 went live on Ethereum mainnet on January 30, 2026, and its core feature, stVaults, was released the same day.
In V2, users deposited ETH into the existing shared pool (Lido Core), received stETH, and could use it across DeFi (decentralized finance). Lido Core is the shared-pool part that remains in V3. On top of this shared pool, V3 lets validator operators and funds create their own stVaults. Each stVault carries settings such as operating fees, insurance terms, the stETH issuance rate, and whether issued stETH is re-deployed, so the combination of risk and yield can vary.
Through this, Lido aims to make stETH a common foundation that the staking products of various operators can share.
Overview of Lido V3 (stVaults)
In Lido V2, the shared pool (Lido Core), with a single yield-and-risk profile, handled the conversion of ETH into stETH and the redemption of stETH back into ETH. Redemption time depends on the amount: small amounts settle within about a day, while large amounts can take longer because they require validators to exit. Deposited ETH was distributed across multiple validator operators through a mechanism called the Staking Router, a design meant to avoid concentration under the Lido DAO. Because rewards were averaged across the whole, however, users could not choose which validator operator they were assigned to, and they deployed the stETH they received into DeFi and elsewhere on their own.
With stVaults, distribution terms — operating fees, profitability, and MEV (the extra revenue a validator earns from things like block ordering) — can be set per vault. The party a user places trust in also shifts from the Lido DAO as a whole to the specific validator operator running that vault. Some vaults deploy the issued stETH into DeFi within the vault to produce even higher yield. The stETH a stVault issues is the same as the stETH issued by Lido Core. As described below, however, by keeping stETH issuance below the value deposited into the vault, the design maintains an over-collateralized state in which collateral always exceeds the stETH, securing its backing.
Lido V3 itself does not raise yield. Still, for institutional investors who previously could not use liquid staking because an indeterminate set of validator operators or the DAO was involved in operations, being able to fix the trusted party to a specific operator becomes the entry point to using it.
The figure below shows the difference between Lido Core and stVaults. In Lido Core, depositing ETH into the shared pool returns stETH. In stVaults, a validator operator is chosen per vault, and stETH is issued within limits as needed.
Limits and Risks of stVaults
The actors in stVaults are four: the vault manager, the validator operator, Lido Core, and stETH holders. The figure below shows their relationship. The vault manager deposits the ETH it holds and handles stETH issuance, repayment, and withdrawal. The validator operator runs validators but does not hold the authority to issue the vault’s ETH or stETH.
stETH Issuance Cap and Ratio
Lido Core issues stETH against ETH at a 1:1 ratio in principle. In stVaults, by contrast, when you deposit ETH into a vault you receive that vault’s own share (a token representing your stake). Because each vault has different fees and risks, this share cannot be exchanged interchangeably across vaults the way stETH can. Instead, the ETH deposited into the vault is used as collateral to issue stETH up to a set proportion, connecting the vault to Lido’s shared layer.
What determines how much stETH can be issued is the Reserve Ratio (RR). The RR is the portion of the vault’s value held back as collateral headroom; at an RR of 5%, up to 95 stETH can be issued against 100 deposited ETH. Since the RR is only a cap on stETH issuance, the full 100 ETH can still be used for staking itself.
A vault issuing stETH is close to borrowing stETH against its collateral, and to withdraw the collateral the vault must return that stETH. In other words, for the vault, issued stETH is a liability with a repayment obligation. The vault therefore pays fees and the like — for borrowing stETH — out of its validator rewards.
Choosing an Operator
Being able to choose an operator is, flipped around, also a risk. If the chosen validator operator’s operations suffer a fault or mistake, slashing (a penalty for protocol violations in which part of the staked assets is confiscated) or penalties can push yield negative. Operator quality therefore needs to be checked thoroughly in advance. There are also cases where the vault manager and the validator operator are separate parties, which is another point to verify.
Example Use Cases
stVaults are not only about chasing high APR (annual percentage rate). They fall broadly into three types — a dedicated-vault type, a DeFi-embedded type, and a distributed-operation type — and the purpose and the risks change with each.
1. Dedicated Validator Operation + stETH Issuance Type (Institutions, etc.)
The intended users are institutional investors and funds that wanted to use liquid staking but could not previously, because issuing stETH through Lido Core meant an indeterminate set of validator operators and the Lido DAO sat in between. The vault manager is the institutional side that puts in the capital, and the validator operator is the side that operates under their delegation. The strength of this type is that, whereas previously staking ETH and delegating validator operation earned only validator rewards, here the staked ETH can also be used as collateral to issue stETH.
As noted earlier, stETH is a liability, so repayment and fees apply; but you can stake with a trusted party while also putting stETH to use.
2. DeFi-Embedded Type (High-APR Product)
This type takes the stETH issued against the vault’s collateral and puts it to work again as collateral in DeFi to push APR higher. In return, it carries the risk of stETH price divergence, liquidation, and the smart-contract risk of the DeFi protocols it uses.
The yield is higher than issuing stETH through Lido Core, but this is something a user could also obtain by issuing stETH themselves and re-collateralizing it in DeFi. This type lets you hand that effort to the vault in exchange for a fee.
A real example of a vault with DeFi built in is the vault provided by Rocksolid.
3. Distributed Validator Operation (Robustness-Focused)
This type leverages DVT (Distributed Validator Technology), also used in part by V2’s Staking Router. DVT splits the operation of a single validator across multiple operators so that signing continues even if some operators fail. Rather than maximizing stETH issuance or APR, this type prioritizes operational fault tolerance. The goal is to delegate validator operation itself safely, more than to issue stETH.
When choosing a stVault, clarifying the purpose — whether you want a safe delegation partner, want to issue and use stETH, or want to maximize APR — makes it easier to pick a type.
Recent Lido V3 Updates
According to Lido’s official announcements from spring 2026 onward, stVaults TVL (total value locked) still sits at about 5,500 ETH, well below the annual target of 1.05 million ETH that Lido has set. The current stage is one of preparing the environment so that custodians (asset-management firms) and other operators can adopt stVaults more easily.
In May 2026, Cactus Custody added support for stVaults, and its customers can now create their own stVaults and perform operations including stETH issuance and repayment.
Also in May 2026, Lido obtained Cantina’s Web3SOC certification. Web3SOC is an audit framework that can assess Web3-specific matters such as on-chain DAO governance and key management. It can serve as assessment material when institutional investors consider adopting Lido. Note, however, that it does not guarantee the safety of the smart contracts; it is material for assessment only.
Conclusion
In V2, the groundwork as a liquid-staking protocol was laid: a stETH redemption feature and a mechanism for distributing staking across multiple operators. In V3, on top of that, came functionality as a shared foundation that supplies liquidity to each company’s staking service.
In particular, the type that combines dedicated validator operation with stETH issuance, raised in the use cases, widens the room to combine liquid staking with the now-mainstream service of simply taking on ETH validator operation.
References
- Lido V3 launch announcement
- Lido V2 mainnet launch announcement
- Lido on Ethereum Withdrawals FAQ
- On the speed of Lido withdrawals
- Staking Router documentation
- Lido tokens integration guide
- Lido V3 technical documentation
- Lido V3 design and implementation proposal
- stVaults documentation center
- Basic stVault with optional liquidity
- DeFi Wrapper guide for end-user products
- stVaults economy examples
- Predeposit Guarantee explanation
- DeFi Wrapper technical design
- vaults-wrapper v1.1.0
- stVaults monthly update, April 2026
- Accessing stVaults via Cactus Link announcement
- Lido Poolside Recap, May 2026
- Lido Earn first-loss protection announcement
- Lido Web3SOC certification announcement