ethereum-optimism · sbvegan · Nov 21, 2025 · Nov 21, 2025 · Nov 21, 2025
@@ -3,9 +3,9 @@ title: Chain Operator Configurations
 description: Learn how to configure an OP Stack chain.
 ---
 
-OP Stack chains can be configured for the Chain Operator's needs. Each  
-component of the stack has its own considerations. See the following for 
-documentation for details on configuring each piece.
+OP Stack chains can be configured for the Chain Operator's needs. 
+Each component of the stack has its own considerations. 
+See the following for documentation for details on configuring each piece.
 
 <Steps>
 

@@ -3,12 +3,9 @@
 description: Learn about the OP Stack rollup deployment configurations.
 ---
 
-New OP Stack blockchains are currently configured with a deployment 
-configuration JSON file inside that is passed into the smart contract 
-[deployment script](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/scripts/deploy/Deploy.s.sol).
-You can see example deployment configuration files in the
-[deploy-config directory](https://github.com/ethereum-optimism/optimism/tree/develop/packages/contracts-bedrock/deploy-config).
-This document highlights the deployment configurations and their values.
+<Warning>
+    This documentation is out of date.
+</Warning>
 
 <Info>
   The Rollup configuration is an active work in progress and will likely evolve
@@ -1106,7 +1103,7 @@

 ***

 #### enableGovernance

 EnableGovernance determines whether to include governance token predeploy.


@@ -3,11 +3,8 @@ title: Using Blobs
 description: Learn how to switch to using blobs for your chain.
 ---
 
-This guide walks you through how to switch to using blobs for your chain after Ecotone is activated.
-
-<Info>
-  This guide is intended for chains already upgraded to Ecotone.
-</Info>
+This guide walks you through how to switch to using blobs for your chain. 
+This feature was introduced in with the Ecotone network upgrade.
 
 ## Switch to using blobs
 

@@ -3,10 +3,6 @@
 description: A guide for chain operators on managing private keys on their chain, covering hot and cold wallets, and the use of an HSM.
 ---
 
-
-
-# Managing your keys
-
 This guide informs chain operators on important key management considerations. 
 There are certain [privileged roles](/op-stack/protocol/privileged-roles) that 
 need careful consideration. The privileged roles are categorized as hot wallets
@@ -33,9 +29,9 @@
 ## Cold wallets 

 The addresses for the cold wallets cannot be used without human intervention. 
 These can be set up as multisig contracts, so they can be controlled by groups 
 of community members and avoid a single point of failure. The signers behind a
 multisig should probably also use a hardware wallet. 

 <Info>
  Refer to the [privileged roles](/op-stack/protocol/privileged-roles) documentation

@@ -3,9 +3,6 @@ title: Troubleshooting chain operations
 description: Learn solutions to common problems when troubleshooting chain operations.
 ---
 
-
-# Troubleshooting: chain operations
-
 This page lists common troubleshooting scenarios and solutions for chain operators.
 
 ## EvmError in contract deployment

@@ -1,12 +1,8 @@
 ---
-title: Block explorer
-description: Learn how to deploy a Blockscout block explorer for your OP Stack chain.
+title: Blockscout block explorer
+description: Blockscout an open source block explorer for the OP Stack.
 ---
 
-
-
-# Deploying a block explorer
-
 [Blockscout](https://www.blockscout.com/) is an open source block explorer that supports OP Stack chains.
 Keep reading for a quick overview on how to deploy Blockscout for your OP Stack chain.
 

@@ -1,5 +1,5 @@
 ---
-title: Conductor
+title: OP Conductor
 description: Learn what the op-conductor is and how to use it to create a highly available and reliable sequencer.
 ---
 
@@ -75,7 +75,7 @@

 ## Setup

 At OP Labs, op-conductor is deployed as a kubernetes statefulset because it
 requires a persistent volume to store the raft log. This guide describes
 setting up conductor on an existing network without incurring downtime.

@@ -86,7 +86,7 @@
 This setup guide has the following assumptions:

 *   3 deployed sequencers (sequencer-0, sequencer-1, sequencer-2) that are all
    in sync and in the same vpc network
 *   sequencer-0 is currently the active sequencer
 *   You can execute a blue/green style sequencer deployment workflow that
    involves no downtime (described below)
@@ -353,7 +353,7 @@
 #### --paused (`PAUSED`)

 <Info>
  There is no configuration state, so if you unpause via RPC and then restart,
  it will start paused again.
 </Info>

@@ -370,9 +370,9 @@
 ### RPCs

 Conductor exposes [admin RPCs](https://github.com/ethereum-optimism/optimism/blob/develop/op-conductor/rpc/api.go#L17)
 on the `conductor` namespace.

 #### conductor_overrideLeader

 `OverrideLeader` is used to override the leader status, this is only used to
 return true for `Leader()` & `LeaderWithID()` calls. It does not impact the
@@ -397,7 +397,7 @@
  </Tabs.Tab>
 </Tabs>

 #### conductor_pause

 `Pause` pauses op-conductor.

@@ -417,7 +417,7 @@
  </Tabs.Tab>
 </Tabs>

 #### conductor_resume

 `Resume` resumes op-conductor.

@@ -437,7 +437,7 @@
  </Tabs.Tab>
 </Tabs>

 #### conductor_paused

 Paused returns true if the op-conductor is paused.

@@ -457,7 +457,7 @@
  </Tabs.Tab>
 </Tabs>

 #### conductor_stopped

 Stopped returns true if the op-conductor is stopped.

@@ -485,7 +485,7 @@
  <Tabs.Tab>
    ```sh
    curl -X POST -H "Content-Type: application/json" --data \
        '{"jsonrpc":"2.0","method":"conductor_sequencerHealthy","params":[],"id":1}'  \
        http://127.0.0.1:8547
    ```
  </Tabs.Tab>
@@ -497,7 +497,7 @@
  </Tabs.Tab>
 </Tabs>

 #### conductor_leader

 <Info>
  API related to consensus.
@@ -594,7 +594,7 @@
  </Tabs.Tab>
 </Tabs>

 #### conductor_removeServer

 <Info>
  API related to consensus.
@@ -618,7 +618,7 @@
  </Tabs.Tab>
 </Tabs>

 #### conductor_transferLeader

 <Info>
  API related to consensus.
@@ -686,7 +686,7 @@
  </Tabs.Tab>
 </Tabs>

 #### conductor_active

 <Info>
  API called by `op-node`.

@@ -1,5 +1,5 @@
 ---
-title: Deployer
+title: OP Deployer
 description: Learn how op-deployer can simplify deploying a standard OP Stack Chain.
 ---
 
@@ -46,7 +46,7 @@
 ## Deployment usage

 <Info>
  Deploying an OP Stack chain involves deploying multiple contracts, which can consume a substantial amount of gas. On testnets like Sepolia, costs may fluctuate significantly depending on network congestion. We recommend ensuring your deployer wallet has a buffer of **at least 1.5 to  3.5 ETH** , depending on gas prices and configuration. Always check current gas estimates before deploying.
 </Info>

 The base use case for `op-deployer` is deploying new OP Chains. This process is broken down into three steps:
@@ -70,7 +70,7 @@
 ```

 *   Replace `<l2-chain-id>` with the exact value.
 *   The `--workdir` flag specifies the output directory for the generated intent file and related configs. You can name this directory anything you like , `.deployer` is just an example.

 This command will create a directory called `.deployer` in your current working directory containing the intent file and an empty `state.json` file. `state.json` is populated with the results of your deployment, and never needs to be edited directly.

@@ -131,7 +131,7 @@
 *   **l2ProxyAdminOwner**
 *   **systemConfigOwner**

 HSMs (hardware security modules) are recommended for the following hot-wallets:

 *   **unsafeBlockSigner**
 *   **batcher**
@@ -225,7 +225,7 @@
 *   `http://` or `https://` - Points to a target directory containing contract artifacts. The URL should directly reference the directory containing the `forge-artifacts` directory, in this case, the bytecode will be downloaded from the URL specified.

 <Info>
  When using any scheme other than tag://, you must set configType to either custom or standard-overrides in your intent file.
 </Info>

 For example:
@@ -269,7 +269,7 @@

 Superchain configuration will be set to the Superchain-wide defaults - i.e., your chain will be opted into the [Superchain pause](https://specs.optimism.io/protocol/superchain-config.html#pausability) and will use the same [protocol versions](https://github.com/ethereum-optimism/specs/blob/main/specs/protocol/superchain-upgrades.md) address as other chains on the Superchain.
 You will need to specify additional arguments depending on what you're trying to do.
 See below for a reference of each supported CLI arg:

 *   Deployment targets:

@@ -277,7 +277,7 @@

    *   `live`: Deploys directly to a live L1 network. Requires `-l1-rpc-url` and `-private-key`.
    *   `genesis`: Generates an L1 genesis file for local testing or development.
    *   `calldata`: Produces calldata for multisig wallets, enabling offline deployment.
    *   `noop`: Performs a dry-run without actual deployment, useful for testing configurations.

    Choose the deployment target that best fits your use case.
@@ -331,7 +331,7 @@
 op-deployer inspect rollup --workdir .deployer <l2-chain-id> > .deployer/rollup.json
 ```

 Now that you have your `genesis.json` and `rollup.json` you can spin up a node on your network. You can also use the following inspect subcommands to get additional chain artifacts:

 ```bash
 op-deployer inspect l1 --workdir .deployer <l2-chain-id># outputs all L1 contract addresses for an L2 chain
@@ -364,7 +364,7 @@

 ### Bootstrap proxy

 The `bootstrap proxy` command deploys a new `ERC-1967` proxy admin, which is required for upgradeability of the superchain contracts.

 **Command usage**

@@ -441,7 +441,7 @@
 | --paused                       | Whether the superchain starts paused                                                                                                              | No (defaults to false)  | false                                                                                    |
 | --required-protocol-version    | Minimum required protocol version address                                                                                                         | No                      | 1.0.0                                                                                    |
 | --recommended-protocol-version | Recommended protocol version                                                                                                                      | No                      | 1.0.0                                                                                    |
 | --outfile                      | File to write output JSON                                                                                                                         | No (defaults to stdout) | superchain-output.json                                                                   |
 | --cache-dir                    | Directory to cache artifacts                                                                                                                      | No                      | .artifacts-cache                                                                         |

 **Example:**
@@ -504,7 +504,7 @@
 | --protocol-versions-proxy             | Address of protocol versions proxy               | Yes      | -                    | Result from superchain command                                                           |
 | --upgrade-controller                  | Address of upgrade controller                    | Yes      | -                    | 0x0000...0000                                                                            |
 | --use-interop                         | Whether to enable interoperability features      | No       | false                | true                                                                                     |
 | --outfile                             | File to write output JSON                        | No       | stdout               | implementations-output.json                                                              |
 | --cache-dir                           | Directory to cache artifacts                     | No       | -                    | .artifacts-cache                                                                         |

 ### Understanding MIPS version

@@ -1,6 +1,6 @@
 ---
-title: op-txproxy
+title: OP Txproxy
 description: A passthrough proxy service that can apply additional constraints on transactions prior to reaching the sequencer.
 ---
 
 A [passthrough proxy](https://github.com/ethereum-optimism/infra/tree/main/op-txproxy) for the execution engine endpoint. This proxy does not forward all RPC traffic and only exposes a specific set of methods. Operationally, the ingress router should only re-route requests for these specific methods.
@@ -21,7 +21,7 @@

 `--sendRawTxConditional.enabled (default: true) ($OP_TXPROXY_SENDRAWTXCONDITIONAL_ENABLED)`

 When disabled, requests will fail with the `-32003` (transaction rejected) json rpc error code with a message stating that the method is disabled.
 #### Rate limits

 Even though the op-geth implementation of this endpoint includes rate limits, it is instead applied here to terminate these requests early.
@@ -35,7 +35,7 @@
 *   Transaction targets are only 4337 Entrypoint contracts

 <Info>
  The motivating factor for this endpoint is to enable permissionless 4337 mempools, hence the restricted usage of this method to just [Entrypoint](https://github.com/eth-infinitism/account-abstraction/blob/develop/contracts/core/EntryPoint.sol) transactions.

  Please open up an issue if you'd like this restriction to be optional via configuration to broaden usage of this endpoint.
 </Info>
@@ -45,7 +45,7 @@
 `--sendRawTxConditional.backend ($OP_TXPROXY_SENDRAWTXCONDITIONAL_BACKENDS)`

 <Info>
  Per the [specification](/op-stack/features/send-raw-transaction-conditional), conditional transactions are not gossiped between peers. Thus, if you use replicas in an active/passive sequencer setup, this request must be broadcasted to all replicas.

  [proxyd](./proxyd) as an egress router for this method supports this broadcasting functionality.
 </Info>

@@ -1,5 +1,5 @@
 ---
-title: op-validator
+title: OP Validator
 description: Learn how to use op-validator to validate chain configurations and deployments.
 ---
 
@@ -65,7 +65,7 @@

 ## Usage

 The validator supports different protocol versions through subcommands:

 ```bash
 op-validator validate [version] [flags]

@@ -1031,7 +1031,7 @@
     },
     {
       "source": "/operators/chain-operators/management/snap-sync",
-      "destination": "/chain-operators/guides/management/snap-sync"
+      "destination": "/chain-operators/guides/features/snap-sync"
     },
     {
       "source": "/operators/chain-operators/management/troubleshooting",
@@ -1696,6 +1696,22 @@
     {
       "source": "/chain-operators/reference/privileged-roles",
       "destination": "/op-stack/protocol/privileged-roles"
+    },
+    {
+      "source": "chain-operators/guides/management/blobs",
+      "destination": "chain-operators/guides/features/blobs"
+    },
+    {
+      "source": "chain-operators/guides/management/snap-sync",
+      "destination": "chain-operators/guides/features/snap-sync"
+    },
+    {
+      "source": "/chain-operators/tools/fee-calculator",
+      "destination": "/op-stack/transactions/fees"
+    },
+    {
+      "source": "/chain-operators/tools/op-challenger",
+      "destination": "chain-operators/guides/configuration/op-challenger-config-guide"
     }
   ],
   "navigation": {
@@ -1719,7 +1735,8 @@
                   "chain-operators/guides/configuration/getting-started",
                   "chain-operators/guides/configuration/batcher",
                   "chain-operators/guides/configuration/proposer",
-                  "chain-operators/guides/configuration/rollup"
+                  "chain-operators/guides/configuration/rollup",
+                  "chain-operators/guides/configuration/op-challenger-config-guide"
                 ]
               },
               {
@@ -1740,17 +1757,17 @@
                   "chain-operators/guides/features/setting-min-base-fee",
                   "chain-operators/guides/features/setting-da-footprint",
                   "chain-operators/guides/features/flashblocks-guide",
-                  "chain-operators/guides/features/alt-da-mode-guide"
+                  "chain-operators/guides/features/alt-da-mode-guide",
+                  "chain-operators/guides/features/blobs",
+                  "chain-operators/guides/features/snap-sync"
                 ]
               },
               {
                 "group": "Management",
                 "pages": [
                   "chain-operators/guides/management/best-practices",
-                  "chain-operators/guides/management/blobs",
                   "chain-operators/guides/management/key-management",
                   "chain-operators/guides/management/operations",
-                  "chain-operators/guides/management/snap-sync",
                   "chain-operators/guides/management/troubleshooting"
                 ]
               }
@@ -1793,7 +1810,6 @@
             "pages": [
               "chain-operators/tools/chain-monitoring",
               "chain-operators/tools/explorer",
-              "chain-operators/tools/fee-calculator",
               "chain-operators/tools/op-challenger",
               "chain-operators/tools/op-conductor",
               "chain-operators/tools/op-deployer",