TL;DR
Lido turns ETH into stETH, a rebasing claim on a pool that the stETH contract put at 9,697,092 ETH on 7 November. That is about 21.8% of all active staked ETH on the beacon chain. The core contracts have run since December 2020 with no protocol-level exploit. Governance re-read the same on-chain as in October. Last month's open item has mostly closed. MetaMask Staking (listed as "Consensys") ran 11,213 validators in the original curated module and 133 in curated v2, and Lido's registries now show every one of them exited. A Dual Governance proposal enacted on 23 October capped new deposits to it at zero in both modules. Neither MetaMask nor Lido has reported a slashing or a loss, and neither has published a root cause. The Cooldown and withdrawal queue The wait between asking to withdraw and getting your funds: a fixed cooldown (7 days for HYPE staking) or a queue that clears as cash comes back. that stood at 136,099 ETH on 2 October is down to about 5,300 ETH.
Checklist
Audits & contracts. The official Audit A security firm's review of a protocol's code. It lowers the odds of a bug but does not rule one out, so check what was in scope. page was re-read on 7 November. Every firm named here appears on it: Certora, MixBytes, Statemind, ChainSecurity, Sigma Prime, Cyfrin and Composable Security. The 2026 entries now include Staking Router v3 audits from July 2026 by Certora, Statemind and MixBytes. That closes last month's open point about press-attributed audits. Other 2026 entries are CSM v3 and curated v2 audits by Certora and Statemind (June), Oracle The price feed a protocol trusts to value collateral. A wrong or manipulated price can cause unfair liquidations or let bad loans through. v8 work by Composable Security and MixBytes, and the CircuitBreaker audits by Cyfrin and MixBytes. Since the last report the staking router has gained a fifth module, named "Community Staking 0x02", which holds 30 validators. No audit entry carries that name, so whether the CSM v3 audits cover it is not verified in this review.
Admin control. Re-read on-chain on 7 November. Dual Governance returns persisted and effective state 1 (Normal). The EmergencyProtectedTimelock returns 259,200 seconds after submit and 86,400 seconds after schedule, 96h in total, and emergency mode is off. The Emergency Activation and Emergency Execution committees are the same two addresses as in October. Both are Safe Multisig A wallet that needs several keyholders to sign, such as 5 of 9. Safer than one key, but only as safe as the people who hold the keys. with the same seven signers. Activation has a threshold of 4 and execution a threshold of 5, both read on-chain this run. Emergency protection still ends on 20 June 2027. The Timelock A built-in delay between an admin approving a change and the change taking effect, so users can withdraw first if they disagree. has processed 15 proposals. Number 15 was the MetaMask Staking deposit cap, which went through the full flow. Aragon vote 206 was enacted on 19 October and Dual Governance execution followed on 23 October. That is the governance path working on a real incident. On 28 October a committee member asked on the forum to rotate one signer address to a new hardware wallet. On-chain, the old address is still an owner of both Safes, so the rotation has not executed yet. stETH holders can still stretch the delay by locking 1% of supply and trigger a rage quit at 10%.
Oracle. The AccountingOracle HashConsensus again returns quorum 5 with nine members. Five keys still decide the balance behind every rebase. Lido published a post-mortem for the 25 July misreport on its forum on 6 August. It ties the incident to the Staking Router v3 release. Slow BLS signature checks delayed oracle reports by 3 to 6 hours between 24 and 28 July. A zero-division bug stopped some exit-bus reports from being produced between 26 and 28 July, which slowed withdrawals slightly. On the missed 32 ETH deposit itself, the post-mortem says the exact cause was not established and could not be reproduced. Its working assumption is a race condition between data sources. Lido has since added three-way matching and logging between those sources. No funds were lost, the next day's report corrected the figure, and the protocol's rebase sanity limits would have halted a larger deviation. An oracle error with no confirmed cause keeps this dimension yellow. The nine member addresses were read this run, but the October report did not record them, so whether any member changed in between is not verified in this review.
Liquidity & exit. The queue is back to normal. The withdrawal queue holds 38 unfinalized requests worth 5,335 ETH, against 1,253 ETH buffered on the stETH contract. On 2 October it held 305 requests worth 136,099 ETH. The queue is not paused. Lido's estimator gives finalization on 11 November 12:30 UTC for both 100 and 10,000 stETH, about four days out, and labels both "exitValidators". The estimate moves within the day: an earlier reading this run gave 9 November for 100 stETH, served from validator balances. CoinGecko prices stETH at about 1.000 ETH. The main Curve pool holds 17,977 ETH against 19,673 stETH. It quotes 10,000 stETH at 0.11% below par, and a 50,000 stETH sale drains the ETH side. At size, the queue is the exit and the pool is not.
Yield: real vs emission. Real and modest. The contract reports a 999 Basis point (bp) One hundredth of a percent: 1 bp = 0.01%, so 25 bp is 0.25%. The exit costs on the funding page are in bp. fee. Lido's API shows a seven-day average of 2.486% and a latest daily APR Yearly rate without compounding. Funding here is shown as an APR: the hourly rate × 8,760. of 2.713% as of 6 November. One daily print in that window, 3.227% on 31 October, pulls the average up. LDO Emissions and points Emissions are new tokens a protocol issues to pay rewards; they count in the reward yield. Points may turn into tokens later and are never counted in a rate. do not prop up any of this.
Holder concentration. This run measured what the last one could not. The head state of a public beacon node lists 813,446 active validators holding 44,423,431 ETH. Lido's 9,697,092 pooled ETH is about 21.8% of that. The figure is approximate, because Lido's pool also counts buffered ETH. That share is large, but it sits below the one-third level at which a single pool could stall finality. Inside Lido, the original curated module runs 183,753 of 217,751 active validators by count, or 84.4%, down from 87.2%. The Community Staking Module runs 24,332 (11.2%), SimpleDVT 5,000, curated v2 4,636 and the new 0x02 module 30. Since Staking Router v3, validators can hold more than 32 ETH, so count shares are not stake shares. Curated module 1's active count fell by about 53,000 since 2 October, while the pool lost only about 144,000 ETH. Consolidation into larger validators would explain that gap, but it was not confirmed: not verified in this review.
Track record. No core-protocol exploit since launch, and DeFiLlama's hacks list has no entry for Lido itself. Two third-party entries mention Lido or stETH: SmartCredit's Leverage Borrowing to hold a position larger than your capital. At 3x you hold $3 for every $1 of your own, and gains, losses and liquidation risk grow with it. Lido staking module in May 2026 (about $72K) and Reddio RedSonic's stETH accounting bug in September 2026. Neither was a Lido contract. 2026 has four notable operational events. In March a CSM operator was slashed and its own bond paid. In April a third-party bridge hack impaired about $21M in the Lido-branded EarnETH vault, and the DAO backstopped it. In July the oracle misreported. On 30 September MetaMask Staking disclosed an infrastructure compromise. There were also smaller operator incidents, for example Gateway.fm (node operator 35), whose August downtime and delayed exits cost about 1.0 ETH, which it repaid to the DAO with no slashing. On the MetaMask event, the registries now show all 11,346 of its Lido validators exited, with a target limit of zero in soft mode in both curated modules. The forum thread does not mention any slashing, penalty figure, reserve fund draw or root cause. Whether the exited balances have fully withdrawn back to Lido was not checked: not verified in this review. The only loss figure in public is a researcher's estimate of about 0.36 ETH in diverted block tips, which neither company has confirmed. So far every loss has fallen on an operator, a vault or the DAO, not on stETH holders. The record stays yellow because four notable events in ten months is a pattern, and two of them still have no established root cause.
Worst case
The MetaMask scenario, correlated slashing before the exits finished, did not happen, and that operator no longer runs active Lido validators. The structural worst case is unchanged. Five of nine oracle keys could publish a false balance, and the rebase would spread it across every holder, though the sanity limits cap how far one report can move. A correlated failure at a large curated operator could cause a slashing too big for the operator's own stake, and the rebase would spread that loss too. The 96h timelock and the stETH veto give holders time to react to a hostile upgrade, but the emergency committees keep their override until June 2027. The likelier loss is duller. In a panic the queue lengthens, as it did in early October, and stETH slips below ETH. Anyone forced to sell size into Curve takes heavy Slippage and price impact How much worse than the quoted price a large trade fills, because it eats into the order book. Our exit costs measure it in bp against the mid price. past roughly 10,000 stETH.
Bottom line
Solid. No dimension is red, and the incident that justified watching this report has resolved without touching stETH principal. Governance proved itself on that incident, since the deposit cap went through the full Dual Governance flow. The exit path is short again. Three things stay yellow. The 5-of-9 oracle's July error has a published post-mortem but no confirmed cause. The pool is a fifth of all staked ETH and mostly runs through one module. And 2026 has been a busy year for incidents. Re-check when MetaMask or Lido publishes a root cause, and whenever the queue estimate stretches past a week.
Data appendix
- TVL: ~$21.82B (DeFiLlama
lido, 2026-11-07 about 12:45 UTC). On 2 October the live field read $27.08B. In ETH terms the pool is 9,697,092 ETH against 9,841,182 ETH on 2 October, down about 1.5%, so most of the dollar drop comes from the ETH price (about $2,240 on CoinGecko). stETH market cap per CoinGecko is about $21.7B. 90d and ATH this run: not verified in this review (2 October reading: ATH $42.52B on 2025-08-23). - Audits: docs.lido.fi/security/audits, re-read 7 November. All seven named firms present. Staking Router v3: Certora, Statemind and MixBytes (07-2026). CSM v3 and CM v2: Certora and Statemind (06-2026). Report count not redone. Audit coverage of module 5 "Community Staking 0x02": not verified in this review.
- Admin/governance: DualGovernance 0xC1db28B3301331277e307FDCfF8DE28242A4486E returns persisted and effective state 1 (Normal). EmergencyProtectedTimelock 0xCE0425301C85c5Ea2A0873A2dEe44d78E02D2316 returns afterSubmitDelay 259,200s, afterScheduleDelay 86,400s, isEmergencyModeActive false, governance set to the DualGovernance address, and getProposalsCount 15. Emergency protection: mode duration 2,592,000s (30 days), protection ends 1,813,449,600 (2027-06-20 00:00 UTC). Emergency Activation Committee 0x8B7854488Fde088d686Ea672B6ba1A5242515f45 (Safe, getThreshold 4, 7 owners) and Emergency Execution Committee 0xC7792b3F2B399bB0EdF53fECDceCeB97FBEb18AF (Safe, getThreshold 5, 7 owners). Both are unchanged from 2 October. The owner sets match the seven members confirmed on the forum in April 2026. The 28 October rotation request from 0x237Cddf3aA765260cf6b60E064065Da7c3Aa1559 to 0x3554630ec64e7756007dF4137abf7c5881C533D0 has not executed: the old address is still an owner on both Safes. LDO market cap about $268M (CoinGecko), about 1.2% of TVL Total value locked: the dollar value of everything deposited in a protocol or pool. It shows size, not safety..
- Oracle: AccountingOracle HashConsensus 0xD624B08C83bAECF0807Dd2c6880C3154a5F0B288 returns getQuorum 5 and nine members. Membership changes since 2 October and the mapping of members to organisations: not verified in this review. 25 July misreport: Lido post-mortem in the forum security disclosure thread, 6 August 2026. Exact cause of the missed 32 ETH pending deposit not established; working assumption is a race condition between consensus-layer, execution-layer and key API responses.
- Staking modules and node operators: StakingRouter 0xFdDf38947aFB03C621C71b06C9C70bce73f12999 lists five modules. Active validators (deposited minus exited): module 1 curated-onchain-v1 183,753 (84.4%), module 2 SimpleDVT 5,000 (2.3%), module 3 Community Staking 24,332 (11.2%), module 4 curated-onchain-v2 4,636 (2.1%), module 5 Community Staking 0x02 30, total 217,751. These are count shares, not stake shares. NodeOperatorsRegistry 0x55032650b14df07b85bF18A3a3eC8E0Af2e028d5 has 39 operators. Operator 21 ("Consensys", MetaMask Staking): 11,213 deposited, 11,213 exited, 0 stuck, targetLimitMode 1 with target 0. Curated v2 module 0xDa5F930cE326EB5205085D66c72A4E79d60cB8C1, operator 6 (MetaMask Staking): 133 deposited, 133 exited, targetLimitMode 1 with target 0. Stake-weighted shares: not verified in this review.
- Holder concentration: Beacon node (ethereum-beacon-api.publicnode.com, head state, status=active): 813,446 active validators, 44,423,431 ETH balance (44,333,744 ETH effective). Lido pooled 9,697,092 ETH, about 21.8%. LDO top holders and unlocks: not verified in this review.
- Peg and exit: stETH about 1.000 ETH (CoinGecko). Curve pool 0xDC24316b9AE028F1497c275EB9192a3Ea0f67022 holds 17,977.2 ETH and 19,672.9 stETH. get_dy quotes: 1,000 stETH returns 999.74 ETH, 10,000 returns 9,988.69 (0.11% below par), and 50,000 returns 17,972.1, which drains the ETH side. WithdrawalQueue 0x889edC2eDab5f40e902b864aD4d7AdE8E412F9B1: lastRequestId 141,018, lastFinalized 140,980, 38 unfinalized, 5,335.28 ETH unfinalized, not paused. Buffer 1,252.51 ETH on the stETH contract. wq-api.lido.fi: 100 and 10,000 stETH both to 2026-11-11 12:30 UTC (type exitValidators). Ethereum-wide exit and entry queue: not verified in this review.
- Yield: Lido API, latest daily APR 2.713% (6 November), 7-day SMA 2.486%. On-chain getFee 999 bp.
- Recent-news scan (2026-11-07): The research.lido.fi thread "[Security Disclosure] MetaMask Staking Precautionary Out of Order Exits" has updates on 5, 14, 19 and 23 October. They cover a soft-mode target limit of zero for MetaMask Staking in CMv1 (operator 21) and CMv2 (operator 6), passed in Aragon vote 206 (enacted 19 October) and executed through Dual Governance proposal 15 on 23 October. The thread gives no slashing report, loss figure, reserve fund draw or root cause. Press coverage from early October describes the exit plan, not an outcome. On 21 September Gateway.fm (node operator 35) posted a post-mortem of two August incidents: no slashing, 1.0054 ETH reimbursed to the DAO. On 5 November a GlobeNewswire release reported that Lido Earn Vault and curator A shared deposit pool run by code or by a curator. The curator chooses which markets get your money and sets the limits, for a fee. (EarnETH, EarnUSD) added Firelight first-loss cover. The release could not be opened this run, and it concerns the Earn vaults, not stETH: not verified in this review. An aggregator mention of a Lido DAO legal hearing in November was not traced to a primary source: not verified in this review. DeFiLlama's hacks list (api.llama.fi/hacks, read 7 November) has no entry for Lido itself. Swell, a different liquid staking protocol unrelated to Lido, appears there for a hot-wallet key compromise dated 21 October. Maintained monthly. Methodology: DeFi Research Instruction v2.