Research
14 min read

Published on
May 12, 2026
With the introduction of Lido V3, Ethereum staking moves closer to what institutions have been asking for over the past several years: liquidity without surrendering operational control.
Historically, institutions faced a structural trade-off. They could stake natively and retain full validator ownership, but sacrifice liquidity. Or they could access liquid staking through pooled models, where assets, operators, and risks are commingled across a broad validator set.
Lido V3 dissolves this trade-off through stVaults.
For Luganodes, V3 is a staking OS. It is modern infrastructure that allows us to deliver segregated, operator-specific staking solutions to institutions that require precision, transparency, and compliance alignment.
An stVault is a non-custodial smart contract that functions as a private staking container. Unlike Lido's Core Pool, where ETH is distributed across a large operator set and risk is socialized, an stVault is single-staker and single-operator.
An stVault is a non-custodial smart contract vault where one institution deposits ETH and designates one validator operator. Assets, rewards, and slashing exposure are never shared with other participants.
When staking through a Luganodes stVault:
Asset Segregation Your ETH is never commingled with other depositors.
Operator Specificity You explicitly designate Luganodes as your validator operator.
Custom Configuration MEV relay policies, client diversity, and infrastructure preferences can be structured around your internal risk and compliance mandates.
This structure aligns more closely with how institutional allocators already manage counterparty exposure: isolated, auditable, and attributable.
In our conversations with treasury teams, fund managers, and ETF issuers, the primary concern is rarely headline yield. It is counterparty clarity and risk containment.
stVaults introduce three capabilities that address those concerns directly.
Institutions operate under strict counterparty and jurisdictional requirements. Under pooled staking models, exposure is distributed across a broad and evolving validator set.
With stVaults, exposure is explicitly limited to your chosen operator.
Your vault's validators are transparently attributable. Geographic distribution, client mix, and operational track record can be independently evaluated. Risk committees can assess a defined validator group rather than a dynamic DAO-managed set.
This clarity simplifies internal approval processes and external audits.
Lido V2 applied a flat 10% fee on staking rewards.
V3 introduces a modular fee structure:
| Fee Component | Applied To | Rate | General Formula |
|---|---|---|---|
| Infrastructure Fee | Total staked value | 1% | Total ETH x APR x 1% |
| Reservation Liquidity Fee | Mintable stETH capacity | 0% (DAO variable) | Currently inactive at launch |
| Liquidity Fee | Actually minted stETH only | 6.5% | Minted ETH x APR x 6.5% |
For institutions, this creates capital efficiency optionality.
If an institution stakes 10,000 ETH but mints only 20% into stETH to maintain operational liquidity, an institution avoids paying a liquidity premium on 80% of their rewards, driving the effective protocol fee down to 2.3% on the minted portion.
This allows allocators to size their liquidity exposure precisely, paying a fee only on the portion of stake they choose to make liquid, not on the full position.
Note that these values are excluding the operator fees.
A recurring institutional concern is governance risk, specifically, whether a DAO vote could materially alter validator rules, fee structures, or technical parameters.
V3 introduces a Safety Hatch mechanism that allows vault owners to disconnect their vault from future Lido governance upgrades.
Safety Hatch: A governance opt-out mechanism in Lido V3 that allows a vault owner to disconnect from future DAO upgrades. Once activated, the vault operates as standalone native staking while retaining existing rewards and operator continuity.
If governance direction diverges from your internal mandate, your vault can ossify into a standalone native staking configuration while retaining rewards and operator business continuity.
This mechanism reduces long-term governance uncertainty, an important consideration for balance-sheet allocators operating on multi-year horizons.
Under Lido V2's Core Pool, rewards and slashing are socialized. If one operator underperforms or is penalized, the impact is distributed across all stETH holders.
stVaults change this risk profile.
Slashing exposure is contained within the specific node operator group associated with your vault. If you designate Luganodes as your operator, your risk is not influenced by operational performance elsewhere in the Lido ecosystem.
From a risk management perspective, this transforms staking from pooled exposure to attributable exposure.
Internal due diligence can focus on a single operator's infrastructure design, performance history, client diversification, and incident response framework.
Luganodes maintains a zero-slashing track record, diversified client infrastructure, and geographic redundancy designed to minimize operational risk, factors that directly influence vault health stability.
stVaults introduce more granular accounting mechanics to ensure minted stETH remains fully backed. To understand this, we have to distinguish between the ETH you choose not to mint and the Reserve the protocol requires you to keep.
Reserve Ratio (RR): The minimum percentage of unminted ETH a vault must hold as collateral against its outstanding stETH. A 5% Reserve Ratio on 2,000 minted stETH requires 100 ETH locked as a buffer.
Imagine an institution stakes 10,000 ETH in a vault.
While the owner sees 8,000 ETH as available, the protocol only tracks that 100 ETH Reserve. As long as the vault earns rewards, this cushion stays thick. If performance drops or rewards don't come through, the vault's total value stays flat while the stETH liability grows through rebasing. The cushion shrinks toward a minimum point.
Forced Rebalancing Threshold (FRT): The critical reserve level, set at 0.25% below the Reserve Ratio, at which the protocol permissionlessly burns stETH from the vault to restore full backing. A 5% RR vault triggers at 4.75%.
If vault health declines due to slashing or poor performance and the reserve crosses the FRT, the protocol acts to protect the broader ecosystem. It will permissionlessly trigger a rebalance, burning stETH from the vault to restore the 1:1 backing ratio.
One vault underperforming never affects the rest of the stETH holder base.
The FRT is set at exactly 0.25% below the Reserve Ratio; for a 5% RR vault, that places the threshold at 4.75%. Under worst-case assumptions, this offset gives operators a minimum of 16 days to respond before a forced rebalance is triggered.
Lido assigns Reserve Ratios based on two dimensions: Category, which reflects operator credentials and protocol assessment, and Tier, which reflects ETH volume.
Because the 1:1 ratio is a global rule, unverified vaults are treated with maximum caution. They must maintain a 50% Reserve Ratio, a strict 50
balance between minted stETH and locked ETH reserves.For institutional providers with a proven track record, these ratios are significantly relaxed.
Luganodes is a Professional Category qualified vault operator with opt-in DVT integrations. Combined with institutional-grade infrastructure reliability and active slashing protection, this materially reduces the risk surface for dedicated vault deployments. In practice, it means staying well clear of the FRT while driving effective fees as low as possible.
Beyond institutional allocators, stVaults provide a structured yield framework for Layer 2 ecosystems.
An L2 foundation can maintain ecosystem ETH inside a foundation-owned stVault, designate its preferred operator, and issue a native LST backed by that segregated stake.
This model allows L2s to:
Rather than relying solely on sequencer revenue or external restaking designs, L2s can internalize staking yield within a defined governance boundary.
The reason to choose stVaults is what pooled staking has never offered: a position that is yours alone.
Under V2, your ETH entered a shared pool. The operator set was DAO-determined. Slashing elsewhere affected you. Governance votes shifted parameters without your input. The design was built for scale and accessibility.
V3 is built for something different. Institutions operating under counterparty mandates, audit requirements, or internal risk frameworks need staking that matches how they manage every other asset class: segregated, attributable, with a defined counterparty they have chosen and can evaluate.
stVaults deliver that. Your ETH, your operator, your slashing boundary, your governance opt-out. The liquidity you need, sized to what you actually require, not to what the pool demands.
The economics follow from the structure. Protocol fees scale with how much liquidity you consume, but total cost depends on your full operator arrangement.
The point of V3 is sovereignty.
Lido V3 shifts the node operator's role from passive validator participant to strategic infrastructure partner. The operator you choose now directly determines your reserve ratio, your effective fee, your slashing exposure, and your long-term governance flexibility.
Luganodes is a Lido-verified Professional Category operator with opt-in DVT integrations through Obol and SSV. That combination places us in the lowest reserve ratio tier the protocol offers, down to 2% for DVT-configured vaults, which translates directly into higher capital efficiency and a larger buffer from the Forced Rebalancing Threshold.
Beyond the protocol parameters, Luganodes brings a zero-slashing track record, geographically distributed bare-metal infrastructure, diversified client setup, and compliance-aligned MEV relay configuration. Every one of these factors is independently verifiable by your risk committee.
For institutions that have read this far, the choice of operator is an essential decision. It is the variable that determines how much of V3's efficiency gains you actually capture.
Lido V3 introduces a modular framework that separates liquidity, infrastructure, and governance exposure.
For institutions seeking ETH staking that mirrors traditional risk management principles, i.e. segregated assets, defined counterparties, configurable exposure; stVaults offer a structure that aligns with those expectations.
For Luganodes and our clients, this is an evolution toward staking that is not only liquid, but operationally sovereign.
Lido V2 pooled all depositor ETH into a shared validator set, meaning your assets, rewards, and slashing exposure were commingled with thousands of other stakers. V3 introduces stVaults, private staking containers where a single institution deposits with a single designated operator. The result is segregated assets, attributable risk, and configurable fee exposure that pooled staking structurally cannot offer.
An stVault is a non-custodial smart contract that functions as a private staking container within the Lido V3 protocol. One institution deposits ETH, designates one validator operator, and mints stETH only against the portion of stake they choose to make liquid. Assets are never commingled with other depositors, and slashing exposure is isolated to the chosen operator's performance.
V3 replaces Lido V2's flat 10% fee with a modular structure. An Infrastructure Fee of 1% applies to your total staked value. A Liquidity Fee of 6.5% applies only to the ETH you actually mint as stETH. If you stake 10,000 ETH but only mint 20% as stETH, your effective protocol fee drops to 2.3%. Note that node operator fees apply separately on top of protocol fees, unlike V2 where they are included in the flat fee.
Not necessarily. Protocol fees in V3 vary depending on how much stETH you mint, and node operator fees are agreed separately. The total cost depends on both. The more important question is what you get for that cost: a dedicated vault, a single chosen operator, isolated slashing exposure, and governance flexibility that pooled staking cannot provide.
By default, stVaults participate in Lido governance, meaning DAO votes could adjust fee parameters or technical conditions over time. V3 addresses this through a Safety Hatch mechanism that lets vault owners opt out of future governance upgrades. Once activated, the vault operates as standalone native staking while retaining existing rewards and operator continuity, giving balance-sheet allocators a predictable long-term configuration.
Yes, and this is the core structural change in V3. Under the Core Pool, Lido allocated your ETH across its full operator set with no depositor input. With an stVault, you explicitly designate your operator at deployment. That operator, their infrastructure track record, client setup, and MEV configuration, becomes the defined counterparty your risk committee can independently evaluate. Luganodes operates as a Lido-verified Professional Category stVault operator with opt-in DVT integrations through Obol and SSV.
Luganodes is a world-class, non-custodial blockchain infrastructure provider that has rapidly gained recognition in the industry for offering institutional-grade services. It was born out of the Lugano Plan B Program, an initiative driven by Tether and the City of Lugano. Luganodes maintains an exceptional 99.9% uptime with round-the-clock monitoring by SRE experts. With support for 45+ PoS networks, it ranks among the top validators on Polygon, Polkadot, Sui, and Tron. Luganodes prioritizes security and compliance, holding the distinction of being one of the first staking providers to adhere to all SOC 2 Type II, GDPR, and ISO 27001 standards as well as offering Chainproof insurance to institutional clients.
The information herein is for general informational purposes only and does not constitute legal, business, tax, professional, financial, or investment advice. No warranties are made regarding its accuracy, correctness, completeness, or reliability. Luganodes and its affiliates disclaim all liability for any losses or damages arising from reliance on this information. Luganodes is not obligated to update or amend any content. Use of this at your own risk. For any advice, please consult a qualified professional.