Lido: Daily Yield Below Expected Due to Missing Validator Deposit Report; No Funds at Risk

iconKuCoinFlash
Share
AI summary iconSummary
Lido reported a lower-than-expected daily yield on July 26 (UTC+8), with stETH rebase at 2.04% instead of the anticipated 2.15% due to a missed validator deposit. The issue arose from an oracle report that omitted a 32 ETH deposit. Lido confirmed no funds are at risk and advised users to take no action. The team is actively resolving the issue, with the next rebase expected to restore the correct balance. This update is part of ongoing ETH news and highlights a key development in crypto today.

ME News reports that on July 26 (UTC+8), Lido announced it is investigating an issue related to today’s stETH rebase. According to the protocol’s accounting oracle report, today’s annualized yield (APR) was 2.04%, rather than the expected 2.15%. This was not due to protocol penalties, and no funds are at risk; the discrepancy arose because an ongoing validator deposit (32 ETH) was omitted from the oracle report. Contributors have carefully verified the total balance of Lido validators on the Ethereum consensus layer at the time of the oracle report’s release (and since), finding no indications of any funds at risk. Users do not need to take any action. The team is currently investigating the root cause. Once the fix is implemented, the next rebase will include the previously undercounted balance. (Source: PANews)

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.