None
EN
Lido publishes post-mortem on Staking Router v3 incident, traces bug to accounting oracle oversight
['Editorial Team']
Crypto Briefing
But when you’re the largest liquid staking protocol on Ethereum, even a minor accounting hiccup warrants a public autopsy.
AdvertisementDuring 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 systemic flaw in the SRv3 architecture itself.
The SRv3 upgrade in contextStaking Router v3, formally tracked as LIP-35, represents one of the most consequential infrastructure changes Lido has shipped.