Skip to content

Commit

Permalink
Update Lido CSM Docs (#441)
Browse files Browse the repository at this point in the history
* Update Lido CSM Docs

* add-ss-lido-csm-docs
  • Loading branch information
chuygarcia92 authored Oct 21, 2024
1 parent 069e3fb commit 3e655f4
Show file tree
Hide file tree
Showing 5 changed files with 32 additions and 45 deletions.
77 changes: 32 additions & 45 deletions docs/user/staking/ethereum/lsd-pools/lido.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,12 @@
# Lido
# Lido Community Staking Module (CSM)

---

### **Lido Overview**
### **Lido CSM Overview**

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.

Ethereum plays a significant role in the Lido ecosystem, with more than [9 million ETH](https://lido.fi/ethereum) staked through the platform. Lido stakes these assets on behalf of the users, who receive stETH in return. A set of permissioned **node operators** are responsible for managing the staking infrastructure.

Recently, Lido introduced the [**Community Staking Module** (CSM)](https://csm.testnet.fi/?ref=dappnode), the first Lido Ethereum module with a **permissionless entry**. By first providing an ETH-based bond, anyone can now become a node operator by running validators in the Lido protocol. The module was designed for solo stakers and community stakers, providing them with the unique ability of becoming Ethereum validator with way less than 32 ETH and one of the friendliest UX possible, but may be utilized by anyone, including professional operators.
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.testnet.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.

:::info
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).
Expand All @@ -18,76 +16,65 @@ Becoming a Lido Node Operator is recommended for users with some experience in r

### **Become a Lido Node Operator with Dappnode**

**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** 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. An overview of the process is how the Lido CSM UI will greet you when first connecting your wallet to the dApp:

---
![Lido-CSM1](/img/lido-csm-ss-docs1.png)

<!-- ---
---

### **Package Key Features**
### **First Steps to create a Node Operator in Dappnode**

- **DAO Governance**: Governed by a DAO to ensure decentralization and security.
- **Community Staking Module**: Enables the community to participate as node operators staking on behalf of the DAO with way less than the 32 ETH required for solo staking.
1. **Getting your Dappnode ready**:

--- -->
- Navigate to [Dappnode Staking for Ethereum](http://my.dappnode/stakers/ethereum) or [Dappnode Staking for Holesky](http://my.dappnode/stakers/holesky).
- Select your desired execution and consensus clients.
- Choose Web3Signer to upload the keystores.
- 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).

### **First Steps to create a Node Operator in Dappnode**
:::warning
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.
:::

1. **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:
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:

- Holesky: `0xF0179dEC45a37423EAD4FaD5fCb136197872EAd9`.
- Ethereum: _coming soon_.
- We recommend using official tools like the [Wagyu Key Gen Tool](https://wagyu.gg/) to create the keystores. This step is crucial and mandatory.
- Ethereum: `0xb9d7934878b5fb9610b3fe8a5e441e8fad7e293f`.
- 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.

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.

2. **Set up the Infrastructure**:

- Navigate to [Dappnode Staking for Ethereum](http://my.dappnode/stakers/ethereum) or [Dappnode Staking for Holesky](http://my.dappnode/stakers/holesky).
- Select your desired execution and consensus clients.
- Choose Web3signer to upload the keystores.
- Configure MEV Boost with as many relays as possible.
![Lido-CSM2](/img/lido-csm-ss-docs2.png)

:::warning
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.
Make sure you correcly set the withdrawal address up, otherwise the Lido CSM won't let you move forward with the validator deposits.
:::

3. **Upload the Keystores in your Dappnode**:

- Go to the Web3signer UI for [Ethereum](http://brain.web3signer.dappnode) or [Holesky](http://brain.web3signer-holesky.dappnode).
- Upload the keystores and tag them with "Lido".
- The fee recipient will be automatically set to `0xE73a3602b99f1f913e72F8bdcBC235e206794Ac8` for Holesky. It is not editable.
- The fee recipient will be automatically set to `0xE73a3602b99f1f913e72F8bdcBC235e206794Ac8` for Holesky and `0x388C818CA8B9251b393131C08a736A67ccB19297` for Mainnet. It is not editable.

:::danger
Do not edit the fee recipient address. Doing so will result in penalties.
:::
![Lido-CSM3](/img/lido-csm-ss-docs3.png)

:::caution
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.
:::

:::danger
Do not edit the fee recipient address. Doing so will result in penalties.
:::

4. **Register as a Lido Node Operator & your validators**:

- Navigate to the [Lido Deposit UI](https://csm.testnet.fi/?ref=dappnode) and complete the deposit process.
- Your node operator setup is now complete!

<!-- (or do it locally directly from your dappnode installing [this package](http://my.dappnode/installer/dnp/)!) -->

5. **Manage Your Node Operator performance in Dappnode (coming soon)**: Dappnode will provide a dashboard to monitor the performance of your node operator by aggregating data from the operator itself and the dappnode host machine, allowing Node operators to monitor their performance and take action if needed to ensure the best possible performance, acting as professional operators.

---

### **FAQs**

<details>
<summary><b>Where can I track the performance of validator as Node Operator?</b></summary>

Dappnode will provide you a UI in form of a dappnode package where you will be able to track the performance of your validator as Node Operator taking advantage of the data provided by the operator itself and the dappnode host machine.
</details>
- Navigate to the [Lido Deposit UI](https://csm.testnet.fi/?ref=dappnode) and complete the deposit process by submitting the `deposit_data.json` file you generated with your keystore(s).
![Lido-CSM4](/img/lido-csm-ss-docs4.png)
- You'll be prompted to sign an ETH bond depending on the number of validators you're submitting to the CSM.
- 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!

---

Refer to the Lido documentation for the Community Staking Module for more details:
Refer to the Lido Community Staking Module documentation for more details:

- [Lido Community Staking Overview](https://blog.lido.fi/lido-community-staking-an-overview/)
- [Lido Community Staking Module](https://operatorportal.lido.fi/modules/community-staking-module#block-d3ad2b2bd3994a06b19dccc0794ac8d6)
- [Lido Community Staking Module](https://operatorportal.lido.fi/modules/community-staking-module)
Binary file added static/img/lido-csm-ss-docs1.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/img/lido-csm-ss-docs2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/img/lido-csm-ss-docs3.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/img/lido-csm-ss-docs4.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 3e655f4

Please sign in to comment.