From 2e51ff1851ee938c86346a9758e3779190a48e21 Mon Sep 17 00:00:00 2001 From: berzan <106833240+berzanorg@users.noreply.github.com> Date: Fri, 14 Nov 2025 09:57:33 +0700 Subject: [PATCH 1/4] Update changed link --- docs/ops.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ops.md b/docs/ops.md index 4df37807d..565e59c10 100644 --- a/docs/ops.md +++ b/docs/ops.md @@ -13,7 +13,7 @@ The following are the steps you need to take to add a chain to the registry: ### 0. Standard Chains: Deploy your chain with `op-deployer` If you are deploying a standard chain, it _must_ be deployed with `op-deployer` to be considered standard in the Superchain Registry. Check out -the [docs](https://docs.optimism.io/builders/chain-operators/tools/op-deployer) for more information on how to use it. +the [docs](https://docs.optimism.io/chain-operators/tools/op-deployer) for more information on how to use it. > [!TIP] > We recommend that most chains use `op-deployer`. `op-deployer` can be configured to support L3s, alt-DA and custom gas token chains. From 09b0e483b9f403a7817cae0d8498c7f8d6afc0cb Mon Sep 17 00:00:00 2001 From: berzan <106833240+berzanorg@users.noreply.github.com> Date: Fri, 14 Nov 2025 10:00:56 +0700 Subject: [PATCH 2/4] Update changed links --- docs/hardfork-activation-inheritance.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/hardfork-activation-inheritance.md b/docs/hardfork-activation-inheritance.md index d7d984b31..940907592 100644 --- a/docs/hardfork-activation-inheritance.md +++ b/docs/hardfork-activation-inheritance.md @@ -12,8 +12,8 @@ For a chain to "receive" a particular default (superchain-wide) hardfork activat To "receive" a hardfork activation time for a given chain means that the downstream OP Stack components will apply that activation time when starting up using a network flag specifying the chain in question. At the time of writing, this is implemented for -* [op-geth](https://docs.optimism.io/builders/node-operators/configuration/base-config#initialization-via-network-flags) -* [op-node](https://docs.optimism.io/builders/node-operators/configuration/base-config#configuring-op-node) +* [op-geth](https://docs.optimism.io/node-operators/guides/base-config#initialization-via-network-flags) +* [op-node](https://docs.optimism.io/node-operators/guides/base-config#configuring-op-node) > [!NOTE] > Since [version 2.0](https://github.com/ethereum-optimism/superchain-registry/pull/816) of the superchain registry, the inherited hardfork activation times are applied directly to each chain's individual chain config TOML file. What you see is what you get (unlike in previous iterations of the registry, where the inheritance was applied "magically" by Go bindings). From bfb1d6e38f7c7d0b88e243675966dc0b30432e05 Mon Sep 17 00:00:00 2001 From: berzan <106833240+berzanorg@users.noreply.github.com> Date: Fri, 14 Nov 2025 10:10:09 +0700 Subject: [PATCH 3/4] Update changed links --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 083e0f63b..591cec3b7 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ Welcome to the Superchain Registry
> [!WARNING] -> Starting on March 1st, 2025, all standard chains who wish to be added to the Superchain registry **MUST** be deployed using [OP Deployer](https://docs.optimism.io/builders/chain-operators/tools/op-deployer). +> Starting on March 1st, 2025, all standard chains who wish to be added to the Superchain registry **MUST** be deployed using [OP Deployer](https://docs.optimism.io/chain-operators/tools/op-deployer). The Superchain Registry is an index of chains which serves as the source of truth for who’s in the Superchain Ecosystem and what modifications they’ve made to their chains. @@ -24,7 +24,7 @@ A glossary, with key terms and more information about Superchain levels and requ ### Downstream packages -The Superchain configs are stored in a minimal form and embedded in downstream OP-Stack software ([`op-node`](https://github.com/ethereum-optimism/optimism) and [`op-geth`](https://github.com/ethereum-optimism/op-geth)). This means that after a chain has been added to the registry and the dependency on the registry updates in the downstream software, it is possible to start an `op-node` instance [using the `--network` flag](https://docs.optimism.io/builders/node-operators/configuration/consensus-config#network) (and also an `op-geth` instance [using the `--op-network` tag](https://docs.optimism.io/builders/node-operators/configuration/execution-config#op-network-betaop-network)) which will successfully sync with other nodes on that network. +The Superchain configs are stored in a minimal form and embedded in downstream OP-Stack software ([`op-node`](https://github.com/ethereum-optimism/optimism) and [`op-geth`](https://github.com/ethereum-optimism/op-geth)). This means that after a chain has been added to the registry and the dependency on the registry updates in the downstream software, it is possible to start an `op-node` instance [using the `--network` flag](https://docs.optimism.io/node-operators/guides/consensus-config#network) (and also an `op-geth` instance [using the `--op-network` tag](https://docs.optimism.io/node-operators/guides/execution-config#op-network%2C-beta-op-network )) which will successfully sync with other nodes on that network. ### Hardfork activations If you would like your chain to automatically receive superchain-wide coordinated hardfork activations, you can enable this by: From 2df59b23a6e07a646003361212565904d1c38856 Mon Sep 17 00:00:00 2001 From: berzan <106833240+berzanorg@users.noreply.github.com> Date: Fri, 14 Nov 2025 10:10:10 +0700 Subject: [PATCH 4/4] Update changed links --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 083e0f63b..591cec3b7 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ Welcome to the Superchain Registry
> [!WARNING] -> Starting on March 1st, 2025, all standard chains who wish to be added to the Superchain registry **MUST** be deployed using [OP Deployer](https://docs.optimism.io/builders/chain-operators/tools/op-deployer). +> Starting on March 1st, 2025, all standard chains who wish to be added to the Superchain registry **MUST** be deployed using [OP Deployer](https://docs.optimism.io/chain-operators/tools/op-deployer). The Superchain Registry is an index of chains which serves as the source of truth for who’s in the Superchain Ecosystem and what modifications they’ve made to their chains. @@ -24,7 +24,7 @@ A glossary, with key terms and more information about Superchain levels and requ ### Downstream packages -The Superchain configs are stored in a minimal form and embedded in downstream OP-Stack software ([`op-node`](https://github.com/ethereum-optimism/optimism) and [`op-geth`](https://github.com/ethereum-optimism/op-geth)). This means that after a chain has been added to the registry and the dependency on the registry updates in the downstream software, it is possible to start an `op-node` instance [using the `--network` flag](https://docs.optimism.io/builders/node-operators/configuration/consensus-config#network) (and also an `op-geth` instance [using the `--op-network` tag](https://docs.optimism.io/builders/node-operators/configuration/execution-config#op-network-betaop-network)) which will successfully sync with other nodes on that network. +The Superchain configs are stored in a minimal form and embedded in downstream OP-Stack software ([`op-node`](https://github.com/ethereum-optimism/optimism) and [`op-geth`](https://github.com/ethereum-optimism/op-geth)). This means that after a chain has been added to the registry and the dependency on the registry updates in the downstream software, it is possible to start an `op-node` instance [using the `--network` flag](https://docs.optimism.io/node-operators/guides/consensus-config#network) (and also an `op-geth` instance [using the `--op-network` tag](https://docs.optimism.io/node-operators/guides/execution-config#op-network%2C-beta-op-network )) which will successfully sync with other nodes on that network. ### Hardfork activations If you would like your chain to automatically receive superchain-wide coordinated hardfork activations, you can enable this by: