Detailed Guide: Lido CSM with Google Cloud Credits

1. Prerequisites

1. Install WireGuard, a VPN client required to connect to the visual interface of Dappnode. You can install it for your operating system from here: https://www.wireguard.com/install/

Setting up a Google Cloud account

1. Go to https://cloud.google.com/free and activate the free trial. It will ask for your credit card details, but you won’t be charged.

2. Open the Google Cloud Console.

1. Create a VM (Virtual Machine)

1. Select the following configuration under the “Machine configuration” section:

2. Name: use any name, e.g., Lido-Workshop

3. Region: choose your preferred region for this test. Note: For Mainnet use, it’s best to diversify geographically and avoid popular regions like Europe or the US.

4. Zone: any.

5. Machine family: E2

6. Machine type: e2-standard-8, 16 GB memory

1. In the “OS and Storage” section, click Change.

1. Select the following options:

   1. Operating system: Debian

   2. Version: Debian GNU/Linux 12 (bookworm)

   3. Boot disk type: Balanced persistent disk

   4. Size: 300 GB

1. In the “Networking” section, check the boxes for HTTP and HTTPS traffic.

1. In the “Observability” section, uncheck both options.

1. When you’re done, click Create at the bottom of the screen. You should see something like this:

1. Now we need to open the WireGuard port in the console so we can access it later. Go to https://console.cloud.google.com/net-security/firewall-manager/firewall-policies/ and click Create firewall rule.

1. Configure the firewall as follows:

   1. Name: Wireguard

   2. Targets: All instances in the network

   3. Source filter and range: IPv4 with range 0.0.0.0/0

   4. Protocols and ports: Specific protocols and ports → UDP 51820

3. Installing Dappnode

1. Open the dropdown menu under the Connect tab. For convenience, select “Open in another browser window.” Click Authorize when prompted.

1. Now that we’re in the command-line interface, we’ll install Dappnode using scripts. You can read more in the official Dappnode documentation: https://docs.dappnode.io/.

2. Copy and paste the following commands:

   1. Update all system packages:

      sudo apt update -y && sudo apt upgrade -y

   2. Install prerequisite services:

      sudo wget -O - https://prerequisites.dappnode.io | sudo bash

   3. Install Dappnode:

      sudo wget -O - https://installer.dappnode.io | sudo bash

   4. Restart the machine:

      sudo shutdown -r now

3. When the machine restarts, the connection will be lost. Reopen the terminal in another tab as in step 1. You should see something like this:

4. Accessing Dappnode

1. Use the command dappnode_connect to see all the ways to access the Dappnode interface. In this case, we’ll use WireGuard credentials.

Example:

[Interface]
PrivateKey = uIz2EnOQYdrBJH3qiYL5I8OSXfp+NqXGNPKrNzX02lg=
ListenPort = 51820
Address = 10.24.0.2/32
DNS = 172.33.1.2, 10.20.0.2

[Peer]
PublicKey = DXDtdMps60FXkRpCp75wsYe8tGrqDCQlHZ39Ea4ZiTI=
PresharedKey = VIEwmWlIcLI48owu4nKBta7D25/P2qDBjjEO0dVd4+Y=
AllowedIPs = 172.33.0.0/16, 10.20.0.0/24
Endpoint = 8db634b28e82639f.dyndns.dappnode.io:51820

1. Abre WireGuard y en la esquina inferior izquierda haz click en “Añadir Tunnel vacío”.

1. Go back to the terminal and copy the credentials. Example:

[Interface]
Address = 10.24.0.2
PrivateKey = AIBMuyREhY4K94w2azghxG9NJWHhOmBfvBI+B4pEwVs=
ListenPort = 51820
DNS = 172.33.1.2,10.20.0.2

[Peer]
PublicKey = 6+ICyimhPEu22egPCaAhU5ClDwbgxp2oSBrfImLS7wI=
PresharedKey = 9JadZ1DLo4EDhSCdLJgZDnmDgVvfEpnn5BZdy77ipvU=
Endpoint = 6a30df7055d895c4.dyndns.dappnode.io:51820
AllowedIPs = 172.33.0.0/16,10.20.0.0/24

1. Paste the credentials and give the tunnel any name. Click Save to store the tunnel.

1. Once saved, activate the tunnel using the button shown below.

1. Finally, go to http://my.dappnode/. Set your username and password, and save the security token. After this, follow the Dappnode interface instructions and configure:

   1. Repository Source: Remote (for testnet; if setting up mainnet, you can use your own clients as the repository source, which is recommended for a final setup).

   2. System Auto Updates: Off (automatic updates can cause performance issues if something goes wrong — it’s better to do them manually when you can monitor your node).

   3. Enable System Notifications: For this workshop, leave it blank. Here you can set up a Telegram bot or email notifications to monitor your machine status.

5. Setting up your node in Dappnode

1. Go to the Stakers tab at http://my.dappnode/stakers/. Select the network (Hoodi in this case), execution and consensus clients, enable Web3Signer, and enable MEV-Boost relays from the list of relays vetted by Lido for Hoodi. Scroll down, click Apply changes, and wait for the clients to install.

1. In the Dashboard, you’ll see the status of your clients. When both appear in green, they’re synchronized and it’s safe to move to the next step.

6. Generating keys for Lido CSM (testnet)

1. Go to https://wagyu.gg/ and install the tool. Generate a recovery seed phrase and select the network. Write down and confirm the phrase. Choose how many validators you want to generate. Encrypt the keystores with a secure password.

2. IMPORTANT: Set the withdrawal address to Lido’s withdrawal vault: Hoodi: 0x4473dCDDbf77679A643BdB654dbd86D67F8d32f2

3. Confirm the password. Select the destination folder to store the keystores and deposit data. You’ll receive:

   1. keystore-m_<timestamp>.json: the keystore to upload to your node

   2. deposit_data-<timestamp>.json: the deposit data

7. Importing the keys into your node and the Lido protocol

7.1. Importing keys into Dappnode

1. Go to the web3signer package in your Dappnode.

2. Click Import, then drag the keystores you generated in the previous step, enter your password, and select Lido as the staking protocol. This will automatically set the fee recipient to Lido’s address.

7.2. Importing keys into Lido CSM

1. Go to the Lido CSM page for Hoodi (https://csm.testnet.fi/) and connect your wallet.

2. Click Create a Node Operator.

3. Inside the widget, upload your deposit_data file, ensure you have enough testnet ETH, and deposit it into the protocol.