Configure an execution node for Prysm

Looking for an end-to-end guide?

If you're looking for end-to-end configuration guidance, refer to our Quickstart.

Select a configuration

If you're looking for the simplest configuration, select Geth and IPC:

Operating system:
Linux, MacOS, Arm64
Windows

Network:
Mainnet
Sepolia
Holesky

Execution client:
Geth
Nethermind
Besu

EN-BN connection:
HTTP-JWT
IPC

Execution client:
Nethermind
Besu
Geth

Download the latest stable release of Nethermind for your operating system from the Nethermind downloads page.

Extract the contents into your execution folder. Run the following command to start your execution node by replacing <PATH_TO_JWT_FILE> by the path to the JWT file generated during the previous step:

Extract the contents into your execution folder. Run the following command to start your execution by replacing <PATH_TO_IPC_FILE> by any empty path on your file system. The execution layer client will create an IPC file at this location:

Windows
Linux, MacOS, Arm64

Mainnet
Sepolia
Holesky

nethermind --config mainnet --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true --JsonRpc.JwtSecretFile=<PATH_TO_JWT_FILE>

nethermind --config mainnet --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true --JsonRpc.IpcUnixDomainSocketPath=<PATH_TO_IPC_FILE>

nethermind --config sepolia --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true--JsonRpc.JwtSecretFile=<PATH_TO_JWT_FILE&gt

nethermind --config sepolia --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true --JsonRpc.IpcUnixDomainSocketPath=<PATH_TO_IPC_FILE>

nethermind --config holesky --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true--JsonRpc.JwtSecretFile=<PATH_TO_JWT_FILE>

nethermind --config holesky --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true --JsonRpc.IpcUnixDomainSocketPath=/path/to/<your.ipc>

Mainnet
Sepolia
Holesky

./nethermind --config mainnet --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true --JsonRpc.JwtSecretFile=<PATH_TO_JWT_FILE>

./nethermind --config mainnet --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true --JsonRpc.IpcUnixDomainSocketPath=<PATH_TO_IPC_FILE>

./nethermind --config sepolia --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true--JsonRpc.JwtSecretFile=<PATH_TO_JWT_FILE&gt

./nethermind --config sepolia --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true --JsonRpc.IpcUnixDomainSocketPath=<PATH_TO_IPC_FILE>

./nethermind --config holesky --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true--JsonRpc.JwtSecretFile=<PATH_TO_JWT_FILE>

./nethermind --config holesky --JsonRpc.Enabled true --HealthChecks.Enabled true --HealthChecks.UIEnabled true --JsonRpc.IpcUnixDomainSocketPath=/path/to/<your.ipc>

See Nethermind's command-line options for parameter definitions.

Ensure that the latest 64-bit version of the Java JDK is installed. Download the latest stable release of Besu from the Besu releases page. OS-specific instructions are available on Besu's binary installation page.

Run the following command to start your execution node replacing <PATH_TO_JWT_FILE> by the path to the JWT file generated during the previous step:

Mainnet
Sepolia
Holesky

besu --network=mainnet --rpc-http-enabled --engine-jwt-enabled=true --engine-jwt-secret=<PATH_TO_JWT_FILE> --engine-host-allowlist="*"

besu --network=sepolia --rpc-http-enabled --engine-jwt-enabled=true --engine-jwt-secret=<PATH_TO_JWT_FILE> --engine-host-allowlist="*"

besu --network=holesky --rpc-http-enabled --engine-jwt-enabled=true --engine-jwt-secret=<PATH_TO_JWT_FILE> --engine-host-allowlist="*"

See Besu's command-line options for parameter definitions.

Download and run the latest 64-bit stable release of Geth for your operating system from the Geth downloads page.

Move the geth executable into your execution directory.

Navigate to your execution directory and run the following command to start your execution node by replacing <PATH_TO_JWT_FILE> by the path to the JWT file generated during the previous step:

Navigate to your execution directory and run the following command to start your execution node by replacing <PATH_TO_IPC_FILE> by any empty path on your file system. The execution layer client will create an IPC file at this location:

Windows
Linux, MacOS, Arm64

Mainnet
Sepolia
Holesky

geth --mainnet --http --http.api eth,net,engine,admin --authrpc.jwtsecret=<PATH_TO_JWT_FILE>

geth --mainnet --http --http.api eth,net,engine,admin --ipcpath=<PATH_TO_IPC_FILE>

geth --sepolia --http --http.api eth,net,engine,admin --authrpc.jwtsecret=<PATH_TO_JWT_FILE>

geth --sepolia --http --http.api eth,net,engine,admin --ipcpath=<PATH_TO_IPC_FILE>

geth --holesky --http --http.api eth,net,engine,admin --authrpc.jwtsecret=<PATH_TO_JWT_FILE>

geth --holesky --http --http.api eth,net,engine,admin --ipcpath=<PATH_TO_IPC_FILE>

Mainnet
Sepolia
Holesky

./geth --mainnet --http --http.api eth,net,engine,admin --authrpc.jwtsecret=<PATH_TO_JWT_FILE>

./geth --mainnet --http --http.api eth,net,engine,admin --ipcpath=<PATH_TO_IPC_FILE>

./geth --sepolia --http --http.api eth,net,engine,admin --authrpc.jwtsecret=<PATH_TO_JWT_FILE>

./geth --sepolia --http --http.api eth,net,engine,admin --ipcpath=<PATH_TO_IPC_FILE>

./geth --holesky --http --http.api eth,net,engine,admin --authrpc.jwtsecret=<PATH_TO_JWT_FILE>

./geth --holesky --http --http.api eth,net,engine,admin --ipcpath=<PATH_TO_IPC_FILE>

The execution layer client cannot sync without an attached beacon node. We'll see how to setup a beacon node in the next step.

Congratulations - you’re now running an execution node that your Prysm beacon node can connect to.

Select a configuration​

Select a configuration