6 hours ago
6
Lido resolved a minor hiccup in its stETH rebase on July 26 after a reporting oracle accidentally overlooked a single validator deposit of 32 ETH. The omission briefly distorted the protocol’s reported staking yield, but no funds were at risk and no user action was required.
What actually happened
Lido’s accounting oracle, the system responsible for calculating staking rewards and triggering the daily stETH rebase, failed to include a pending validator deposit in its report. That 32 ETH omission caused the protocol to report a daily annualized percentage rate of 2.04%, when the expected figure was closer to 2.15%.
The subsequent rebase incorporated the corrected balance, bumping the reported APR to 2.29%. That overshoot relative to the expected 2.15% makes sense. Two rebases effectively split the reporting of what should have been a single smooth calculation.
Lido’s built-in guardrails are designed to tolerate fluctuations up to 3.6% of Total Value Locked over a 36-day period. The actual deviation from this incident fell well within those bounds, meaning the protocol’s automated safety checks treated this as routine noise rather than an emergency.
Preliminary analysis points to a “pending-deposit inclusion issue” as the root cause. The oracle’s snapshot of validator balances was taken at a moment when the 32 ETH deposit was in transit but hadn’t yet been formally registered on the Beacon Chain.
The oracle gets an upgrade
Lido contributors moved quickly. An updated version of the oracle was deployed and audited on the same day, July 26. The enhancement is designed to improve reporting efficiency and, critically, make it easier to investigate similar discrepancies if they arise in the future.
A full root-cause analysis and post-mortem are still in progress. Lido’s contributors have signaled that detailed findings will be published once the investigation wraps up.
The fact that validator balances confirmed consistency throughout the incident is the most important technical detail. Validators kept validating, rewards kept accruing, and stETH holders’ claims on those rewards remained intact. Only the reporting layer had a momentary blind spot.
What this means for stETH holders and the broader market
For existing stETH holders, the practical impact was zero. No funds were lost, no penalties were incurred, and the yield discrepancy self-corrected within a single rebase cycle.
The APR swing from 2.04% to 2.29% across two consecutive rebases illustrates a subtlety that casual observers sometimes miss. Daily APR figures are inherently noisy, fluctuating based on block proposals, MEV extraction, attestation performance, and the timing of deposit inclusion in oracle snapshots. The corrected figure landing at 2.29%, meaningfully above the expected 2.15%, suggests the protocol’s actual staking performance was healthy throughout.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.
English (US) ·