# Generating CSM keystores

## Pre-flight checks for existing solo stakers

1. Make sure that you have the mnemonic (24-word seed phrase) of your existing validator keys in case you overwrite them by mistake while going through this process
2. Make sure you have removed duplicates of your existing solo staking validator keys on the `$HOME` directory of your node machine. Otherwise, remove them now.

```sh
# on your node machine
sudo rm -r ~/validator_keys
```

{% hint style="info" %}
This is to reduce the risk of importing your existing solo staking keystores by mistake into your CSM validator client, which can lead to slashing.&#x20;
{% endhint %}

## Generate CSM keystores

Visit the Validator key generation page and follow the steps accordingly to generate CSM-valid validator keystores.&#x20;

{% content-ref url="/pages/xKRzukcuy2WXF2GE7amh" %}
[Validator key generation](/keystore-generation-and-mev-boost/validator-key-generation.md)
{% endcontent-ref %}

{% hint style="info" %}
Recall that the steps for both native solo staking and CSM are the same except for the requirement to use a specific`withdrawal_address` of the `Lido Withdrawal Vault.`

* **Mainnet:** [`0xB9D7934878B5FB9610B3fE8A5e441e8fad7E293f`](https://etherscan.io/address/0xb9d7934878b5fb9610b3fe8a5e441e8fad7e293f)
* **Hoodi:** [`0x4473dCDDbf77679A643BdB654dbd86D67F8d32f2`](https://hoodi.cloud.blockscout.com/address/0x4473dCDDbf77679A643BdB654dbd86D67F8d32f2)&#x20;
  {% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dvt-homestaker.stakesaurus.com/bonded-validators-setup/lido-csm/generating-csm-keystores.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
