> ## Documentation Index
> Fetch the complete documentation index at: https://docs.optimism.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Execution client configuration

> Configure op-reth as your OP Stack execution client and migrate off end-of-support op-geth.

The execution client provides the EVM runtime and transaction processing for your OP Stack node.

> [!WARNING]
>
> **op-geth has reached end-of-support (2026-05-31) and does not support the now-active Karst hardfork, so op-geth nodes can no longer follow the canonical chain.** Migrate to op-reth, the primary supported execution client. See the [op-geth deprecation notice](https://docs.optimism.io/notices/archive/op-geth-deprecation) for the full migration plan.

> [!NOTE]
>
> Always run your execution client and consensus client in a 1:1 configuration. Don't run multiple execution clients behind one consensus client, or vice versa.

## What a running node needs

The execution client is one of three pieces. Before configuring it, make sure you have:

1. **L1 endpoints** for the settlement layer of the chain you are syncing: an L1 execution RPC endpoint and an L1 Beacon API endpoint. Your consensus client reads batch data and blobs from them.
2. **A consensus client**, also called the rollup node: op-node or kona-node. It derives the canonical chain from L1 and drives the execution client over the Engine API. See [Consensus client configuration](https://docs.optimism.io/node-operators/guides/configuration/consensus-clients.md).
3. **An execution client**, configured below.

## Execution clients

> [tab] op-reth
>
> [op-reth](https://github.com/paradigmxyz/reth) is a Rust-based execution client and the primary supported path for OP Stack nodes going forward. The [Superchain Registry](https://github.com/ethereum-optimism/superchain-registry) chain configurations are compiled into the binary, so registry chains work by name through `--chain` (for example `--chain unichain` or `--chain unichain-sepolia`).
>
> ### Install
>
> Two supported install paths:
>
> * **Docker image**, wired up end to end in [Running a Node With Docker](https://docs.optimism.io/node-operators/tutorials/node-from-docker.md).
> * **From source.** op-reth lives at `rust/op-reth/` inside the Optimism monorepo and builds with Cargo. Follow [Building and running an OP Stack node from source](https://docs.optimism.io/node-operators/tutorials/run-node-from-source.md), which pins op-node and op-reth to the same coordinated release tag.
>
> ### Minimal configuration
>
> ```bash theme={null}
> op-reth node \
>   --chain optimism \
>   --rollup.sequencer https://mainnet-sequencer.optimism.io \
>   --http \
>   --ws \
>   --authrpc.port 9551 \
>   --authrpc.jwtsecret /path/to/jwt.hex
> ```
>
> ### OP Stack specific flags
>
> op-reth's `Rollup` flag group holds the behavior that exists only on OP Stack chains. Two matter to most operators:
>
> * `--rollup.sequencer <uri>` (shown above) is the sequencer endpoint that transactions submitted to this node are forwarded to, since the sequencer is what builds blocks. Aliases: `--rollup.sequencer-http`, `--rollup.sequencer-ws`.
> * `--rollup.disable-tx-pool-gossip` stops the node from gossiping its transaction pool to peers. Omit it on a personal node; set it on a replica you operate as a provider.
>
> The rest of the group covers the interop filter, subblocks, and historical RPC. For the full list with the binary's own descriptions, see the [`op-reth node` flag listing](https://docs.optimism.io/node-operators/op-reth/cli/op-reth/node), and [Understanding the op-reth CLI](https://docs.optimism.io/node-operators/op-reth/cli/overview.md) for how the flag groups fit together.
>
> ### Subblocks
>
> To serve pre-confirmed state from a chain that streams [Subblocks](https://docs.optimism.io/op-stack/features/subblocks.md), point op-reth at the chain's WebSocket stream:
>
> ```bash theme={null}
> op-reth node \
>   --chain optimism \
>   --rollup.sequencer https://mainnet-sequencer.optimism.io \
>   --flashblocks-url wss://op-mainnet-fb-ws-pub.optimism.io/ws \
>   --http \
>   --ws \
>   --authrpc.port 9551 \
>   --authrpc.jwtsecret /path/to/jwt.hex
> ```
>
> The node then answers requests carrying the `pending` block tag from subblock state, executing each subblock's transactions against its own view of the chain. It does not need the stream's `state_root`, which subblocks leave zeroed. The flag keeps its `flashblocks` spelling; `--websocket-url` is an accepted alias.
>
> `--flashblocks-url` on its own is what an ordinary node wants. Leave `--flashblock-consensus` unset: it drives the chain forward from the stream by submitting completed sequences through `engine_newPayload`, which is a specialized topology, not an addition to a normal node following op-node. Enabling it also turns on local state-root computation for the last subblock in each sequence, which an ordinary node has no use for.
>
> ### Historical proofs
>
> Permissionless chains need \~28 days of historical state for withdrawal proving. Follow the [Running op-reth with Historical Proofs](https://docs.optimism.io/node-operators/tutorials/reth-historical-proofs.md) tutorial to set up the `--proofs-history` (v2) store on op-reth v2.2.3 or later.
>
> ### Pruning
>
> op-reth defaults to an archive node. To reclaim disk, prune the state and receipt segments and keep block bodies. Body pruning is unsupported: op-reth rejects `--minimal` at startup, and `--prune.bodies.distance` is advised against. See [Pruning op-reth](https://docs.optimism.io/node-operators/guides/management/archive-node.md#pruning-op-reth).
>
> ### Complete reference
>
> * [op-reth configuration reference](https://docs.optimism.io/node-operators/reference/op-reth-config.md)
> * [op-reth historical proof configuration](https://docs.optimism.io/node-operators/reference/op-reth-historical-proof-config.md)
> * [reth.rs documentation](https://reth.rs/run/opstack)

> [tab] Nethermind
>
> [Nethermind](https://github.com/NethermindEth/nethermind) is a .NET-based alternative execution client.
>
> ### Minimal configuration
>
> ```bash theme={null}
> nethermind \
>   -c op-mainnet \
>   --data-dir path/to/data/dir \
>   --jsonrpc-jwtsecretfile path/to/jwt.hex
> ```
>
> ### Additional resources
>
> * [Nethermind OP Stack documentation](https://docs.nethermind.io/get-started/running-node/l2-networks)
> * [Nethermind configuration reference](https://docs.nethermind.io/fundamentals/configuration)

## JWT secret

The execution client and consensus client communicate over the Engine API using a shared JWT secret:

```bash theme={null}
openssl rand -hex 32 > jwt-secret.txt
```

This file must be identical for both your execution client and your consensus client.

## op-geth (legacy, end of support 2026-05-31)

> [!WARNING]
>
> **op-geth has reached end-of-support (2026-05-31) and does not support the now-active Karst hardfork, so op-geth nodes can no longer follow the canonical chain.** Migrate to op-reth, the primary supported execution client. See the [op-geth deprecation notice](https://docs.optimism.io/notices/archive/op-geth-deprecation) for the full migration plan.

> [accordion] op-geth configuration (legacy)
>
> [op-geth](https://github.com/ethereum-optimism/op-geth) is a minimal fork of go-ethereum optimized for the OP Stack.
>
> > [!NOTE]
> >
> > Although the Docker image is called `op-geth`, the actual binary is still named `geth` to minimize differences from go-ethereum. See the [op-geth diff viewer](https://op-geth.optimism.io/?utm_source=op-docs\&utm_medium=docs) for details.
>
> ### Minimal configuration
>
> ```bash theme={null}
> geth \
>   --datadir=/data/optimism \
>   --http \
>   --http.addr=0.0.0.0 \
>   --http.port=8545 \
>   --http.api=eth,net,web3 \
>   --authrpc.jwtsecret=/path/to/jwt-secret.txt \
>   --op-network=op-mainnet \
>   --rollup.sequencerhttp=https://mainnet-sequencer.optimism.io/ \
>   --rollup.disabletxpoolgossip
> ```
>
> Defaults: snap sync mode, no WebSocket server, no metrics.
>
> ### OP Stack specific flags
>
> * `--rollup.sequencerhttp`: HTTP endpoint of the sequencer for transaction submission
> * `--rollup.disabletxpoolgossip`: Disables transaction pool gossip (for replica nodes)
> * `--rollup.historicalrpc`: Enables historical RPC endpoint for upgraded networks (OP Mainnet pre-bedrock archive nodes)
>
> ### Complete reference
>
> The op-geth configuration reference has been retired; see the [op-reth configuration reference](https://docs.optimism.io/node-operators/reference/op-reth-config.md) for the equivalent op-reth flags.
