stVaults Metrics
This page defines every stVault metric and gives the formula behind it.
The metrics fall into two families:
- State metrics describe the stVault right now. They are derived from the latest oracle report plus the on-chain flows since that report, and every one of them can be read from the
Dashboardcontract. - Performance metrics describe what happened between two oracle reports. They are computed off-chain from consecutive reports by the Web UI and the CLI.
Notationβ
Formulas below use these short names:
| Symbol | Meaning |
|---|---|
| Total Value | |
| stETH Liability, in ETH | |
| Reserve Ratio, as a fraction | |
| Forced Rebalance Threshold, as a fraction | |
| Minimal Reserve | |
| unsettled Lido fees | |
| undisbursed Node Operator fee | |
| length of the report period, in seconds | |
| 31,536,000 β the annualization constant (365 days) |
On-chain the ratios are stored in basis points (10000 = 100%), and share amounts are converted with the stETH share rate. The formulas here use fractions and ETH for readability.
stVault parametersβ
Reserve Ratioβ
Defines the share of the collateral that is reserved when the Vault Owner mints stETH. stETH isn't minted for this amount. Set by the Tier the stVault belongs to.
Forced Rebalance Thresholdβ
Defines the minimum allowed ratio of Total Value to stETH Liability. Crossing it makes the stVault subject to forced rebalancing. Always lower than the Reserve Ratio.
Minimal Reserveβ
The amount of ETH that is always reserved in the stVault regardless of Total Value. 1 ETH by default, and may be increased in response to a correlated slashing event according to the Risk management framework.
stETH minting limitβ
Absolute maximum for the minting capacity, defined by the stVault's Tier. Changing it requires changing the Tier.
Node Operator feeβ
The share of the gross staking rewards that the Node Operator charges for providing validation services. Stored as feeRate in basis points, and changing it requires confirmation from both the Vault Owner and the Node Operator Manager β see Roles and permissions.
State metricsβ
Total Valueβ
The total amount of ETH attributed to the stVault. It splits into ETH deposited to validators and ETH held on the stVault balance, and rewards accrue to both:
Between reports it is the last reported value adjusted by the net flows that happened since:
Not Staked stVault Balanceβ
ETH held on the stVault contract balance and not deposited to validators, and therefore not earning rewards. ETH staged for pending validator activations is excluded.
stETH Liabilityβ
The amount of stETH the Vault Owner minted in the stVault, backed by the ETH collateral. Stored in shares, so its ETH value increases daily with the stETH rebase:
Undisbursed Node Operator feeβ
Accumulated but not yet disbursed Node Operator fee. Increases the total locked ETH.
Growth is the value the stVault gained on its own, as opposed to the ETH that was supplied into it. Two details matter here: it is measured from the latest oracle report, not from the live Total Value, and it includes value still held in quarantine β the fee accrues on quarantined value too.
is the high-water mark of growth already accounted for: it moves up whenever the fee is disbursed, and also when an amount is explicitly exempted from the fee base. Because of the , a drop in stVault value accrues no new fee until the growth exceeds that mark again β the Node Operator is not paid twice for recovering the same value.
Unsettled Lido feesβ
Accumulated but not yet settled Lido fees. Increases the total locked ETH. The Lido fee is charged on every oracle report and consists of the infrastructure fee, the liquidity fee and the reservation liquidity fee.
Locked by fees obligations (unsettled fees)β
ETH locked in the stVault because of the undisbursed Node Operator fee and unsettled Lido fees.
Reserveβ
The part of the collateral that is reserved when minting and for which stETH isn't minted. It is capped by the value the stVault has on top of its liability:
Collateralβ
The ETH locked to cover the stETH liability under the Reserve Ratio, or to maintain the connection to Lido Core.
The liability used here is the maximum liability observed during the current report period, not the current one. Minting and then repaying within the same period does not release the collateral until the next report.
Total Lockβ
The total amount of ETH locked in the stVault: the collateral plus everything the stVault owes in fees.
Pending unlockβ
ETH eligible for unlocking after stETH was repaid, but still awaiting confirmation from the next oracle report. It is the gap between the liability the collateral is still sized for and the liability that remains:
where is the maximum liability observed during the current report period.
Total stETH minting capacityβ
The amount of stETH the Vault Owner can mint within the Reserve Ratio boundaries, respecting the Minimal Reserve:
On-chain the capacity is denominated in shares, not in ETH.
It can additionally be capped by:
- the stVault's personal stETH minting limit;
- the Tier remaining capacity;
- the Node Operator remaining capacity;
- the total stVaults remaining capacity;
- Lido Core staking rate limits (learn more).
Remaining stETH minting capacityβ
How much more stETH can still be minted:
Utilization Ratioβ
The share of the minting capacity currently used:
At 100% no further stETH can be minted. Above 100% the stVault is at or beyond its intended liability limit and approaches the forced rebalancing zone.
Health Factorβ
Shows how well the stETH Liability is backed by the Total Value. The primary indicator of stVault health:
The stVault is healthy while HF β₯ 100%. Below that it becomes subject to forced rebalancing. See the Health monitoring guide for the risk bands used in the Web UI.
Available to withdrawβ
ETH that can be withdrawn from the stVault balance right now. It is the lower of what is liquid and what is unlocked, reduced by the fees the stVault owes:
While the stVault is pending disconnection, nothing is withdrawable.
Lido Core reference metricsβ
Lido Core APRβ
Gross annualized rewards earned by validators in Lido Core, before the protocol fee is taken. This is the rate the Lido fee components are charged against.
stETH APRβ
What an stETH holder receives: the Lido Core APR net of the Lido protocol fee, currently 10% of staking rewards.
The fee is collected by minting new shares, so this return is exactly the growth of the stETH share rate:
This is the benchmark to compare the stVault's own Net staking APR against: if the stVault earns less than plain stETH after fees, its configuration or performance needs a review. See Last Lido APR for stETH for the canonical calculation.
Node Operator fee at Lido Coreβ
The average share of staking rewards that Lido Core Node Operators receive for providing validation services.
Performance metricsβ
These are computed between two consecutive oracle reports. prev and curr denote the opening and closing report of the period.
Gross staking rewardsβ
The ETH earned by validators β the increase in Total Value with ETH inflows and outflows excluded:
Any change in stVault value not captured by inOutDelta is currently counted as staking rewards. Slashing penalties and other stVault-level ETH movements therefore land in this metric rather than being tracked separately.
Node Operator rewardsβ
The ETH payable to the Node Operator as its fee β its share of the gross staking rewards.
Because the Node Operator can disburse the fee at any moment, the period fee is computed from a claim-invariant helper rather than from the balance:
The two terms do not overlap: subtracts the settled mark rather than including it, so together they cover the whole growth the fee has been charged on, taken or not.
moves up on fee exemptions and manual corrections as well as on disbursements, so the first term is not the same as ETH actually paid out. In a period where growth was exempted or the mark was corrected, this figure counts that value as Node Operator earnings. Read it together with the actual disbursements when either has happened.
Lido feesβ
The Lido protocol fee for the period, tracked as a running cumulative sum in the report:
The Lido fee is the sum of three components infraFee + liquidityFee + reservationFee, each charged on a different base.
The fee rates are annual, and a report covers a fraction of a year, so every component is scaled by the elapsed share of the year:
Infrastructure feeβ
Charged for using the stVaults infrastructure, calculated from Total Value:
Liquidity feeβ
Charged for actual liquidity usage, calculated from the stETH Liability:
Reservation liquidity feeβ
Charged for liquidity on demand, calculated from the stETH minting capacity:
Net staking rewardsβ
What remains of the staking rewards after both fees:
stETH rebaseβ
The growth of the stETH liability caused by the stETH rebase. The liability grows at exactly the stETH APR β both are the same share rate growth, one expressed in ETH and the other as a percentage.
Only the shares held at the start of the period are counted, which keeps the metric comparable to the APR figures:
stVault bottom lineβ
The final result for the Vault Owner inside the stVault perimeter β net staking rewards after the stETH liability growth:
A negative bottom line means the stETH liability grew faster than the stVault earned, which is common while new validators sit in the activation queue.
APR metricsβ
All three annualize a period result against the opening Total Value:
They differ only in the numerator.
The denominator is the Total Value at the start of the period, so ETH supplied mid-period is not reflected in it. A large deposit therefore produces a one-period spike or dip in all three APR figures, which levels out in the next period.
Gross staking APRβ
Validator rewards expressed as a yearly percentage of Total Value, before any fee deductions.
Net staking APRβ
Estimated yearly return after fees, but without the stETH liability growth from the rebase.
Carry Spreadβ
Estimated yearly return after both fees and stETH liability growth.
A positive Carry Spread does not guarantee an increase in Health Factor. With a fixed Forced Rebalance Threshold, Health Factor rises when assets grow faster than liabilities in percentage terms and falls when liabilities grow faster than assets.
Restoring an unhealthy stVaultβ
Three metrics show how much of each corrective action is needed to bring the Utilization Ratio back to 100%. See the Health emergency guide for a worked comparison.
ETH to rebalanceβ
The ETH to send from the stVault balance to Lido Core, writing off the same stETH liability 1:1:
This brings the liability back to exactly the Reserve Ratio capacity, and it is the same expression VaultHub uses for forced rebalancing. The amount is positive whenever the Utilization Ratio is above 100%, which can happen while the stVault is still healthy β the protocol only enforces the rebalance once the Forced Rebalance Threshold is breached. On-chain the result is additionally capped at the full liability, and if the liability already exceeds Total Value, rebalancing alone cannot fix the position and the stVault is considered to have bad debt.
Unlike the two metrics below, this expression ignores the fee obligation, exactly as the contract does. While unsettled fees are outstanding, they shrink the capacity, so rebalancing this amount leaves the Utilization Ratio slightly above 100%.
stETH to repayβ
The stETH to acquire externally and repay, which reduces the liability without touching Total Value:
ETH to supplyβ
The ETH to add to the stVault, which raises Total Value without touching the liability:
Relatedβ
- Health monitoring guide β which of these to watch and how often
- CLI metrics calculation reference β the off-chain methodology in full