Lido adds direct ETH staking from four layer-2 networks

Lido added direct ETH staking from Arbitrum, Base, Linea and Optimism to its main interface on October 15, allowing users to initiate staking without manually transferring assets to Ethereum and returning the resulting token to a layer-2 network.

Users receive wstETH on the network where they begin the transaction. The underlying validator stake still resides on Ethereum mainnet; the new interface and cross-chain infrastructure coordinate the movement of assets between networks. That distinction matters because this is a new access route to Ethereum staking, not validator staking performed independently by the four layer-2 systems.

Two routes sit behind the interface

The quicker route exchanges ETH or wrapped ETH for wstETH held in a dedicated liquidity pool on the originating network. Chainlink documentation calls this “fast staking.” Deposited assets can later be moved to Ethereum in batches, staked through Lido and used to replenish the layer-2 pool with newly created wstETH.

A slower route applies when immediate pool liquidity is unavailable or when that method is selected. It moves ETH from the layer-2 network to Ethereum, stakes it and sends the resulting wstETH back. Chainlink’s Cross-Chain Interoperability Protocol coordinates the cross-chain instructions and transfers involved in the system.

The distinction creates an important limitation. Receiving wstETH promptly through the fast route does not mean the user’s particular ETH has already entered an Ethereum validator. It means the local pool has supplied the liquid-staking token while subsequent transactions rebalance assets across networks.

Lido’s official deployment record lists direct-staking contracts for all four supported networks, including sender, pool, synchronization and administrative components. That record verifies deployed infrastructure but does not establish that every route has equal liquidity, transaction costs or processing reliability at any particular moment.

wstETH preserves rewards without rebasing balances

Lido describes wstETH as the non-rebasing form of stETH. Its token balance remains fixed while the amount of stETH represented by each unit changes as protocol rewards accrue. That structure is commonly easier for layer-2 applications to integrate than a token whose wallet balance changes through rebasing.

Direct staking consequently removes several manual steps, but it does not remove the underlying dependencies. The fast route depends on available wstETH in a local pool and an oracle-derived conversion rate. The slower route depends on cross-chain messaging, Ethereum staking and the return bridge. Both routes also rely on deployed smart contracts and the continued operation of their associated controls.

Chainlink’s integration guide tells developers to check pool liquidity, retrieve current oracle data dynamically, use proxy rather than implementation addresses and account for slippage. It also says its tutorial is provided without warranties, has not been audited as an integration template and may omit checks or error handling. Those cautions limit what can be inferred from the documentation alone.

Availability is not adoption evidence

Lido previously documented direct-staking rails on Arbitrum, Base and Optimism, while its current deployment page also identifies Linea contracts. The October 15 development puts access from all four networks inside Lido’s principal staking interface, rather than proving the underlying design is entirely new.

Neither Lido’s opened records nor the corroborating report supplied launch-day deposit volume, user counts, pool-by-pool liquidity, measured cost savings or failure-rate data. The sources therefore support a narrower conclusion: the interface now exposes four direct layer-2 staking routes, but their adoption and operational performance remain unmeasured.

The feature also leaves ordinary staking risks intact. Lido’s disclosures identify smart-contract vulnerabilities, validator penalties and differences between the exchange price and represented value of its staking tokens. Cross-chain execution and local liquidity add further operational dependencies. Follow-up evidence should include route-level activity, pool capacity, completed cross-chain settlements and any incident or pause disclosures.