# Client Configuration

Many execution, consensus, and validator clients need custom flags or parameters to work best with Distributed Validators. These settings are often dispersed across a number of documentation pages or example repos. This page aims to be a reference for each client and the specific additions they may require.

## Lighthouse

### Consensus Client

Nothing specific for distributed validators is required. If you are configuring MEV-boost, consult the settings you need [here](https://github.com/ObolNetwork/obol-gitbook/blob/version-v1.3.0/adv/advanced/quickstart-builder-api.mdx#consensus-clients).

### Validator Client

Required flags:

```shell
--distributed
```

## Lodestar

### Consensus Client

Nothing specific for distributed validators is required. If you are configuring MEV-boost, consult the settings you need [here](https://github.com/ObolNetwork/obol-gitbook/blob/version-v1.3.0/adv/advanced/quickstart-builder-api.mdx#consensus-clients).

### Validator Client

Required flags:

```shell
--distributed
```

## Nimbus

### Consensus Client

When running a Nimbus Consensus Client you must add the following flag **to `charon run`**:

```shell
--feature-set-enable=json_requests
```

### Validator Client

Required flags:

```shell
--distributed
```

## Prysm

### Consensus Client

Nothing specific for distributed validators is required. If you are configuring MEV-boost, consult the settings you need [here](https://github.com/ObolNetwork/obol-gitbook/blob/version-v1.3.0/adv/advanced/quickstart-builder-api.mdx#consensus-clients).

### Validator Client

Required flags:

```shell
--distributed
```

## Teku

### Consensus Client

Required flags:

```shell
--validators-graffiti-client-append-format=DISABLED
```

### Validator Client

Required flags:

```shell
--Xobol-dvt-integration-enabled
```


---

# 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://docs.obol.org/docs/advanced-and-troubleshooting/troubleshooting/client_configurations.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.