Layer 2 networks

Before you begin

• Running a Layer 2 (L2) node requires access to a Layer (L1) node—either on-premises or an external RPC provider. If you also plan to run an L1 node with Nethermind, note that you will need two Nethermind instances—one for the L1 node and another for the L2 node.
• If both the L1 and L2 nodes run on the same machine, ensure they use different ports and data directories.

OP Stack

An Optimism node consists of two parts: op-node, a rollup node, analogous to a consensus client in Ethereum paired with an L2 execution client.

Important

Similar to the L1 node, the L2 instance of Nethermind also requires a properly configured Engine API to communicate to op-node.

OP Mainnet

Note

For OP Mainnet, the L1 node must be running on Ethereum Mainnet.

To run Nethermind on the OP Mainnet, use the following command:

nethermind \
  -c op-mainnet \
  --data-dir path/to/data/dir \
  --jsonrpc-jwtsecretfile path/to/jwt.hex

Below is a sample command to run op-node paired with Nethermind, assuming they both are running on the same machine:

export L1_RPC_URL=... # The URL of the L1 node RPC interface
export L1_BEACON_URL=... # The URL of the L1 node Beacon interface

op-node \
  --l1=$L1_RPC_URL \
  --l1.rpckind=standard \
  --l1.beacon=$L1_BEACON_URL \
  --l2=http://localhost:8551 \
  --l2.jwt-secret=path/to/jwt.hex \
  --syncmode=execution-layer \
  --network=op-mainnet

OP Sepolia

Note

For OP Sepolia, the L1 node must be running on Sepolia.

To run Nethermind on the OP Sepolia, use the following command:

nethermind \
  -c op-sepolia \
  --data-dir path/to/data/dir \
  --jsonrpc-jwtsecretfile path/to/jwt.hex

Below is a sample command to run op-node paired with Nethermind, assuming they both are running on the same machine:

export L1_RPC_URL=... # The URL of the L1 node RPC interface
export L1_BEACON_URL=... # The URL of the L1 node Beacon interface

op-node \
  --l1=$L1_RPC_URL \
  --l1.rpckind=standard \
  --l1.beacon=$L1_BEACON_URL \
  --l2=http://localhost:8551 \
  --l2.jwt-secret=path/to/jwt.hex \
  --syncmode=execution-layer \
  --network=op-sepolia

For available settings, see op-node configuration options.

See also

• Run a node in the Superchain

Taiko

A Taiko node consists of two parts: taiko-client, analogous to a consensus client in Ethereum paired with an L2 execution client.

Important

Similar to the L1 node, the L2 instance of Nethermind also requires a properly configured Engine API to communicate to taiko-client.

Taiko Mainnet

Note

For Taiko Mainnet, the L1 node must be running on Ethereum Mainnet.

To run Nethermind on Taiko Mainnet, use the following command:

nethermind \
  -c taiko-mainnet \
  --data-dir path/to/data/dir \
  --jsonrpc-jwtsecretfile path/to/jwt.hex

Below is a sample command to run taiko-client paired with Nethermind, assuming they both are running on the same machine:

export L1_WS_URL=... # The URL of the L1 node WebSocket interface
export L1_BEACON_URL=... # The URL of the L1 node Beacon interface

taiko-client driver \
  --l1.ws $L1_WS_URL \
  --l1.beacon $L1_BEACON_URL \
  --l2.ws ws://localhost:8545 \
  --taikoL1 0x06a9Ab27c7e2255df1815E6CC0168d7755Feb19a \
  --taikoL2 0x1670000000000000000000000000000000010001 \
  --jwtSecret path/to/jwt.hex \
  --l2.auth http://localhost:8551 \
  --verbosity 3 \
  --p2p.sync \
  --p2p.checkPointSyncUrl https://rpc.mainnet.taiko.xyz

Taiko Hekla

Note

For Taiko Hekla, the L1 node must be running on Holesky.

To run Nethermind on Taiko Hekla, use the following command:

nethermind \
  -c taiko-hekla \
  --data-dir path/to/data/dir \
  --jsonrpc-jwtsecretfile path/to/jwt.hex

Below is a sample command to run taiko-client paired with Nethermind, assuming they both are running on the same machine:

export L1_WS_URL=... # The URL of the L1 node WebSocket interface
export L1_BEACON_URL=... # The URL of the L1 node Beacon interface

taiko-client driver \
  --l1.ws $L1_WS_URL \
  --l1.beacon $L1_BEACON_URL \
  --l2.ws ws://localhost:8545 \
  --taikoL1 0x79C9109b764609df928d16fC4a91e9081F7e87DB \
  --taikoL2 0x1670090000000000000000000000000000010001 \
  --jwtSecret path/to/jwt.hex \
  --l2.auth http://localhost:8551 \
  --verbosity 3 \
  --p2p.sync \
  --p2p.checkPointSyncUrl https://rpc.hekla.taiko.xyz

For more information about the taiko-client, see its README.

See also

• Run a Taiko proposer