ToC

Overview

Hi everyone, thank you for joining the 4th round of testing for Lido’s integration of Obol based DVT on Holesky. All participating members have been split into various clusters that represent your group to operate DVs (distributed validators) and will represent an entry in the Lido Node Operator registry. Each cluster will coordinate in a corresponding Discord channel thread that will be used to set up a Protofire Safe Multisig, represent an entry in the Lido Node Operator registry, coordinate a DKG ceremony, and run distributed validators on the Holesky testnet.

Prerequisites

• Fill out this form to additional teammates (if they do not already have roles) that will be directly involved in running your individual node: https://forms.gle/3vyr8pVhtGSS8bTx9
• A server to run your node located in the region for your specific cluster
  • Please note many participants have experienced issues with Contabo, we would recommend using a different provider
  • One you can give a static public IP to and open ports on
  • We recommend the following specs if you’re going to use the template docker-repo that contains the Beacon Node and Execution Client. Charon alone uses negligible disk space of not more than a few MBs.
    • RECOMMENDED SPECS:
      • 8 physical cores (16 virtual) with good CPU single-core performance
      • 32GB RAM
      • 2TB NVME storage
    • MINIMUM SPECS:
      • A CPU with 2+ physical cores (or 4 vCPUs)
      • 8GB RAM
      • 1.5TB+ free SSD disk space
• Plan which setup track you will use that offers the Lido specific version of the Obol Charon client - there are multiple options and set up guides will be shared for all of them:
  • The template docker-compose repo for lido DVs. You can also use an existing beacon node and other Charon deployment methods if you have tested that setup before, but note that the Charon version must align with the one used in the docker-compose repo.
  • Dappnode Lido x Obol Simple DVT Integration
  • Stereum Lido x Obol Simple DVT Integration
  • eth-docker Lido x Obol Simple DVT Integration (downstream version developed by Lido DAO contributors)
• Agreement on who will deploy the SAFE, stage transactions, and execute the transactions once approved. This person is referred to as the cluster coordinator.
• Join the relevant Discord thread for your cluster. The name of the thread is also the name of your cluster that should be referenced where needed.

First Steps

When your team has chosen the cluster coordinator, please tag @kimonsh and @perrier. A form (linked below) will be used to collect each cluster member’s Ethereum addresses that they plan to use to sign messages in the SAFE, sign the distributed validator config and receive validators’ rewards to.

Each cluster member must submit the form and verify the address(es) they would like to use. Each cluster member should submit up to two addresses.

1. Required: Your individual manager address. This will be your address used for the SAFE Multisig and for signing messages related to your distributed validator cluster in the DV Launchpad. The launchpad only supports Metamask* at the moment so you need to be able to connect to Dapps via Metamask (which can also import a hardware wallet for example). If you would like to, it can also act as your individual reward address. Each cluster member must submit the address and verification (see “Address Verification” below) in the form.

*Multisig support will be added in the future, however is not available at this time

2. Optional: Your reward address. This will be the address added to the reward splitter contract. The splitter contract will evenly distribute rewards between all members of your cluster. This rewards address should be used if you would like to use an address other than the one used for your manager address to collect rewards. If you provide a reward address you will need to sign a message verifying ownership of it in addition to the manager address’s verification.

Each individual participant is responsible for the security and storage of the private key(s) related to these addresses. Please confirm that you have your seed phrase backed up and the address is secure before submitting. This is crucial for signing transactions and receiving rewards over the coming years.

Use this form to submit your address and verification link (see verification instructions below): https://forms.gle/9sSmLHVWpNu2Qs9k9

Address Verification Instructions

Use the following guide to prepare and sign a message that will be used for verification of your chosen manager and (where applicable) reward address:

In case of using externally owned account (EOA):

1. Sign the message on mainnet using the text (add your specific details within <>: with the private key you’ll use as the signing key. One of the options is using Etherscan.
   1. Go to https://etherscan.io/verifiedSignatures
   2. Press the “Sign Message” button and connect your wallet
   3. Input the address you’re verifying (your Individual Manager Address or Individual Rewards Address)
   4. Enter your message using the following template (add your specific details within <>: “<my name> is joining Lido x Obol cluster <cluster name> with address <public address>”
   5. Press sign message and if the message is successfully signed, publish it.
   6. Submit the verified signature URL via the form (e.g. https://etherscan.io/verifySig/27336).

• In case of using SAFE Multisig (ONLY FOR INDIVIDUAL REWARD ADDRESSES):

SAFE Multisig

Once the form is filled out, please tag @kimonsh and @perrier and wait for confirmation to proceed further.

Once each cluster members has submitted the form and Lido NOM team has approved, the addresses will be shared to the group and the cluster coordinator will create the 5/7 threshold Safe Multisig using each cluster member’s individual manager address on Holesky (https://holesky-safe.protofire.io/). When the Safe is created, share the Safe URL for your cluster to review and tag @kimonsh and @perrier. This address will be your cluster’s representation in the Lido Simple DVT Node Operator Registry on Holesky.

Each cluster should also pin a message with basic info in their threads:

<participant name>   :  <ETH address here>   | <participant cluster identifier>
<participant2 name>  :  <ETH address here>   | <participant3 cluster identifier>
<participant3 name>  :  <ETH address here>   | <participant3 cluster identifier>

repeat above 'n' times where 'n' = cluster size

The cluster identifier will be obtained at the end of the DKG (steps below). Update the message to reflect it once done.

During this time, the testnet Simple DVT Module Committee will add your cluster to the Lido Node Operator Registry using the SAFE multisig you provided.

⚠️Do Not Proceed Until Given Instructions by the Lido Team

Operator Joining Flow - Obol Default

Operator Joining Flow - eth-docker

Operator Joining Flow - Stereum

Operator Joining Flow - Dappnode

⚠️Do Not Proceed Until Given Instructions by the Lido Team

Validator Deposit & Activation

<aside> ⚠️ Do not go through the standard deposit flow (either in the DV Launchpad or on ethereum.org), please follow the steps below to deposit and activate the validators instead.

</aside>

Once each member's DV node is synced (both the EL, CL and that Charon is happy), it is time to activate the validator. You can check the health of your cluster by opening your local Grafana dashboard.

# Open Grafana dashboard
open <http://localhost:3000/d/singlenode/>

• The cluster coordinator will submit the deposit data to the Simple DVT module. This can be done through the Lido Operators UI, by pasting the data from the deposit-data.json file from the .charon folder. Make sure to include all three batches of 50 keys when using the tool. The cluster coordinator should use the WalletConnect integration to stage this transaction in the Safe UI.
• The rest of the operators need to use the Safe UI to confirm the transaction before signing.

  • Each Operator should CAREFULLY confirm that the transaction data matches the deposit-data.json file they have.

  • This can be done by connecting to the Lido Operators UI via your multi-sig (use Walletconnect).

  • Pasting the data from your copy of the deposit-data.json in the submitter

    

  • Copy the transaction data field shown below to e.g. https://text-compare.com/

    

  • In your Safe, copy the result for Data (hex encoded) for your cluster and

  • If the data matches, message in your cluster thread that you confirm it matches, then confirm the transaction in the Safe.

  • 5 independent parties of the cluster should confirm via their cluster thread that the keys submitted to the Lido registry match those in their depsoit data file before the transaction is executed by the cluster coordinator.

Please state when the two steps above have been completed in your Discord thread and await confirmation from the Lido team. Please tag @kimonsh and @perrier.

• Following a review that the key has been correctly submitted, the Simple DVT Module Committee will increase the clusters limit to 5 validators.
• The Lido and Obol teams will continue monitoring the performance of the cluster as the validators come online. Use the Grafana client to check if your node and the whole cluster are healthy.

Claiming Rewards

Exiting Validators

No action is required from operators to exit their validators. When starting their node stack, the dv-exit package will send the partial exit for that peer to the Obol sidecar where it will be stored and aggregated into a full signature when a threshold of peers do the same, ready to be served by Lido’s ejector when requested.

Resources

Simple DVT Splitters

0xF0179dEC45a37423EAD4FaD5fCb136197872EAd9