Skip to content

Commit

Permalink
Revise OP Stack docs
Browse files Browse the repository at this point in the history
  • Loading branch information
rubo committed Oct 8, 2024
1 parent 70de260 commit 42022a6
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/get-started/running-node/l2-networks.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ sidebar_position: 2
An Optimism node [consists of two nodes](https://docs.optimism.io/builders/node-operators/architecture): op-node, a rollup node, analogous to a consensus client in Ethereum, paired with a Layer 2 (L2) execution client, and a Layer 1 (L1) node of a pair of execution and consensus clients.

:::info Before you begin
- Running the OP stack requires running two instances of Nethermind—one for the L1 node and another for the L2 node, replacing op-geth.
- Running the OP stack requires access to an 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, replacing op-geth.
- Depending on which OP Stack network you want to run on, the L1 node must be configured respectively. For instance, for OP Mainnet, the L1 node must run on Ethereum Mainnet. For OP Sepolia, on Sepolia.
- Ensure your L1 node is up and running on the respective network before running the OP Stack. See [Running a node on Ethereum](running-node.md#ethereum).
:::
Expand Down

0 comments on commit 42022a6

Please sign in to comment.