Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
ETH Lido fixed the stETH yield calculation problem, which was solved after the oracle upgrade.
Lido said that the stETH yield calculation problem related to its accounting oracle has been fixed through the oracle upgrade, and no user funds have been affected. The liquidity pledge agreement characterized the incident as a reporting issue rather than an asset loss.
This update stems from a security disclosure posted on the Lido Research Forum that described a slight understatement of the overall consensus-side balance of the agreement in an accounting oracle report. In short, the way stETH yields are calculated produces numbers that do not exactly match the actual on-chain balance of the agreement.
Such yield calculation problems affect the reporting and reflection of pledge rewards, rather than the existence of underlying pledged assets. Lido has characterized the matter as an accounting difference, and the agreement had previously investigated the stETH yield recalculation differences and subsequently confirmed a resolution.
Relationship between oracle upgrades and repairs
Lido's accounting oracle is the component responsible for reporting the verifier balances and rewards of the Ethereum consensus layer back to the protocol, driving the stETH base adjustments and the display of yields. When there is a deviation in the reported data, the yield based on this calculation will also deviate.
According to the disclosure, the repair was made after the Oracle upgrade. Lido did not disclose full details of the underlying code changes in the materials provided, and this article does not speculate on the connection between upgrades and solutions.
Why did Lido say that no user funds were affected?
For holders, the most critical point is custody security: Lido states that no user funds were affected. The issue was described as an understatement of balances in oracle reports, rather than a security breach, attack or theft of contract funds. This difference is important. Accounting or reporting differences may affect the numbers seen by users without moving or endangering the pledged ETH that supports stETH. Lido attributed the non-impact assessment to itself and should be regarded as a statement of the agreement itself rather than an independent audit conclusion.
What this means for stETH holders and the Ethereum pledge
For current stETH holders, the real point is that the reports behind the yields have been corrected, and Lido said the asset itself has never been at risk. Accurate yield calculations are critical for liquidity pledges because holders rely on reported revaluation bases to assess returns and price stETH in DeFi. Lido remains the largest liquidity pledge agreement on Ethereum, and stETH is widely used as collateral, which is why reports of base calculation errors affecting stETH APRs have attracted attention. The broader stETH ecosystem continues to be active, including funding from the Ethereum Foundation paid out in stETH. This article is limited to confirmed fixes and Lido's impact statement and does not address price or market impact.
Lido also shared the update through its official X channel.
FAQs
What is the stETH yield calculation problem?
The slight understatement of the overall consensus-side balance of the agreement in the accounting oracle report affected the calculation of the stETH yield.
Does this issue affect user funds?
Lido said no user funds were affected, describing it as reporting discrepancies rather than losses or attacks.
Is the problem fixed through Oracle upgrade?
Lido said the issue was resolved after its accounting oracle was upgraded.
Do stETH holders need to take any action?
The disclosure did not indicate any user action;Lido said the issue had been fixed on the protocol side.
