From 0893fc5104f91f0f4e4623f7295fe1dfe6c1e619 Mon Sep 17 00:00:00 2001 From: ddtrvlr <117272307+wearedood@users.noreply.github.com> Date: Mon, 24 Nov 2025 12:45:42 +0100 Subject: [PATCH] fix(docs): Correct Standard Rollup Charter link path The original link pointed to '/superchain/concepts/blockspace-charter' but should reference '/superchain/concepts/standard-rollup-charter' to match the actual Standard Rollup Charter document. This fix ensures developers can access the correct documentation when following links in the Superchain Registry guide. --- superchain/superchain-registry.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/superchain/superchain-registry.mdx b/superchain/superchain-registry.mdx index 3d0925467..86fa41ed3 100644 --- a/superchain/superchain-registry.mdx +++ b/superchain/superchain-registry.mdx @@ -15,10 +15,10 @@ An OP Stack Standard Rollup follows the Standard Rollup Charter. This configuration targets the Optimism Collective's highest bar for security, uptime, and decentralization. -You can find more details in the [Standard Rollup Charter documentation](/superchain/concepts/blockspace-charter). +You can find more details in the [Standard Rollup Charter documentation](/superchain/concepts/standard-rollup-charter). - We **strongly** recommend using the [op-deployer](/operators/chain-operators/tools/op-deployer) to deploy L1 contracts and generate the L2 genesis file that meets the configuration requirements outlined in the [Standard Rollup Charter](/superchain/concepts/blockspace-charter). + We **strongly** recommend using the [op-deployer](/operators/chain-operators/tools/op-deployer) to deploy L1 contracts and generate the L2 genesis file that meets the configuration requirements outlined in the [Standard Rollup Charter](/superchain/concepts/standard-rollup-charter). ## Joining the Registry