Lido SRv3 Rollout Hits Snag with Accounting Oracle Glitch

Lido's Staking Router v3 (SRv3) experienced an unexpected issue during its rollout, causing a minor accounting hiccup that briefly skewed the daily stETH rebase to an incorrect 2.04% APR figure.

The incident was caused by an AccountingOracle glitch that omitted a single 32 ETH validator deposit in its calculations.

Lido's post-mortem report revealed that the bug was an operational edge case specific to the migration period, not a systemic flaw in the SRv3 architecture itself. No user funds were lost, and no one got rugged during this incident.

The SRv3 upgrade, formally tracked as LIP-35, is considered one of the most consequential infrastructure changes Lido has shipped. It modifies deposit flows, enables stake consolidation across node operators, and lays groundwork for Lido to take advantage of changes introduced by Ethereum's Pectra upgrade.