🦏
ETH Home Staking Collection
DVT Home Staking Curriculum
DVT Home Staking Curriculum
  • The DVT Home Staking Curriculum
  • Curriculum breakdown & timeline
  • Understanding ETH validators
    • Introduction to ETH Validators
    • Roles & Responsibilities of a node operator
    • Rewards and penalties
    • Importance of client diversity
    • Distributed Validator Technologies (DVTs)
    • Economics of using DVTs (WIP)
      • Diva Staking (WIP)
      • Obol (WIP)
      • SSV (WIP)
    • Bonded Validators
    • Economics of bonded validators (WIP)
  • Hardware & systems setup
    • Setup Overview
    • Hardware & system requirements
    • Procuring your hardware
    • Assemble your hardware
    • Practicing for free on Cloud VMs
      • Google Cloud
      • Alibaba Cloud
  • Linux OS, Networking, & Security
    • Install and prepare the OS
    • Networking & network security
    • Device level security setup
    • Verifying checksums
  • Installing & configuring your EL+CL clients
    • Set up and configure execution layer client
      • Nethermind
      • Besu
      • Geth
      • Erigon
      • Reth
    • Set up and configure consensus layer client
      • Teku BN
      • Nimbus BN
      • Lodestar BN
      • Lighthouse BN
      • Prysm BN
  • Keystore generation & MEV-Boost
    • Validator key generation
    • Set up and configure MEV-boost
  • Native Solo Staking Setup
    • Validator client setup
      • Teku VC
      • Nimbus VC
      • Lodestar VC
      • Lighthouse VC
      • Prysm VC
    • Depositing 32 ETH into your validator
    • Exiting your validator
  • Monitoring, Maintenance, and Updates
    • Set up monitoring suite
      • Installing & configuring Prometheus
      • Installing & configuring Node Exporter
      • Installing & configuring Grafana
      • Beaconcha.in App API
      • Client Uptime Check
    • Maintenance & Updates
      • Nethermind
      • Besu
      • Teku
      • Nimbus
      • Lodestar
      • Updating the monitoring suite
      • Preparing for Pectra
  • DVT Setup
    • Diva Staking
      • Diva Staking client setup
        • Default - All-in-one setup
        • Advanced - with standalone Lodestar VC
      • Registering your Diva node
      • Updating your Diva client
      • Monitoring your Diva Node
    • Obol
      • Techne Bronze Speedrun (Launchpad)
      • Obol + Bonded Validators (Techne Silver)
        • Obol + Lido CSM
    • SSV
      • SSV + Lido CSM (WIP)
      • SSV Operator
      • SSV Staker
  • Bonded Validators Setup
    • Lido CSM
      • Generating CSM keystores
      • Set Fee Recipient Address
        • Method 1: Configure on validator keys
        • Method 2: Configure on separate validator client
        • Verifying Fee Recipient Registered on MEV Relays
      • Upload/Remove/View validator keys
      • Rewards & bonds
      • Exiting CSM validators
        • "Lazy" exits (TESTNET ONLY)
        • Proper Exits
      • Role/Address management
      • Monitoring
      • Automations
        • CSM with ETHPillar
        • CSM with ETH Docker
        • CSM with Dappnode
    • Puffer
      • Non-Enclave: 2 ETH
    • Ether.fi
      • Receive distributed validator keyshares
    • Stader (WIP)
    • Rocketpool (WIP)
  • Liquid Staking Vaults
    • Stakewise V3
  • Mainnet
    • Mainnet Deployment
    • Heroglpyhs (WIP)
  • Best practices
    • Slashing prevention
    • Maximising uptime and performance
    • Optimising security
    • Managing your withdrawal wallet
  • Tips
    • Advanced networking
    • Downloading files from your node
  • Useful resources
    • General resources
    • Holesky Faucets
  • Automation/tools
    • ETHPillar
    • ETH Docker
    • Automated power on/off
      • Wake-on-LAN (WoL)
      • Network UPS Tools (NUT)
    • Validator Healthcheck Alerts
  • Solo Stakers Guild
    • Lido CSM+SSV+Obol (Testnet)
Powered by GitBook
On this page
  • Upload keys
  • Remove keys
  • View keys
  1. Bonded Validators Setup
  2. Lido CSM

Upload/Remove/View validator keys

PreviousVerifying Fee Recipient Registered on MEV RelaysNextRewards & bonds

Last updated 2 months ago

Upload keys

  • Go to the Lido CSM Widget and connect your wallet. MAKE SURE THAT YOU ARE ON THE CORRECT NETWORK (i.e., Holesky or Mainnet).

    • Mainnet:

    • Holesky:

  • Select Become a Node Operator and then Create a Node Operator

  • On the Lido CSM Widget, upload your deposit data file and select the corresponding bond type (ETH, stETH, wstETH), and provide the desired bond amount

Print the contents of the deposit_data.json file on your node machine, then copy & paste the contents into CSM Widget directly.

  • Identify the actual file name of your deposit_data.json file on your node

ls ~/validator_keys
  • Print the contents:

sudo cat ~/validator_keys/deposit_data-<timestamp>.json
#replace <timestamp> with the actual numbers in your file name

Transfer the deposit_data-<timestamp>.json file from the USB used in the validator key generation step onto your working device (e.g., laptop with Metamask), then upload the file.

  • Finally, select Submit, sign the transaction with your connected wallet, and you are all set.

DO NOT DEPOSIT 32 ETH using the deposit data file generated this way as the Lido CSM will make the deposit for you. Doing so will result in a loss of funds.

Remove keys

The Node Operator can delete uploaded keys voluntarily (e.g., duplicate keys) if it has not been deposited yet.

A fee is confiscated from the Node Operator's bond on each deleted key to cover maximal possible operational costs associated with the queue processing. Keys (via the deposit data file) can be deleted in continuous batches (e.g., from index 5 to 10).

  • Go to the Lido CSM Widget, under the KEYS header

  • Select the REMOVE tab on the widget

  • Select the keys you want to remove--

Once your keys have been removed, the associated bond amounts that you deposited earlier will be available for claiming under the Bond & Rewards tab.

Keys that have been deposited cannot be deleted and only can be exited.

View keys

You can also view the status of the keys pertaining to your uploaded deposit data file and take the necessary actions.

Status
What it means
What to do?

Active

Make sure your validator node is online to perform its duties

Depositable

Key is valid and bond is sufficient. Pending deposit from Lido Protocol

Maintain sufficient bond amounts

Exited

Key has been exited

None

Unbonded

Bond is insufficient for this key, which can be Active or otherwise

- Active key: Top up bond or exit key - Non-active key: Top up bond or do nothing

Duplicated

Key has been uploaded twice

Remove duplicate key

Invalid

Uploaded key has an invalid signature

Remove key

Stuck

Exit request for Active Key was not fulfilled within 96 hours

Exit key

Now you just need to wait for the Lido CSM to deposit your validator keys (using your deposit data file). This is a first-in, first-out process so expect a queue when demand is high. More details on this process

More details .

Key has been deposited & is either pending activation or active on the

here
here
beacon chain
https://csm.lido.fi/
https://csm.testnet.fi/