Skip to content

Commit fc1ae26

Browse files
pablomendezroyopablomendezroyo
committed
Add steps to register
1 parent 6b9914b commit fc1ae26

File tree

1 file changed

+42
-38
lines changed

1 file changed

+42
-38
lines changed

‎docs/user/staking/ethereum/lsd-pools/lido/register.md‎

Lines changed: 42 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -8,58 +8,62 @@
88

99
## **First Steps to create a Node Operator in Dappnode**
1010

11-
1. **Getting your Dappnode ready**:
11+
### 1. **Getting your Dappnode ready**
1212

13-
- Navigate to [Dappnode Staking for Ethereum](http://my.dappnode/stakers/ethereum) or [Dappnode Staking for Holesky](http://my.dappnode/stakers/holesky).
14-
- Select your desired execution and consensus clients.
15-
- Choose Web3Signer to upload the keystores.
16-
- Configure MEV Boost with as many relays as possible. For additional info on MEV in CSM, check the [Lido CSM Docs](https://operatorportal.lido.fi/modules/community-staking-module).
13+
- Navigate to [Dappnode Staking for Ethereum](http://my.dappnode/stakers/ethereum) or [Dappnode Staking for Holesky](http://my.dappnode/stakers/holesky).
14+
- Select your desired execution and consensus clients.
15+
- Choose Web3Signer to upload the keystores.
16+
- Configure MEV Boost with as many relays as possible. For additional info on MEV in CSM, check the [Lido CSM Docs](https://operatorportal.lido.fi/modules/community-staking-module).
1717

18-
:::warning
19-
It is mandatory to choose at least one relay to ensure the node operator does not propose vanilla blocks. When uploading the keystores with the "Lido" tag, this requirement will be automatically checked. As a Lido Node Operator, it is your responsibility to ensure that your infrastructure is properly using MEV Boost.
20-
:::
18+
:::warning
19+
It is mandatory to choose at least one relay to ensure the node operator does not propose vanilla blocks. When uploading the keystores with the "Lido" tag, this requirement will be automatically checked. As a Lido Node Operator, it is your responsibility to ensure that your infrastructure is properly using MEV Boost.
20+
:::
2121

22-
2. **Create the Keystores & Deposit Data**: In order to run a validator, you need to generate the necessary keystores and deposit data. The keystores **must** be created with the withdrawal credential of Lido:
22+
### 2. **Create the Keystores & Deposit Data**
2323

24-
- Holesky: `0xF0179dEC45a37423EAD4FaD5fCb136197872EAd9`.
25-
- Ethereum: `0xb9d7934878b5fb9610b3fe8a5e441e8fad7e293f`.
26-
- We recommend using official tools like [Staking-Deposit-CLI](https://github.com/ethereum/staking-deposit-cli) or the [Wagyu Key Gen Tool](https://wagyu.gg/) to create the keystores. This step is crucial and mandatory.
24+
:::info
25+
In order to run a validator, you need to generate the necessary keystores and deposit data. The keystores **must** be created with the withdrawal credential of Lido:
26+
:::
2727

28-
The validator Keystores will be used to run the validators on the Ethereum network, while the deposit data will be used to register the validators in the Lido protocol.
28+
- Holesky: `0xF0179dEC45a37423EAD4FaD5fCb136197872EAd9`.
29+
- Ethereum: `0xb9d7934878b5fb9610b3fe8a5e441e8fad7e293f`.
30+
- We recommend using official tools like [Staking-Deposit-CLI](https://github.com/ethereum/staking-deposit-cli) or the [Wagyu Key Gen Tool](https://wagyu.gg/) to create the keystores. This step is crucial and mandatory.
2931

30-
![Lido-CSM2](/img/lido-csm-ss-docs2.png)
32+
The validator Keystores will be used to run the validators on the Ethereum network, while the deposit data will be used to register the validators in the Lido protocol.
3133

32-
:::warning
33-
Make sure you correcly set the withdrawal address up, otherwise the Lido CSM won't let you move forward with the validator deposits.
34-
:::
34+
![Lido-CSM2](/img/lido-csm-ss-docs2.png)
3535

36-
3. **Upload the Keystores in your Dappnode**:
36+
:::warning
37+
Make sure you correcly set the withdrawal address up, otherwise the Lido CSM won't let you move forward with the validator deposits.
38+
:::
3739

38-
- Go to the Web3signer UI for [Ethereum](http://brain.web3signer.dappnode) or [Holesky](http://brain.web3signer-holesky.dappnode).
39-
- Upload the keystores and tag them with "Lido".
40-
- The fee recipient will be automatically set to `0xE73a3602b99f1f913e72F8bdcBC235e206794Ac8` for Holesky and `0x388C818CA8B9251b393131C08a736A67ccB19297` for Mainnet. It is not editable.
40+
### 3. **Upload the Keystores in your Dappnode**
4141

42-
![Lido-CSM3](/img/lido-csm-ss-docs3.png)
42+
- Go to the Web3signer UI for [Ethereum](http://brain.web3signer.dappnode) or [Holesky](http://brain.web3signer-holesky.dappnode).
43+
- Upload the keystores and tag them with "Lido".
44+
- The fee recipient will be automatically set to `0xE73a3602b99f1f913e72F8bdcBC235e206794Ac8` for Holesky and `0x388C818CA8B9251b393131C08a736A67ccB19297` for Mainnet. It is not editable.
4345

44-
:::caution
45-
Double-check that your Lido keystores are tagged correctly. This is crucial to ensure that the node operator is properly set up, and has the correct fee recipient set.
46-
:::
46+
![Lido-CSM3](/img/lido-csm-ss-docs3.png)
4747

48-
:::danger
49-
Do not edit the fee recipient address. Doing so will result in penalties.
50-
:::
48+
:::caution
49+
Double-check that your Lido keystores are tagged correctly. This is crucial to ensure that the node operator is properly set up, and has the correct fee recipient set.
50+
:::
5151

52-
4. **Register as a Lido Node Operator & your validators**:
52+
:::danger
53+
Do not edit the fee recipient address. Doing so will result in penalties.
54+
:::
5355

54-
- Navigate to the [Lido Deposit UI](https://csm.lido.fi/?ref=dappnode) and complete the deposit process by submitting the `deposit_data.json` file you generated with your keystore(s).
55-
![Lido-CSM4](/img/lido-csm-ss-docs4.png)
56-
- You'll be prompted to sign an ETH bond depending on the number of validators you're submitting to the CSM.
57-
- Once the deposit has been confirmed, the CSM and then the Beacon Chain will process your deposit. Keep in mind you'll have to wait 16-24 hours plus the Becaon Chain's entry queue for your validators to activate. Your node operator setup is now complete!
56+
### 4. **Register as a Lido Node Operator & your validators**
5857

59-
5. **Setup notifications**
58+
- Navigate to the [Lido Deposit UI](https://csm.lido.fi/?ref=dappnode) and complete the deposit process by submitting the `deposit_data.json` file you generated with your keystore(s).
59+
![Lido-CSM4](/img/lido-csm-ss-docs4.png)
60+
- You'll be prompted to sign an ETH bond depending on the number of validators you're submitting to the CSM.
61+
- Once the deposit has been confirmed, the CSM and then the Beacon Chain will process your deposit. Keep in mind you'll have to wait 16-24 hours plus the Becaon Chain's entry queue for your validators to activate. Your node operator setup is now complete!
6062

61-
- Get your bot token and user ID from the [Telegram BotFather](https://core.telegram.org/bots/tutorial#obtain-your-bot-token) and [userinfobot](https://t.me/userinfobot) respectively.
62-
- Introduce your bot token and user ID and confirm
63-
- You should receive a confirmation message from the bot.
63+
### 5. **Setup notifications**
6464

65-
![lido-notifications-onboarding](/img/lido-notifications-onboarding.png)
65+
- Get your bot token and user ID from the [Telegram BotFather](https://core.telegram.org/bots/tutorial#obtain-your-bot-token) and [userinfobot](https://t.me/userinfobot) respectively.
66+
- Introduce your bot token and user ID and confirm
67+
- You should receive a confirmation message from the bot.
68+
69+
![lido-notifications-onboarding](/img/lido-notifications-onboarding.png)

0 commit comments

Comments
 (0)