Lido stETH rebase APR falls short after 32 ETH validator accounting delay
Key Takeaways
- •The stETH daily rebase APR was reported at 2.04%, below the expected 2.15%, because an accounting oracle omitted a 32 ETH validator deposit.
- •Lido contributors verified that validator funds were not missing and that no protocol penalties occurred.
- •The discrepancy affected reported distributable rewards rather than actual staking performance on the Beacon Chain.
- •Lido’s team is investigating the root cause and expects a future rebase to restore the omitted balances once the pending deposit is captured.
- •Market conditions stayed stable, with stETH near ETH parity, total value locked around $17.5 billion, and about 9.34 million ETH staked.

Lido DAO’s latest accounting discrepancy briefly understated reported staking yields for stETH, pointing to an operational reporting issue rather than a protocol failure.
The daily rebase APR came in at 2.04%, below the expected 2.15%, after the accounting oracle missed a 32 ETH validator deposit. Contributors later verified validator balances and found no missing funds and no protocol penalties.
That finding moved the focus away from security concerns and toward accounting accuracy within Lido’s staking reporting process. For stETH holders, the daily rebase is the mechanism that reflects accumulated staking rewards in token balances, so even a temporary reporting mismatch can affect the yield figure users see. The lower rebase reflected delayed recognition of rewards, not weaker validator performance.
The team is still investigating the root cause before deploying a fix. Once the issue is addressed, the next rebase is expected to restore the omitted balances and bring reported staking yields back in line.
Source of the discrepancy
The reporting issue originated during validator accounting, not during reward generation. As the accounting oracle prepared its daily snapshot, one 32 ETH validator deposit was still moving between reporting stages and was left outside the finalized update.
Because the process relies on snapshot-based accounting, the timing created a temporary mismatch in recorded deposits. The validator balances were already reflected on the Beacon Chain, but the oracle did not include the deposit in that reporting cycle.
Instead of changing actual staking performance, the synchronization delay affected only the oracle’s calculation of distributable rewards for the period. That distinction matters because Lido’s accounting layer reports balances and rewards from Ethereum validators; it does not determine whether those validators earned rewards on the Beacon Chain.
After the pending deposit completes the accounting process, later oracle updates should capture the balance. That would allow future rebases to reflect the full validator position without permanently reducing staking rewards.
Market conditions remain stable
The incident was followed by broader stabilization in market conditions. The stETH-to-ETH price ratio stayed close to parity, indicating that holders continued to rely on Lido’s redemption mechanism.
Total value locked also remained near $17.5 billion. At the same time, the protocol continued to show a 2.2% staking APR, while about 9.34 million Ethereum (ETH) remained staked. That indicated users did not carry out large-scale withdrawals after the announcement.
Staking inflows continued to move in line with broader Ethereum trends rather than weakening independently. The steady participation suggested that the market treated the event as a temporary operational issue.
Despite the short-term accounting glitch, Lido remained the largest liquid staking protocol on Ethereum. For a protocol of that size, small reporting errors can draw attention because stETH is widely used across decentralized finance as a liquid staking token, making accurate and timely oracle reporting important for users and integrations that track balances and yields.
The stETH accounting discrepancy was caused by a delayed 32 ETH validator deposit, not by a protocol or security failure. Lido DAO expects the next stETH rebase to restore the omitted rewards once the accounting update captures the pending validator deposit.