dappnode · mateumiralles · Jan 14, 2026 · Jan 14, 2026 · Jan 14, 2026
@@ -12,16 +12,16 @@ Keystore files contain critical information for managing your validators. When y
 
 2. Access the `/import` tab in Brain UI:
 
-   - Mainnet [Staking Brain](http://brain.web3signer.dappnode/import)
+   - Mainnet [Staking Brain](http://brain.web3signer.dappnode)
 
-   - Holesky [Staking Brain](http://brain.web3signer-holesky.dappnode/import)
+   - Hoodi [Staking Brain](http://brain.web3signer-hoodi.dappnode)
 
 3. Select the “Lido” Tag:
    While uploading your keystore files, make sure to tag them with “Lido” to designate automatically the required fee recipient from the Lido protocol:
 
    - Mainnet: `0x388C818CA8B9251b393131C08a736A67ccB19297`
 
-   - Holesky: `0xE73a3602b99f1f913e72F8bdcBC235e206794Ac8`
+   - Hoodi: `0x9b108015fe433F173696Af3Aa0CF7CDb3E104258`
 
    :::danger
    Do not edit the fee recipient address. Doing so will result in penalties.
@@ -41,7 +41,7 @@ The Lido CSM UI serves as the central interface for managing validator keys and
 
 1. Access the Lido CSM UI:
 
-   Navigate to the Lido CSM package UI. - [Mainnet UI](http://ui.lido-csm-mainnet.dappnode/) - [Holesky UI](http://ui.lido-csm-holesky.dappnode/)
+   Navigate to the Lido CSM package UI. - [Mainnet UI](http://ui.lido-csm-mainnet.dappnode/) - [Hoodi UI](http://ui.lido-csm-hoodi.dappnode/)
 
 2. Connect Your Wallet:
 
@@ -53,7 +53,7 @@ The Lido CSM UI serves as the central interface for managing validator keys and
 
    - Follow the on-screen prompts to grant the necessary permissions.
 
-   - Ensure the wallet’s network matches the intended environment (e.g., Mainnet or Holesky).
+   - Ensure the wallet’s network matches the intended environment (e.g., Mainnet or Hoodi).
 
 4. Verify Connection:
 

@@ -47,10 +47,10 @@ Once you setup your notifications, you will receive a test notification to confi
 Once your notifications are setup, you will receive notificatios for the following events:
 
 - Lido Smart Contract events:
-  - [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.
+  - [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-report-submitted](/img/lido-csm-report-submitted.png)
-  - [Lido CSM events](https://docs.lido.fi/staking-modules/csm/guides/events/#contract-csm): check the Lido documentation for more details.
-  - [Lido CSFeeDistributor](https://docs.lido.fi/staking-modules/csm/guides/events/#contract-csfeedistributor): check the Lido documentation for more details.
+  - [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.
+  - [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.
 - Validator exit:
   - Exit requested: you will receive a notification when the validator exit has been requested.
     ![lido-csm-exit-requested](/img/lido-csm-exit-requested.png)
@@ -60,9 +60,9 @@ Once your notifications are setup, you will receive notificatios for the followi
     ![lido-csm-exit-failed](/img/lido-csm-exit-failed.png)
 - Performance:
   - Above the treshold: you will receive a notification when your validator is performing above the treshold.
-  ![lido-csm-performance-notification-above](/img/lido-csm-performance-notification-above.png)
+    ![lido-csm-performance-notification-above](/img/lido-csm-performance-notification-above.png)
   - Below the treshold: you will receive a notification when your validator is performing below the treshold.
-  ![lido-csm-performance-notification-below](/img/lido-csm-performance-notification-below.png)
+    ![lido-csm-performance-notification-below](/img/lido-csm-performance-notification-below.png)
 - Operator stuck: you will receive a notification when your operator is stuck indicating the epoch range.
   ![lido-csm-stuck](/img/lido-csm-stuck.png)
 - Relays (comming soon):

@@ -6,7 +6,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.
 
-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.
+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.
 
 :::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).
@@ -31,7 +31,7 @@ The main functionalities covered by Dappnode in the Lido CSM package are:
 - **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.
 - **Ejector**: whenever any of your validator requires to be exited, it will be done automatically sending you the corresponding notification.
 - **Track multiple Node Operators**: you can track multiple Node Operators from the same DAppNodePackage-lido-csm.
-- **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.
+- **Performance**: your validators performance will be tracked and you will be notified if they are not performing as expected according to the Lido thresholds.
 - **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.
 - **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.
 - **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
 You can check the list of allowed relays in the smart contracts:
 
 - **Mainnet relays**: See `get_relays` from [Mainnet](https://etherscan.io/address/0xf95f069f9ad107938f6ba802a3da87892298610e#readContract#F4)
-- **Holesky relays**: See `get_relays` from [Holesky](https://holesky.etherscan.io/address/0x2d86C5855581194a386941806E38cA119E50aEA3#readContract#F4)
+- **Hoodi relays**: See `get_relays` from [Hoodi](https://hoodi.etherscan.io/address/0x279d3A456212a1294DaEd0faEE98675a52E8A4Bf#readContract#F4)
 
 :::warning
 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
 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.
 :::
 
-For more details on MEV in CSM, visit the [Lido CSM Docs](https://operatorportal.lido.fi/modules/community-staking-module).
+For more details on MEV in CSM, visit the [Lido CSM Docs](https://operatorportal.lido.fi/modules/community-staking-module#block-99fed4cdcc7641f1af431ddb8afafbec).
 
 ## Testnet
 
-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**.
+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**.
 
 ## Execution Client RPC
 
@@ -145,7 +145,7 @@ Changing the RPC is done at your own risk. Dappnode is not responsible for any p
    Infura).
 2. Navigate to the `/config` tab of your Lido CSM package:
    - [Mainnet Lido CSM package's config tab](http://my.dappnode/packages/my/lido-csm-mainnet.dnp.dappnode.eth/config)
-   - [Holesky Lido CSM package's config tab](http://my.dappnode/packages/my/lido-csm-holesky.dnp.dappnode.eth/config)
+   - [Hoodi Lido CSM package's config tab](http://my.dappnode/packages/my/lido-csm-hoodi.dnp.dappnode.eth/config)
 3. Change the `RPC_URL` environment variable in the **Lido Events Section**.
 4. Click the `Update` button
    ![lido-csm-config-tab](/img/lido-csm-config-tab.png)
@@ -154,7 +154,7 @@ Changing the RPC is done at your own risk. Dappnode is not responsible for any p
 After the first scan we suggest to change it back again to:
 
 - `http://execution.mainnet.dncore.dappnode:8545`
-- `http://execution.holesky.dncore.dappnode:8545`
+- `http://execution.hoodi.dncore.dappnode:8545`
   :::
 
 ---

@@ -7,7 +7,7 @@ The **Performance** tab allows you to monitor the performance of your Lido valid
 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.
 
 - On **Mainnet**, reports are distributed every **28 days**.
-- On **Holesky**, reports are distributed every **7 days**.
+- On **Hoodi**, reports are distributed every **7 days**.
 
 ## Lido Report Cards
 
@@ -39,7 +39,7 @@ The **Range Selector** controls all the data displayed in the Performance tab. I
 - **Ever** (From the first report that included a validator associated with your Node Operator)
 
   :::info
-  On **Holesky**, an additional **week** range is available since reports are distributed weekly.
+  On **Hoodi**, an additional **week** range is available since reports are distributed weekly.
   :::
 
 ## Node Operator Efficiency vs. Lido Average Efficiency

@@ -10,12 +10,12 @@
 
 ### 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).
+- Navigate to [Dappnode Staking for Ethereum](http://my.dappnode/stakers/ethereum) or [Dappnode Staking for Hoodi](http://my.dappnode/stakers/hoodi).
 - 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).
   - Mainnet relays see `get_relays` from [Mainnet](https://etherscan.io/address/0xf95f069f9ad107938f6ba802a3da87892298610e#readContract)
-  - Holesky relays see `get_relays` from [Holesky](https://holesky.etherscan.io/address/0x2d86C5855581194a386941806E38cA119E50aEA3#readContract)
+  - Hoodi relays see `get_relays` from [Hoodi](https://hoodi.etherscan.io/address/0x279d3A456212a1294DaEd0faEE98675a52E8A4Bf#readContract#F4)
 
 :::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.
@@ -27,8 +27,8 @@ It is mandatory to choose at least one relay to ensure the node operator does no
 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: `0xb9d7934878b5fb9610b3fe8a5e441e8fad7e293f`.
+- Hoodi: `0x4473dCDDbf77679A643BdB654dbd86D67F8d32f2`.
 - 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.
@@ -43,7 +43,7 @@ Make sure you correcly set the withdrawal address up, otherwise the Lido CSM won
 
 To install the Lido CSM package, select the variant that suits your needs:
 
-- [Holesky package](http://my.dappnode/installer/dnp/lido-csm-holesky.dnp.dappnode.eth)
+- [Hoodi package](http://my.dappnode/installer/dnp/lido-csm-hoodi.dnp.dappnode.eth)
 - [Ethereum package](http://my.dappnode/installer/dnp/lido-csm-mainnet.dnp.dappnode.eth)
 
 ### 4. Register as Node Operator
@@ -58,7 +58,7 @@ To install the Lido CSM package, select the variant that suits your needs:
 
 While registering as a node operator, the UI will verify that you meet the following requirements:
 
-- Stake Requirement: You need 2 ETH or an equivalent amount in stETH or wstETH for the first validator.
+- Stake Requirement: You need either 2.4 ETH or 1.5 ETH, or an equivalent amount in stETH or wstETH for the first validator.
 - Infrastructure Setup: Your Dappnode must be running:
   - An execution client.
   - A consensus client.
@@ -91,7 +91,7 @@ You must start the conversation with the bot using `/start` so it can send you n
 
   - Select or drag-and-drop the keystore files associated with your `deposit_data.json`.
   - Enter the password for the keys in the provided field.
-  ![Lido-CSM4](/img/lido-csm-ss-docs5.png)
+    ![Lido-CSM4](/img/lido-csm-ss-docs5.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!
@@ -57,12 +57,12 @@ const FeatureList: FeatureItem[] = [
     Image: require("@site/static/img/lido-csm.jpeg").default,
     description: (
       <>
-        Community Staking Module (CSM) will most likely be the third Lido on
-        Ethereum module after the Curated Module and Simple DVT, and the first
-        to offer permissionless entry allowing community stakers to operate
-        validators by providing an ETH-based bond. Dappnode facilitates this
-        process by providing a user-friendly interface for community stakers to
-        stake on Ethereum and Holesky as node operators.
+        Community Staking Module (CSM) is the third Lido on Ethereum module
+        after the Curated Module and Simple DVT, and the first to offer
+        permissionless entry allowing community stakers to operate validators by
+        providing an ETH-based bond. Dappnode facilitates this process by
+        providing a user-friendly interface for community stakers to stake on
+        Ethereum and Hoodi as node operators.
       </>
     ),
     url: "/docs/user/staking/ethereum/lsd-pools/lido/overview",