From cd9ba72bfa5b9d047d249acd1e2b6a8e1dc21995 Mon Sep 17 00:00:00 2001 From: krofax Date: Fri, 17 Jan 2025 16:05:42 +0100 Subject: [PATCH 01/37] Add standandard config page --- pages/superchain/_meta.json | 3 +- pages/superchain/standard-configuration.mdx | 162 ++++++++++++++++++++ words.txt | 2 + 3 files changed, 166 insertions(+), 1 deletion(-) create mode 100644 pages/superchain/standard-configuration.mdx diff --git a/pages/superchain/_meta.json b/pages/superchain/_meta.json index 8fcebc30b..beff32e4d 100644 --- a/pages/superchain/_meta.json +++ b/pages/superchain/_meta.json @@ -1,5 +1,6 @@ { "superchain-explainer": "The Superchain explainer", "superchain-registry": "The Superchain Registry", - "blockspace-charter": "Blockspace Charters and the Standard Rollup Charter" + "blockspace-charter": "Blockspace Charters and the Standard Rollup Charter", + "standard-configuration": "Standard Configuration" } diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx new file mode 100644 index 000000000..152ba120a --- /dev/null +++ b/pages/superchain/standard-configuration.mdx @@ -0,0 +1,162 @@ +--- +title: Standard configuration +lang: en-US +description: Leane about the standard configuration, how the OP-Deployer aids standardization, and why adhering to these standards is essential. +--- + +# Standard configuration in the OP Stack + +The **standard configuration** within the OP Stack ensures that chains deployed in the Superchain ecosystem adhere to a consistent set of technical and governance parameters. +This standardization is critical for interoperability, network integrity, and ease of integration across the Superchain. + +This guide provides an in-depth explanation of what defines a standard configuration, how the OP-Deployer aids standardization, and why adhering to these standards is essential. + +## What is a Standard chain? + +A standard chain in the OP Stack refers to a rollup that adheres to the following principles: + +1. **Technical conformance**: + * Compliance with the OP Stack Specifications, including gas fees, block structure, and other protocol-level parameters. + These requirements are currently a draft, pending governance approval. For more details, please see + this [governance thread](https://gov.optimism.io/t/season-6-draft-standard-rollup-charter/8135) + and the actual requirements in the [OP Stack Configurability Specification](https://specs.optimism.io/protocol/configurability.html). + * Utilization of officially supported features and modules of the OP Stack. + +A standard OP Stack chain must implement: + +* **Protocol Contracts** + * Standard L1 contracts for cross-domain messaging + * Specified bridge implementations + * Standard governance contracts + +* **System Configuration** + * Standard L2 block time + * Specified gas parameters + * Default system addresses + +* **Network Settings** + * Standard RPC endpoints + * Specified network parameters + * Compatible chain ID allocation + +2. **Governance alignment**: + * Adherence to governance principles outlined in the [Blockspace Charter](/superchain/blockspace-charter). + * Transparent and collaborative decision-making aligned with the Superchain ecosystem. + +3. **Interoperability**: + * Maintaining compatibility with other chains in the Superchain ecosystem for seamless cross-chain interactions. + +Chains that deviate from these principles, such as introducing unsupported features like custom gas tokens, are considered non-standard configurations. + +## Role of OP-Deployer in Standardization + +The [OP-Deployer](https://github.com/ethereum-optimism/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. +Key features include: + +* **Preconfigured Templates**: + * OP-Deployer provides templates that encapsulate best practices, ensuring that your chain is configured according to standard specifications. + +* **Automated Validations**: + * The tool performs checks during the deployment process to flag any deviations from standard configurations, such as unsupported modules or governance misalignments. + +* **Ease of Customization within standards**: + * While ensuring compliance, OP-Deployer allows for minor, non-breaking customizations to suit specific use cases. + +By using OP-Deployer, developers can reduce the complexity of chain deployment while ensuring alignment with Superchain standards. + + + The Rollup configuration is an active work in progress and will likely evolve + significantly as time goes on. If something isn't working about your + configuration, you can refer to the [source code](https://github.com/ethereum-optimism/optimism/blob/develop/op-chain-ops/genesis/config.go). + + +## Why standardization matters + +Standardization benefits the Superchain ecosystem in several ways: + +* **Interoperability**: + * Enables seamless interactions between chains, such as cross-chain messaging and token transfers. + +* **Simplified Development**: + * Reduces the learning curve for developers by providing consistent and predictable configurations. + +* **Ecosystem Growth**: + * Encourages a thriving ecosystem by lowering barriers to entry and fostering collaboration. + +* **Reduced Support Overhead**: + + * Minimizes the need for custom support by ensuring uniformity across deployments. + + Native ETH as gas token: All transactions on the network must use ETH for gas payments, maintaining consistency with Ethereum's native token model. + +### Standard feature + +* Standard block time (2s): + Blocks must be produced every 2 seconds to ensure predictable transaction processing and network synchronization. + +* Default system contracts: + Core protocol contracts must use unmodified implementations provided by the OP Stack to guarantee security and compatibility. + +* Standard bridge implementations: + Cross-chain communication must use official bridge contracts to ensure secure and standardized asset transfers. + +* Specified sequencer configurations: + Sequencer settings must follow prescribed parameters for transaction ordering and submission to maintain network stability. + +## What is Not Standard? + +Certain configurations are explicitly not part of the standard setup. For example: + +* **Custom Gas Tokens**: + * Introducing a gas token other than the default is currently not considered standard. + +* **Non-Conforming Modules**: + * Using modules not officially supported by the OP Stack. + +* Custom gas tokens: + Using tokens other than ETH for gas payments deviates from the standard and isn't currently supported in the Superchain ecosystem. + +* Modified block times: + Changing the 2-second block time breaks network synchronization expectations and isn't compatible with standard configurations. + +* Custom bridge implementations: + Using modified or custom bridge contracts risks security and interoperability, making them non-standard. + +* 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). + +## Superchain Registry + +The [Superchain Registry](/superchain/superchain-registry) is the authoritative index of all chains within the Superchain ecosystem. It ensures: + +* **Transparency**: + * All registered chains are publicly listed with their configurations. + +* **Compliance verification**: + * Chains listed in the registry are verified for adherence to the standard configuration. + +* **Community trust**: + * Being part of the registry signals reliability and alignment with Superchain principles. + +## Next Steps + +1. **Understand standards**: + * Familiarize yourself with the [Op Stack specifications](https://specs.optimism.io/protocol/configurability.html) and the Blockspace Charter. + +2. **Use OP-Deployer**: + * Leverage OP-Deployer to ensure your chain aligns with standard configurations. + +3. **Seek guidance**: + * Consult the [developer support](https://github.com/ethereum-optimism/developers/discussions) team for clarifications on standardization. + +4. **Contribute to the ecosystem**: + * Engage with the Superchain community to share feedback and propose improvements. + +## References + +* [OP Stack Specifications](https://specs.optimism.io/protocol/configurability.html) +* [Blockspace Charter](https://docs.optimism.io/superchain/blockspace-charter) +* [OP-Deployer Repository](https://github.com/ethereum-optimism/op-deployer) +* [Superchain Registry](https://github.com/ethereum-optimism/superchain-registry) diff --git a/words.txt b/words.txt index 23795ef2b..e9d6a704e 100644 --- a/words.txt +++ b/words.txt @@ -167,6 +167,7 @@ JSPATH jspath jwtsecret Keccak +Leane leveldb lightkdf logfile @@ -264,6 +265,7 @@ PPROF pprof Precommitments precommitments +Preconfigured preconfigured predeploy Predeployed From 165105b1d1876e48d9a9e9dfe920039932d6aebf Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Fri, 17 Jan 2025 16:15:18 +0100 Subject: [PATCH 02/37] fin lint issues --- pages/superchain/standard-configuration.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 152ba120a..74da4cbd4 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -50,7 +50,7 @@ Chains that deviate from these principles, such as introducing unsupported featu ## Role of OP-Deployer in Standardization -The [OP-Deployer](https://github.com/ethereum-optimism/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. +The [OP-Deployer](/builders/chain-operators/tools/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. Key features include: * **Preconfigured Templates**: @@ -158,5 +158,4 @@ The [Superchain Registry](/superchain/superchain-registry) is the authoritative * [OP Stack Specifications](https://specs.optimism.io/protocol/configurability.html) * [Blockspace Charter](https://docs.optimism.io/superchain/blockspace-charter) -* [OP-Deployer Repository](https://github.com/ethereum-optimism/op-deployer) * [Superchain Registry](https://github.com/ethereum-optimism/superchain-registry) From d7440724ea1c52e26cc66cff7e46896809762c32 Mon Sep 17 00:00:00 2001 From: krofax Date: Fri, 17 Jan 2025 16:21:28 +0100 Subject: [PATCH 03/37] Import callout --- pages/superchain/standard-configuration.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 74da4cbd4..22195d4a9 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -4,6 +4,8 @@ lang: en-US description: Leane about the standard configuration, how the OP-Deployer aids standardization, and why adhering to these standards is essential. --- +import { Callout } from 'nextra/components' + # Standard configuration in the OP Stack The **standard configuration** within the OP Stack ensures that chains deployed in the Superchain ecosystem adhere to a consistent set of technical and governance parameters. From ac92b86eb1d47ed90223891241398aac0ed50ef5 Mon Sep 17 00:00:00 2001 From: krofax Date: Fri, 17 Jan 2025 16:30:29 +0100 Subject: [PATCH 04/37] clean extra spaces --- pages/superchain/standard-configuration.mdx | 47 ++++++++++----------- 1 file changed, 23 insertions(+), 24 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 22195d4a9..57e47cd9a 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -8,7 +8,7 @@ import { Callout } from 'nextra/components' # Standard configuration in the OP Stack -The **standard configuration** within the OP Stack ensures that chains deployed in the Superchain ecosystem adhere to a consistent set of technical and governance parameters. +The standard configuration within the OP Stack ensures that chains deployed in the Superchain ecosystem adhere to a consistent set of technical and governance parameters. This standardization is critical for interoperability, network integrity, and ease of integration across the Superchain. This guide provides an in-depth explanation of what defines a standard configuration, how the OP-Deployer aids standardization, and why adhering to these standards is essential. @@ -17,7 +17,7 @@ This guide provides an in-depth explanation of what defines a standard configura A standard chain in the OP Stack refers to a rollup that adheres to the following principles: -1. **Technical conformance**: +1. Technical conformance: * Compliance with the OP Stack Specifications, including gas fees, block structure, and other protocol-level parameters. These requirements are currently a draft, pending governance approval. For more details, please see this [governance thread](https://gov.optimism.io/t/season-6-draft-standard-rollup-charter/8135) @@ -26,26 +26,25 @@ A standard chain in the OP Stack refers to a rollup that adheres to the followin A standard OP Stack chain must implement: -* **Protocol Contracts** +* Protocol Contracts: * Standard L1 contracts for cross-domain messaging * Specified bridge implementations - * Standard governance contracts -* **System Configuration** +* System Configuration * Standard L2 block time * Specified gas parameters * Default system addresses -* **Network Settings** +* Network Settings: * Standard RPC endpoints * Specified network parameters * Compatible chain ID allocation -2. **Governance alignment**: +2. Governance alignment: * Adherence to governance principles outlined in the [Blockspace Charter](/superchain/blockspace-charter). * Transparent and collaborative decision-making aligned with the Superchain ecosystem. -3. **Interoperability**: +3. Interoperability: * Maintaining compatibility with other chains in the Superchain ecosystem for seamless cross-chain interactions. Chains that deviate from these principles, such as introducing unsupported features like custom gas tokens, are considered non-standard configurations. @@ -55,13 +54,13 @@ Chains that deviate from these principles, such as introducing unsupported featu The [OP-Deployer](/builders/chain-operators/tools/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. Key features include: -* **Preconfigured Templates**: +* Preconfigured templates: * OP-Deployer provides templates that encapsulate best practices, ensuring that your chain is configured according to standard specifications. -* **Automated Validations**: +* Automated validations: * The tool performs checks during the deployment process to flag any deviations from standard configurations, such as unsupported modules or governance misalignments. -* **Ease of Customization within standards**: +* Ease of customization within standards: * While ensuring compliance, OP-Deployer allows for minor, non-breaking customizations to suit specific use cases. By using OP-Deployer, developers can reduce the complexity of chain deployment while ensuring alignment with Superchain standards. @@ -76,16 +75,16 @@ By using OP-Deployer, developers can reduce the complexity of chain deployment w Standardization benefits the Superchain ecosystem in several ways: -* **Interoperability**: +* Interoperability: * Enables seamless interactions between chains, such as cross-chain messaging and token transfers. -* **Simplified Development**: +* Simplified Development: * Reduces the learning curve for developers by providing consistent and predictable configurations. -* **Ecosystem Growth**: +* Ecosystem Growth: * Encourages a thriving ecosystem by lowering barriers to entry and fostering collaboration. -* **Reduced Support Overhead**: +* Reduced Support Overhead: * Minimizes the need for custom support by ensuring uniformity across deployments. @@ -109,10 +108,10 @@ Standardization benefits the Superchain ecosystem in several ways: Certain configurations are explicitly not part of the standard setup. For example: -* **Custom Gas Tokens**: +* Custom Gas Tokens: * Introducing a gas token other than the default is currently not considered standard. -* **Non-Conforming Modules**: +* Non-Conforming Modules: * Using modules not officially supported by the OP Stack. * Custom gas tokens: @@ -133,27 +132,27 @@ For a detailed list of standard configurations, refer to the [Standard rollup co The [Superchain Registry](/superchain/superchain-registry) is the authoritative index of all chains within the Superchain ecosystem. It ensures: -* **Transparency**: +* Transparency: * All registered chains are publicly listed with their configurations. -* **Compliance verification**: +* Compliance verification: * Chains listed in the registry are verified for adherence to the standard configuration. -* **Community trust**: +* Community trust: * Being part of the registry signals reliability and alignment with Superchain principles. ## Next Steps -1. **Understand standards**: +1. Understand standards: * Familiarize yourself with the [Op Stack specifications](https://specs.optimism.io/protocol/configurability.html) and the Blockspace Charter. -2. **Use OP-Deployer**: +2. Use OP-Deployer: * Leverage OP-Deployer to ensure your chain aligns with standard configurations. -3. **Seek guidance**: +3. Seek guidance: * Consult the [developer support](https://github.com/ethereum-optimism/developers/discussions) team for clarifications on standardization. -4. **Contribute to the ecosystem**: +4. Contribute to the ecosystem: * Engage with the Superchain community to share feedback and propose improvements. ## References From 02c69d4e6ea637b3d122835d3d1b453decb687d3 Mon Sep 17 00:00:00 2001 From: krofax Date: Fri, 17 Jan 2025 16:32:21 +0100 Subject: [PATCH 05/37] clean syntax error --- pages/superchain/standard-configuration.mdx | 30 ++++++++++----------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 57e47cd9a..7bad77481 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -76,19 +76,19 @@ By using OP-Deployer, developers can reduce the complexity of chain deployment w Standardization benefits the Superchain ecosystem in several ways: * Interoperability: - * Enables seamless interactions between chains, such as cross-chain messaging and token transfers. + Enables seamless interactions between chains, such as cross-chain messaging and token transfers. * Simplified Development: - * Reduces the learning curve for developers by providing consistent and predictable configurations. + Reduces the learning curve for developers by providing consistent and predictable configurations. * Ecosystem Growth: - * Encourages a thriving ecosystem by lowering barriers to entry and fostering collaboration. + Encourages a thriving ecosystem by lowering barriers to entry and fostering collaboration. * Reduced Support Overhead: + Minimizes the need for custom support by ensuring uniformity across deployments. - * Minimizes the need for custom support by ensuring uniformity across deployments. - - Native ETH as gas token: All transactions on the network must use ETH for gas payments, maintaining consistency with Ethereum's native token model. + Native ETH as gas token: + All transactions on the network must use ETH for gas payments, maintaining consistency with Ethereum's native token model. ### Standard feature @@ -109,10 +109,10 @@ Standardization benefits the Superchain ecosystem in several ways: Certain configurations are explicitly not part of the standard setup. For example: * Custom Gas Tokens: - * Introducing a gas token other than the default is currently not considered standard. + Introducing a gas token other than the default is currently not considered standard. * Non-Conforming Modules: - * Using modules not officially supported by the OP Stack. + Using modules not officially supported by the OP Stack. * Custom gas tokens: Using tokens other than ETH for gas payments deviates from the standard and isn't currently supported in the Superchain ecosystem. @@ -133,27 +133,27 @@ For a detailed list of standard configurations, refer to the [Standard rollup co The [Superchain Registry](/superchain/superchain-registry) is the authoritative index of all chains within the Superchain ecosystem. It ensures: * Transparency: - * All registered chains are publicly listed with their configurations. + All registered chains are publicly listed with their configurations. * Compliance verification: - * Chains listed in the registry are verified for adherence to the standard configuration. + Chains listed in the registry are verified for adherence to the standard configuration. * Community trust: - * Being part of the registry signals reliability and alignment with Superchain principles. + Being part of the registry signals reliability and alignment with Superchain principles. ## Next Steps 1. Understand standards: - * Familiarize yourself with the [Op Stack specifications](https://specs.optimism.io/protocol/configurability.html) and the Blockspace Charter. + Familiarize yourself with the [Op Stack specifications](https://specs.optimism.io/protocol/configurability.html) and the Blockspace Charter. 2. Use OP-Deployer: - * Leverage OP-Deployer to ensure your chain aligns with standard configurations. + Leverage OP-Deployer to ensure your chain aligns with standard configurations. 3. Seek guidance: - * Consult the [developer support](https://github.com/ethereum-optimism/developers/discussions) team for clarifications on standardization. + Consult the [developer support](https://github.com/ethereum-optimism/developers/discussions) team for clarifications on standardization. 4. Contribute to the ecosystem: - * Engage with the Superchain community to share feedback and propose improvements. + Engage with the Superchain community to share feedback and propose improvements. ## References From 40a58791e33e5717332f65884170a78b0505e8f7 Mon Sep 17 00:00:00 2001 From: krofax Date: Fri, 17 Jan 2025 16:32:39 +0100 Subject: [PATCH 06/37] added links --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 7bad77481..5d14c3457 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -158,5 +158,5 @@ The [Superchain Registry](/superchain/superchain-registry) is the authoritative ## References * [OP Stack Specifications](https://specs.optimism.io/protocol/configurability.html) -* [Blockspace Charter](https://docs.optimism.io/superchain/blockspace-charter) +* [Blockspace Charter](/superchain/blockspace-charter) * [Superchain Registry](https://github.com/ethereum-optimism/superchain-registry) From f03bebd908b980d93307e9cf9191fa0d29a1b2e8 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Fri, 17 Jan 2025 16:34:31 +0100 Subject: [PATCH 07/37] Update words.txt Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- words.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/words.txt b/words.txt index e9d6a704e..784d3a3f5 100644 --- a/words.txt +++ b/words.txt @@ -167,7 +167,7 @@ JSPATH jspath jwtsecret Keccak -Leane +Learn leveldb lightkdf logfile From eda4386b537d82340ab10fa7d8108cea6bf1a23d Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Fri, 17 Jan 2025 16:34:52 +0100 Subject: [PATCH 08/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 5d14c3457..fee709d46 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -1,7 +1,7 @@ --- title: Standard configuration lang: en-US -description: Leane about the standard configuration, how the OP-Deployer aids standardization, and why adhering to these standards is essential. +description: Learn about the standard configuration, how the OP-Deployer aids standardization, and why adhering to these standards is essential. --- import { Callout } from 'nextra/components' From d7048d04b3f4f3821cf9173ac85bbfe132722218 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Fri, 17 Jan 2025 17:05:10 +0100 Subject: [PATCH 09/37] made indentation fixes --- pages/superchain/_meta.json | 2 +- pages/superchain/standard-configuration.mdx | 84 +++++++-------------- 2 files changed, 29 insertions(+), 57 deletions(-) diff --git a/pages/superchain/_meta.json b/pages/superchain/_meta.json index beff32e4d..e60b9015b 100644 --- a/pages/superchain/_meta.json +++ b/pages/superchain/_meta.json @@ -2,5 +2,5 @@ "superchain-explainer": "The Superchain explainer", "superchain-registry": "The Superchain Registry", "blockspace-charter": "Blockspace Charters and the Standard Rollup Charter", - "standard-configuration": "Standard Configuration" + "standard-configuration": "The Standard configuration" } diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index fee709d46..36c9606b6 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -6,7 +6,7 @@ description: Learn about the standard configuration, how the OP-Deployer aids st import { Callout } from 'nextra/components' -# Standard configuration in the OP Stack +# The Standard configuration The standard configuration within the OP Stack ensures that chains deployed in the Superchain ecosystem adhere to a consistent set of technical and governance parameters. This standardization is critical for interoperability, network integrity, and ease of integration across the Superchain. @@ -17,34 +17,18 @@ This guide provides an in-depth explanation of what defines a standard configura A standard chain in the OP Stack refers to a rollup that adheres to the following principles: -1. Technical conformance: +1. **Technical conformance:** * Compliance with the OP Stack Specifications, including gas fees, block structure, and other protocol-level parameters. These requirements are currently a draft, pending governance approval. For more details, please see this [governance thread](https://gov.optimism.io/t/season-6-draft-standard-rollup-charter/8135) and the actual requirements in the [OP Stack Configurability Specification](https://specs.optimism.io/protocol/configurability.html). * Utilization of officially supported features and modules of the OP Stack. -A standard OP Stack chain must implement: - -* Protocol Contracts: - * Standard L1 contracts for cross-domain messaging - * Specified bridge implementations - -* System Configuration - * Standard L2 block time - * Specified gas parameters - * Default system addresses - -* Network Settings: - * Standard RPC endpoints - * Specified network parameters - * Compatible chain ID allocation - -2. Governance alignment: +2. **Governance alignment:** * Adherence to governance principles outlined in the [Blockspace Charter](/superchain/blockspace-charter). * Transparent and collaborative decision-making aligned with the Superchain ecosystem. -3. Interoperability: +3. **Interoperability:** * Maintaining compatibility with other chains in the Superchain ecosystem for seamless cross-chain interactions. Chains that deviate from these principles, such as introducing unsupported features like custom gas tokens, are considered non-standard configurations. @@ -54,14 +38,14 @@ Chains that deviate from these principles, such as introducing unsupported featu The [OP-Deployer](/builders/chain-operators/tools/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. Key features include: -* Preconfigured templates: - * OP-Deployer provides templates that encapsulate best practices, ensuring that your chain is configured according to standard specifications. +* **Preconfigured templates:** + OP-Deployer provides templates that encapsulate best practices, ensuring that your chain is configured according to standard specifications. -* Automated validations: - * The tool performs checks during the deployment process to flag any deviations from standard configurations, such as unsupported modules or governance misalignments. +* **Automated validations:** + The tool performs checks during the deployment process to flag any deviations from standard configurations, such as unsupported modules or governance misalignments. -* Ease of customization within standards: - * While ensuring compliance, OP-Deployer allows for minor, non-breaking customizations to suit specific use cases. +* **Ease of customization within standards:** + While ensuring compliance, OP-Deployer allows for minor, non-breaking customizations to suit specific use cases. By using OP-Deployer, developers can reduce the complexity of chain deployment while ensuring alignment with Superchain standards. @@ -75,55 +59,43 @@ By using OP-Deployer, developers can reduce the complexity of chain deployment w Standardization benefits the Superchain ecosystem in several ways: -* Interoperability: +* **Interoperability:** Enables seamless interactions between chains, such as cross-chain messaging and token transfers. -* Simplified Development: +* **Simplified Development:** Reduces the learning curve for developers by providing consistent and predictable configurations. -* Ecosystem Growth: +* **Ecosystem Growth:** Encourages a thriving ecosystem by lowering barriers to entry and fostering collaboration. -* Reduced Support Overhead: +* **Reduced Support Overhead:** Minimizes the need for custom support by ensuring uniformity across deployments. - Native ETH as gas token: + **Native ETH as gas token:** All transactions on the network must use ETH for gas payments, maintaining consistency with Ethereum's native token model. ### Standard feature -* Standard block time (2s): - Blocks must be produced every 2 seconds to ensure predictable transaction processing and network synchronization. - -* Default system contracts: +* **Default system contracts:** Core protocol contracts must use unmodified implementations provided by the OP Stack to guarantee security and compatibility. -* Standard bridge implementations: +* **Standard bridge implementations:** Cross-chain communication must use official bridge contracts to ensure secure and standardized asset transfers. -* Specified sequencer configurations: +* **Specified sequencer configurations:** Sequencer settings must follow prescribed parameters for transaction ordering and submission to maintain network stability. ## What is Not Standard? Certain configurations are explicitly not part of the standard setup. For example: -* Custom Gas Tokens: +* **Custom Gas Tokens:** Introducing a gas token other than the default is currently not considered standard. -* Non-Conforming Modules: +* **Non-Conforming Modules:** Using modules not officially supported by the OP Stack. -* Custom gas tokens: - Using tokens other than ETH for gas payments deviates from the standard and isn't currently supported in the Superchain ecosystem. - -* Modified block times: - Changing the 2-second block time breaks network synchronization expectations and isn't compatible with standard configurations. - -* Custom bridge implementations: - Using modified or custom bridge contracts risks security and interoperability, making them non-standard. - -* Modified system contracts: +* **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). @@ -132,27 +104,27 @@ For a detailed list of standard configurations, refer to the [Standard rollup co The [Superchain Registry](/superchain/superchain-registry) is the authoritative index of all chains within the Superchain ecosystem. It ensures: -* Transparency: +* **Transparency:** All registered chains are publicly listed with their configurations. -* Compliance verification: +* **Compliance verification:** Chains listed in the registry are verified for adherence to the standard configuration. -* Community trust: +* **Community trust:** Being part of the registry signals reliability and alignment with Superchain principles. ## Next Steps -1. Understand standards: +1. **Understand standards:** Familiarize yourself with the [Op Stack specifications](https://specs.optimism.io/protocol/configurability.html) and the Blockspace Charter. -2. Use OP-Deployer: +2. **Use OP-Deployer:** Leverage OP-Deployer to ensure your chain aligns with standard configurations. -3. Seek guidance: +3. **Seek guidance:** Consult the [developer support](https://github.com/ethereum-optimism/developers/discussions) team for clarifications on standardization. -4. Contribute to the ecosystem: +4. **Contribute to the ecosystem:** Engage with the Superchain community to share feedback and propose improvements. ## References From fd1a28e2d779118e54503fd36f94057d85387cef Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Fri, 17 Jan 2025 17:37:08 +0100 Subject: [PATCH 10/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 36c9606b6..2a03587e5 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -74,7 +74,7 @@ Standardization benefits the Superchain ecosystem in several ways: **Native ETH as gas token:** All transactions on the network must use ETH for gas payments, maintaining consistency with Ethereum's native token model. -### Standard feature +### Standard features * **Default system contracts:** Core protocol contracts must use unmodified implementations provided by the OP Stack to guarantee security and compatibility. From 89c070edba1259d639941bb9f2591aaf24bead86 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Fri, 17 Jan 2025 17:37:22 +0100 Subject: [PATCH 11/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 2a03587e5..32032efc9 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -116,7 +116,7 @@ The [Superchain Registry](/superchain/superchain-registry) is the authoritative ## Next Steps 1. **Understand standards:** - Familiarize yourself with the [Op Stack specifications](https://specs.optimism.io/protocol/configurability.html) and the Blockspace Charter. + Familiarize yourself with the [OP Stack specifications](https://specs.optimism.io/protocol/configurability.html) and the Blockspace Charter. 2. **Use OP-Deployer:** Leverage OP-Deployer to ensure your chain aligns with standard configurations. From f0739a6d906d4bd58bba1b20c55e62a9b5c10e6d Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:43:34 +0100 Subject: [PATCH 12/37] updated description Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 32032efc9..39a9430e5 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -1,7 +1,7 @@ --- title: Standard configuration lang: en-US -description: Learn about the standard configuration, how the OP-Deployer aids standardization, and why adhering to these standards is essential. +description: Learn what makes a chain standard, how op-deployer helps with standardization, and why being standard matters. --- import { Callout } from 'nextra/components' From 568cd7db00dcfa6c06e2f0decc45046867bf8a0b Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:44:07 +0100 Subject: [PATCH 13/37] updated standardization comment Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 39a9430e5..f65451097 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -9,7 +9,7 @@ import { Callout } from 'nextra/components' # The Standard configuration The standard configuration within the OP Stack ensures that chains deployed in the Superchain ecosystem adhere to a consistent set of technical and governance parameters. -This standardization is critical for interoperability, network integrity, and ease of integration across the Superchain. +This standardization is critical for Superchain interoperability, network security, and ease of upgrading your chain. This guide provides an in-depth explanation of what defines a standard configuration, how the OP-Deployer aids standardization, and why adhering to these standards is essential. From 5af7697ea91660bc8361bebb4864940aaadfd3fc Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:44:38 +0100 Subject: [PATCH 14/37] updated meta json --- pages/superchain/_meta.json | 2 +- pages/superchain/standard-configuration.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/superchain/_meta.json b/pages/superchain/_meta.json index e60b9015b..47b18a2f5 100644 --- a/pages/superchain/_meta.json +++ b/pages/superchain/_meta.json @@ -2,5 +2,5 @@ "superchain-explainer": "The Superchain explainer", "superchain-registry": "The Superchain Registry", "blockspace-charter": "Blockspace Charters and the Standard Rollup Charter", - "standard-configuration": "The Standard configuration" + "standard-configuration": "What makes a chain standard" } diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 32032efc9..19c48e335 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -1,12 +1,12 @@ --- -title: Standard configuration +title: What makes a chain standard? lang: en-US description: Learn about the standard configuration, how the OP-Deployer aids standardization, and why adhering to these standards is essential. --- import { Callout } from 'nextra/components' -# The Standard configuration +# What makes a chain standard? The standard configuration within the OP Stack ensures that chains deployed in the Superchain ecosystem adhere to a consistent set of technical and governance parameters. This standardization is critical for interoperability, network integrity, and ease of integration across the Superchain. From 1f8db948bca3597ab178656f0f8da1a58ffd04b3 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:46:22 +0100 Subject: [PATCH 15/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index f65451097..2a05c915a 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -18,7 +18,7 @@ This guide provides an in-depth explanation of what defines a standard configura A standard chain in the OP Stack refers to a rollup that adheres to the following principles: 1. **Technical conformance:** - * Compliance with the OP Stack Specifications, including gas fees, block structure, and other protocol-level parameters. + * Compliance with the consensus parameters, policy parameters, admin roles, and service roles defined in the specifications. These requirements are currently a draft, pending governance approval. For more details, please see this [governance thread](https://gov.optimism.io/t/season-6-draft-standard-rollup-charter/8135) and the actual requirements in the [OP Stack Configurability Specification](https://specs.optimism.io/protocol/configurability.html). From fcf5e79e00e93151c63c1ec1a7eaed5939e28d93 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:46:33 +0100 Subject: [PATCH 16/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 2a05c915a..8fe2700f5 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -92,8 +92,6 @@ Certain configurations are explicitly not part of the standard setup. For exampl * **Custom Gas Tokens:** Introducing a gas token other than the default is currently not considered standard. -* **Non-Conforming Modules:** - Using modules not officially supported by the OP Stack. * **Modified system contracts:** Any alterations to core system contracts break standardization and aren't supported in the official OP Stack specification. From ba16dd9d4d6c11389656b417cf6602391620f823 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:46:54 +0100 Subject: [PATCH 17/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 8fe2700f5..a1ed214a0 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -19,9 +19,7 @@ A standard chain in the OP Stack refers to a rollup that adheres to the followin 1. **Technical conformance:** * Compliance with the consensus parameters, policy parameters, admin roles, and service roles defined in the specifications. - These requirements are currently a draft, pending governance approval. For more details, please see - this [governance thread](https://gov.optimism.io/t/season-6-draft-standard-rollup-charter/8135) - and the actual requirements in the [OP Stack Configurability Specification](https://specs.optimism.io/protocol/configurability.html). + For more details, please see the [OP Stack Configurability Specification](https://specs.optimism.io/protocol/configurability.html). * Utilization of officially supported features and modules of the OP Stack. 2. **Governance alignment:** From 0302205a580acf7b658a2cbfc21368e13c04ca5c Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:47:03 +0100 Subject: [PATCH 18/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index a1ed214a0..70acf10b1 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -103,8 +103,8 @@ The [Superchain Registry](/superchain/superchain-registry) is the authoritative * **Transparency:** All registered chains are publicly listed with their configurations. -* **Compliance verification:** - Chains listed in the registry are verified for adherence to the standard configuration. +* **Superchain levels:** + Chains listed in the registry are denoted with a [`superchain_level`](https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/glossary.md#superchain-level-and-rollup-stage) which tells you which chains are standard. * **Community trust:** Being part of the registry signals reliability and alignment with Superchain principles. From c05b1cc28e7ff6a4fb000c3068e15c412ccf306f Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:47:10 +0100 Subject: [PATCH 19/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 70acf10b1..82b97ca84 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -107,7 +107,7 @@ The [Superchain Registry](/superchain/superchain-registry) is the authoritative Chains listed in the registry are denoted with a [`superchain_level`](https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/glossary.md#superchain-level-and-rollup-stage) which tells you which chains are standard. * **Community trust:** - Being part of the registry signals reliability and alignment with Superchain principles. + Being part of the registry signals reliability and alignment with Optimism Collective principles. ## Next Steps From 1b0baaa9ac1e9698ebb0cd0a3845995e16e2c061 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:47:18 +0100 Subject: [PATCH 20/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 82b97ca84..fb67af91c 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -121,7 +121,7 @@ The [Superchain Registry](/superchain/superchain-registry) is the authoritative Consult the [developer support](https://github.com/ethereum-optimism/developers/discussions) team for clarifications on standardization. 4. **Contribute to the ecosystem:** - Engage with the Superchain community to share feedback and propose improvements. + Engage with the [Optimism Collective](https://community.optimism.io/) to share feedback and propose improvements. ## References From 6c02432edc15c4f8b3e050bab5f038e156c1c3ec Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:47:26 +0100 Subject: [PATCH 21/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index fb67af91c..d412a83cc 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -114,8 +114,8 @@ The [Superchain Registry](/superchain/superchain-registry) is the authoritative 1. **Understand standards:** Familiarize yourself with the [OP Stack specifications](https://specs.optimism.io/protocol/configurability.html) and the Blockspace Charter. -2. **Use OP-Deployer:** - Leverage OP-Deployer to ensure your chain aligns with standard configurations. +2. **Use op-deployer:** + Leverage op-deployer to ensure your chain aligns with standard configurations. 3. **Seek guidance:** Consult the [developer support](https://github.com/ethereum-optimism/developers/discussions) team for clarifications on standardization. From f5f40066a7c3bd2a25ce8163207c97cd4e566006 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:47:46 +0100 Subject: [PATCH 22/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index d412a83cc..2f934085b 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -77,8 +77,6 @@ Standardization benefits the Superchain ecosystem in several ways: * **Default system contracts:** Core protocol contracts must use unmodified implementations provided by the OP Stack to guarantee security and compatibility. -* **Standard bridge implementations:** - Cross-chain communication must use official bridge contracts to ensure secure and standardized asset transfers. * **Specified sequencer configurations:** Sequencer settings must follow prescribed parameters for transaction ordering and submission to maintain network stability. From 4720a1e3cc55c5a46518510935a7b8057fb7abbf Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:48:03 +0100 Subject: [PATCH 23/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 2f934085b..32f38001e 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -23,7 +23,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 governance principles outlined in the [Blockspace Charter](/superchain/blockspace-charter). + * Adherence to the [Standard Rollup Charter](/superchain/blockspace-charter#the-standard-rollup-charter). * Transparent and collaborative decision-making aligned with the Superchain ecosystem. 3. **Interoperability:** From 73fcc9ed9039918fc98e5ae5f70a66e9ebcc7e62 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:48:30 +0100 Subject: [PATCH 24/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 32f38001e..9c201946c 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -27,7 +27,7 @@ A standard chain in the OP Stack refers to a rollup that adheres to the followin * Transparent and collaborative decision-making aligned with the Superchain ecosystem. 3. **Interoperability:** - * Maintaining compatibility with other chains in the Superchain ecosystem for seamless cross-chain interactions. + * Maintaining compatibility with the Superchain protocol level cross-chain interactions. Chains that deviate from these principles, such as introducing unsupported features like custom gas tokens, are considered non-standard configurations. From 5a11ad5eb3c8b1c408ecb01a864b6ba356425628 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:48:48 +0100 Subject: [PATCH 25/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 9c201946c..5b6c34f9d 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -31,7 +31,7 @@ A standard chain in the OP Stack refers to a rollup that adheres to the followin Chains that deviate from these principles, such as introducing unsupported features like custom gas tokens, are considered non-standard configurations. -## Role of OP-Deployer in Standardization +## Role of op-deployer in standardization The [OP-Deployer](/builders/chain-operators/tools/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. Key features include: From 9bc9f2c897e9e574b4931dc97055d8af91106786 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:49:05 +0100 Subject: [PATCH 26/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 5b6c34f9d..28d58f73f 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -33,7 +33,7 @@ Chains that deviate from these principles, such as introducing unsupported featu ## Role of op-deployer in standardization -The [OP-Deployer](/builders/chain-operators/tools/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. +The [op-deployer](/builders/chain-operators/tools/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. Key features include: * **Preconfigured templates:** From af3410700883041462be35c624a82f9914467bc0 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:49:19 +0100 Subject: [PATCH 27/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 28d58f73f..ea7920ad3 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -36,8 +36,8 @@ Chains that deviate from these principles, such as introducing unsupported featu The [op-deployer](/builders/chain-operators/tools/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. Key features include: -* **Preconfigured templates:** - OP-Deployer provides templates that encapsulate best practices, ensuring that your chain is configured according to standard specifications. +* **Default values:** + op-deployer provides default values that adhere to standard specifications. * **Automated validations:** The tool performs checks during the deployment process to flag any deviations from standard configurations, such as unsupported modules or governance misalignments. From 1d44c66f1e79310e7f5e496e63891d30794f10c0 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:49:32 +0100 Subject: [PATCH 28/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index ea7920ad3..5252a4933 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -39,8 +39,6 @@ Key features include: * **Default values:** op-deployer provides default values that adhere to standard specifications. -* **Automated validations:** - The tool performs checks during the deployment process to flag any deviations from standard configurations, such as unsupported modules or governance misalignments. * **Ease of customization within standards:** While ensuring compliance, OP-Deployer allows for minor, non-breaking customizations to suit specific use cases. From e23a1ed686bca6941da04325e375774d08cd98f4 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:50:08 +0100 Subject: [PATCH 29/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 5252a4933..ae22a8a9c 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -41,7 +41,7 @@ Key features include: * **Ease of customization within standards:** - While ensuring compliance, OP-Deployer allows for minor, non-breaking customizations to suit specific use cases. + The op-deployer tool allows for overriding default values. For example, you can override the L2 block time to 1s, which is standard. However, please ensure you know what you're doing when applying overrides because they may violate standard specifications. By using OP-Deployer, developers can reduce the complexity of chain deployment while ensuring alignment with Superchain standards. From 84f5aac64747580baa505da4169bf95357a85912 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:50:29 +0100 Subject: [PATCH 30/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index ae22a8a9c..c82045c4a 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -43,7 +43,7 @@ Key features include: * **Ease of customization within standards:** The op-deployer tool allows for overriding default values. For example, you can override the L2 block time to 1s, which is standard. However, please ensure you know what you're doing when applying overrides because they may violate standard specifications. -By using OP-Deployer, developers can reduce the complexity of chain deployment while ensuring alignment with Superchain standards. +By using op-deployer, chain operators can reduce the complexity of chain deployment while ensuring alignment with Superchain standards. The Rollup configuration is an active work in progress and will likely evolve From a946a995335073db07eb45b95da8d9d7e7675b01 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:50:45 +0100 Subject: [PATCH 31/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 5 ----- 1 file changed, 5 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index c82045c4a..186eb0d1a 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -45,11 +45,6 @@ Key features include: By using op-deployer, chain operators can reduce the complexity of chain deployment while ensuring alignment with Superchain standards. - - The Rollup configuration is an active work in progress and will likely evolve - significantly as time goes on. If something isn't working about your - configuration, you can refer to the [source code](https://github.com/ethereum-optimism/optimism/blob/develop/op-chain-ops/genesis/config.go). - ## Why standardization matters From 4b5621672265a0fa9ddf1d5b4c3bd4fa5121fe75 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:57:24 +0100 Subject: [PATCH 32/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 186eb0d1a..17850497a 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -51,7 +51,7 @@ By using op-deployer, chain operators can reduce the complexity of chain deploym Standardization benefits the Superchain ecosystem in several ways: * **Interoperability:** - Enables seamless interactions between chains, such as cross-chain messaging and token transfers. + A standard stack and security model makes your chain eligible for interactions between other standard chains, such as single block cross-chain messaging and token transfers. * **Simplified Development:** Reduces the learning curve for developers by providing consistent and predictable configurations. From b52a2cbf3a8267bfc5107d108476a7ebbe459427 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:57:49 +0100 Subject: [PATCH 33/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 17850497a..956abae5c 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -53,8 +53,8 @@ Standardization benefits the Superchain ecosystem in several ways: * **Interoperability:** A standard stack and security model makes your chain eligible for interactions between other standard chains, such as single block cross-chain messaging and token transfers. -* **Simplified Development:** - Reduces the learning curve for developers by providing consistent and predictable configurations. +* **Simplified upgrade path:** + Reduces the complexity of upgrading your chain to the latest version. * **Ecosystem Growth:** Encourages a thriving ecosystem by lowering barriers to entry and fostering collaboration. From ededf8541eab72bb7be5299e00d39cc1c76860b2 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:58:33 +0100 Subject: [PATCH 34/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 956abae5c..559251994 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -68,7 +68,7 @@ Standardization benefits the Superchain ecosystem in several ways: ### Standard features * **Default system contracts:** - Core protocol contracts must use unmodified implementations provided by the OP Stack to guarantee security and compatibility. + Core protocol contracts must use governance approved release implementations of the OP Stack to provide security and compatibility. * **Specified sequencer configurations:** From c2b82086b901760de9a7aa4da43d933e39368807 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:58:50 +0100 Subject: [PATCH 35/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 559251994..d779afc43 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -56,8 +56,6 @@ Standardization benefits the Superchain ecosystem in several ways: * **Simplified upgrade path:** Reduces the complexity of upgrading your chain to the latest version. -* **Ecosystem Growth:** - Encourages a thriving ecosystem by lowering barriers to entry and fostering collaboration. * **Reduced Support Overhead:** Minimizes the need for custom support by ensuring uniformity across deployments. From 1c005eacd7ff2d15bad808350b8c45370d61704a Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 13:59:06 +0100 Subject: [PATCH 36/37] Update pages/superchain/standard-configuration.mdx Co-authored-by: soyboy <85043086+sbvegan@users.noreply.github.com> --- pages/superchain/standard-configuration.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index d779afc43..ca92bd990 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -60,8 +60,6 @@ Standardization benefits the Superchain ecosystem in several ways: * **Reduced Support Overhead:** Minimizes the need for custom support by ensuring uniformity across deployments. - **Native ETH as gas token:** - All transactions on the network must use ETH for gas payments, maintaining consistency with Ethereum's native token model. ### Standard features From 3e616c32582ce477cebe39259bd1fad83a718b0f Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Sun, 19 Jan 2025 14:00:52 +0100 Subject: [PATCH 37/37] resolve comments --- pages/superchain/standard-configuration.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 9639b99d9..4a9f2b42e 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -11,7 +11,7 @@ import { Callout } from 'nextra/components' The standard configuration within the OP Stack ensures that chains deployed in the Superchain ecosystem adhere to a consistent set of technical and governance parameters. This standardization is critical for Superchain interoperability, network security, and ease of upgrading your chain. -This guide provides an in-depth explanation of what defines a standard configuration, how the OP-Deployer aids standardization, and why adhering to these standards is essential. +This guide provides an in-depth explanation of what defines a standard configuration, how the [op-deployer](/builders/chain-operators/tools/op-deployer) aids standardization, and why adhering to these standards is essential. ## What is a Standard chain? @@ -33,21 +33,21 @@ A standard chain in the OP Stack refers to a rollup that adheres to the followin Chains that deviate from these principles, such as introducing unsupported features like custom gas tokens, are considered non-standard configurations. -## Role of OP-Deployer in Standardization +## Role of op-deployer in Standardization -The [OP-Deployer](/builders/chain-operators/tools/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. +The [op-deployer](/builders/chain-operators/tools/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. Key features include: * **Preconfigured templates:** - OP-Deployer provides templates that encapsulate best practices, ensuring that your chain is configured according to standard specifications. + op-deployer provides templates that encapsulate best practices, ensuring that your chain is configured according to standard specifications. * **Automated validations:** The tool performs checks during the deployment process to flag any deviations from standard configurations, such as unsupported modules or governance misalignments. * **Ease of customization within standards:** - While ensuring compliance, OP-Deployer allows for minor, non-breaking customizations to suit specific use cases. + While ensuring compliance, op-deployer allows for minor, non-breaking customizations to suit specific use cases. -By using OP-Deployer, developers can reduce the complexity of chain deployment while ensuring alignment with Superchain standards. +By using op-deployer, developers can reduce the complexity of chain deployment while ensuring alignment with Superchain standards. The Rollup configuration is an active work in progress and will likely evolve @@ -118,8 +118,8 @@ The [Superchain Registry](/superchain/superchain-registry) is the authoritative 1. **Understand standards:** Familiarize yourself with the [OP Stack specifications](https://specs.optimism.io/protocol/configurability.html) and the Blockspace Charter. -2. **Use OP-Deployer:** - Leverage OP-Deployer to ensure your chain aligns with standard configurations. +2. **Use op-deployer:** + Leverage op-deployer to ensure your chain aligns with standard configurations. 3. **Seek guidance:** Consult the [developer support](https://github.com/ethereum-optimism/developers/discussions) team for clarifications on standardization.