Lido published a post-mortem on July 25 detailing an incident during the rollout of Staking Router v3. A bug in the AccountingOracle omitted a single 32 ETH validator deposit during the migration to the new balance-based accounting system, causing an incorrect stETH rebase calculation with a wrong 2.04% APR figure. No user funds were lost. This upgrade enables validators with effective balances up to 2,048 ETH, up from the previous 32 ETH cap. Despite three audits conducted by Certora, Statemind, and MixBytes, the bug surfaced as an operational edge case specific to the migration period, not a systemic flaw in the SRv3 architecture itself.
Source: Read the original article
