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.
