Lido DAO vote #206 has reached quorum and was enacted, approving a proposal to set MetaMask Staking’s target validator limit to zero in two Lido staking modules. The parameter change was not yet effective when checked.

A Lido contributor said on 19 October that implementation depends on Dual Governance Proposal #15, whose execution was scheduled for 23 October at 13:14 UTC. That separates the completed LDO vote from the later onchain action that would apply the new limits.

What the vote changes

The proposal sets targetLimit = 0 with soft-limit mode enabled for MetaMask Staking—formerly Consensys Staking—in both the Curated Module v1 and v2. Its stated purpose is to stop new deposits being allocated to the operator while the precautionary response continues.

A zero target is an allocation control, not an instruction to seize user assets, burn LDO, unwind every existing position immediately or change stETH redemption rights. The Lido discussion says the affected operators are identified separately in the two module contracts and require distinct update calls.

The “soft” setting also matters: it describes how the module limits future allocation relative to the operator’s current validator count. It is not a statement that validators were slashed or that customer withdrawal keys were compromised.

Why MetaMask exited validators

MetaMask disclosed on 30 September that part of its infrastructure was affected by a security incident. It said it was proactively exiting affected validators in its non-custodial staking operations as a precaution, in coordination with clients and partners.

In a 1 October update, MetaMask said its investigation had found no indication that MetaMask wallets or customer funds were affected. The company also said its staking operation did not manage withdrawal keys on behalf of clients.

Lido’s disclosure warned that the exits could lead to foregone rewards and possible downtime penalties. It said exited ETH would return to the protocol gradually through the validator exit, withdrawal and re-entry cycle, then estimated at up to 45 days because of the entry queue. It told stETH holders that no action was required.

Enacted is not the same as executed

The governance sequence has three distinct facts:

• Vote #206 included the proposed MetaMask target-limit calls and was enacted on 19 October.
• The parameter change still depends on Dual Governance Proposal #15.
• Execution was scheduled for 23 October at 13:14 UTC; NetNapz did not verify early execution or a completed transaction.

Until the final execution is confirmed onchain, reporting the limit as already active would overstate the current state. Conversely, the enacted vote is more than a discussion-stage proposal: it establishes the DAO decision while leaving implementation pending.

NetNapz assessment

The measure narrows future exposure to one node operator while the incident response is assessed. Lido’s pooled architecture and multiple operators are intended to reduce dependence on any single operator, but diversification does not remove operational, queue or penalty risks.

The meaningful follow-up is execution evidence: the relevant contract calls, their transaction status and the resulting module parameters after 23 October. Additional verified MetaMask findings would determine whether the limit remains precautionary or requires a longer-term governance response.

This event does not establish a loss to wallets or customer funds, a change in stETH’s claim structure, a protocol-wide halt or new demand for LDO. LDO governance participation and token-market effects require separate evidence.

Sources and verification limits

• Lido Research: MetaMask Staking precautionary exits and vote #206 updates, checked 21 October 2026.
• MetaMask user update, published 1 October 2026.

NetNapz checked the published governance and incident statements but did not audit MetaMask infrastructure or independently reproduce Lido contract execution. No current price, yield or flow claim is made.