> 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;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.slingnode.com/slingnode.ethereum/readme/supported-clients.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.