Path to Curated Module as Public Good Operator

General
1

Hey Lido community :waving_hand:

I am writing on behalf of Erigon, the team running the Ethereum execution layer client and Caplin (consensus layer client). With CMv2 now live and the Public Good Operator type active, we wanted to formally introduce ourselves and share where we stand.

Who We Are

Erigon is one of Ethereum’s execution layer clients, running alongside Geth, Nethermind, Besu, and Reth. We also develop Caplin, our consensus layer client, making us one of the few teams building both EL and CL implementations.

Our Journey with Lido

Since late 2025, we’ve been working with the NOM team (Will, Ivan, Sat) to support Lido operators who want to validate Ethereum using Erigon+Caplin.

We’re now running the same stack ourselves. Same client, same guides, same failure modes — which means when an operator hits something, we’ve usually hit it too.

Hoodi Testnet - the dry run:

  • We deployed 15 validators as a deliberate learning exercise before touching mainnet. It paid off: we found and fixed a Caplin issue that was hurting attestation performance, and worked out all the operational details — key generation, pre-signed exit messages, ejector setup, monitoring — in an environment where mistakes cost nothing.

Mainnet - Live:

  • Our CSM Node Operator is now active with 500 keys deposited and is already participating in validation.

The setup:

  • 2x Erigon+Caplin nodes (3.5), each in a different European datacenter

  • Lighthouse VC

  • MEV-Boost with the Lido-vetted relay set

  • validator-ejector running on both EL nodes

  • Private network between all nodes

The two nodes sit in separate cities for HA, and we’ve tested that properly rather than assuming it works. We can take one EL/CL node out for maintenance — version upgrade, kernel patch, whatever — while the other keeps serving the VC, with no impact on validator duties. That was the main thing we wanted to prove before putting real stake behind it.

Governance:

  • Voted FOR on LIP-33, LIP-35, SDVTM wind-down

  • Voted FOR on 0x02 CSM launch and CMv2 Penalty Framework

  • Holding LDO and actively following governance discussions

Why Public Good Operator?

We noticed that CMv2 went live in July with the Public Good Operator type, and the first rebates were awarded to seven client teams on July 24th.

Looking at the Node Operator Type Assessment Framework, the Public Good Operator type is defined as:

“an entity developing or substantially supporting in a financial manner an Ethereum Execution, Consensus Layer or validator client.”

As developers of both an EL client (Erigon) and a CL client (Caplin), we believe we clearly meet these criteria. Client diversity remains critical for Ethereum’s resilience, and having a client team as a node operator creates a direct feedback loop: operational insights improve the client for everyone running it.

Our Ask

We understand that the Public Good Operator type is assignable to existing Curated Node Operators, and that new operators typically enter through onboarding rounds as Professional Operators.

However, we note that the Node Operator Type Assessment Framework provides for exceptional onboarding cases where the CMC may propose operators that “enable meaningful collaboration with an important ecosystem participant” or “advance the protocol’s strategic objectives.”

As developers of both an Execution Layer and Consensus Layer client, we believe we could represent such an exceptional case. We’d welcome guidance from the CMC and community on whether this path is appropriate, or whether we should wait for the next standard onboarding round.

Specific questions:

  1. Is an exceptional onboarding case viable for a client team like Erigon?

  2. If not, what is the expected timeline for the next onboarding round?

  3. Are there additional steps we should take to strengthen our application?

In the meantime, we continue building our operational track record in CSM and participating in Lido governance.

Happy to answer any questions about Erigon, Caplin, or our infrastructure.

Links:

5 Likes
2

Hey @bloxster,

Thanks very much for the post and introduction of Erigon to the broader community here.

It’s great to hear that you’re participating in CSM as well as in DAO governance - these are great steps to become more deeply involved in the Lido Node Operator ecosystem.

I’ll take the opportunity presented by your questions to discuss onboarding and the Lido Node Operator set more broadly.

On timing and the CMv2 migration

With CMv2 having gone live only in recent weeks, Node Operators are currently in the process of deploying validator infra and submitting bonds and keys to the new module, while the protocol is beginning to direct ETH inflows to the initial seed deposits for the new 0x02 validators. With an entry queue of ~ 40 days, the first validators should activate in September and validator migrations from CMv1 to CMv2 are expected to begin thereafter. This process will likely take between 4-6 months.

Given the operational lift this migration requires from both Lido DAO contributors and the Node Operators themselves, I don’t believe it would be prudent to onboard any new Node Operators to CMv2 until, at minimum, the migration has been completed.

On the exceptional onboarding case

While Erigon continues to drive value to the Ethereum ecosystem, the exceptional onboarding provision is generally aimed at opportunities that would strengthen the protocol in a more material way than the addition of a single Node Operator - even one that has contributed as much to Ethereum as Erigon has. Several client teams have expressed interest in joining the Curated Module over the past months, so my recommendation would be that if the DAO decides to onboard new Node Operators with a Public Goods focus, it should do so via a broader onboarding round rather than case-by-case exceptions.

On the outlook for a new onboarding round

That said, I don’t believe current conditions are conducive to onboarding new Node Operators to the Curated Module. The market environment is already putting pressure on the existing Curated set, with weak ETH/USD prices and declining per-validator reward rates. The recent discussion around EIP-8363 adds a significant amount of uncertainty to the staking ecosystem on top of that - if the changes from this proposal were introduced, onboarding additional Node Operators would be completely unfeasible (in reality, the set would more likely need to shrink given how significantly the economics would be diminished). For both of these reasons, I personally would not suggest opening an onboarding round in the near or medium term - not until there is both a recovery in existing Node Operator economics and more certainty around the future of Ethereum’s staking rewards.

On strengthening your application

I think between your involvement in CSM, governance, and ecosystem contributions, you appear to be setting a strong foundation. Without getting into deeper technical details via the forum, I would recommend reviewing the stVault Extended Application, which should be a good guide to the type of questions the CMC would assess in a future onboarding round.

Again, thank you for the thoughtful post and for Erigon’s continued contributions to the ecosystem. I would personally love to see another onboarding round take place in the future, but I strongly believe it should only happen when the current Node Operator set is in a position of strength and sustainability.

4 Likes
3

Thanks @KimonSh for the detailed and transparent response. Really appreciated you taking the time to explain the current landscape.

We fully understand the priorities around the CMv2 migration and the challenging market conditions. It makes sense to ensure the existing Node Operator set is stable and sustainable before considering any expansion.

Meanwhile we’re happy to contribute to the Lido ecosystem with our CSM nodes while building our operational track record, participating in governance, and following the stVault Extended Application framework you mentioned as guidance for the type of questions CMC would assess in a possible future round.

Looking forward to contributing to any future onboarding discussions when timing and conditions are right.

2 Likes