Lido proposes a permissionless 0x02 CSM module

What happened

Lido contributors proposed a separate permissionless CSM using 0x02 withdrawal credentials and validator balances up to 2,048 ETH.

What changed

A concrete design entered governance discussion with proposed bond, fee, penalty, capacity, queue, and delegated-role parameters.

What did not change

Within June it had not been approved, deployed, or activated; the exact module allocation and top-up seats were not final, and 0x01 operators had no direct migration path.

Confirmed

• The proposal calls for a new CSM v3 instance using 0x02 credentials.
• The proposed maximum validator balance is 2,048 ETH.
• Proposed bonds are 32 ETH and 30 ETH, with a 2% operator and 8% DAO split.
• The proposed combined 0x01/0x02 capacity ceiling is 20%.
• The CSM Committee would receive penalty, queue, bond-curve, and pause roles.

Still open

• Approval and deployment after June 30.
• Final capacity, queue seats, addresses, role holders, thresholds, audits, and activation conditions.
• Realized slashing, exit, liquidity, and concentration effects.

What it means for an advisor

• Monitor approval and deployment, then review concentration, slashing, queue, and delegated-control assumptions.
• Do not infer that the proposal is operative or safer than existing CSM.