> For the complete documentation index, see [llms.txt](https://docs.slingnode.com/slingnode.ethereum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slingnode.com/slingnode.ethereum/readme/supported-clients.md).

# Supported clients

Supported execution clients:

* Geth
* Nethermind
* Besu
* Erigon

Supported consensus clients: 

* Lighthouse
* Prysm
* Teku
* Nimbus (checkpoint sync currently not supported)
* Lodestar

Supported validator clients: 

* Lighthouse
* Prysm
* Teku
* Nimbus\*
* Lodestar

### Managing validators

slingnode.ethereum enables deployment of the validator clients but doesn't include feature to perform validator management tasks such as:

* importing keys
* exporting/importing slashing protection database

Those can be accomplished using a [separate role - slingnode.ethereum\_node\_mgmt. ](https://slingnode.gitbook.io/slingnode.ethereum_node_mgmt/)

Alternatively, the [Ethereum keymanager API](< https://ethereum.github.io/keymanager-APIs/>) can be used to handle those tasks. Validator API are disabled by default, refer to [Enabling Validator Client API](/slingnode.ethereum/enabling-validator-client-api.md) for the guide on how to deploy the validator clients with the API enabled and accessible.

#### Why two separate roles?&#x20;

The roles were separated in order to preserve separation of concerns. The roles can be thought of as follows:&#x20;

* slingnode.ethereum is a configuration and deployment role
* slingnode.ethereum\_node\_mgmt is a management role&#x20;

Combining both together would make them overly complicated and more difficult to understand. We like keeping it simple.&#x20;