Lido’s proposed route for running larger Ethereum validators would require a 32 ETH entry bond, compared with 2.4 ETH for its existing default route. That higher collateral can become more efficient once enough stake is allocated to the validator, but an operator’s profile and place in the funding queue determine how useful the advantage is.

The October 1 deployment plan outlines Community Staking Module 0x02, a separate module for permissionless operators alongside the existing 0x01 route. It would support compounding validators with up to 2,048 ETH of effective stake, compared with 32 ETH for existing-route validators. Each validator is identified by a key.

The route remains on Hoodi testnet, with mainnet expected in Q4 2026. The deployment post describes preparations for mainnet and puts the module’s Staking Router parameters to a later vote. The July 20 approval of the launch proposal and September 1 testnet announcement were earlier milestones, rather than mainnet activation.

Measured as operator fees per ETH bonded, the new route reaches parity with a first existing default key near 747 ETH under equal yield and performance. But an operator spreading a 32 ETH budget across existing default keys raises that modeled threshold to about 1,330 ETH. These are fee-efficiency comparisons before costs, penalties and funding delays.

The proposed bond is 32 ETH for the first key and 30 ETH for each additional key. Under Lido’s existing 0x01 default profile, the amounts are 2.4 ETH and 1.3 ETH respectively.

The distinction between collateral and stake matters. The bond is the operator’s security deposit, held as stETH to cover losses and charges.

Source link