EtherFi Strengthens weETH Bridge Security with 4/4 DVN Consensus and Rate Limits
EtherFi Strengthens weETH Bridge Security with 4/4 DVN Consensus and Rate Limits
🔒 Bridge security lockdown
EtherFi has implemented significant security upgrades to its weETH bridging infrastructure following a security review:
Key Changes:
- DVN threshold increased from 2 to 4/4 (unanimous consensus required)
- Message libraries pinned on LayerZero send/receive pathways
- Stricter rate limits implemented on EtherFi-owned bridge contracts
Security Improvements:
- LayerZero's multisig can no longer modify weETH bridge configuration on-chain
- Every inbound message must be attested by all 4 DVNs
- Per-route rate limits contain potential damage on controlled contracts, independent of bridge providers
LayerZero's team has independently reviewed and confirmed the new configuration. The changes apply across all chains where weETH bridging is active, with both Liquid minting and redemption now enabled under enhanced security parameters.
Under the guidance of our security partners, we will be unpausing LayerZero bridging for weETH and eETH over the next 24 hours. More updates soon.
EtherFi Liquid vaults are unaffected by the recent Kelp rsETH incident. Liquid vault users will not experience any drawdowns. More details coming soon. In the meantime, your funds are secure.
3/ After these changes: > LayerZero's multisig has no on-chain path to modify weETH bridge config > Every inbound message must be attested by all 4 DVNs > Per-route rate limits bound blast radius on contracts we fully control, independent of any bridge provider LayerZero's
2/ What changed — three things, executed on every pathway: > Pinned the LayerZero send/receive message libraries > Pinned the DVN set and raised the threshold to 4/4 (unanimous) > Tightened pair-wise rate limits on EtherFi-owned bridge contracts
LayerZero bridging for weETH is now live across all chains, with Liquid minting and redemption enabled. We've strengthened security by increasing DVNs from 2 to 4 and implementing stricter rate limits. The safety of our users is our number one priority. More updates as we turn
Under the guidance of our security partners, we will be unpausing LayerZero bridging for weETH and eETH over the next 24 hours. More updates soon.
🌉 ether.fi Deprecating weETH Bridges on 8 Chains
**ether.fi is consolidating its cross-chain infrastructure** by deprecating weETH bridging on eight networks: Scroll, Swell, Bera, zkSync, Mode, Blast, Morph, and Sonic. **Key Details:** - Bridging will be disabled at the end of June - Users holding weETH on affected chains must bridge back to Ethereum or another supported chain before the deadline - The move aims to strengthen security by focusing resources on chains with higher activity and integration depth [View full details](https://etherfi.gitbook.io/etherfi/getting-started/multichain-ecosystem/weeth-partial-bridge-deprecation)
🔒 EtherFi Cuts weETH Bridge Support Across 8 Chains
EtherFi is deprecating weETH bridging on eight chains by end of June 2026, following a recent security hardening initiative. **Affected chains:** - Scroll - Swell - Bera - zkSync - Mode - Blast - Morph - Sonic **Key details:** - Bridging will be disabled at the end of June - Users must bridge weETH back to Ethereum or another supported chain before the deadline - The move consolidates resources to chains with higher activity and integration depth **Context:** This follows a protocol-wide security review completed on April 23, which closed a latent risk proactively. No exploit occurred, but the team now has full control over security-relevant bridge parameters. The consolidation strategy mirrors broader industry trends, with projects like Allbridge also phasing out support for lower-activity chains to focus security resources more effectively.
🤝 EtherFi Proposes 5,000 ETH Contribution to rsETH Exploit Relief Fund
**EtherFi Foundation Steps Up After rsETH Exploit** The EtherFi Foundation is proposing to contribute **5,000 ETH** to a dedicated relief vehicle aimed at addressing the rsETH shortfall from this week's exploit. **Key Points:** - The relief vehicle is designed to protect users and prevent bad debt from spreading across DeFi protocols - EtherFi has been coordinating closely with [Aave](https://aave.com) and other ecosystem partners - The Foundation emphasizes that an ecosystem-wide, coordinated response is essential for proper resolution - This follows earlier commitments, including a 2,000 ETH treasury contribution to DeFi United **Broader Ecosystem Response:** Over 71,700 users and multiple DeFi partners have rallied together, including Aave, Ethena, Mantle, Lido Finance, Arbitrum, and others. EtherFi and Aave are aligned on next steps, with the final recovery plan, user instructions, and timeline to be announced shortly.
Ether.fi Plans Multi-Provider Security Upgrade for weETH Cross-Chain Infrastructure
Ether.fi is implementing two major security enhancements for its weETH token infrastructure: **Multi-Provider Quorum** - Evaluating addition of a second independent messaging stack (CCIP or Wormhole) alongside existing LayerZero integration - Goal: prevent any single messaging provider from unilaterally authorizing weETH mints or releases - Creates redundancy in cross-chain message verification **L2 Risk Assessment** - Conducting systematic review of every blockchain where weETH is deployed - Will deprecate chains whose trust assumptions no longer meet security standards - Process coordinated with L2 teams and security community for orderly transitions These changes reflect growing emphasis on defense-in-depth strategies for cross-chain token bridges, addressing single points of failure in messaging infrastructure.