Lido on Ethereum Onboarding Process
Congratulations and welcome to the Lido on Ethereum Node Operator set! Below you’ll find important information related to the onboarding process and other helpful resources. If you have any questions please feel free to ask in our Telegram group or the #Lido-Testnet Discord channel. The timeline is intended to give a general impression of the order and workload involved. We encourage you to read through this entire page before starting, to familiarize yourself with the process. Be advised the setup an testing of the Exits infrastructure in particular requires quite some time, so plan accordingly.
First Steps:
- Team-specific telegram groups to coordinate sensitive information and keep in touch at a team level will be created. As a part of onboarding, you will also be added to channels with the broader Lido Operator set.
- Discord: Please ensure all team members have joined with the provided usernames and verified themselves in the #Rules channel. Shortly thereafter you will be added to the
#lido-testnetchannel. - Email nom@lido.fi with your organization’s logo (preferably in AI or SVG format). This will be included in the blog post announcing the onboarding, as well as in the list of operators at the bottom of www.lido.fi and www.lido.fi/ethereum. The blog post will also include a section introducing your organization: please provide a few sentences introducing your organization, and why you are (hopefully) excited about joining Lido on Ethereum.
- Forums: Please create an account on the Lido forums (https://research.lido.fi/). DAO updates and open discussion will be posted here frequently. We ask that you please monitor the forums over the course of every week, and feel free to participate in the discussion if you would like. Because Lido is a DAO, all opinions are valued and diversity of thought is encouraged.
Testnet Setup
The purpose of the testnet is to become familiarized with Lido NO key management operations and give you time to integrate them into your setups, as well as set up the infrastructure necessary to process validator exit requests.
Please note that validators spun up on the testnet should be using the same setup as you will use on mainnet from an infra perspective, as the expectation is that you continue to run them as the testnet is utilized for general network and Lido protocol upgrade testing.
1) Please ensure that you have EL and CL nodes running and sync'd ASAP. 2) Please share the address** (1 per NO) you are going to use for the testnet – a small amount of testnet ETH for on-chain actions (eg key submission) and voting/Easy Track motions will be required. You can share these addresses directly in the "lido-testnet" channel.
**RE: the "Node Operator Address". This is your identity in the Node Operator Registry contract (rewards will be sent here and you will need it to log into and submit keys to the Registry). It should not be the same address/account you will use on mainnet (for testnet it can be a hot wallet, but for mainnet you should use something more secure).
The main document you are going to use is the official Lido Node Operator Manual
Required Testnet Activities
Any updates to this list will be announced and pinned in the Lido-Testnet Discord channel:
- Notify DAO contributors once ready so that an Aragon vote to add you to the Node Operator Registry can be created.
- Prepare 10 validator keys, check and submit them to the node operators registry (refer to manual for details) via the CLI or https://operators-holesky.testnet.fi/
- Wait ~30 mins for the Operators UI to refresh, or ask another operator or Lido team to check the keys with our key checking tool and once you've got "all clear" from testnet participants — kick off the Easy Track motion to increase the key limit to 10 (see here: https://docs.lido.fi/guides/easy-track-guide/#node-operators-guide-to-easy-track).
- (NOTE: on the testnet we have lowered the cap of keys that can be submitted at one time to 5, since we would like all operators to test the process of splitting keys into multiple batches for submission and not have to spin up a lot of validators).
- Once the limit is increased, ping a coordinator to deposit some Buffered Ether (make sure your keys are loaded into your validator client and that it's up and running first!).
- Once the validators have received their chunks of 32 test ether you can continue with setting up the exits tooling as described in Lido on Ethereum Validator Exits
- Lido Node Operator Manual
- Key generation tool: https://github.com/ethereum/staking-deposit-cli/
Goerli | |
NO Dashboard | |
Key Submitter | |
Staking Widget | |
Keys-api | |
Easy Track | |
Contracts |
Holesky | |
NO Dashboard | |
Key Submitter | |
Staking Widget | |
Keys-api | |
Easy Track | |
Contracts |
NOTE: The Lido on Ethereum protocol testnet is currently transitioning from Goerli to Holesky. New participants in any testnet activities following Nov 1, 2023 will do so on Holesky.
Mainnet Setup:
Required Mainnet Activities
- As a safety precaution, it is highly recommended that infrastructure for Lido is segregated from other stakeholders and validator keys are not comingled.
- Create your "mainnet node operator registry address", this will be used to manage your node operator in the registry and will be used to submit key and receive rewards in. Please note that this address can be changed but requires a full Aragon DAO vote to do so.
- You will be asked to share this address with us and then share it publicly as well so that it can be included in the governance omnibus. Example tweet: https://twitter.com/Stakely_io/status/1480479529411874816 Tweet template:
- Required elements: tag @lidoFinance, desired register name, address for the register ”Hello @LidoFinance, confirming our team is joining Lido as Node Operator "TEAM_NAME" with address “ADDRESS.”
- Please do not proceed with this until asked to do so - Governance Operations will ask once they are ready to prepare the the on-chain vote to add new operators.
- Once the vote is enacted you will be asked to submit 100 keys and then create a motion to raise your limit accordingly. New node operators are asked to not submit more than 100 keys for their first week, so that we can make sure everything runs smoothly.
- Once that week is up and assuming all progresses as planned, you will be free to submit as many keys as you wish (within reason).
- Operators dashboard and key submitter: https://operators.lido.fi/
- Submitter for new validator keys: https://operators.lido.fi/submitter
- Widget for staking: https://stake.lido.fi/
- DAO UI: https://vote.lido.fi
- Manual/Docs: https://docs.lido.fi/
- Deployed Mainnet contracts https://docs.lido.fi/deployed-contracts
- Key generation tool: https://github.com/ethereum/staking-deposit-cli/
Lido on Ethereum Key Submission and Limit Increase Process
Detailed instructions for the key submission and limit increase processes are documented in the Lido on Ethereum Docs. This guide covers:
- Generation of signing keys
- Finding the Lido withdrawal address
- Validating and submitting the keys through: https://operators.lido.fi/submitter
- The Easy Track submission process used to increase operator key limits
Important to note, that the Submitted count will forever increase. Generally, the Active count is Submitted - Exited. Please keep that in mind when increasing the Key Limit for your registered Operator.
Troubleshooting
Removing Key Duplicates
Ongoing Operations and Expectations
All Lido Node Operators are expected to adhere to the basic guidelines as discussed during the onboarding process including e.g. maintaining segregated and performant infrastructure, monitoring relevant communication channels, and updating the NOM team of any organizational changes or infrastructure updates. To read the full list of ongoing expectations see: Ethereum Ongoing Operations & Expectations
Follow & Contribute
