You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user/staking/ethereum/lsd-pools/lido/notifications.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,10 +47,10 @@ Once you setup your notifications, you will receive a test notification to confi
47
47
Once your notifications are setup, you will receive notificatios for the following events:
48
48
49
49
- Lido Smart Contract events:
50
-
-[Lido VEVO events](https://docs.lido.fi/staking-modules/csm/guides/events/#contract-vebo): the most important event to remark is the validator exit request event, that will trigger the Ejector to exit the validator.
50
+
-[Lido VEBO events](https://docs.lido.fi/run-on-lido/csm/alerts-and-monitoring/expert-custom-alerts/#contract-vebo): the most important event to remark is the validator exit request event, that will trigger the Ejector to exit the validator.
-[Lido CSM events](https://docs.lido.fi/staking-modules/csm/guides/events/#contract-csm): check the Lido documentation for more details.
53
-
-[Lido CSFeeDistributor](https://docs.lido.fi/staking-modules/csm/guides/events/#contract-csfeedistributor): check the Lido documentation for more details.
52
+
-[Lido CSM events](https://docs.lido.fi/run-on-lido/csm/alerts-and-monitoring/expert-custom-alerts/#contract-csm): check the Lido documentation for more details.
53
+
-[Lido CSFeeDistributor](https://docs.lido.fi/run-on-lido/csm/alerts-and-monitoring/expert-custom-alerts#contract-csfeedistributor): check the Lido documentation for more details.
54
54
- Validator exit:
55
55
- Exit requested: you will receive a notification when the validator exit has been requested.
Copy file name to clipboardExpand all lines: docs/user/staking/ethereum/lsd-pools/lido/overview.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
7
7
Lido is a **liquid staking** solution for Ethereum that addresses the liquidity issues of traditional staking. Instead of locking up assets and losing access to them, users can stake through Lido and receive liquid tokens. These tokens retain the value of the staked assets and can be used elsewhere while still earning staking rewards.
8
8
9
-
Lido, with over [9,8 million ETH](https://lido.fi/ethereum) staked on its platform, is a significant contributor in the Ethereum ecosystem. To broaden and diversify its network of node operators, Lido recently introduced the [**Community Staking Module** (CSM)](https://csm.lido.fi/?ref=dappnode), the first Lido module with a **permissionless entry** for Ethereum staking. By first providing an ETH-based bond, anyone can now become a node operator by running validators in the Lido protocol. Designed with solo stakers in mind, the CSM lowers the barrier to becoming an Ethereum validator with 2.4 ETH, requiring far less than the standard 32 ETH, and offers a user-friendly experience. While tailored for smaller stakers, it is open to all, including professional operators.
9
+
Lido, with over [8 million ETH](https://lido.fi) staked on its platform, is a significant contributor in the Ethereum ecosystem. To broaden and diversify its network of node operators, Lido introduced the [**Community Staking Module** (CSM)](https://lido.fi/csm), the first Lido module with a **permissionless entry** for Ethereum staking. By first providing an ETH-based bond, anyone can now become a node operator by running validators in the Lido protocol. Designed with solo stakers in mind, the CSM lowers the barrier to becoming an Ethereum validator with 2.4 ETH, requiring far less than the standard 32 ETH, and offers a user-friendly experience. While tailored for smaller stakers, it is open to all, including professional operators.
10
10
11
11
:::info
12
12
Becoming a Lido Node Operator is recommended for users with some experience in running validators. The process requires a basic understanding of the Ethereum network and the Lido protocol. If you are new to staking, we recommend setting up a validator on the Testnet first to familiarize yourself with the process, see [Staking on the Ethereum Testnet](/docs/user/staking/ethereum/solo/holesky.md).
@@ -31,7 +31,7 @@ The main functionalities covered by Dappnode in the Lido CSM package are:
31
31
-**Telegram Notifications**: you can setup notifications for your Node Operator to be informed about any event. You need to configure the user ID and Telegram token to received your notifications.
32
32
-**Ejector**: whenever any of your validator requires to be exited, it will be done automatically sending you the corresponding notification.
33
33
-**Track multiple Node Operators**: you can track multiple Node Operators from the same DAppNodePackage-lido-csm.
34
-
-**Performance**: your validators attestations performance will be tracked and you will be notified if they are not performing as expected according to the Lido tresholds.
34
+
-**Performance**: your validators performance will be tracked and you will be notified if they are not performing as expected according to the Lido thresholds.
35
35
-**MEV boost relays**: you will receive notifications whenever your validators are using relays blocklisted in the Lido CSM or not using any relay at all.
36
36
-**Import keystores directly from the Lido CSM**: you can import your keystores directly from the Lido CSM to your DAppNodePackage-lido-csm and they will be automatically tagged as Lido.
37
37
-**Infraestructure monitoring**: you will be able to visualize the status of your infraestructure (EC - CC - Signer - MEV Boost).
@@ -99,7 +99,7 @@ Lido CSM only allows certain relays for your node configuration. You must use at
99
99
You can check the list of allowed relays in the smart contracts:
100
100
101
101
-**Mainnet relays**: See `get_relays` from [Mainnet](https://etherscan.io/address/0xf95f069f9ad107938f6ba802a3da87892298610e#readContract#F4)
102
-
-**Holesky relays**: See `get_relays` from [Holesky](https://holesky.etherscan.io/address/0x2d86C5855581194a386941806E38cA119E50aEA3#readContract#F4)
102
+
-**Hoodi relays**: See `get_relays` from [Hoodi](https://hoodi.etherscan.io/address/0x279d3A456212a1294DaEd0faEE98675a52E8A4Bf#readContract#F4)
103
103
104
104
:::warning
105
105
You must select at least one relay to ensure the node operator does not propose vanilla blocks. As a Lido Node Operator, it is your responsibility to ensure that your infrastructure is correctly using MEV Boost.
@@ -113,11 +113,11 @@ The Lido CSM Dappnode package also includes infrastructure checks and warnings i
113
113
You can select/unselect relays in the [Stakers](http://my.dappnode/stakers) tab in the Dappmanager or directly modify the relay URLs in the `MEV Boost` package configuration tab.
114
114
:::
115
115
116
-
For more details on MEV in CSM, visit the [Lido CSM Docs](https://operatorportal.lido.fi/modules/community-staking-module).
116
+
For more details on MEV in CSM, visit the [Lido CSM Docs](https://operatorportal.lido.fi/modules/community-staking-module#block-99fed4cdcc7641f1af431ddb8afafbec).
117
117
118
118
## Testnet
119
119
120
-
The Lido Community Staking Module is available on the Ethereum Mainnet. If you are new to staking, we recommend setting up a validator on the Testnet first to familiarize yourself with the process. The process is the same, the dappnode package for Lido CSM in testnet is **lido-csm-holesky.dnp.dappnode.eth**.
120
+
The Lido Community Staking Module is available on the Ethereum Mainnet. If you are new to staking, we recommend setting up a validator on the Testnet first to familiarize yourself with the process. The process is the same, the dappnode package for Lido CSM in testnet is **lido-csm-hoodi.dnp.dappnode.eth**.
121
121
122
122
## Execution Client RPC
123
123
@@ -145,7 +145,7 @@ Changing the RPC is done at your own risk. Dappnode is not responsible for any p
145
145
Infura).
146
146
2. Navigate to the `/config` tab of your Lido CSM package:
Copy file name to clipboardExpand all lines: docs/user/staking/ethereum/lsd-pools/lido/performance.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ The **Performance** tab allows you to monitor the performance of your Lido valid
7
7
Before diving into the details, it's essential to understand what a **Lido CSM report** is. These reports contain performance data for all validators in the CSM and are distributed via IPFS hashes by the Lido team.
8
8
9
9
- On **Mainnet**, reports are distributed every **28 days**.
10
-
- On **Holesky**, reports are distributed every **7 days**.
10
+
- On **Hoodi**, reports are distributed every **7 days**.
11
11
12
12
## Lido Report Cards
13
13
@@ -39,7 +39,7 @@ The **Range Selector** controls all the data displayed in the Performance tab. I
39
39
-**Ever** (From the first report that included a validator associated with your Node Operator)
40
40
41
41
:::info
42
-
On **Holesky**, an additional **week** range is available since reports are distributed weekly.
42
+
On **Hoodi**, an additional **week** range is available since reports are distributed weekly.
43
43
:::
44
44
45
45
## Node Operator Efficiency vs. Lido Average Efficiency
Copy file name to clipboardExpand all lines: docs/user/staking/ethereum/lsd-pools/lido/register.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,12 +10,12 @@
10
10
11
11
### 1. **Getting your Dappnode ready**
12
12
13
-
- Navigate to [Dappnode Staking for Ethereum](http://my.dappnode/stakers/ethereum) or [Dappnode Staking for Holesky](http://my.dappnode/stakers/holesky).
13
+
- Navigate to [Dappnode Staking for Ethereum](http://my.dappnode/stakers/ethereum) or [Dappnode Staking for Hoodi](http://my.dappnode/stakers/hoodi).
14
14
- Select your desired execution and consensus clients.
15
15
- Choose Web3Signer to upload the keystores.
16
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).
17
17
- Mainnet relays see `get_relays` from [Mainnet](https://etherscan.io/address/0xf95f069f9ad107938f6ba802a3da87892298610e#readContract)
18
-
-Holesky relays see `get_relays` from [Holesky](https://holesky.etherscan.io/address/0x2d86C5855581194a386941806E38cA119E50aEA3#readContract)
18
+
-Hoodi relays see `get_relays` from [Hoodi](https://hoodi.etherscan.io/address/0x279d3A456212a1294DaEd0faEE98675a52E8A4Bf#readContract#F4)
19
19
20
20
:::warning
21
21
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.
@@ -27,8 +27,8 @@ It is mandatory to choose at least one relay to ensure the node operator does no
27
27
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:
- 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.
33
33
34
34
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.
@@ -43,7 +43,7 @@ Make sure you correcly set the withdrawal address up, otherwise the Lido CSM won
43
43
44
44
To install the Lido CSM package, select the variant that suits your needs:
@@ -58,7 +58,7 @@ To install the Lido CSM package, select the variant that suits your needs:
58
58
59
59
While registering as a node operator, the UI will verify that you meet the following requirements:
60
60
61
-
- Stake Requirement: You need 2 ETH or an equivalent amount in stETH or wstETH for the first validator.
61
+
- Stake Requirement: You need either 2.4 ETH or 1.5 ETH, or an equivalent amount in stETH or wstETH for the first validator.
62
62
- Infrastructure Setup: Your Dappnode must be running:
63
63
- An execution client.
64
64
- A consensus client.
@@ -91,7 +91,7 @@ You must start the conversation with the bot using `/start` so it can send you n
91
91
92
92
- Select or drag-and-drop the keystore files associated with your `deposit_data.json`.
93
93
- Enter the password for the keys in the provided field.
94
-
94
+
95
95
96
96
- You'll be prompted to sign an ETH bond depending on the number of validators you're submitting to the CSM.
97
97
- 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!
0 commit comments