Lido said a rollout issue tied to Staking Router v3 caused its AccountingOracle to omit a single 32 ETH validator deposit, briefly pushing the daily stETH rebase to an incorrect 2.04% APR figure. The contributors published a post-mortem on July 25 and said the anomaly was detected and corrected without material financial impact to stakers, with no user funds lost. The incident emerged during the shift from Lido’s legacy per-validator accounting model to a new balance-based system designed to support validators with effective balances of up to 2,048 ETH, up from the previous 32 ETH cap. Lido described the problem as an operational edge case during migration, not a broader flaw in the SRv3 architecture. The episode highlights a familiar DeFi pattern: security audits can clear code before launch, but live upgrades can still expose operational issues. SRv3, formally LIP-35, was approved through Snapshot governance and on-chain votes across May and July 2026, with audits by Certora, Statemind and MixBytes completed before mainnet activation. The upgrade also changes deposit flows, allows stake consolidation across node operators and prepares Lido for Ethereum’s Pectra upgrade. Lido had previously published another incident report in February involving roughly 5,572 validators and arranged compensation for affected parties. LDO, the protocol’s governance token, rose about 12% around the time the SRv3 vote passed, though that rally later faded.