Lido encountered a small glitch when its oracle missed a pending 32 ETH validator deposit, skewing the reported staking yield for a short time. The reported annual percentage rate (APR) dropped to 2.04% instead of the expected 2.15%. After the oracle update, the APR was adjusted upward to 2.29%, reflecting the corrected value.
How the deposit omission affected stETH rewards
The root cause was a timing issue: the oracle took its snapshot before the 32 ETH deposit was fully registered on the Beacon Chain. This led to one rebase missing the deposit, then the next rebase effectively catching up, causing an overshoot in reported rewards. However, Lido’s safety mechanisms limit deviations to 3.6% of the Total Value Locked over 36 days, and this event stayed well within those boundaries.
Importantly, no actual funds or staking rewards were lost or compromised. Validators continued to process blocks, and stETH holders retained their rightful claims without interruption. The issue was isolated to the reporting layer, which momentarily failed to capture all pending deposits.
Steps taken to prevent similar issues
Responding swiftly, Lido’s developers rolled out an upgraded and audited oracle on the same day, designed to improve how validator deposits are included in snapshots. This update aims to reduce discrepancies and ease troubleshooting if any similar situations occur. A detailed post-mortem is underway, with Lido promising full transparency once the analysis is complete.
This incident highlights how daily APR figures for staking tokens like stETH can fluctuate due to block proposal timing, MEV effects, and attestation performance. Such noise is usually smoothed out over longer periods but can cause short-term swings visible to holders.
The quick resolution reassures stETH holders that yield reports remain reliable and accurate despite occasional hiccups in data feeds. This episode also shows the importance of solid oracle systems in DeFi protocols.
