Lido’s wstETH expansion and validator consolidation
Lido is migrating 8 million stETH worth $16.5 billion to a post-Pectra validator design to reduce network traffic. The expansion also introduces one-click cross-chain staking through a collaboration between LI.FI, Chainlink, and Lido to bring wstETH to various layer 2 networks.
Lido moves 8 million stETH worth $16.5 billion to the post-Pectra validator design. This migration uses a separate consensus-layer consolidation queue instead of the standard Ethereum deposit and activation queue. The move reduces the validator count and network message traffic. Operators consolidate onto fewer validators and back stake with their own capital for the first time. Will Shannon, the head of node operator mechanisms at Lido Labs Foundation, says operators consolidate onto fewer validators. All 34 existing curated operators expect to transition to CMv2, and no operators are leaving because of the bond requirement. LDO gained 1.85% over the past 24 hours. Ethereum holds $34.687b in DeFi TVL, while Base holds $4.576b and Solana holds $4.558b. Lido holds $28.2 billion in total value locked as of October 2026.
One-click bridging mechanics
LI.FI, Chainlink, and Lido combine to offer one-click cross-chain staking. This setup allows users to input ETH on Arbitrum and receive wstETH on Arbitrum in a single transaction. LI.FI acts as the order router widget to retrieve price quotes directly from the API, making Lido’s wstETH available on supported L2s without Ethereum gas. This makes the wstETH available to a vast number of users through frontends like Jumper, MetaMask, Rabby, and Phantom. The implementation consists of an L1-side bridge and an L2-side bridge. Chainlink CCIP operates on the backend to securely bridge wstETH, WETH, and ETH between mainnet and remote chains by separating validation from execution so that a failure in delivery does not leave assets in limbo. Chainlink Automation powers the FastStaking feature by continuously rebalancing pools to allow atomic swapping of ETH for wstETH at the exact same rate as mainnet. The Custom Quote API, built on top of the Chainlink direct staking suite of contracts, returns price and routing information in an aggregator-friendly way. You should check the specific APR before you bridge.
Arbitrum integration hurdles
Lido plans to integrate wstETH and stETH into Arbitrum via a custom gateway. This option provides full control over the tokens bridging flow and allows for pausing or unpausing functionality and limits for bridged amounts. However, this custom gateway requires development and an audit, which takes 8 to 12 weeks. The proposal names five core contributors as signers for the Bridge Guardian Multi-sig: @vsh, @skozin, @ujenjt, @kadmil, and @psirex. The multi-sig requires at least a 4/7 threshold for both the Ethereum and Optimism sides. The team rejected the Standard ERC20 gateway because it lacks upgradeability and prevents Lido from updating the implementation to share minting and burning rights with exchanges. The team dismissed the L1CustomGateway because using it assumes that registered tokens conform to the ICustomToken interface. Since wstETH is not upgradable and does not implement this interface, Lido would have to use a wrapper or replacement token, which would worsen the user experience.
| Integration Feature | Standard ERC20 Gateway | Custom Gateway |
|---|---|---|
| Development | None | Required |
| Launch Speed | Fastest | 8-12 weeks |
| Upgradeability | None | Full |
| Control | Low | High |
The DAO Agent triggers implementation upgrades on L1 via DAO voting and manages deposits and withdrawals on the L1 side, while the Ethereum mainnet Bridge Guardian Multi-sig manages L1 deposits and withdrawals in an emergency. The Optimism Bridge Guardian Multi-sig triggers implementation on the L2 side and manages L2 deposits and withdrawals. Lido researchers considered skipping the L2 multi-sig to rely on messages from L1, but they decided to use an L2 multi-sig to handle potential L1-L2 connectivity issues and maintain security. Will the required development time delay the launch of other L2 integrations?
Join the discussion