ethereum-optimism · sbvegan · Nov 16, 2025 · Nov 15, 2025 · Nov 15, 2025 · Nov 15, 2025
@@ -15,9 +15,9 @@
 *   Sponsor the gas fees for transactions
 *   Enable users to pay gas in the token(s) of their choice
 
 ## Bundlers
 
-The OP Stack includes support for the `eth_sendRawTransactionConditional` RPC method to assist bundlers on shared 4337 mempools. See the [specification](/stack/features/send-raw-transaction-conditional) for how this method is implemented in op-geth.
+The OP Stack includes support for the `eth_sendRawTransactionConditional` RPC method to assist bundlers on shared 4337 mempools. See the [specification](/op-stack/features/send-raw-transaction-conditional) for how this method is implemented in op-geth.
 
 If used by the chain operator, also see the supplemental [op-txproxy](/operators/chain-operators/tools/op-txproxy) service which may apply additional restrictions prior to reaching the block builder.
 
@@ -31,27 +31,27 @@

 ## Account abstraction tools

 Ready to enable account abstraction experiences in your app? Here's some helpful information on account abstraction infrastructure like ERC-4337 bundler and gas manager APIs that are available on OP Mainnet:

 *   [Alchemy](https://www.alchemy.com/account-abstraction): 
    Account Kit is a complete solution for account abstraction. Using Account Kit, you can create a smart contract wallet for every user that leverages account abstraction to simplify every step of your app's onboarding experience. It also offers Gas Manager and Bundler APIs for sponsoring gas and batching transactions.

 *   [Biconomy](https://docs.biconomy.io/): is an Account Abstraction toolkit that enables you to provide the simplest UX for your app or wallet. It offers modular smart accounts, as well as paymasters and bundlers as a service for sponsoring gas and executing transactions at scale.

 *   [GroupOS](https://docs.groupos.xyz/introduction/group-os): provides Smart Wallets that are ERC-4337 compliant smart wallets, offering full flexibility, programmability and extensibility as well as out-of-the-box toolkit groups need to gaslessly onboard and activate wallets to games, applications, and/or protocols.

 *   [Openfort](https://openfort.io/docs): is an open-source alternative to wallet infrastructure solutions. The core offerings—Openfort Kit, Invisible Wallet, and Cross-app Wallet - enable rapid integration of wallet functionality, intuitive onboarding, and flexible user journeys for any application or ecosystem.

 *   [Pimlico](https://docs.pimlico.io/): provides an infrastructure platform that makes building smart accounts simpler. If you are developing an ERC-4337 smart account, they provide bundlers, verifying paymasters, ERC-20 paymasters, and much more.

 *   [Reown](https://reown.com/?utm_source=optimism&utm_medium=docs&utm_campaign=backlinks) gives developers the tools to build user experiences that make digital ownership effortless, intuitive, and secure. Using Reown's AppKit SDK, you can enable your users to create a smart wallet using their social logins, configure a paymaster to sponsor gas fees, enable chain abstraction and a lot more.

 *   [Safe](https://docs.safe.global/home/what-is-safe): provides modular smart account infrastructure and account abstraction stack via their Safe\{Core\} Account Abstraction SDK, API, and Protocol.

 *   [Stackup](https://docs.stackup.sh/docs): provides smart account tooling for building account abstraction within your apps. They offer Paymaster and Bundler APIs for sponsoring gas and sending account abstraction transactions.

 *   [thirdweb](https://portal.thirdweb.com/react/v5/account-abstraction/get-started?utm_source=opdocs&utm_medium=docs):
    offers the complete tool-kit to leverage account abstraction technology to enable seamless user experiences for your users. This includes Account Factory contracts that lets your users spin up Smart Accounts, Bundler for UserOps support, and Paymaster to enable gas sponsorships. 

 ## Helpful tips


@@ -57,7 +57,7 @@

 The `op-batcher` has the capabilities to send multiple blobs per single blob transaction. This is accomplished by the use of multi-frame channels, see the [specs](https://specs.optimism.io/protocol/derivation.html#frame-format?utm_source=op-docs&utm_medium=docs) for more technical details on channels and frames.

 A minimal batcher configuration (with env vars) to enable 6-blob batcher transactions is:

 ```
 ```
@@ -110,7 +110,7 @@
 In this case, make sure the miner API namespace is enabled for the correct transport protocol (HTTP or WS), see next paragraph.
 ```

 The new RPC `miner_setMaxDASize` is available in `op-geth` since `v1.101411.1`. It has to be enabled by adding the miner namespace to the correct API flags, like

 ```
 GETH_HTTP_API: web3,debug,eth,txpool,net,miner
@@ -155,7 +155,7 @@
 
 The batch type. 0 for `SingularBatch` and 1 for `SpanBatch`. The default value
 is `0` for `SingularBatch`.
-See the [span batch feature page](/operators/chain-operators/features/span-batches) to learn more.
+See the [span batch feature page](/op-stack/features/span-batches) to learn more.
 
 <Tabs items={['Syntax', 'Example', 'Environment Variable']}>
   <Tabs.Tab>`--batch-type=<value>`</Tabs.Tab>
@@ -286,7 +286,7 @@

 Indicates if, during startup, the batcher should wait for a recent batcher tx
 on L1 to finalize (via more block confirmations). This should help avoid
 duplicate batcher txs. The default value is `false`.

 <Tabs items={['Syntax', 'Example', 'Environment Variable']}>
  <Tabs.Tab>`--wait-node-sync=<value>`</Tabs.Tab>
@@ -541,7 +541,7 @@

 Headers to pass to the remote signer. Format `key=value`.\
 Value can contain any character allowed in an HTTP header.\
 When using env vars, split multiple headers with commas.\
 When using flags, provide one key-value pair per flag.

 <Tabs items={['Syntax', 'Example', 'Environment Variable']}>
@@ -746,7 +746,7 @@

 #### log.format

 Format the log output. Supported formats: 'text', 'terminal', 'logfmt', 'json',
 'json-pretty'. The default value is `text`.

 <Tabs items={['Syntax', 'Example', 'Environment Variable']}>

@@ -5,7 +5,7 @@
 
 This page lists all configuration options for op-proposer. The op-proposer posts
 output roots (proposals) to L1, making them available for verifiers. Withdrawals to L1 must reference an output root.
-If the chain is running permissioned fault proofs, only the [designated proposer](/superchain/privileged-roles#proposer) can submit output roots.
+If the chain is running permissioned fault proofs, only the [designated proposer](/op-stack/protocol/privileged-roles) can submit output roots.
 With [permissionless fault proofs](/op-stack/fault-proofs/explainer), anyone can make a proposal.
 
 ## Proposer policy
@@ -319,7 +319,7 @@

 #### log.format

 Format the log output. Supported formats: 'text', 'terminal', 'logfmt', 'json',
 'json-pretty'. The default value is text.

 <Tabs items={['Syntax', 'Example', 'Environment Variable']}>

@@ -992,7 +992,7 @@
 Alt-DA Mode enables seamless integration of various Data Availability (DA) 
 Layers, regardless of their commitment type, into the OP Stack. This allows 
 any chain operator to launch an OP Stack chain using their favorite DA Layer 
-for sustainably low costs. Learn more [here](/stack/beta-features/alt-da-mode).
+for sustainably low costs. Learn more [here](/op-stack/features/experimental/alt-da-mode).
 
 ***
 
@@ -1106,7 +1106,7 @@

 ***

 #### enableGovernance

 EnableGovernance determines whether to include governance token predeploy.


@@ -8,7 +8,7 @@
   These features may experience stability issues, and we encourage feedback from our early users.
 </Info>
 
-This guide provides a walkthrough for chain operators who want to run an Alt-DA Mode chain. See the [Alt-DA Mode Explainer](/stack/beta-features/alt-da-mode) for a general overview of this OP Stack configuration.
+This guide provides a walkthrough for chain operators who want to run an Alt-DA Mode chain. See the [Alt-DA Mode Explainer](/op-stack/features/experimental/alt-da-mode) for a general overview of this OP Stack configuration.
 An Alt-DA Mode OP Stack chain enables a chain operator to post and read data to any alternative data availability layer that has built a functioning OP Stack DA Server.
 
 <Info>
@@ -104,7 +104,7 @@

 Alt DA teams who want to be featured on this page must meet the following criteria:

 *   Functional [DA Server](https://specs.optimism.io/experimental/alt-da.html#da-server?utm_source=op-docs&utm_medium=docs), maintained in your own repo
 *   Supporting detailed documentation, to be referenced [here](#setup-your-da-server)
 *   Functioning OP Stack devnet using your DA server with linked configuration, contract addresses, and RPC address

@@ -166,7 +166,7 @@

 Update the following CLI parameters for both `op-node` and `op-batcher`:

 | Former CLI param          | Current CLI param        |
 | ------------------------- | ------------------------ |
 | `--plasma.enabled`        | `--altda.enabled`        |
 | `--plasma.da-server`      | `--altda.da-server`      |
@@ -177,7 +177,7 @@

 #### op-node

 | Former env var                  | Current env var                |
 | ------------------------------- | ------------------------------ |
 | `OP_NODE_PLASMA_ENABLED`        | `OP_NODE_ALTDA_ENABLED`        |
 | `OP_NODE_PLASMA_DA_SERVER`      | `OP_NODE_ALTDA_DA_SERVER`      |
@@ -186,7 +186,7 @@

 #### op-batcher

 | Former env var                     | Current env var                   |
 | ---------------------------------- | --------------------------------- |
 | `OP_BATCHER_PLASMA_ENABLED`        | `OP_BATCHER_ALTDA_ENABLED`        |
 | `OP_BATCHER_PLASMA_DA_SERVER`      | `OP_BATCHER_ALTDA_DA_SERVER`      |
@@ -195,7 +195,7 @@

 #### op-alt-da (formerly op-plasma) daserver

 | Former env var                             | Current env var                        |
 | ------------------------------------------ | -------------------------------------- |
 | `OP_PLASMA_DA_SERVER_ADDR`                 | `OP_ALTDA_SERVER_ADDR`                 |
 | `OP_PLASMA_DA_SERVER_PORT`                 | `OP_ALTDA_SERVER_PORT`                 |
@@ -214,6 +214,6 @@
 
 ## Next steps
 
-*   Additional questions? See the FAQ section in the [Alt-DA Mode Explainer](/stack/beta-features/alt-da-mode#faqs).
+*   Additional questions? See the FAQ section in the [Alt-DA Mode Explainer](/op-stack/features/experimental/alt-da-mode#faqs).
 *   For more detailed info on Alt-DA Mode, see the [specs](https://specs.optimism.io/experimental/alt-da.html?utm_source=op-docs&utm_medium=docs).
 *   If you experience any problems, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions).
@@ -92,7 +92,7 @@ The steps below explain how to update the `daFootprintGasScalar` parameter on-ch
 
   <Step title="Call the setDAFootprintGasScalar() method">
    <Info>
-    The [SystemConfig owner](https://docs.optimism.io/chain-operators/reference/privileged-roles#system-config-owner) is the only address that can make these changes.
+    The [SystemConfig owner](/op-stack/protocol/privileged-roles) is the only address that can make these changes.
     </Info>
     To update the `daFootprintGasScalar`, call the following method on the `SystemConfig` contract:
 

@@ -32,7 +32,7 @@ The steps below explain how to update the `minBaseFee` parameter on-chain using
 
   <Step title="Call the setMinimumBaseFee() method">
    <Info>
-    Note that the owner of the `SystemConfig` contract is the [System Config Owner address](https://docs.optimism.io/chain-operators/reference/privileged-roles#system-config-owner), so this transaction must be sent from that address.
+    Note that the owner of the `SystemConfig` contract is the [System Config Owner address](/op-stack/protocol/privileged-roles), so this transaction must be sent from that address.
     </Info>
     To update the minimum base fee, call the following method on the `SystemConfig` contract:
 

@@ -8,7 +8,7 @@
 # Managing your keys
 
 This guide informs chain operators on important key management considerations. 
-There are certain [privileged roles](/superchain/privileged-roles) that 
+There are certain [privileged roles](/op-stack/protocol/privileged-roles) that 
 need careful consideration. The privileged roles are categorized as hot wallets
 or cold wallets.
 
@@ -33,11 +33,11 @@
 ## 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](/superchain/privileged-roles) documentation
+  Refer to the [privileged roles](/op-stack/protocol/privileged-roles) documentation
   for more information about these different addresses and their security concerns.
 </Info>
@@ -42,7 +42,7 @@
 <Steps>
   <Step title="Setup Key Management and Privileged Roles">
 *   Configure hot wallets and cold wallets using the guide for [Managing Your Keys](/operators/chain-operators/management/key-management).
-  *   Refer to the [Privileged Roles](/superchain/privileged-roles) guide for detailed security information.
+  *   Refer to the [Privileged Roles](/op-stack/protocol/privileged-roles) guide for detailed security information.
 
   </Step>
 
@@ -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          |

@@ -1,6 +1,6 @@
 ---
 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](/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.
+  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>

@@ -21,7 +21,7 @@
 *   **Permissionless dispute game**: Open to anyone to propose or challenge
 
 <Info>
-  In the Permissioned dispute game (PDG), the [challenger role](/superchain/privileged-roles#challenger) is a protocol-level permission assigned to specific addresses, allowing them to initiate or respond to disputes. This role is distinct from the op-challenger service, which is an off-chain monitoring service responsible for automatically detecting discrepancies and submitting challenges.
+  In the Permissioned dispute game (PDG), the [challenger role](/op-stack/protocol/privileged-roles) is a protocol-level permission assigned to specific addresses, allowing them to initiate or respond to disputes. This role is distinct from the op-challenger service, which is an off-chain monitoring service responsible for automatically detecting discrepancies and submitting challenges.
   While the op-challenger service typically operates using an address that has been assigned the challenger role, the protocol-level role itself can be independently assigned, regardless of whether the op-challenger service is in use.
   Refer to the [OP Stack configurability spec](https://specs.optimism.io/protocol/configurability.html) for more details.
 </Info>
@@ -73,9 +73,9 @@

 **Key parameters explained:**

 *   **saltMixer:** A string used to create unique contract addresses
 *   **systemConfig:** The address of your chain's `SystemConfig` contract
 *   **proxyAdmin:** The Address of your chain's `ProxyAdmin` contract
 *   **delayedWETH:** The Address of the `DelayedWETH` contract (use zero address to deploy a new one)
 *   **disputeGameType:** For permissionless games, use `GameTypes.CANNON`
 *   **disputeAbsolutePrestate:** The absolute prestate hash for the game

@@ -8,7 +8,7 @@ description: Learn how to add support for a new DA Layer within the OP Stack.
   These features may experience stability issues, and we encourage feedback from our early users.
 </Info>
 
-[Alt-DA Mode](/stack/beta-features/alt-da-mode) enables seamless integration of any DA Layer, regardless of their commitment type, into the OP Stack. After a DA Server is built for a DA Layer, any chain operator can launch an OP Stack chain using that DA Layer for sustainably low costs.
+[Alt-DA Mode](/op-stack/features/experimental/alt-da-mode) enables seamless integration of any DA Layer, regardless of their commitment type, into the OP Stack. After a DA Server is built for a DA Layer, any chain operator can launch an OP Stack chain using that DA Layer for sustainably low costs.
 
 ## Build your DA server
 
@@ -36,7 +36,7 @@ Our suggestion is for every DA Layer to build and maintain their own DA Server,
 </Steps>
 
 ## Run Alt-DA
-Follow our guide on [how to operate an Alt-DA Mode chain](/operators/chain-operators/features/alt-da-mode), except instead of using the S3 DA server, use the DA server that you built.
+Follow our guide on [how to operate an Alt-DA Mode chain](/chain-operators/guides/features/alt-da-mode-guide), except instead of using the S3 DA server, use the DA server that you built.
 
 ## Next steps
 

@@ -168,7 +168,7 @@
 *   The **ProxyAdmin Owner** has the authority to upgrade proxy contracts.
 *   The **Guardian** has emergency powers like pausing withdrawals and changing the respected game type.
 
-For detailed information about privileged roles and their security implications, refer to the [privileged roles documentation](/superchain/privileged-roles).
+For detailed information about privileged roles and their security implications, refer to the [privileged roles documentation](/op-stack/protocol/privileged-roles).
 
 ### Adding the PermissionlessDisputeGame to a chain
 
@@ -258,9 +258,9 @@

 You have two main options for executing this step:

 ### Option 1: Execute using a multisig

 If your privileged role (such as the Guardian) is controlled by a multisig or DAO governance system, use the provided JSON payload (`input.json`):

 <Expandable title="Create an `input.json` file with the transaction to update the `respectedGameType`: ">


@@ -203,11 +203,15 @@
     },
     {
       "source": "/operators/chain-operators/features/flashblocks",
-      "destination": "/chain-operators/reference/features/flashblocks/chain-operators"
+      "destination": "/chain-operators/guides/features/flashblocks-guide"
     },
     {
       "source": "/operators/chain-operators/features/flashblocks/apps",
-      "destination": "/chain-operators/reference/features/flashblocks/apps"
+      "destination": "/op-stack/features/flashblocks"
+    },
+    {
+      "source": "/chain-operators/reference/features/flashblocks/apps",
+      "destination": "/op-stack/features/flashblocks"
     },
     {
       "source": "/builders/chain-operators/tools/chain-monitoring",
@@ -299,7 +303,7 @@
     },
     {
       "source": "/stack/explainer",
-      "destination": "/superchain/superchain-explainer"
+      "destination": "/superchain/introduction/superchain-explainer"
     },
     {
       "source": "/stack/beta-features/custom-gas-token",
@@ -331,7 +335,7 @@
     },
     {
       "source": "/chain/security/privileged-roles",
-      "destination": "/superchain/privileged-roles"
+      "destination": "/op-stack/protocol/privileged-roles"
     },
     {
       "source": "/chain/differences",
@@ -983,19 +987,27 @@
     },
     {
       "source": "/operators/chain-operators/features/alt-da-mode",
-      "destination": "/chain-operators/reference/features/alt-da-mode"
+      "destination": "/chain-operators/guides/features/alt-da-mode-guide"
+    },
+    {
+      "source": "/chain-operators/reference/features/alt-da-mode",
+      "destination": "/chain-operators/guides/features/alt-da-mode-guide"
     },
     {
       "source": "/operators/chain-operators/features/bridged-usdc-standard",
-      "destination": "/chain-operators/reference/features/bridged-usdc-standard"
+      "destination": "/op-stack/features/bridged-usdc-standard"
     },
     {
       "source": "/operators/chain-operators/features/preinstalls",
       "destination": "/chain-operators/reference/features/preinstalls"
     },
     {
       "source": "/operators/chain-operators/features/span-batches",
-      "destination": "/chain-operators/reference/features/span-batches"
+      "destination": "/op-stack/features/span-batches"
+    },
+    {
+      "source": "/chain-operators/reference/features/span-batches",
+      "destination": "/op-stack/features/span-batches"
     },
     {
       "source": "/operators/chain-operators/management",
@@ -1199,7 +1211,7 @@
     },
     {
       "source": "/stack/beta-features/alt-da-mode",
-      "destination": "/chain-operators/guides/features/alt-da-mode"
+      "destination": "/op-stack/features/experimental/alt-da-mode"
     },
     {
       "source": "/stack/design-principles",
@@ -1251,7 +1263,7 @@
     },
     {
       "source": "/stack/features/send-raw-transaction-conditional",
-      "destination": "/chain-operators/reference/rpc/send-raw-transaction-conditional"
+      "destination": "/op-stack/features/send-raw-transaction-conditional"
     },
     {
       "source": "/stack/getting-started",
@@ -1423,15 +1435,15 @@
     },
     {
       "source": "/superchain/privileged-roles",
-      "destination": "/chain-operators/reference/privileged-roles"
+      "destination": "/op-stack/protocol/privileged-roles"
     },
     {
       "source": "/superchain/standard-configuration",
       "destination": "/chain-operators/reference/standard-configuration"
     },
     {
-      "source": "/superchain/superchain-registry",
-      "destination": "/chain-operators/reference/superchain-registry"
+      "source": "/chain-operators/reference/superchain-registry",
+      "destination": "/superchain/superchain-registry"
     },
     {
       "source": "/superchain/superchain-upgrades",
@@ -1503,7 +1515,7 @@
     },
     {
       "source": "/operators/chain-operators/features/flashblocks/chain-operators",
-      "destination": "/chain-operators/reference/features/flashblocks/chain-operators"
+      "destination": "/chain-operators/guides/features/flashblocks-guide"
     },
     {
       "source": "/stack/smart-contracts/op-deployer-upgrade",
@@ -1660,6 +1672,30 @@
     {
       "source": "/concepts/security/fp-security",
       "destination": "/op-stack/fault-proofs/fp-security"
+    },
+    {
+      "source": "/chain-operators/reference/features/flashblocks/chain-operators",
+      "destination": "/chain-operators/guides/features/flashblocks-guide"
+    },
+    {
+      "source": "/chain-operators/reference/features/bridged-usdc-standard",
+      "destination": "/op-stack/features/bridged-usdc-standard"
+    },
+    {
+      "source": "/chain-operators/reference/features/preinstalls",
+      "destination": "/op-stack/features/preinstalls"
+    },
+    {
+      "source": "/chain-operators/reference/rpc/send-raw-transaction-conditional",
+      "destination": "/op-stack/features/send-raw-transaction-conditional"
+    },
+    {
+      "source": "/chain-operators/reference/superchain-explainer",
+      "destination": "/superchain/introduction/superchain-explainer"
+    },
+    {
+      "source": "/chain-operators/reference/privileged-roles",
+      "destination": "/op-stack/protocol/privileged-roles"
     }
   ],
   "navigation": {
@@ -1701,9 +1737,10 @@
               {
                 "group": "Features",
                 "pages": [
-                  "chain-operators/guides/features/alt-da-mode",
                   "chain-operators/guides/features/setting-min-base-fee",
-                  "chain-operators/guides/features/setting-da-footprint"
+                  "chain-operators/guides/features/setting-da-footprint",
+                  "chain-operators/guides/features/flashblocks-guide",
+                  "chain-operators/guides/features/alt-da-mode-guide"
                 ]
               },
               {
@@ -1770,38 +1807,13 @@
             "pages": [
               "chain-operators/reference/architecture",
               "chain-operators/reference/opcm",
-              "chain-operators/reference/privileged-roles",
               "chain-operators/reference/standard-configuration",
-              "chain-operators/reference/superchain-explainer",
-              "chain-operators/reference/superchain-registry",
               "chain-operators/reference/superchain-upgrades",
               {
                 "group": "Components",
                 "pages": [
                   "chain-operators/reference/components/op-supervisor"
                 ]
-              },
-              {
-                "group": "Features",
-                "pages": [
-                  "chain-operators/reference/features/alt-da-mode",
-                  "chain-operators/reference/features/bridged-usdc-standard",
-                  "chain-operators/reference/features/preinstalls",
-                  "chain-operators/reference/features/span-batches",
-                  {
-                    "group": "Flashblocks",
-                    "pages": [
-                      "chain-operators/reference/features/flashblocks/apps",
-                      "chain-operators/reference/features/flashblocks/chain-operators"
-                    ]
-                  }
-                ]
-              },
-              {
-                "group": "RPC",
-                "pages": [
-                  "chain-operators/reference/rpc/send-raw-transaction-conditional"
-                ]
               }
             ]
           }
@@ -1990,9 +2002,18 @@
           {
             "group": "Introduction",
             "pages": [
-              "op-stack/introduction/op-stack",
-              "op-stack/introduction/fact-sheet"
+              "/op-stack/introduction/op-stack",
+              "/op-stack/introduction/fact-sheet"
             ]
+          },
+              {
+                "group": "Features",
+                "pages": [
+                  "/op-stack/features/flashblocks",
+                  "/op-stack/features/bridged-usdc-standard",
+                  "/op-stack/features/span-batches",
+                  "/op-stack/features/send-raw-transaction-conditional"
+                ]
           },
           {
             "group": "Protocol Information",
@@ -2004,7 +2025,8 @@
               "/op-stack/protocol/derivation-pipeline",
               "/op-stack/protocol/outages",
               "/op-stack/protocol/network-upgrades",
-              "/op-stack/protocol/smart-contracts"
+              "/op-stack/protocol/smart-contracts",
+              "/op-stack/protocol/privileged-roles"
             ]
           },
           {
@@ -2070,7 +2092,9 @@
           {
             "group": "Concepts",
             "pages": [
-              "superchain/concepts/blockspace-charter"
+              "/superchain/introduction/superchain-explainer",
+              "superchain/concepts/blockspace-charter",
+              "/superchain/superchain-registry"
             ]
           }
         ]

@@ -12,7 +12,7 @@ The Optimism Collective will be testing improved incident response features on t
 
 ## What's happening
 
-1.  During this exercise, the privileged [`GUARDIAN`](/superchain/privileged-roles#guardian) address will call the `pause` function on the `SuperchainConfig`.
+1.  During this exercise, the privileged [`GUARDIAN`](/op-stack/protocol/privileged-roles#guardian) address will call the `pause` function on the `SuperchainConfig`.
 2.  Members of the Optimism Collective's security team will ensure that the pause is executed correctly and the incident response improvements worked as intended.
 3.  Then the `unpause` function will be called to resume normal operations.