Lido says it has resolved an stETH yield calculation issue linked to its accounting oracle after an oracle upgrade, adding that no user funds were affected. The liquid staking protocol described the incident as a reporting and accounting problem rather than a loss of assets.

The update follows a security disclosure published on Lido’s research forum, which said there had been a minor underreporting of the protocol’s total consensus-layer-side balances in an accounting oracle report. In practical terms, the figures used to calculate stETH yield did not fully align with the protocol’s actual on-chain balances.

The issue affected how staking rewards were reported and reflected, not whether the underlying staked assets existed. Lido characterized the matter as an accounting discrepancy and had previously opened an investigation into the stETH yield recalculation discrepancy before confirming that it had been resolved.

Accounting Oracle Upgrade Tied to Resolution

Lido’s accounting oracle is the component that reports validator balances and rewards from Ethereum’s consensus layer back into the protocol. Those reports help determine how stETH rebases and how yield is displayed to users. If the reported balance is inaccurate, the yield calculation derived from that data can also be inaccurate.

According to the disclosure, the issue was fixed following an upgrade to the accounting oracle. Lido’s documentation describes the accounting oracle as part of the protocol’s oracle system for reporting consensus-layer data into Lido; the relevant documentation is available at docs.lido.fi/guides/oracle-spec/accounting-oracle/.

The materials provided do not include a full technical breakdown of the specific code change behind the upgrade. The confirmed link is that Lido said the issue was resolved after the accounting oracle was upgraded.

Lido Says User Funds Were Not Affected

Lido’s central impact statement is that no user funds were affected. The issue was described as an underreporting of balances in an oracle report, not as a security breach, exploit, drained contract, or loss of staked assets.

That distinction is relevant because a reporting discrepancy can affect the numbers users see without moving or endangering the ETH backing stETH. Lido’s no-impact assessment is the protocol’s own statement and should not be read as an independent audit conclusion unless such a review is separately published.

For stETH holders, Lido’s position is that the reporting behind yield has been corrected and that the assets themselves were not at risk. The disclosure does not indicate that users need to take any action, with Lido presenting the fix as having been implemented on the protocol side.

Relevance for stETH and Ethereum Staking

Accurate yield calculation is a core function for liquid staking because holders rely on reported rebases to track returns and because stETH is used across DeFi. Lido remains the largest liquid staking protocol on Ethereum, and stETH is widely used as collateral, which is why reports of a rebasing miscalculation affecting stETH APR drew attention.

The broader stETH ecosystem continues to see activity, including an Ethereum Foundation grant paid in stETH. This article is limited to the confirmed fix, the accounting oracle issue, and Lido’s statement on user funds, and does not address price or market effects.

Lido also shared the update through its official channel on X: https://x.com/LidoFinance/status/2081077386737549616.