Lido stETH Rebase Falls Short After 32 ETH Accounting Delay
Key Takeaways
- •The stETH daily rebase APR was reported at 2.04% after a 32 ETH validator deposit was missed by the accounting oracle.
- •Lido contributors found no missing funds, protocol penalties, or evidence of a security failure.
- •The discrepancy was caused by delayed accounting recognition rather than weaker validator performance.
- •Lido expects a future oracle update and the next rebase to include the omitted balance and align reported yields.
- •stETH market metrics remained stable, with the stETH-to-ETH ratio near parity and total value locked near $17.5 billion.

Lido DAO’s latest accounting discrepancy briefly understated staking yields for stETH, pointing to an operational reporting issue rather than a protocol failure.
The daily rebase APR was reported at 2.04% instead of the expected 2.15% after the accounting oracle missed a 32 ETH validator deposit. Contributors reviewed validator balances and found no missing funds and no protocol penalties.
The finding shifted the focus from security concerns to accounting accuracy. For stETH holders, the rebase is the mechanism through which staking rewards are reflected in token balances, so the accuracy of the oracle’s daily snapshot affects reported yield even when the underlying validators continue operating normally. The lower rebase reflected delayed reward recognition rather than weaker validator performance. Lido’s team is still investigating the root cause before deploying a fix. 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 in validator accounting, not in reward generation. As the accounting oracle prepared its daily snapshot, one 32 ETH validator deposit remained in transit between reporting stages and was not included in the finalized update.
Because the accounting process is snapshot-based, the timing created a temporary mismatch in recorded deposits. The validator balances had already been reflected on the Beacon Chain, but they were not captured in the oracle’s completed reporting cycle.
The synchronization delay did not change staking performance. Instead, it affected how the oracle calculated distributable rewards for that specific cycle. In Ethereum staking, 32 ETH is the standard validator deposit size, which explains why a single missed validator deposit could create a measurable but limited difference in the reported daily APR.
Once the pending deposit completes the accounting process, subsequent oracle updates are expected to include the balance. That would allow future rebases to reflect the full validator position without permanently reducing staking rewards.
stETH market metrics remain stable
The stETH-to-ETH price ratio stabilized close to parity, indicating that holders continued to rely on Lido’s redemption mechanism after the accounting issue.
Total value locked remained near $17.5 billion. The protocol also continued to show a 2.2% staking APR, while around 9.34 million ETH remained staked. Those figures indicated that users did not conduct large-scale withdrawals after the announcement.
Staking inflows continued to track broader Ethereum trends rather than weakening independently. Participation remained steady, suggesting the incident was treated as a temporary operational event.
Despite the short-term accounting glitch, Lido retained its position as the largest liquid staking protocol on Ethereum. That position makes routine accounting and oracle reliability important beyond a single rebase, because stETH is widely used as a liquid representation of staked ETH across Ethereum markets and applications.
Summary
The stETH accounting discrepancy was linked to a delayed 32 ETH validator deposit and was not described as 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.