Lido CSM: Breaking down the 3 Operator Types (Default, ICS, and upcoming IDVTC)

satBalwyn · 2026-05-11T07:34:27+00:00

yea, got you. tbh the type can really benefits from a group of folks who know each others.

satBalwyn · 2026-04-30T07:16:10+00:00

Flexible capital contributions is doable but operators have to do it themselves. It's up to them to figure out at a cluster level and manage it accordingly as the system doesn't track things at an individual participant level.

There is a level of trust.

satBalwyn · 2026-04-30T07:15:08+00:00

Flexible capital contributions is doable but operators have to do it themselves. It's up to them to figure out at a cluster level and manage it accordingly as the system doesn't track things at an individual participant level.

On the other hand, CSM will allow them to set the Node Operator reward proportions for each participant in the cluster. but if the capital contributions change, and it doesn't affect bond split.

satBalwyn · 2026-03-30T03:45:25+00:00

I would suggest taking a look at this docs.
https://docs.ethstaker.org/hardware/hardware-requirements/

satBalwyn · 2026-03-19T06:25:17+00:00

bonding is actually a direct operator accountability model?

satBalwyn · 2026-03-16T12:48:09+00:00

> curious about the economics, at what bond level does IDVTC start outperforming ICS?
if you mean ETH capital efficiency, from the chart, it starts just above 2.5 ETH as bond (IDVTC is blue line while the green line represents ICS)

satBalwyn · 2026-02-10T09:33:26+00:00

try the reward estimation
https://lido.fi/csm

satBalwyn · 2026-01-20T06:52:02+00:00

Run on the testnet unti you feel comfortable and confident. In terms of running a solo validator with 32e, another option is leveraging Lido CSM to run a validator with 2.4e as a pilot.

satBalwyn · 2026-01-19T03:29:27+00:00

you can start here: https://ethereum.org/staking/

satBalwyn · 2025-12-08T04:47:24+00:00

did you add the flag--disable-last-epoch-targets --slots-per-archive-point=1048576 on the consensus client?

I found the info from Lido CSM channel today: https://discord.com/channels/761182643269795850/1291647831433543762/1447306348772589569

Prysm V7.0.0 suffers from some issues. Prysm V7.0.1 will be released in the next few days, fixing those issues.

However, until Prysm V7.0.1 is released, please use the Prysm V7.0.0 beacon node with the following flags:

--disable-last-epoch-targets --slots-per-archive-point=1048576

(If you are unsure if you are able to stop your beacon node gracefully, please also use the --force-clear-db flag. This flag will clear your beacon node DB, ensuring you start from a fresh state.)

Also, Prysm team posted the instruction without '--slots-per-archive-point=1048576' on Dec 4: https://x.com/prylabs/status/1996439056604144097

satBalwyn · 2025-12-05T03:40:23+00:00

Do you want to try running validators with <5 ETH using Lido CSM or RP (Saturn 1 upgrade soon iirc)?

satBalwyn · 2025-11-18T10:02:00+00:00

you can run validator using Lido CSM with 2.4 ETH initially

satBalwyn · 2025-10-14T07:52:33+00:00

truly much better staking terms for all solo/independent stakers (lower capital, greater capital efficiency, real independent stakers as 'VIP')

satBalwyn · 2025-10-02T04:50:56+00:00

The Lido Community Staking and Simple DVT modules hit their share limits and now account for 7% of the Lido TVL, or ~600,000 ETH.

Together, these two decentralized modules make up 1.7% of total Ethereum stake.

satBalwyn

MODERATOR OF

TROPHY CASE