Three teams describe different kinds of exposure

Lido, Ether.fi and Maple have issued statements addressing their positions after the Binance incident. The disclosures concern different products and relationships, rather than establishing a single status for decentralized finance.

Lido said at 22:33 UTC on October 29 that stETH was unaffected and its staking protocol continued operating, including withdrawals. It separately said Lido Earn had no direct exposure and was monitoring developments to manage risk. The withdrawal statement concerned the staking protocol; it should not be read as a blanket description of every Earn product.

At 22:38 UTC, Ether.fi reported no direct exposure and said user funds were safe. Its short statement did not provide a product-by-product operational breakdown.

Maple said at 22:36 UTC that it had no Binance positions, was monitoring the situation and was operating normally. These are the respective teams' disclosures, not independent audits of their holdings.

Normal operations do not mean instant redemption

Product mechanics remain relevant even when a team reports no disruption. Lido's withdrawal documentation describes a queue whose timing depends on demand, available ETH and validator exits. Continued operation therefore does not imply every redemption settles immediately.

Ether.fi's Liquid documentation describes an automated product allocating assets across DeFi strategies. Maple's transparency page explains that its lending products derive returns from institutional loans and retain credit risk, including possible principal loss. These background mechanics are not evidence that either product suffered incident-related losses.

Reading the limits of the statements

No direct exposure, no exchange positions and continued protocol operations answer different questions. None alone establishes that market-price movements, counterparties or every downstream integration are unaffected.

The practical distinction is between an identified exchange relationship and the broader risks inherent in a product. Our DeFi guide and staking-risk explainer cover those foundations. Follow the main incident report for exchange-specific developments.

Primary statements verified October 30, 2026, 05:48 UTC. Operational assurances are attributed to the issuing teams.