Liquid staking protocol Lido disclosed an anomaly in its daily stETH rebase that resulted in a lower-than-expected annual percentage rate for token holders on July 27, 2026. The protocol's accounting oracle reported a daily rebase APR of 2.04%, falling short of the anticipated 2.15%. Lido contributors confirmed the discrepancy stemmed from a single in-flight validator deposit of 32 ETH inadvertently omitted from the oracle report. The protocol emphasized no user funds were ever at risk. For context, stETH rebases adjust token balances daily to reflect accrued staking rewards, meaning any under-calculation directly affects holder yields until corrected.
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. Users were advised that no action was required on their part while the root cause was being investigated.
Lido Deploys Oracle Update and Confirms Rebase Correction
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 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.
FAQ
What caused the lower stETH rebase APR reported by Lido on July 27, 2026?
The lower APR (2.04% instead of the anticipated 2.15%) was caused by a single in-flight validator deposit of 32 ETH that was inadvertently omitted from the protocol's accounting oracle report. Lido contributors confirmed this was a reporting edge case and not a protocol-level failure or slashing event.
How did Lido correct the stETH rebase discrepancy?
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 made holders whole. Lido deployed an audited update to the protocol oracle to accelerate reporting and improve detection of similar edge cases.
Were any user funds at risk during the Lido stETH rebase anomaly?
No. Lido confirmed that no user funds were ever at risk. The protocol's automated guard-rails did not activate because the actual delta fell within the permissible threshold of 3.6% of total value locked within a 36-day window, and the validator set remained fully accounted for.
