Lido Identifies Oracle Underreporting Behind Lower stETH Rebase, Confirms No Funds At Risk
In Brief
Lido identifies oracle underreporting behind lower stETH rebase. No funds at risk, automatic guard-rails functioned as designed.
Liquid staking protocol Lido has disclosed an anomaly in its daily stETH rebase that resulted in a lower-than-expected annual percentage rate (APR) for token holders. On the day in question, the protocol’s accounting oracle reported a daily rebase APR of 2.04%, falling short of the anticipated 2.15%. Lido contributors confirmed that the discrepancy stemmed from a single in-flight validator deposit of 32 ETH that was inadvertently omitted from the oracle report, and emphasized that no user funds were ever at risk.
The issue was first flagged by the protocol’s accounting oracle, prompting an immediate review by Lido’s technical contributors. After verifying the aggregate balance of Lido validators on Ethereum’s Consensus Layer at the time of the report, the team confirmed that the validator set remained fully accounted for and that the missing deposit represented a reporting edge case rather than a protocol-level failure or slashing event. For context, stETH rebases adjust token balances daily to reflect accrued staking rewards, meaning any under-calculation directly affects holder yields until corrected. Users were advised that no action was required on their part while the root cause was being investigated.
Automatic Safeguards and Swift Resolution
Lido noted that its protocol includes automated guard-rails designed to cap allowable deviations in daily rebase values. Because the actual delta fell within the permissible threshold—specifically, 3.6% of total value locked (TVL) within a 36-day window—the automated circuit breakers did not activate. The team explained that had the miscalculation been significantly larger, these safeguards would have automatically halted the settlement of the oracle report, thereby preventing any downstream liquidations on lending markets that use stETH as collateral.
The following day’s rebase completed as expected and incorporated the ETH omitted from the previous report, resulting in an extrapolated APR of 2.29% that effectively made holders whole. Lido has since deployed an audited update to the protocol oracle intended to accelerate reporting and improve detection of similar edge cases in the future. Contributors continue to analyze the root cause, with a full post-mortem expected to be published in the coming days. In the interim, the protocol has reassured users that the incident was isolated and that its validator balances remain secure.
Disclaimer
In line with the Trust Project guidelines, please note that the information provided on this page is not intended to be and should not be interpreted as legal, tax, investment, financial, or any other form of advice. It is important to only invest what you can afford to lose and to seek independent financial advice if you have any doubts. For further information, we suggest referring to the terms and conditions as well as the help and support pages provided by the issuer or advertiser. MetaversePost is committed to accurate, unbiased reporting, but market conditions are subject to change without notice.
About The Author
Alisa, a dedicated journalist at the MPost, specializes in crypto, AI, investments, and the expansive realm of Web3. With a keen eye for emerging trends and technologies, she delivers comprehensive coverage to inform and engage readers in the ever-evolving landscape of digital finance.
More articles
Alisa, a dedicated journalist at the MPost, specializes in crypto, AI, investments, and the expansive realm of Web3. With a keen eye for emerging trends and technologies, she delivers comprehensive coverage to inform and engage readers in the ever-evolving landscape of digital finance.
