Skip to content

Commit b415170

Browse files
author
Diego Mazo
committed
New text in the overview
1 parent 19582fd commit b415170

File tree

1 file changed

+19
-9
lines changed

1 file changed

+19
-9
lines changed

docs/user/staking/ethereum/lsd-pools/lido/overview.md

Lines changed: 19 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,27 +6,37 @@
66

77
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.
88

9-
Lido, with over [9 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 and community stakers in mind, the CSM lowers the barrier to becoming an Ethereum validator, 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 [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.
1010

1111
:::info
1212
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).
1313
:::
1414

1515
## **Lido CSM in dappnode**
1616

17-
Dappnode provides an easy-to-use and intuitive interface for most of the infrastructure needed to become a Lido Node Operator. The process is straightforward and requires only a few steps to set up a node operator and start earning rewards. Dappnode takes care of the Lido protocol requirements, such as exiting validator when needed, and provides a user-friendly interface to manage the node operator.
17+
Dappnode provides an easy-to-use and intuitive interface for most of the infrastructure needed to become a Lido Node Operator. The process is straightforward and requires only a few steps to set up a node operator and start earning rewards.
1818

19-
The main functionalities covered by Dappnode are:
19+
Steps to become Node Operator
20+
1. Go to Dappnode platform https://my.dappnode/
21+
2. Go to Dappstore tab in the left menu
22+
3. Search and install Lido CSM package
23+
4. Once it is installed, go to packages tab and click on the name of the Lido CSM package and find the section Ui below the version title.
24+
5. You will be in the Lido interface, connect your wallet and start the staking process.
2025

21-
- **Notifications**: you can easily setup notifications for your NO to be informed about any event.
26+
Dappnode takes care of the Lido protocol requirements, such as exiting validator when needed, and provides a user-friendly interface to manage the node operator.
27+
28+
29+
The main functionalities covered by Dappnode in the Lido CSM package are:
30+
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.
2232
- **Ejector**: whenever any of your validator requires to be exited, it will be done automatically sending you the corresponding notification.
23-
- **Track multiple NOs**: you can track multiple NOs from the same DAppNodePackage-lido-csm.
33+
- **Track multiple Node Operators**: you can track multiple Node Operators from the same DAppNodePackage-lido-csm.
2434
- **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.
2535
- **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.
2636
- **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.
2737
- **Infraestructure monitoring**: you will be able to visualize the status of your infraestructure (EC - CC - Signer - MEV Boost).
2838

29-
### **Notifications**
39+
### **Telegram Notifications**
3040

3141
You will be able to setup your notifications either during the onboarding process if you are registering as a new Node Operator and from the UI navigating to `/notifications`. You must provide:
3242

@@ -53,12 +63,12 @@ Once your notifications are setup, you will receive notificatios for the followi
5363
The Ejector is a service that will automatically exit your validator when needed. You will receive a notification when the validator has been successfully exited and when the exit has failed, letting you know that a manual exit is required. The ejector has the following characteristics:
5464

5565
- **Automatic exit**: the Ejector will automatically exit your validator when needed.
56-
- **Notifications**: you will receive a notification when the validator has been successfully exited and when the exit has failed, letting you know that a manual exit is required.
66+
- **Ejector Notifications**: you will receive a notification when the validator has been successfully exited and when the exit has failed, letting you know that a manual exit is required.
5767
- **Retry mechanism**: the Ejector will retry the exit process if it fails, ensuring that the validator is exited successfully.
5868

5969
![lido-notification-ejector](/img/lido-notification-ejector.png)
6070

61-
### **Track multiple NOs**
71+
### **Track multiple Node Operators**
6272

6373
The DAppNodePackage-lido-csm allows you to track multiple Node Operators from the same package. This feature is useful if you are managing multiple Node Operators and want to keep track of their performance and status in one place. To make the package to track a new Node Operator, you must sign in with the new Node Operator's wallet and import the keystores.
6474

@@ -70,7 +80,7 @@ Make sure to import the correct keystores for each Node Operator. Importing the
7080

7181
You can import your keystores directly from the DAppNodePackage-lido-csm UI during the onboarding process or from the `/keystores` section (comming soon). The keystores will be automatically tagged as Lido, and you will be able to use them to run validators in the Lido protocol. These keystores will be located in the web3signer package, for further editing or deleting them you must go to the web3signer UI.
7282

73-
Whenever there are 1 or more keystores that belongs to your NO and are not imported you will be able to see the following message in the DAppNodePackage-lido-csm UI:
83+
Whenever there are 1 or more keystores that belongs to your Node Operator and are not imported you will be able to see the following message in the DAppNodePackage-lido-csm UI:
7484

7585
![lido-keystore-not-imported](/img/lido-keystore-not-imported.png)
7686

0 commit comments

Comments
 (0)