Lido Proposes Penalty Framework for Curated Module v2 Node Operators

Lido's stETH rebase has returned to normal after yesterday's miscalculation, which resulted in a lower-than-expected daily APR of 2.04% instead of 2.15%. **What happened:** - A single validator with a pending 32 ETH deposit was unaccounted for in the oracle report - Today's rebase included the missing ETH, with an extrapolated APR of 2.29% - An audited protocol oracle update has been implemented to improve report speed **Key points:** - No funds were at risk at any point - The issue was an edge case, not protocol penalties - Contributors are completing root cause analysis - A full post-mortem will be published soon No user action was required throughout the incident.

Lido's protocol demonstrated its built-in safety mechanisms during a recent stETH rebase miscalculation incident. The protocol features **automatic guard-rails** that govern allowable values for daily rebases. Key details: - The actual delta was 3.6% of TVL within a 36-day window - This fell within the allowable range, so automated stops did not trigger - Had the delta been significantly larger, guard-rails would have automatically halted the accounting oracle report settlement The safety mechanism ensures that **oracle miscalculations cannot trigger liquidations on lending markets**. This protective layer activates when deviations exceed predetermined thresholds, preventing cascading effects across DeFi protocols that use stETH as collateral. The incident involved a single in-flight validator deposit (32 ETH) being unaccounted for, resulting in a daily rebase APR of 2.04% instead of 2.15%. No funds were at risk, and the issue has been resolved with subsequent rebases accounting for the previously under-calculated balances.

The Lido Core upgrade has successfully passed all required checkpoints and is ready for mainnet deployment. **Key milestones completed:** - Testnet deployment finished - Two independent security audits completed - On-chain DAO vote approved (July 15-17) - Dual Governance review passed with no veto **What's included:** - Community Staking Module (CSM) upgrade to v3 - New Curated Module v2 - Built on Staking Router v3 **For stakers:** No action required. This is a protocol-level upgrade that will be deployed automatically to mainnet.

Lido has published multiple security audit reports for its upcoming protocol upgrades: **Staking Router v3 & Community Staking V3:** - [Certora audit report](https://github.com/lidofinance/audits/blob/main/Certora%20Staking%20Router%20v3%20Audit%20Report%2007-2026.pdf) - [Statemind audit report](https://github.com/lidofinance/audits/blob/main/Statemind%20Staking%20Router%20v3%20Audit%20Report%2007-2026.pdf) **Voting Contracts & Easy Track Factories:** - [MixBytes audit report](https://github.com/lidofinance/audits/blob/main/MixBytes%20Lido%20Easy%20Track%20Factories%20(SRv3%20CSMv3%20CMv2)%20Security%20Audit%20Report%2007-2026.pdf) **Off-chain Oracle:** - [Composable Security consultation report](https://github.com/lidofinance/audits/blob/main/Composable%20Security%20Lido%20Oracle%20V8_0_2%20Security%20Consultation%20Report.pdf) Staking Router v3 introduces stake reallocation through consolidations, support for large validator deposits, and streamlined validator management.

Lido has completed security audits for its Core upgrade, maintaining its standard practice of dual independent reviews. **What was audited:** - Smart contracts - Governance components - Off-chain infrastructure The protocol continues its track record of rigorous security practices, having conducted over 100 audits throughout its history with no user funds lost to date.