Open Onboardings
To apply, click the link to the application form for the onboarding for which you wish to be considered.
Interested in learning more about the Lido onboarding process? The guides below discuss relevant information to prospective node operators including ongoing expectations and the nuances of how Lido protocols operate across different networks.
Lido Community Staking Module: Permissionless validation using the largest staking protocol
Learn about how to join the Community Staking Module!
Community Staking Module (CSM) is the Lido on Ethereum protocol’s first module with permissionless entry, allowing any node operator — and especially community stakers, from solo stakers, to groups of friends, to amateur operators — to operate validators by providing an ETH-based bond (security collateral).
In an effort to enhance the protocol’s decentralization by incorporating a broader range of operators, CSM introduces the following features to make solo staking more attractive and accessible:
- EL rewards and MEV are smoothed with other Lido modules, so CSM Node Operators can potentially gain more consistent and stable rewards;
- A reasonably low bond for Node Operators to attract more prospective operators;
- No secondary token security collateral is required, with bonds accepted in ETH, stETH, wstETH and rewards received via stETH;
- Node Operators are provided with a friendly UX and pay less gas fees for on-chain operations compared to other options in the market;
- Node Operators may potentially gain more validator rewards (on a total ETH spent basis) than vanilla solo staking.
Lido on Ethereum: Distributed Validator Technology (DVT) Testing
Starting in 2022, Lido DAO contibutors have worked together with the Obol Network and SSV Network teams to trial DVT on the Goerli and Holesky testnets. The recently passed Simple DVT Module opens up the potential for solo stakers, community stakers, and professional node operators to form clusters of participants that will utilize DVT to run validators using the Lido protocol.
Post merge, two initial pilot programs were conducted, successfully demonstrating the ability to use a DVT configuration in the Lido Node Operator Registry on Goerli with both Obol Network and SSV Network.
Currently, there are no Simple DVT testnets planned for the future, but the community may decide to throw support behind them resuming! In the meantime, operators who wish to test DVT using the Lido protocol may do so using the CSM testnet.
Stay up to date on Onboarding Announcements
Lido Node Operator Excellence
Contributors have drafted an Operator Set Strategy with guiding principles around what kinds of qualities the Lido protocol seeks to exhibit in its underlying node operator in validator set. In general, good Operators should exhibit:
Good Performance
Node Operators should perform well in order to provide stAsset holders competitive returns.
Robustness and Resilience
Node Operators should be operating diversified hardware and software infrastructure and plan for adverse events. Risk management, business continuity planning, and especially proper processes around things like key management are of paramount importance.
Ethos Alignment
Node Operators should be aligned with the ethos and values of the underlying network(s), including by giving back to the greater staking ecosystem and the networks that they operate on.
Lido Operator Set Types
Lido conducts periodic onboardings facilitated by the Lido Node Operator Subgovernance Group (LNOSG), where potential NOs are invited to apply during an open application process, are evaluated by the LNOSG, and approved for addition to the operator set by the DAO.
This approach is currently used on: Lido on Ethereum, Lido on Polygon.
Node Operators can join and leave the Lido operator set at any time on their own.
This approach is currently used on: Lido on Ethereum (specifically on the CSM module has been designed to be permissionless, although it is currently in Early Adoption mode).
Lido employs an algorithm (could be on/off chain or a mix of both) to filter the list of all active validators on a network based on desired criteria. Stake is then allocated across these validators based on a further set of criteria.
Currently none of the Lido on X protocols use this approach.
A mixed approach using the previously listed types can be employed for sub-sets of the a Lido operator set on a network. For example, 30% could be permissioned / curated, and 40% permissionless (algorithmic), and 30% permissionless (open).
This approach is currently used on: Lido on Ethereum (via the CSM module).
