ethereum-optimism · sbvegan · Nov 6, 2025 · Nov 6, 2025 · Nov 6, 2025
@@ -6,7 +6,7 @@ body:
   - type: markdown
     attributes:
       value: |
-        Before submitting this suggestion, be sure to read our expectations for [troubleshooting content](https://docs.optimism.io/connect/contribute/style-guide#troubleshooting-guides). <br> For an example troubleshooting guide with problem+solution pairs, see [Troubleshooting: L2 Rollup](https://docs.optimism.io/operators/chain-operators/management/troubleshooting).
+        Before submitting this suggestion, be sure to read our expectations for [troubleshooting content](https://docs.optimism.io/connect/contribute/style-guide#troubleshooting-guides). <br> For an example troubleshooting guide with problem+solution pairs, see [Troubleshooting: L2 Rollup](https://docs.optimism.io/chain-operators/guides/troubleshooting).
   - type: markdown
     id: project_info
     attributes:

@@ -16,9 +16,7 @@
 | Environment           | Purpose                                   | Getting Started                                            |
 | --------------------- | ----------------------------------------- | ---------------------------------------------------------- |
 | **Local development** | Rapid iteration and testing with Supersim | [Setup Supersim guide](/app-developers/tutorials/supersim) |
-| **Interop devnet**    | Large-scale testing on testnets           | [Network specs](/interop/tools/devnet)                     |
-
-For complete network details including RPC endpoints, chain IDs, contract addresses, and bridging instructions, see the [Superchain Interop Devnet Documentation](/interop/tools/devnet).
+| **Interop devnet**    | Large-scale testing on testnets           | [Network specs](/app-developers/guides/building-apps)                     |
 
 ## Deploy your app to devnet in minutes
 

@@ -16,7 +16,7 @@ description: Learn how to transfer ETH across the Superchain interop cluster
 
 Crosschain ETH transfers in the Superchain are facilitated through the [SuperchainETHBridge](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/SuperchainETHBridge.sol) contract.
 This tutorial walks through how to send ETH from one chain to another.
-You can do this on [Supersim](/interop/tools/supersim), [the Interop devnet](/interop/tools/devnet), or production once it is released.
+You can do this on [Supersim](/interop/tools/supersim) or production once it is released.
 
 ### What you'll build
 
@@ -61,7 +61,7 @@ The tutorial uses these primary tools:
   </Step>
 
   <Step title="Configure the network">
-  You can run this tutorial either with [Supersim](/interop/tools/supersim) running locally, or using the [Interop devnet](/interop/tools/devnet).
+  You can run this tutorial either with [Supersim](/interop/tools/supersim) running locally, or using the [Interop devnet](/app-developers/guides/building-apps).
     Select the correct tab and follow the directions. 
 
 

@@ -88,7 +88,7 @@ The implementation consists of three main components:
         ./supersim --interop.autorelay
         ```
 
-        If you are using [the devnets](/interop/tools/devnet), just skip this step.
+        If you are using [the devnets](/app-developers/guides/building-apps), just skip this step.
 
         <Tabs items={['Supersim', 'Devnets']}>
             <Tabs.Tab>

@@ -64,7 +64,7 @@
 
         (1) This should be an address you control (for which you know the private key), which has some ETH on the blockchains in question.
         In the case of Supersim, the default has 10k ETH and you can use it.
-        For the devnets, [see here](/interop/tools/devnet#sending-eth-to-the-interop-devnets) to send ETH.
+        For the devnets, [see here](/app-developers/guides/building-appst#sending-eth-to-the-interop-devnets) to send ETH.
 
     4.  If you change `owner_address`, you need to also set the private key.
         Edit `packages/contracts/.env` to set `DEPLOYER_PRIVATE_KEY` to the private key of an account that has ETH on both devnet blockchains.
@@ -87,7 +87,7 @@
 
       <Tabs.Tab>
         The [SuperchainERC20 Starter Kit](/app-developers/starter-kit) is already set up for [Supersim](/interop/tools/supersim).
-        If you want to use it with a different set of blockchains, for example the [Devnets](/interop/tools/devnet), follow these steps.
+        If you want to use it with a different set of blockchains, for example the [Devnets](/app-developers/guides/building-apps), follow these steps.
 
         1.  Edit `packages/contracts/foundry.toml` to add the RPC endpoints (add the bottom two rows).
 
@@ -126,15 +126,15 @@

    ```solidity
 // SPDX-License-Identifier: MIT
 pragma solidity ^0.8.25;

 import {SuperchainERC20} from "./SuperchainERC20.sol";
 import {Ownable} from "@solady/auth/Ownable.sol";

 contract CustomSuperchainToken is SuperchainERC20, Ownable {
    string private _name;
    string private _symbol;
    uint8 private immutable _decimals;

    constructor(address owner_, string memory name_, string memory symbol_, uint8 decimals_) {
        _name = name_;
@@ -274,5 +274,5 @@
 ## Next steps

 *   Use the [SuperchainERC20 Starter Kit](/app-developers/starter-kit) to deploy your token across the Superchain.
 *   If you'd like a guided walkthrough, check out our [tutorial video](https://x.com/i/status/1866095114374045969) instead.
 *   Review the [Superchain Interop Explainer](/interop/explainer) for answers to common questions about interoperability.
@@ -59,7 +59,7 @@ The tutorial uses these primary tools:
 
   <Step title="Prepare for deployment">
   The Starter Kit already deploys a `SuperchainERC20` token to [Supersim](/interop/tools/supersim).
-    Here are the required changes to deploy it to the [Interop devnet](/interop/tools/devnet).
+    Here are the required changes to deploy it to the [Interop devnet](/app-developers/guides/building-apps).
 
     1.  Edit `packages/contracts/foundry.toml` to add the RPC endpoints for the devnet (add the bottom two rows).
 
@@ -98,7 +98,7 @@ The tutorial uses these primary tools:
             | decimals       | Number of decimal places | 18                       |                                            |
 
             (1) This should be an address you control (for which you know the private key), which has some ETH on the devnets.
-            [See here](/interop/tools/devnet#sending-eth-to-the-interop-devnets) to add ETH to the devnets.
+            [See here](/app-developers/guides/building-apps#sending-eth-to-the-interop-devnets) to add ETH to the devnets.
 
         Here is a sample `packages/contracts/configs/deploy-config.toml` file you can use, as long as you update `owner_address`.
 

@@ -24,7 +24,7 @@

 *   **Contracts releases** are tagged under `op-contracts/v<semver>` (e.g. `op-contracts/v1.6.0`) and contain updates to the Bedrock L1 contracts.

 *   **`op-geth` versioning** includes upstream geth's version within its semver. For example, if upstream geth is at `v1.12.0`, an `op-geth` release might be `v1.101200.0`. The geth major version is used as our minor version (left-padded if needed), and the patch version is appended.

 Always consult release notes for additional details or upgrade instructions.

@@ -75,7 +75,7 @@
 GETH_TXPOOL_NOLOCALS: "true"
 ```
 
-For additional information about these flags, check out our [Execution Layer Configuration Options](/operators/node-operators/configuration/execution-config) doc.
+For additional information about these flags, check out our [Execution Layer Configuration Options](/node-operators/guides/execution-config) doc.
 
 ## Write your own runbooks
 

@@ -119,31 +119,31 @@
        "number": 0
      },
      "l2_time": 1691802540,
      "system_config": {
        "batcherAddr": "0x8f23bb38f531600e5d8fddaaec41f13fab46e98c",
        "overhead": "0x00000000000000000000000000000000000000000000000000000000000000bc",
        "scalar": "0x00000000000000000000000000000000000000000000000000000000000a6fe0",
        "gasLimit": 30000000
      }
    },
    "block_time": 2,
    "max_sequencer_drift": 600,
    "seq_window_size": 3600,
    "channel_timeout": 300,
    "l1_chain_id": 11155111,
    "l2_chain_id": 11155420,
    "regolith_time": 0,
    "canyon_time": 1699981200,
    "delta_time": 1703203200,
    "ecotone_time": 1708534800,
    "batch_inbox_address": "0xff00000000000000000000000000000011155420",
    "deposit_contract_address": "0x16fc5058f25648194471939df75cf27a2fdc48bc",
    "l1_system_config_address": "0x034edd2a225f7f429a63e0f1d2084b9e0a93b538",
    "protocol_versions_address": "0x79add5713b383daa0a138d3c4780c7a1804a8090",
    "da_challenge_address": "0x0000000000000000000000000000000000000000",
    "da_challenge_window": 0,
    "da_resolve_window": 0,
    "use_plasma": false
  }
  ```
  </Step>
@@ -207,5 +207,5 @@
 
 ## Next steps
 
-*   See the [Node Configuration](/operators/node-operators/configuration/base-config) guide for additional explanation or customization.
+*   See the [Node Configuration](/node-operators/guides/base-config) guide for additional explanation or customization.
 *   If you experience difficulty at any stage of this process, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions).
@@ -18,15 +18,15 @@ To enable snap sync, chain operators need to spin up a node which is exposed to
 
 <Info>
 For snap sync, all `op-geth` nodes should expose port `30303` TCP and `30303` UDP to easily find other op-geth nodes to sync from. 
-  *   If you set the port with [`--discovery.port`](/operators/node-operators/configuration/execution-config#discoveryport), then you must open the port specified for UDP. 
-  *   If you set [`--port`](/operators/node-operators/configuration/execution-config#port), then you must open the port specified for TCP.
+  *   If you set the port with [`--discovery.port`](/node-operators/guides/execution-config#discoveryport), then you must open the port specified for UDP. 
+  *   If you set [`--port`](/node-operators/guides/execution-config#port), then you must open the port specified for TCP.
   *   The only exception is for sequencers and transaction ingress nodes.
 </Info>
 
 <Steps>
   <Step title="Setup a snap sync node">
   *   Expose port `30303` (`op-geth`'s default discovery port) to the internet on TCP and UDP.
-    *   Disable transaction gossip with the [`--rollup.disabletxpoolgossip`](/operators/node-operators/configuration/execution-config#rollupdisabletxpoolgossip) flag
+    *   Disable transaction gossip with the [`--rollup.disabletxpoolgossip`](/node-operators/guides/execution-config#rollupdisabletxpoolgossip) flag
   </Step>
 
   <Step title="Enable snap sync on your network">
@@ -36,5 +36,5 @@ For snap sync, all `op-geth` nodes should expose port `30303` TCP and `30303` UD
 
 ## Next Steps
 
-*   See the [Node configuration](/operators/node-operators/configuration/base-config#configuration) guide for additional explanation or customization.
+*   See the [Node configuration](/node-operators/guides/base-config#configuration) guide for additional explanation or customization.
 *   If you experience difficulty at any stage of this process, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions).
@@ -16,8 +16,8 @@
   *   **Chain Architecture**: OP Chains use execution and consensus clients as well as the OP Stack's privileged roles. For more details, see the [Chain Architecture](/operators/chain-operators/architecture) guide.
   *   **Smart Contracts**: OP Chains use several smart contracts on the L1 
   blockchain to manage aspects of the Rollup. Each OP Stack chain has its own 
-  set of [L1 smart contracts](/stack/smart-contracts/smart-contracts), 
-  [L2 predeploy contracts](/stack/smart-contracts/smart-contracts),
+  set of [L1 smart contracts](/concepts/stack/smart-contracts), 
+  [L2 predeploy contracts](/concepts/stack/smart-contracts),
   and [L2 preinstall contracts](/operators/chain-operators/features/preinstalls)
   that are deployed when the chain is created.
   *   **Preinstalls**: OP Chains come with [preinstalled core contracts](/operators/chain-operators/features/preinstalls), making them usable as soon as a chain is initialized on the OP Stack.
@@ -84,7 +84,7 @@

  *   Test [sending L2 transactions](https://github.com/ethereum-optimism/tx-overload) to understand how much load your new chain can handle.
  *   Trace [deposits and withdrawals](/app-developers/tutorials/transactions/sdk-trace-txns) using the SDK or viem.
  *   Run [basic transaction tests](https://metamask.io/) using Metamask.


  </Step></Steps>
@@ -102,7 +102,7 @@
 | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- | ---------------- |
 | [Creating Your Own L2 Rollup](/operators/chain-operators/tutorials/create-l2-rollup)                         | Learn how to spin up your own OP Stack testnet chain                                                                                   | 🟡 Medium        |
 | [Adding Attributes to the Derivation Function](/operators/chain-operators/tutorials/adding-derivation-attributes) | Learn how to modify the derivation function for an OP Stack chain to track the amount of ETH being burned on L1.                       | 🟢 Easy          |
 | [Adding a Precompile](/operators/chain-operators/tutorials/adding-precompiles)                               | Learn how to run an EVM with a new precompile for OP Stack chain operations to speed up calculations that are not currently supported. | 🟢 Easy          |
 | [Modifying Predeployed Contracts](/operators/chain-operators/tutorials/modifying-predeploys)                 | Learn how to modify predeployed contracts for an OP Stack chain by upgrading the proxy.                                                | 🟢 Easy          |
 | [Pause and Unpause the Bridge](/stack/security/pause)                                                        | Learn how to pause `OptimismPortal` as a backup safety mechanism on your OP Stack chain.                                               | 🟢 Easy          |
 | [Integrating a DA Layer](/operators/chain-operators/tutorials/integrating-da-layer)                          | Learn how to integrate a new DA Layer with Alt-DA                                                                                      | 🟢 Easy          |

@@ -5,7 +5,7 @@ description: Learn how OP Contracts Manager deploys the OP Stack with one transa
 
 The OP Contracts Manager is a contract that deploys the L1 contracts for an OP Stack chain in a single transaction. It provides a minimal set of user-configurable parameters to ensure that the resulting chain meets the standard configuration requirements. Additionally, as of [Upgrade 13](https://gov.optimism.io/t/upgrade-proposal-13-opcm-and-incident-response-improvements/9739), instances of OPCM can upgrade existing OP Stack chains.
 
-The version deployed is always a governance-approved contract release. The set of governance approved contract releases can be found on the Optimism Monorepo releases page, and is the set of releases named `op-contracts/vX.Y.Z`. It deploys the [Fault Proof System](/stack/fault-proofs/explainer), using the [PermissionedDisputeGame](/stack/smart-contracts/smart-contracts#permissioneddisputegame).
+The version deployed is always a governance-approved contract release. The set of governance approved contract releases can be found on the Optimism Monorepo releases page, and is the set of releases named `op-contracts/vX.Y.Z`. It deploys the [Fault Proof System](/stack/fault-proofs/explainer), using the [PermissionedDisputeGame](/concepts/stack/smart-contracts#permissioneddisputegame).
 
 ## Purpose
 

@@ -17,7 +17,7 @@ A standard chain in the OP Stack refers to a rollup that adheres to the followin
     *   Utilization of officially supported features and modules of the OP Stack.
 
 2.  **Governance alignment:**
-    *   Adherence to the [Standard Rollup Charter](/superchain/blockspace-charter#the-standard-rollup-charter).
+    *   Adherence to the [Standard Rollup Charter](/concepts/blockspace-charter#the-standard-rollup-charter).
     *   Transparent and collaborative decision-making aligned with the Superchain ecosystem.
 
 3.  **Interoperability:**
@@ -71,7 +71,7 @@ Certain configurations are explicitly not part of the standard setup. For exampl
 *   **Modified system contracts:**
     Any alterations to core system contracts break standardization and aren't supported in the official OP Stack specification.
 
-For a detailed list of standard configurations, refer to the [Standard rollup configuration page](/superchain/blockspace-charter).
+For a detailed list of standard configurations, refer to the [Standard rollup configuration page](/concepts/blockspace-charter).
 
 ## Superchain Registry
 
@@ -106,5 +106,5 @@ The [Superchain Registry](/superchain/superchain-registry) is the authoritative
 ## References
 
 *   [OP Stack Specifications](https://specs.optimism.io/protocol/configurability.html?utm_source=op-docs&utm_medium=docs)
-*   [Blockspace Charter](/superchain/blockspace-charter)
+*   [Blockspace Charter](/concepts/blockspace-charter)
 *   [Superchain Registry](https://github.com/ethereum-optimism/superchain-registry)
@@ -15,10 +15,10 @@ An OP Stack Standard Rollup follows the Standard Rollup Charter.
 
 This configuration targets the Optimism Collective's highest bar for security, uptime, and decentralization.
 
-You can find more details in the [Standard Rollup Charter documentation](/superchain/blockspace-charter).
+You can find more details in the [Standard Rollup Charter documentation](/concepts/blockspace-charter).
 
 <Info>
-  We **strongly** recommend using the [op-deployer](/operators/chain-operators/tools/op-deployer) to deploy L1 contracts and generate the L2 genesis file that meets the configuration requirements outlined in the [Standard Rollup Charter](/superchain/blockspace-charter).
+  We **strongly** recommend using the [op-deployer](/operators/chain-operators/tools/op-deployer) to deploy L1 contracts and generate the L2 genesis file that meets the configuration requirements outlined in the [Standard Rollup Charter](/concepts/blockspace-charter).
 </Info>
 
 ## Joining the Registry

@@ -39,11 +39,11 @@ Networks that have opted into the [hard fork inheritance behavior](/superchain/s
 
 ## `rollup.halt` flags on node binaries
 
-The [`rollup.halt`](/operators/node-operators/configuration/execution-config#rolluphalt) flag is an opt-in configuration option available in both the execution and consensus layer node binaries. 
+The [`rollup.halt`](/node-operators/guides/execution-config#rolluphalt) flag is an opt-in configuration option available in both the execution and consensus layer node binaries. 
 Its primary function is to temporarily halt node activities, during the transition phase of an upgrade, if or when it encounters an incompatible or unsupported protocol version requirement.
 
-*   Execution layer configuration: In the execution layer *(`op-geth`)*, the [`--rollup.halt`](/operators/node-operators/configuration/execution-config#rolluphalt) flag can be set to specify the level of incompatibility (major, minor, patch, none) that will trigger a halt. This ensures that nodes do not process transactions under unsupported protocol versions.
-*   Consensus layer configuration: Similarly, in the consensus layer *(`op-node`)*, the [`--rollup.halt`](/operators/node-operators/configuration/consensus-config#rolluphalt) flag serves the same purpose, allowing nodes to halt when encountering incompatible protocol versions.
+*   Execution layer configuration: In the execution layer *(`op-geth`)*, the [`--rollup.halt`](/node-operators/guides/execution-config#rolluphalt) flag can be set to specify the level of incompatibility (major, minor, patch, none) that will trigger a halt. This ensures that nodes do not process transactions under unsupported protocol versions.
+*   Consensus layer configuration: Similarly, in the consensus layer *(`op-node`)*, the [`--rollup.halt`](/node-operators/guides/configuration/consensus-config#rolluphalt) flag serves the same purpose, allowing nodes to halt when encountering incompatible protocol versions.
 
 <Info>
 Failing to upgrade your node with new hardfork rules will trigger the use of the `rollup.halt` flag on the Superchain signaling and your node will halt.

@@ -29,7 +29,7 @@
 *   Global Events Monitor: made for taking YAML rules as configuration and monitoring the events that are emitted on the chain.
 *   Liveness Expiration Monitor: monitors the liveness expiration on Safes.
 *   Balances Monitor: emits a metric reporting the balances for the configured accounts.
 *   Multisig Monitor: The multisig monitor reports the paused status of the OptimismPortal contract. If set, reports the latest nonce of the configured Safe address and the latest presigned nonce stored in One Password.. The latest presigned nonce is identified by looking for items in the configured vault that follow a `ready-<nonce>.json` name. The highest nonce of this item name format is reported.
 *   Drippie Monitor: tracks the execution and executability of drips within a Drippie contract.
 *   Secrets Monitor: takes a Drippie contract as a parameter and monitors for any drips within that contract that use the `CheckSecrets` dripcheck contract. `CheckSecrets` is a dripcheck that allows a drip to begin once a specific secret has been revealed (after a delay period) and cancels the drip if a second secret is revealed. Monitoring these secrets is important, as their revelation may indicate that the secret storage platform has been compromised and someone is attempting to exfiltrate the ETH controlled by the drip.

@@ -66,7 +66,7 @@
 
 You can find more info on `op-dispute-mon` on [the repo](https://github.com/ethereum-optimism/optimism/tree/develop/op-dispute-mon).
 
-Chain operators can easily create their grafana dashboard for Dispute Monitor using the following json file: [Download the Dispute Monitor JSON](/resources/grafana/dispute-monitor-1718214549035.json).
+Chain operators can easily create their grafana dashboard for Dispute Monitor using the following json file: [Download the Dispute Monitor JSON](/public/resources/grafana/dispute-monitor-1718214549035.json).
 
 ## Offchain component monitoring
 

@@ -3,7 +3,7 @@
 description: Learn how to use op-validator to validate chain configurations and deployments.
 ---
 
-The `op-validator` is a tool for validating Standard OP Stack chain configurations and deployments to ensure they're in compliance with the [Standard Rollup Charter](/superchain/blockspace-charter#the-standard-rollup-charter). It works by calling into the `StandardValidator` smart contracts (`StandardValidatorV180` and `StandardValidatorV200`). These then perform a set of checks, and return error codes for any issues found.
+The `op-validator` is a tool for validating Standard OP Stack chain configurations and deployments to ensure they're in compliance with the [Standard Rollup Charter](/concepts/blockspace-charter#the-standard-rollup-charter). It works by calling into the `StandardValidator` smart contracts (`StandardValidatorV180` and `StandardValidatorV200`). These then perform a set of checks, and return error codes for any issues found.
 
 These checks include:
 
@@ -65,7 +65,7 @@

 ## Usage

 The validator supports different protocol versions through subcommands:

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

@@ -545,7 +545,7 @@
 
 *   Provides visibility into all game statuses for the last 28 days
 *   Essential for production challenger deployments
-*   Create Grafana dashboards using: [Download the Dispute Monitor JSON](/resources/grafana/dispute-monitor-1718214549035.json)
+*   Create Grafana dashboards using: [Download the Dispute Monitor JSON](/public/resources/grafana/dispute-monitor-1718214549035.json)
 
 ## Congratulations