Lido publishes post-mortem on Staking Router v3 incident, traces bug to accounting oracle oversight

Lido’s contributors dropped a post-mortem on July 25 detailing what went wrong during the rollout of Staking Router v3: an AccountingOracle glitch that omitted a single 32 ETH validator deposit and briefly skewed the daily stETH rebase to an incorrect 2.04% APR figure. No user funds were lost. No one got rugged. But when you’re the largest liquid staking protocol on Ethereum, even a minor accounting hiccup warrants a public autopsy. What actually happened The incident traces back to an edge case that surfaced during the transition from Lido’s legacy accounting methodology to the new balance-based system introduced by SRv3. The old system tracked rewards on a per-validator basis. The new one aggregates balances, which is necessary to support the headline feature of SRv3: validators with effective balances up to 2,048 ETH, a massive leap from the previous 32 ETH cap. During that switchover window, the AccountingOracle missed a 32 ETH deposit in its calculations. The resulting anomalous stETH rebase was caught and corrected without material financial impact to stakers. Lido’s post-mortem described the root cause as an operational edge case specific to the migration period, not a syste...