From 9c0d1476f04e3a41671e5c2f2eaf9cb830d92213 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Mon, 7 Apr 2025 20:36:48 +0100 Subject: [PATCH 1/5] add utm source --- components/Footer.tsx | 14 +++++++------- pages/app-developers/bridging/custom-bridge.mdx | 2 +- pages/app-developers/bridging/standard-bridge.mdx | 2 +- pages/app-developers/building-apps.mdx | 4 ++-- pages/app-developers/get-started.mdx | 6 +++--- pages/app-developers/tools.mdx | 6 +++--- pages/app-developers/tools/_meta.json | 2 +- pages/app-developers/tools/build.mdx | 4 ++-- pages/app-developers/tools/build/_meta.json | 2 +- .../tools/build/account-abstraction.mdx | 2 +- .../app-developers/tools/build/block-explorers.mdx | 4 ++-- pages/app-developers/tools/build/faucets.mdx | 6 +++--- pages/app-developers/tools/build/oracles.mdx | 2 +- .../app-developers/tools/connect/rpc-providers.mdx | 2 +- .../tutorials/bridging/cross-dom-bridge-erc20.mdx | 2 +- .../tutorials/bridging/cross-dom-solidity.mdx | 2 +- .../bridging/standard-bridge-custom-token.mdx | 4 ++-- .../bridging/standard-bridge-standard-token.mdx | 4 ++-- .../tutorials/transactions/sdk-estimate-costs.mdx | 2 +- .../tutorials/transactions/send-tx-from-eth.mdx | 2 +- pages/connect/contribute/docs-contribute.mdx | 2 +- pages/connect/contribute/stack-contribute.mdx | 4 ++-- pages/get-started/_meta.json | 2 +- pages/index.mdx | 8 ++++---- pages/notices/holocene-changes.mdx | 2 +- pages/notices/upgrade-14.mdx | 2 +- pages/operators/chain-operators/architecture.mdx | 2 +- .../chain-operators/configuration/batcher.mdx | 2 +- .../chain-operators/configuration/rollup.mdx | 8 ++++---- .../chain-operators/features/alt-da-mode.mdx | 4 ++-- .../chain-operators/features/span-batches.mdx | 2 +- .../chain-operators/tools/op-challenger.mdx | 2 +- .../chain-operators/tools/op-deployer.mdx | 2 +- .../chain-operators/tutorials/chain-dev-net.mdx | 4 ++-- .../chain-operators/tutorials/create-l2-rollup.mdx | 4 ++-- .../tutorials/integrating-da-layer.mdx | 2 +- .../node-operators/configuration/base-config.mdx | 2 +- .../configuration/execution-config.mdx | 2 +- pages/operators/node-operators/json-rpc.mdx | 2 +- .../management/regenesis-history.mdx | 2 +- .../node-operators/management/snapshots.mdx | 6 +++--- .../operators/node-operators/network-upgrades.mdx | 14 +++++++------- pages/stack/beta-features/alt-da-mode.mdx | 4 ++-- pages/stack/components.mdx | 10 +++++----- pages/stack/design-principles.mdx | 4 ++-- pages/stack/differences.mdx | 2 +- pages/stack/fact-sheet.mdx | 2 +- pages/stack/fault-proofs/cannon.mdx | 6 +++--- pages/stack/fault-proofs/challenger.mdx | 6 +++--- pages/stack/fault-proofs/explainer.mdx | 4 ++-- pages/stack/fault-proofs/fp-components.mdx | 4 ++-- pages/stack/fault-proofs/fp-security.mdx | 2 +- pages/stack/fault-proofs/mips.mdx | 4 ++-- pages/stack/interop/explainer.mdx | 2 +- pages/stack/opcm.mdx | 2 +- pages/stack/public-devnets.mdx | 2 +- pages/stack/smart-contracts.mdx | 6 +++--- 57 files changed, 107 insertions(+), 107 deletions(-) diff --git a/components/Footer.tsx b/components/Footer.tsx index 6a37e9726..244e121e2 100644 --- a/components/Footer.tsx +++ b/components/Footer.tsx @@ -29,11 +29,11 @@ export function Footer() {

Tools

@@ -44,7 +44,7 @@ export function Footer() {
  • Get Launch Support
  • Glossary
  • Contribute to the OP Stack
    • -
  • Protocol Specs
    • +
  • Protocol Specs
    • @@ -85,9 +85,9 @@ export function Footer() {
    - Community Agreement - Terms of Service - Privacy Policy + Community Agreement + Terms of Service + Privacy Policy Code of Conduct
    © {new Date().getFullYear()} Optimism Foundation. All rights reserved.
    diff --git a/pages/app-developers/bridging/custom-bridge.mdx b/pages/app-developers/bridging/custom-bridge.mdx index 24a33b7e9..9e105a09f 100644 --- a/pages/app-developers/bridging/custom-bridge.mdx +++ b/pages/app-developers/bridging/custom-bridge.mdx @@ -36,7 +36,7 @@ Consider directly extending or modifying the [`StandardBridge`](https://github.c Doing so will provide you with an audited foundation upon which you can add extra logic. If you choose not to extend the `StandardBridge` contract, you may still want to follow the interface that the `StandardBridge` provides. -Bridges that extend this interface will be compatible with the [Superchain Bridges UI](https://app.optimism.io/bridge). +Bridges that extend this interface will be compatible with the [Superchain Bridges UI](https://app.optimism.io/bridge?utm_source=op-docs&utm_medium=docs). You can read more about the design of the Standard Bridge in the guide on [Using the Standard Bridge](./standard-bridge). ## The Superchain Token List diff --git a/pages/app-developers/bridging/standard-bridge.mdx b/pages/app-developers/bridging/standard-bridge.mdx index 75bac9d26..0f5a934cc 100644 --- a/pages/app-developers/bridging/standard-bridge.mdx +++ b/pages/app-developers/bridging/standard-bridge.mdx @@ -222,7 +222,7 @@ The [Superchain Token List](/superchain/tokenlist) exists to help users discover Consider checking this list to make sure that you're not using the wrong bridged representation of a token when bridging a native token. Developers who are creating their own bridged tokens should consider [adding their token](https://github.com/ethereum-optimism/ethereum-optimism.github.io#adding-a-token-to-the-list) to the Superchain Token List. -Tokens on the Superchain Token List will automatically appear on certain tools like the [Superchain Bridges UI](https://app.optimism.io/bridge). +Tokens on the Superchain Token List will automatically appear on certain tools like the [Superchain Bridges UI](https://app.optimism.io/bridge?utm_source=op-docs&utm_medium=docs). ### Searching the Token List diff --git a/pages/app-developers/building-apps.mdx b/pages/app-developers/building-apps.mdx index 568de13d0..60b17ba1a 100644 --- a/pages/app-developers/building-apps.mdx +++ b/pages/app-developers/building-apps.mdx @@ -31,7 +31,7 @@ To access any Ethereum type network you need an endpoint. [These providers](/app For development purposes we recommend you use either a local development network or [OP Sepolia](https://sepolia-optimism.etherscan.io). That way you don't need to spend real money. -If you need ETH on OP Sepolia for testing purposes, [you can use this faucet](https://console.optimism.io/faucet?utm_source=docs). +If you need ETH on OP Sepolia for testing purposes, [you can use this faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs). ## Interacting with contracts on OP Stack chains @@ -72,4 +72,4 @@ You don't have to upload your source code to [block explorers](/app-developers/t On the test network, it lets you issue queries and transactions from the explorer's user interface. On the production network, it lets users know exactly what your contract does, which is conducive to trust. -Just remember, if you use [the Etherscan API](https://explorer.optimism.io/apis), you need one API key for OP Stack chains and a separate one for OP Sepolia. +Just remember, if you use [the Etherscan API](https://explorer.optimism.io/apis?utm_source=op-docs&utm_medium=docs), you need one API key for OP Stack chains and a separate one for OP Sepolia. diff --git a/pages/app-developers/get-started.mdx b/pages/app-developers/get-started.mdx index 5cc7fb3ea..7cf0619da 100644 --- a/pages/app-developers/get-started.mdx +++ b/pages/app-developers/get-started.mdx @@ -23,7 +23,7 @@ import { Cards, Card, Callout } from 'nextra/components' Reimagine your app with Superchain Interop to deliver the unified UX your users expect. Hack on net-new, bold use cases on Interop devnet. - Explore the [Superchain Dev Console](https://console.optimism.io/) to build, launch, and grow your app on the Superchain. + Explore the [Superchain Dev Console](https://console.optimism.io/?utm_source=op-docs&utm_medium=docs) to build, launch, and grow your app on the Superchain. ## Connect to Superchain Interop @@ -46,12 +46,12 @@ The SuperchainERC20 Starter Kit allows you to focus on what to deploy, not how t | Tool | Description | | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------- | -| [Superchain Faucet](https://console.optimism.io/faucet?utm_source=docs) | One stop shop to grab testnet ETH for any Superchain network. | +| [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) | One stop shop to grab testnet ETH for any Superchain network. | | [Supersim](tools/supersim) | Local multi-chain testing environment for smart contracts. | | [Super CLI](https://github.com/ethereum-optimism/super-cli) | Command-line tool for seamless multichain app deployment and testing. | | [Superchain Relayer](https://github.com/ethereum-optimism/superchain-relayer) | UI for monitoring and managing cross-chain transactions. | | [Interop Docs](/stack/interop) | Comprehensive Interop information in the Optimism Docs. | -| [Superchain Dev Console](https://console.optimism.io/) | Comprensive tool to build, launch, and grow your app on the Superchain. | +| [Superchain Dev Console](https://console.optimism.io/?utm_source=op-docs&utm_medium=docs) | Comprensive tool to build, launch, and grow your app on the Superchain. | ## Handy step-by-step guides diff --git a/pages/app-developers/tools.mdx b/pages/app-developers/tools.mdx index f9cc7d29e..21b2baa4e 100644 --- a/pages/app-developers/tools.mdx +++ b/pages/app-developers/tools.mdx @@ -45,13 +45,13 @@ If you are already familiar with [building on the OP Stack](/stack/getting-start } /> - } /> + } /> } /> - } /> + } /> - } /> + } /> } /> diff --git a/pages/app-developers/tools/_meta.json b/pages/app-developers/tools/_meta.json index 156a476ac..9b60290b9 100644 --- a/pages/app-developers/tools/_meta.json +++ b/pages/app-developers/tools/_meta.json @@ -1,7 +1,7 @@ { "console": { "title": "Superchain Dev Console", - "href": "https://console.optimism.io/?utm_source=docs", + "href": "https://console.optimism.io/?utm_source=op-docs&utm_medium=docs", "newWindow": true }, "supersim": "Supersim Multichain Dev Env", diff --git a/pages/app-developers/tools/build.mdx b/pages/app-developers/tools/build.mdx index 792c48cda..6ada1a1c7 100644 --- a/pages/app-developers/tools/build.mdx +++ b/pages/app-developers/tools/build.mdx @@ -25,7 +25,7 @@ This section provides information on account abstraction, block explorers, testn } /> - } /> + } /> } /> @@ -35,7 +35,7 @@ This section provides information on account abstraction, block explorers, testn } /> - } /> + } /> } /> diff --git a/pages/app-developers/tools/build/_meta.json b/pages/app-developers/tools/build/_meta.json index c6a61f289..383927462 100644 --- a/pages/app-developers/tools/build/_meta.json +++ b/pages/app-developers/tools/build/_meta.json @@ -8,7 +8,7 @@ "analytics-tools": "Analytics Tools", "bridge": { "title": "Superchain bridges", - "href": "https://app.optimism.io/bridge", + "href": "https://app.optimism.io/bridge/?utm_source=op-docs&utm_medium=docs", "newWindow": true }, "gas": { diff --git a/pages/app-developers/tools/build/account-abstraction.mdx b/pages/app-developers/tools/build/account-abstraction.mdx index db70f9fe3..1977a85d2 100644 --- a/pages/app-developers/tools/build/account-abstraction.mdx +++ b/pages/app-developers/tools/build/account-abstraction.mdx @@ -81,4 +81,4 @@ Developer teams who want to feature products/tools on this page must meet the fo 2. **established user base** and OP ecosystem engagement such as governance participation, homegrown TG or Discord participation, etc.; and 3. **actively maintained developer tool** that aligns with OP's commitment to a magical developer experience (e.g., easy-to-use, easy-to-integrate, great DevX, highly rated by community, etc.) -For teams that are supporting but still establishing a user base, we encourage you to share your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and signup to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/). +For teams that are supporting but still establishing a user base, we encourage you to share your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and signup to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/?utm_source=op-docs&utm_medium=docs). diff --git a/pages/app-developers/tools/build/block-explorers.mdx b/pages/app-developers/tools/build/block-explorers.mdx index 16c565a51..0423fc61b 100644 --- a/pages/app-developers/tools/build/block-explorers.mdx +++ b/pages/app-developers/tools/build/block-explorers.mdx @@ -94,7 +94,7 @@ Tenderly Developer Explorer lets you: ## Access to pre-regenesis history -Because of our final regenesis on 11 November 2021, older transactions are not part of the current blockchain and do not appear on [Etherscan](https://explorer.optimism.io/). +Because of our final regenesis on 11 November 2021, older transactions are not part of the current blockchain and do not appear on [Etherscan](https://explorer.optimism.io/?utm_source=op-docs&utm_medium=docs). However, you **can** access transaction history between 23 June 2021 and the final regenesis using a number of different tools. For detailed instructions, see [Regenesis History](/operators/node-operators/management/regenesis-history). ## Inclusion criteria @@ -106,7 +106,7 @@ Developer teams who want to feature products/tools on this page must meet the fo 3. **actively maintained developer tool** that aligns with OP's commitment to a magical developer experience (e.g., easy-to-use, easy-to-integrate, great DevX, highly-rated by community, etc.) For teams that are supporting but still establishing a user base, we encourage you to share your tool on the [community block explorers page](https://github.com/ethereum-optimism/developers/blob/main/community/tools/block-explorers.md). -You can also promote your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and signup to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/). +You can also promote your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and signup to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/?utm_source=op-docs&utm_medium=docs). ## Next Steps diff --git a/pages/app-developers/tools/build/faucets.mdx b/pages/app-developers/tools/build/faucets.mdx index 67aec3aa0..ffb98ce9a 100644 --- a/pages/app-developers/tools/build/faucets.mdx +++ b/pages/app-developers/tools/build/faucets.mdx @@ -36,7 +36,7 @@ Faucets can occasionally also run out of ETH, so if you're having trouble gettin ## Superchain faucet -The [Superchain Faucet](https://console.optimism.io/faucet?utm_source=docs) is a developer tool hosted by Optimism that allows developers to get free testnet ETH to test apps on testnet OP Chains like Base Sepolia, OP Sepolia, PGN Sepolia, Zora Sepolia, and other OP Chains in the Superchain. +The [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) is a developer tool hosted by Optimism that allows developers to get free testnet ETH to test apps on testnet OP Chains like Base Sepolia, OP Sepolia, PGN Sepolia, Zora Sepolia, and other OP Chains in the Superchain. The Superchain Faucet is a great place to start if you're looking for testnet ETH. ## Additional faucets @@ -57,7 +57,7 @@ The Superchain Faucet is a great place to start if you're looking for testnet ET ## Bridge from Sepolia -If you have testnet ETH on Sepolia, you can bridge it to OP Sepolia (and vice versa) using the [Superchain Bridges UI](https://app.optimism.io/bridge) or this collection of [Superchain Testnet Tools](https://www.superchain.tools/). +If you have testnet ETH on Sepolia, you can bridge it to OP Sepolia (and vice versa) using the [Superchain Bridges UI](https://app.optimism.io/bridge/?utm_source=op-docs&utm_medium=docs) or this collection of [Superchain Testnet Tools](https://www.superchain.tools/). ## Inclusion criteria @@ -68,7 +68,7 @@ Developer teams who want to feature products/tools on this page must meet the fo 3. **actively maintained developer tool** that aligns with OP's commitment to a magical developer experience (e.g., easy-to-use, easy-to-integrate, great DevX, highly-rated by community, etc.) For teams that are supporting but still establishing a user base, we encourage you to share your tool on the [community faucets page](https://github.com/ethereum-optimism/developers/blob/main/community/tools/faucets.md). -You can also promote your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and signup to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/). +You can also promote your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and signup to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/?utm_source=op-docs&utm_medium=docs). ## Next steps diff --git a/pages/app-developers/tools/build/oracles.mdx b/pages/app-developers/tools/build/oracles.mdx index 68ae84d2b..282cf7102 100644 --- a/pages/app-developers/tools/build/oracles.mdx +++ b/pages/app-developers/tools/build/oracles.mdx @@ -152,7 +152,7 @@ Developer teams who want to feature products/tools on this page must meet the fo 3. **actively maintained developer tool** that aligns with OP's commitment to a magical developer experience (e.g., easy-to-use, easy-to-integrate, great DevX, highly-rated by community, etc.) For teams that are supporting but still establishing a user base, we encourage you to share your tool on the [community oracles page](https://github.com/ethereum-optimism/developers/blob/main/community/tools/oracles.md). -You can also promote your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and signup to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/). +You can also promote your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and signup to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/?utm_source=op-docs&utm_medium=docs). ## Next steps diff --git a/pages/app-developers/tools/connect/rpc-providers.mdx b/pages/app-developers/tools/connect/rpc-providers.mdx index cfffa3878..183f7178b 100644 --- a/pages/app-developers/tools/connect/rpc-providers.mdx +++ b/pages/app-developers/tools/connect/rpc-providers.mdx @@ -179,7 +179,7 @@ Developer teams who want to feature products/tools on this page must meet the fo 3. **actively maintained developer tool** that aligns with OP's commitment to a magical developer experience (e.g., easy-to-use, easy-to-integrate, great DevX, highly-rated by community, etc.) For teams that are supporting but still establishing a user base, we encourage you to share your tool on the [community node providers page](https://github.com/ethereum-optimism/developers/blob/main/community/tools/node-providers.md). -You can also promote your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and signup to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/). +You can also promote your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and signup to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/?utm_source=op-docs&utm_medium=docs). ## Next steps diff --git a/pages/app-developers/tutorials/bridging/cross-dom-bridge-erc20.mdx b/pages/app-developers/tutorials/bridging/cross-dom-bridge-erc20.mdx index 9871a793f..cf7f98399 100644 --- a/pages/app-developers/tutorials/bridging/cross-dom-bridge-erc20.mdx +++ b/pages/app-developers/tutorials/bridging/cross-dom-bridge-erc20.mdx @@ -98,7 +98,7 @@ You will need to get some ETH on both of these testnets. You can use [this faucet](https://sepoliafaucet.com) to get ETH on Sepolia. You can use the [Superchain - Faucet](https://console.optimism.io/faucet?utm_source=docs) to get ETH on OP + Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) to get ETH on OP Sepolia. diff --git a/pages/app-developers/tutorials/bridging/cross-dom-solidity.mdx b/pages/app-developers/tutorials/bridging/cross-dom-solidity.mdx index 315fcb927..6816cd613 100644 --- a/pages/app-developers/tutorials/bridging/cross-dom-solidity.mdx +++ b/pages/app-developers/tutorials/bridging/cross-dom-solidity.mdx @@ -55,7 +55,7 @@ You will need to get some ETH on both of these testnets. You can use [this faucet](https://sepoliafaucet.com/) to get ETH on Sepolia. -You can use the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=docs) to get ETH on OP Sepolia. +You can use the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) to get ETH on OP Sepolia. ## Review the contracts diff --git a/pages/app-developers/tutorials/bridging/standard-bridge-custom-token.mdx b/pages/app-developers/tutorials/bridging/standard-bridge-custom-token.mdx index d8faaa108..ba0af4646 100644 --- a/pages/app-developers/tutorials/bridging/standard-bridge-custom-token.mdx +++ b/pages/app-developers/tutorials/bridging/standard-bridge-custom-token.mdx @@ -50,7 +50,7 @@ You will need to get some ETH on both of these testnets. You can use [this faucet](https://sepoliafaucet.com/) to get ETH on Sepolia. - You can use the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=docs) to get ETH on OP Sepolia. + You can use the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) to get ETH on OP Sepolia. ## Add OP Sepolia to your wallet @@ -135,5 +135,5 @@ This is exactly what this tutorial was meant to demonstrate. ## Add to the Superchain Token List The [Superchain Token List](https://github.com/ethereum-optimism/ethereum-optimism.github.io#readme) is a common list of tokens deployed on chains within the Optimism Superchain. -This list is used by services like the [Superchain Bridges UI](https://app.optimism.io/bridge). +This list is used by services like the [Superchain Bridges UI](https://app.optimism.io/bridge?utm_source=op-docs&utm_medium=docs). If you want your OP Mainnet token to be included in this list, take a look at the [review process and merge criteria](https://github.com/ethereum-optimism/ethereum-optimism.github.io#review-process-and-merge-criteria). diff --git a/pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx b/pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx index 6c90d391a..1fa7db3bd 100644 --- a/pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx +++ b/pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx @@ -48,7 +48,7 @@ You will need to get some ETH on both of these testnets. You can use [this faucet](https://sepoliafaucet.com) to get ETH on Sepolia. -You can use the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=docs) to get ETH on OP Sepolia. +You can use the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) to get ETH on OP Sepolia. ## Get an L1 ERC-20 token address @@ -110,5 +110,5 @@ Check out the tutorial on [Bridging ERC-20 tokens with viem](./cross-dom-bridge- ## Add to the Superchain Token List The [Superchain Token List](https://github.com/ethereum-optimism/ethereum-optimism.github.io#readme) is a common list of tokens deployed on chains within the Optimism Superchain. -This list is used by services like the [Superchain Bridges UI](https://app.optimism.io/bridge). +This list is used by services like the [Superchain Bridges UI](https://app.optimism.io/bridge?utm_source=op-docs&utm_medium=docs). If you want your OP Mainnet token to be included in this list, take a look at the [review process and merge criteria](https://github.com/ethereum-optimism/ethereum-optimism.github.io#review-process-and-merge-criteria). diff --git a/pages/app-developers/tutorials/transactions/sdk-estimate-costs.mdx b/pages/app-developers/tutorials/transactions/sdk-estimate-costs.mdx index 086030b6f..44b244094 100644 --- a/pages/app-developers/tutorials/transactions/sdk-estimate-costs.mdx +++ b/pages/app-developers/tutorials/transactions/sdk-estimate-costs.mdx @@ -84,7 +84,7 @@ This tutorial explains how estimate transaction costs on OP Sepolia. You will need to get some ETH on OP Sepolia in order to run the code in this tutorial. - You can use the [Superchain faucet](https://console.optimism.io/faucet?utm_source=docs) to get ETH on OP Sepolia. + You can use the [Superchain faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) to get ETH on OP Sepolia. ## Add a private key to your environment diff --git a/pages/app-developers/tutorials/transactions/send-tx-from-eth.mdx b/pages/app-developers/tutorials/transactions/send-tx-from-eth.mdx index 42bbc1f5b..f201098f7 100644 --- a/pages/app-developers/tutorials/transactions/send-tx-from-eth.mdx +++ b/pages/app-developers/tutorials/transactions/send-tx-from-eth.mdx @@ -67,7 +67,7 @@ This tutorial explains how to bridge tokens from Sepolia to OP Sepolia. You will You can use [this faucet](https://sepoliafaucet.com) to get ETH on Sepolia. - You can use the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=docs) to get ETH on OP Sepolia. + You can use the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) to get ETH on OP Sepolia. ## Add a private key to your environment diff --git a/pages/connect/contribute/docs-contribute.mdx b/pages/connect/contribute/docs-contribute.mdx index db2147c1d..7783df705 100644 --- a/pages/connect/contribute/docs-contribute.mdx +++ b/pages/connect/contribute/docs-contribute.mdx @@ -65,7 +65,7 @@ You don't need permission to work on anything, but it's always best to let us kn Before contributing, make sure you're familiar with: -* the [Optimism vision and values](https://www.optimism.io/about) +* the [Optimism vision and values](https://www.optimism.io/about?utm_source=op-docs&utm_medium=docs) * our [contributor guidelines](https://github.com/ethereum-optimism/docs/blob/main/CONTRIBUTING.md) * our [style guide](style-guide) * our [code of conduct](https://github.com/ethereum-optimism/.github/blob/master/CODE_OF_CONDUCT.md) diff --git a/pages/connect/contribute/stack-contribute.mdx b/pages/connect/contribute/stack-contribute.mdx index 562fdfc11..e3c2e9bdd 100644 --- a/pages/connect/contribute/stack-contribute.mdx +++ b/pages/connect/contribute/stack-contribute.mdx @@ -28,7 +28,7 @@ Every contribution makes a difference — no contribution is too small. If you'r ## Component contributions The OP Stack is a decentralized development stack and is constantly evolving as new layers and modules are developed. Anyone can contribute components that can be considered part of the OP Stack as long as those components fit the stack's [design principles and goals](/stack/design-principles). -To start contributing components to the stack, check out some of these [useful ideas](https://github.com/ethereum-optimism/ecosystem-contributions) and get to building! And don't forget that projects can also receive grants from the Collective via [RetroPGF](https://community.optimism.io/docs/citizen-house/how-retro-funding-works/). +To start contributing components to the stack, check out some of these [useful ideas](https://github.com/ethereum-optimism/ecosystem-contributions) and get to building! And don't forget that projects can also receive grants from the Collective via [RetroPGF](https://community.optimism.io/docs/citizen-house/how-retro-funding-works/?utm_source=op-docs&utm_medium=docs). ## Codebase contributions @@ -40,7 +40,7 @@ To make your first contribution to the codebase, check out the [open issues](htt Only the software components included within the current release of the OP Stack codebase are considered in the scope of the OP Stack. - Any usage of the OP Stack outside of the official, intended capabilities of the current release is considered [OP Stack Hacks](https://github.com/ethereum-optimism/developers/tree/main/docs) — unofficial modifications that are useful for experimentation but could have unforeseen results, such as security vulnerabilities, and are likely to cause your chain to no longer be interoperable with the [Optimism Superchain](https://app.optimism.io/superchain/). + Any usage of the OP Stack outside of the official, intended capabilities of the current release is considered [OP Stack Hacks](https://github.com/ethereum-optimism/developers/tree/main/docs) — unofficial modifications that are useful for experimentation but could have unforeseen results, such as security vulnerabilities, and are likely to cause your chain to no longer be interoperable with the [Optimism Superchain](https://app.optimism.io/superchain/?utm_source=op-docs&utm_medium=docs). Developer support for OP Stack Hacks is limited — when in doubt, stick to the capabilities of the current release! diff --git a/pages/get-started/_meta.json b/pages/get-started/_meta.json index 08d110ead..7aa86dc66 100644 --- a/pages/get-started/_meta.json +++ b/pages/get-started/_meta.json @@ -8,7 +8,7 @@ "interop": "Superchain interoperability", "governance": { "title": "Optimism Governance", - "href": "https://community.optimism.io/docs/governance/", + "href": "https://community.optimism.io/docs/governance/?utm_source=op-docs&utm_medium=docs", "newWindow": true }, "+++ BuilderGuides": { diff --git a/pages/index.mdx b/pages/index.mdx index 61b4073c3..d1421dc13 100644 --- a/pages/index.mdx +++ b/pages/index.mdx @@ -29,7 +29,7 @@ import { Cards, Card } from 'nextra/components' # Welcome to the Optimism Docs Welcome to the Optimism Docs, the unified home of the [Optimism Collective's](/connect/resources/glossary#optimism-collective) technical documentation and information about the [OP Stack](/stack/getting-started). -Information about the Optimism Collective's governance, community, and mission can be found on the [Optimism Community Hub](https://community.optimism.io/docs/governance/). +Information about the Optimism Collective's governance, community, and mission can be found on the [Optimism Community Hub](https://community.optimism.io/docs/governance/?utm_source=op-docs&utm_medium=docs). ## Builder guides @@ -49,13 +49,13 @@ Whether you're a developer building an app on OP Mainnet, a node operator runnin Check out these amazing tools, so you can get building with Optimism. - } /> + } /> } /> - } /> + } /> - } /> + } /> } /> diff --git a/pages/notices/holocene-changes.mdx b/pages/notices/holocene-changes.mdx index 9f0e09085..30e67ede1 100644 --- a/pages/notices/holocene-changes.mdx +++ b/pages/notices/holocene-changes.mdx @@ -42,7 +42,7 @@ Holocene contains three changes: * **EIP-1559 configurability**: The elasticity and denominator EIP-1559 parameters become configurable via the `SystemConfig` L1 contract, allowing the gas target and gas limit to be configured independently. * **MIPS contract upgrade**: Updates to support additional calls made by the new `op-program` version. -For more information on the Holocene implementation details, please review [Holocene specification](https://specs.optimism.io/protocol/holocene/overview.html). +For more information on the Holocene implementation details, please review [Holocene specification](https://specs.optimism.io/protocol/holocene/overview.html?utm_source=op-docs&utm_medium=docs). ## For chain operators diff --git a/pages/notices/upgrade-14.mdx b/pages/notices/upgrade-14.mdx index 18627ed56..ab5c2ead2 100644 --- a/pages/notices/upgrade-14.mdx +++ b/pages/notices/upgrade-14.mdx @@ -27,7 +27,7 @@ import { Steps, Callout } from 'nextra/components' * Other Optimism governed chains' upgrades will be tracked in the release management project board. -This page outlines changes related to the Upgrade 14 network upgrade for chain operators, node operators, and users of OP Stack chains. The upgrade proposal is available [here](https://gov.optimism.io/t/upgrade-proposal-14-isthmus-l1-contracts-mt-cannon/9796) and the governance vote is available [here](https://vote.optimism.io/). +This page outlines changes related to the Upgrade 14 network upgrade for chain operators, node operators, and users of OP Stack chains. The upgrade proposal is available [here](https://gov.optimism.io/t/upgrade-proposal-14-isthmus-l1-contracts-mt-cannon/9796) and the governance vote is available [here](https://vote.optimism.io/?utm_source=op-docs&utm_medium=docs). If you experience difficulty at any stage of this process, please reach out to developer support. diff --git a/pages/operators/chain-operators/architecture.mdx b/pages/operators/chain-operators/architecture.mdx index 367302a74..2a9d9a34d 100644 --- a/pages/operators/chain-operators/architecture.mdx +++ b/pages/operators/chain-operators/architecture.mdx @@ -44,7 +44,7 @@ L2 to L1 messaging. ### op-geth -`op-geth` implements the layer 2 execution layer, with [minimal changes](https://op-geth.optimism.io/) +`op-geth` implements the layer 2 execution layer, with [minimal changes](https://op-geth.optimism.io/?utm_source=op-docs&utm_medium=docs) for a secure Ethereum-equivalent application environment. ### op-node diff --git a/pages/operators/chain-operators/configuration/batcher.mdx b/pages/operators/chain-operators/configuration/batcher.mdx index d341b5a3b..069079f05 100644 --- a/pages/operators/chain-operators/configuration/batcher.mdx +++ b/pages/operators/chain-operators/configuration/batcher.mdx @@ -79,7 +79,7 @@ To minimize costs, we recommend setting your `OP_BATCHER_MAX_CHANNEL_DURATION` When there's blob congestion, running with high blob counts can backfire, because you will have a harder time getting blobs included and then fees will bump, which always means a doubling of the priority fees. -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) for more technical details on channels and frames. +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: diff --git a/pages/operators/chain-operators/configuration/rollup.mdx b/pages/operators/chain-operators/configuration/rollup.mdx index aa083cc75..51b846f22 100644 --- a/pages/operators/chain-operators/configuration/rollup.mdx +++ b/pages/operators/chain-operators/configuration/rollup.mdx @@ -40,7 +40,7 @@ This document highlights the deployment configurations and their values. considered a Standard Chain within the Superchain. 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). + and the actual requirements in the [OP Stack Configurability Specification](https://specs.optimism.io/protocol/configurability.html?utm_source=op-docs&utm_medium=docs). ## Deployment configuration values @@ -132,7 +132,7 @@ disable Interop. * **Type:** Number of seconds * **Default value:** nil * **Recommended value:** -* **Notes:** Interoperability is still [experimental](https://specs.optimism.io/interop/overview.html). +* **Notes:** Interoperability is still [experimental](https://specs.optimism.io/interop/overview.html?utm_source=op-docs&utm_medium=docs). * **Standard Config Requirement:** Non-standard feature. *** @@ -454,7 +454,7 @@ SuperchainConfig. Has the ability to pause withdrawals. * **Recommended value:** * **Notes:** Must not be `address(0)` * **Standard Config Requirement:** [0x09f7150D8c019BeF34450d6920f6B3608ceFdAf2](https://etherscan.io/address/0x09f7150D8c019BeF34450d6920f6B3608ceFdAf2) -A 1/1 Safe owned by the Security Council Safe, with the [Deputy Guardian Module](https://specs.optimism.io/protocol/safe-extensions.html#deputy-guardian-module) +A 1/1 Safe owned by the Security Council Safe, with the [Deputy Guardian Module](https://specs.optimism.io/protocol/safe-extensions.html#deputy-guardian-module?utm_source=op-docs&utm_medium=docs) enabled to allow the Optimism Foundation to act as Guardian. *** @@ -1091,7 +1091,7 @@ UseInterop is a flag that indicates if the system is using interop. * **Type:** boolean * **Default value:** None * **Recommended value:** false -* **Notes:** Interoperability is still [experimental](https://specs.optimism.io/interop/overview.html). +* **Notes:** Interoperability is still [experimental](https://specs.optimism.io/interop/overview.html?utm_source=op-docs&utm_medium=docs). * **Standard Config Requirement:** Non-standard feature. *** diff --git a/pages/operators/chain-operators/features/alt-da-mode.mdx b/pages/operators/chain-operators/features/alt-da-mode.mdx index 8e7410742..0bf3ff776 100644 --- a/pages/operators/chain-operators/features/alt-da-mode.mdx +++ b/pages/operators/chain-operators/features/alt-da-mode.mdx @@ -120,7 +120,7 @@ You should use at least the following compatible op\* versions when running your 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), maintained in your own repo +* 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 @@ -231,5 +231,5 @@ After making these changes, your system should be properly configured to use the ## Next steps * Additional questions? See the FAQ section in the [Alt-DA Mode Explainer](/stack/beta-features/alt-da-mode#faqs). -* For more detailed info on Alt-DA Mode, see the [specs](https://specs.optimism.io/experimental/alt-da.html). +* 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). diff --git a/pages/operators/chain-operators/features/span-batches.mdx b/pages/operators/chain-operators/features/span-batches.mdx index cde20f893..1011acbea 100644 --- a/pages/operators/chain-operators/features/span-batches.mdx +++ b/pages/operators/chain-operators/features/span-batches.mdx @@ -59,5 +59,5 @@ To enable span batches, follow these steps: For more detailed information on the design and implementation of span batches, refer to the following resources: -* [Span Batches Specification](https://specs.optimism.io/protocol/delta/span-batches.html#span-batches) +* [Span Batches Specification](https://specs.optimism.io/protocol/delta/span-batches.html#span-batches?utm_source=op-docs&utm_medium=docs) * [Span Batch Design Docs](https://op-tip.notion.site/Span-Batch-Design-Docs-b85e599a47774dcdb8171cc84cab2476) diff --git a/pages/operators/chain-operators/tools/op-challenger.mdx b/pages/operators/chain-operators/tools/op-challenger.mdx index ab59047f2..65a299d47 100644 --- a/pages/operators/chain-operators/tools/op-challenger.mdx +++ b/pages/operators/chain-operators/tools/op-challenger.mdx @@ -230,5 +230,5 @@ This guide provides a walkthrough of setting up the configuration and monitoring ## Next steps * Additional questions? See the FAQ section in the [OP Challenger Explainer](/stack/fault-proofs/challenger). -* For more detailed info on `op-challenger`, see the [specs](https://specs.optimism.io/fault-proof/stage-one/honest-challenger-fdg.html). +* For more detailed info on `op-challenger`, see the [specs](https://specs.optimism.io/fault-proof/stage-one/honest-challenger-fdg.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). diff --git a/pages/operators/chain-operators/tools/op-deployer.mdx b/pages/operators/chain-operators/tools/op-deployer.mdx index 4c21baee7..833250634 100644 --- a/pages/operators/chain-operators/tools/op-deployer.mdx +++ b/pages/operators/chain-operators/tools/op-deployer.mdx @@ -95,7 +95,7 @@ l2ContractsLocator = "tag://op-contracts/v1.7.0-beta.1+l2-contracts" # L2 smart ``` -By default, `op-deployer` will fill in all other configuration variables with those that match the [standard configuration](https://specs.optimism.io/protocol/configurability.html). You can override these default settings by adding them to your intent file using the table below: +By default, `op-deployer` will fill in all other configuration variables with those that match the [standard configuration](https://specs.optimism.io/protocol/configurability.html?utm_source=op-docs&utm_medium=docs). You can override these default settings by adding them to your intent file using the table below: ```toml [globalDeployOverrides] diff --git a/pages/operators/chain-operators/tutorials/chain-dev-net.mdx b/pages/operators/chain-operators/tutorials/chain-dev-net.mdx index ea6f01cf9..13ba03eca 100644 --- a/pages/operators/chain-operators/tutorials/chain-dev-net.mdx +++ b/pages/operators/chain-operators/tutorials/chain-dev-net.mdx @@ -218,6 +218,6 @@ Send some transactions, deploy some contracts, and see what happens! ## Next Steps -* Check out the [protocol specs](https://specs.optimism.io/) for more detail about the rollup protocol. +* Check out the [protocol specs](https://specs.optimism.io/?utm_source=op-docs&utm_medium=docs) for more detail about the rollup protocol. * If you run into any problems, please visit the [chain operators troubleshooting guide](/operators/chain-operators/management/troubleshooting) -* If you run into any problems, please [file an issue](https://github.com/ethereum-optimism/optimism/issues) or join the [Optimism Discord](https://discord.optimism.io/) for help. +* If you run into any problems, please [file an issue](https://github.com/ethereum-optimism/optimism/issues) or join the [Optimism Discord](https://discord.optimism.io/?utm_source=op-docs&utm_medium=docs) for help. diff --git a/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx b/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx index 3c85769fa..0f7d88d13 100644 --- a/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx +++ b/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx @@ -286,7 +286,7 @@ It's recommended to fund the addresses with the following amounts when using Sep * `Batcher` — 0.1 Sepolia ETH * `Proposer` — 0.2 Sepolia ETH -**To get the required Sepolia ETH to fund the addresses, we recommend using the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=docs)** together with [Coinbase verification](https://help.coinbase.com/en/coinbase/getting-started/getting-started-with-coinbase/id-doc-verification). +**To get the required Sepolia ETH to fund the addresses, we recommend using the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs)** together with [Coinbase verification](https://help.coinbase.com/en/coinbase/getting-started/getting-started-with-coinbase/id-doc-verification). @@ -772,5 +772,5 @@ Send some transactions, deploy some contracts, and see what happens! ## Next steps -* Check out the [protocol specs](https://specs.optimism.io/) for more detail about the rollup protocol. +* Check out the [protocol specs](https://specs.optimism.io/?utm_source=op-docs&utm_medium=docs) for more detail about the rollup protocol. * If you run into any problems, please visit the [Chain Operators Troubleshooting Guide](/operators/chain-operators/management/troubleshooting) for help. diff --git a/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx b/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx index 275eb2f06..c6bb231b1 100644 --- a/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx +++ b/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx @@ -58,4 +58,4 @@ Follow our guide on [how to operate an Alt-DA Mode chain](/operators/chain-opera ## Next steps -* For more detail on implementing the DA Server, [see the specification](https://specs.optimism.io/experimental/alt-da.html#da-server). +* For more detail on implementing the DA Server, [see the specification](https://specs.optimism.io/experimental/alt-da.html?utm_source=op-docs&utm_medium=docs#da-server). diff --git a/pages/operators/node-operators/configuration/base-config.mdx b/pages/operators/node-operators/configuration/base-config.mdx index 12118d6b1..d953c5619 100644 --- a/pages/operators/node-operators/configuration/base-config.mdx +++ b/pages/operators/node-operators/configuration/base-config.mdx @@ -34,7 +34,7 @@ To configure your node, you will need to do the following: ## Configuring `op-geth` - Although the Docker image for the Execution Engine is called `op-geth`, the actual binary is still called `geth` in order to minimize differences between `op-geth` and `go-ethereum`. You can see the difference [here](https://op-geth.optimism.io/). + Although the Docker image for the Execution Engine is called `op-geth`, the actual binary is still called `geth` in order to minimize differences between `op-geth` and `go-ethereum`. You can see the difference [here](https://op-geth.optimism.io/?utm_source=op-docs&utm_medium=docs). `op-geth` stores its state in a database that requires initialization. diff --git a/pages/operators/node-operators/configuration/execution-config.mdx b/pages/operators/node-operators/configuration/execution-config.mdx index a85d8ab74..27c33c1e8 100644 --- a/pages/operators/node-operators/configuration/execution-config.mdx +++ b/pages/operators/node-operators/configuration/execution-config.mdx @@ -30,7 +30,7 @@ There are also sub-commands, which can be used to invoke functionality such as t This page list all configuration options for `op-geth`. `op-geth` implements the Execution-Layer, with minimal changes for a secure Ethereum-equivalent application environment. The following are options from [v1.101308.0](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101308.0) -Please note that the executable is still named `geth` to maintain a [minimal diff](https://op-geth.optimism.io/). +Please note that the executable is still named `geth` to maintain a [minimal diff](https://op-geth.optimism.io/?utm_source=op-docs&utm_medium=docs). ## Global options diff --git a/pages/operators/node-operators/json-rpc.mdx b/pages/operators/node-operators/json-rpc.mdx index 8dfd82811..556e69099 100644 --- a/pages/operators/node-operators/json-rpc.mdx +++ b/pages/operators/node-operators/json-rpc.mdx @@ -53,7 +53,7 @@ Optimism specific rollup methods. #### `optimism_outputAtBlock` Get the output root at a specific block. -This method is documented in [the specifications](https://specs.optimism.io/protocol/rollup-node.html#output-method-api). +This method is documented in [the specifications](https://specs.optimism.io/protocol/rollup-node.html?utm_source=op-docs&utm_medium=docs#output-method-api). diff --git a/pages/operators/node-operators/management/regenesis-history.mdx b/pages/operators/node-operators/management/regenesis-history.mdx index 3327c766f..251359299 100644 --- a/pages/operators/node-operators/management/regenesis-history.mdx +++ b/pages/operators/node-operators/management/regenesis-history.mdx @@ -23,7 +23,7 @@ import { Callout, Steps } from 'nextra/components' # Accessing pre-regenesis history This tutorial explains how to access transaction history between 23 June 2021 and the final regenesis. -Because of our final regenesis on 11 November 2021, older transactions are not part of the current blockchain and do not appear on [Etherscan](https://explorer.optimism.io/). +Because of our final regenesis on 11 November 2021, older transactions are not part of the current blockchain and do not appear on [Etherscan](https://explorer.optimism.io/?utm_source=op-docs&utm_medium=docs). ## Dune access diff --git a/pages/operators/node-operators/management/snapshots.mdx b/pages/operators/node-operators/management/snapshots.mdx index fad6d1dc1..1db29ee2e 100644 --- a/pages/operators/node-operators/management/snapshots.mdx +++ b/pages/operators/node-operators/management/snapshots.mdx @@ -60,15 +60,15 @@ Migrated OP Mainnet databases can be generated manually or pre-migrated database ### OP Mainnet (archive node) - You can also download access the [Optimism Foundation datadir explorer](https://datadirs.optimism.io/) to find other snapshots. + You can also download access the [Optimism Foundation datadir explorer](https://datadirs.optimism.io/?utm_source=op-docs&utm_medium=docs) to find other snapshots. | Snapshot Date | Size | Download Link | sha256sum | | ----------------------------- | ---- | ------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------- | -| Latest by Optimism Foundation | >4TB | [Mirror 1](https://datadirs.optimism.io/latest)
    [Mirror 2 (torrent)](https://datadirs.optimism.io/latest.torrent) | [sha256sum](https://datadirs.optimism.io/latest.sha256sum/) | +| Latest by Optimism Foundation | >4TB | [Mirror 1](https://datadirs.optimism.io/latest?utm_source=op-docs&utm_medium=docs)
    [Mirror 2 (torrent)](https://datadirs.optimism.io/latest.torrent?utm_source=op-docs&utm_medium=docs) | [sha256sum](https://datadirs.optimism.io/latest.sha256sum/?utm_source=op-docs&utm_medium=docs) | ### OP Mainnet (legacy) | Snapshot Date | Size | Download Link | sha256sum | | ------------- | ----- | ------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- | -| 2023-06-06 | 2.9TB | [Mirror 1](https://datadirs.optimism.io/mainnet-legacy-archival.tar.zst) | `4adedb61125b81b55f9bdccc2e85092050c65ef2253c86e2b79569732b772829` | +| 2023-06-06 | 2.9TB | [Mirror 1](https://datadirs.optimism.io/mainnet-legacy-archival.tar.zst?utm_source=op-docs&utm_medium=docs) | `4adedb61125b81b55f9bdccc2e85092050c65ef2253c86e2b79569732b772829` | diff --git a/pages/operators/node-operators/network-upgrades.mdx b/pages/operators/node-operators/network-upgrades.mdx index 665432931..c4df0b1df 100644 --- a/pages/operators/node-operators/network-upgrades.mdx +++ b/pages/operators/node-operators/network-upgrades.mdx @@ -32,12 +32,12 @@ Network upgrades are activated by timestamps. Failing to upgrade your OP Stack s | Upgrade | Governance Approval | [Mainnet Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml) | [Sepolia Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/sepolia/superchain.toml) | | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | -| [Holocene](https://specs.optimism.io/protocol/holocene/overview.html) | [approved](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515) | Thu Jan 9 18:00:01 UTC 2025 (`1736445601`) | Tue Nov 26 15:00:00 UTC 2024 (`1732633200`) | -| [Granite](https://specs.optimism.io/protocol/granite/overview.html) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | -| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | -| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | -| [Delta](https://specs.optimism.io/protocol/delta/overview.html) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | -| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | +| [Holocene](https://specs.optimism.io/protocol/holocene/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515) | Thu Jan 9 18:00:01 UTC 2025 (`1736445601`) | Tue Nov 26 15:00:00 UTC 2024 (`1732633200`) | +| [Granite](https://specs.optimism.io/protocol/granite/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | +| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | +| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | +| [Delta](https://specs.optimism.io/protocol/delta/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | +| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | | Bedrock | [approved](https://gov.optimism.io/t/final-upgrade-1-bedrock-protocol-upgrade-v2/5548) | Tue Jun 06 2023 16:28:23 UTC (`1686079703`) at block `105235063` | N/A | ## Upgrade process @@ -86,4 +86,4 @@ then the software is deployed on production networks. ## More information * To check for the latest node software, see the [Software Releases](/operators/node-operators/releases). -* For more information on the governance process see the [governance documentation](https://community.optimism.io/docs/governance/). +* For more information on the governance process see the [governance documentation](https://community.optimism.io/docs/governance/?utm_source=op-docs&utm_medium=docs). diff --git a/pages/stack/beta-features/alt-da-mode.mdx b/pages/stack/beta-features/alt-da-mode.mdx index 5ab767e7f..554a1dbef 100644 --- a/pages/stack/beta-features/alt-da-mode.mdx +++ b/pages/stack/beta-features/alt-da-mode.mdx @@ -35,7 +35,7 @@ Over the past few years, alternative DA Layers have been built as an alternative ## How it works -Alt-DA Mode introduces a standard interface for reading and writing data to Alt-DA Layers and allows any DA Layer team to build and maintain their own [DA Server](https://specs.optimism.io/experimental/alt-da.html#da-server) to enable the OP Stack to communicate with their DA Layer. The DA Server handles any of the custom DA Layer logic, such as key management, interfacing with a DA Layer node, etc. +Alt-DA Mode introduces a standard interface for reading and writing data to Alt-DA Layers and allows any DA Layer team to build and maintain their own [DA Server](https://specs.optimism.io/experimental/alt-da.html?utm_source=op-docs&utm_medium=docs#da-server) to enable the OP Stack to communicate with their DA Layer. The DA Server handles any of the custom DA Layer logic, such as key management, interfacing with a DA Layer node, etc. This abstraction ensures that new features and improvements to Alt-DA Mode will come to all chains using Alt-DA Mode, regardless of the DA Layer they choose to use. Although the Data Availability Challenge (DA Challenge) will be disabled at launch, this integration provides a solution compatible with upcoming OP Stack features. @@ -56,7 +56,7 @@ Alt-DA Mode will always have more trust assumptions than simply posting data to ## Next steps * Ready to get started? Read our guide on how to [deploy your Alt-DA Mode chain](/operators/chain-operators/features/alt-da-mode). -* For more info about how Alt-DA Mode works under the hood, [check out the specs](https://specs.optimism.io/experimental/alt-da.html). +* For more info about how Alt-DA Mode works under the hood, [check out the specs](https://specs.optimism.io/experimental/alt-da.html?utm_source=op-docs&utm_medium=docs). ## FAQs diff --git a/pages/stack/components.mdx b/pages/stack/components.mdx index 2d850436e..dbbc6a3fb 100644 --- a/pages/stack/components.mdx +++ b/pages/stack/components.mdx @@ -46,7 +46,7 @@ The Data Availability Layer defines where the raw inputs to an OP Stack based ch Ethereum DA is currently the most widely used Data Availability module for the OP Stack. When using the Ethereum DA module, source data can be derived from any piece of information accessible on the Ethereum blockchain. This includes Ethereum calldata, events, and 4844 data blobs. -* [Specifications](https://specs.optimism.io/protocol/derivation.html#batch-submission-wire-format) +* [Specifications](https://specs.optimism.io/protocol/derivation.html#batch-submission-wire-format?utm_source=op-docs&utm_medium=docs) * [Source code](https://github.com/ethereum-optimism/optimism/tree/v1.1.4/op-batcher) ### Sequencing @@ -69,7 +69,7 @@ The Derivation Layer defines how the raw data in the Data Availability Layer is The Rollup module derives Engine API inputs from Ethereum block data, Sequencer transaction batches, Deposited transaction events, and more. -* [Specifications](https://specs.optimism.io/protocol/derivation.html#l2-chain-derivation-pipeline) +* [Specifications](https://specs.optimism.io/protocol/derivation.html#l2-chain-derivation-pipeline?utm_source=op-docs&utm_medium=docs) * [Source code](https://github.com/ethereum-optimism/optimism/tree/v1.1.4/op-node) #### Indexer @@ -82,9 +82,9 @@ The Execution Layer defines the structure of state within an OP Stack system and #### EVM -The EVM is an Execution Layer module that uses the same state representation and state transition function as the Ethereum Virtual Machine. The EVM module in the Ethereum Rollup configuration of the OP Stack is a [lightly modified](https://op-geth.optimism.io/) version of the EVM that adds support for L2 transactions initiated on Ethereum and adds an extra L1 Data Fee to each transaction to account for the cost of publishing transactions to Ethereum. +The EVM is an Execution Layer module that uses the same state representation and state transition function as the Ethereum Virtual Machine. The EVM module in the Ethereum Rollup configuration of the OP Stack is a [lightly modified](https://op-geth.optimism.io/?utm_source=op-docs&utm_medium=docs) version of the EVM that adds support for L2 transactions initiated on Ethereum and adds an extra L1 Data Fee to each transaction to account for the cost of publishing transactions to Ethereum. -* [Specifications](https://specs.optimism.io/protocol/exec-engine.html) (where it differs from [geth](https://geth.ethereum.org/)) +* [Specifications](https://specs.optimism.io/protocol/exec-engine.html?utm_source=op-docs&utm_medium=docs) (where it differs from [geth](https://geth.ethereum.org/)) * [Source code](https://github.com/ethereum-optimism/op-geth/tree/09ade3df6d1d3a4f8f308553825348be132bc960) ### Settlement layer @@ -99,7 +99,7 @@ Once a transaction is published and finalized on the corresponding Data Availabi An Attestation-based Fault Proof mechanism uses an optimistic protocol to establish a view of an OP Stack chain. In optimistic settlement mechanisms generally, **Proposer** entities can propose what they believe to be the current valid state of the OP Stack chain. If these proposals are not invalidated within a certain period of time (the "challenge period"), then the proposals are assumed by the mechanism to be correct. In the Attestation Proof mechanism in particular, a proposal can be invalidated if some threshold of pre-defined parties provide attestations to a valid state that is different than the state in the proposal. This places a trust assumption on the honesty of at least a threshold number of the pre-defined participants. -* [Specifications](https://specs.optimism.io/protocol/withdrawals.html) (called [withdrawal transactions](/app-developers/bridging/messaging)) +* [Specifications](https://specs.optimism.io/protocol/withdrawals.html?utm_source=op-docs&utm_medium=docs) (called [withdrawal transactions](/app-developers/bridging/messaging)) * [Source code](https://github.com/ethereum-optimism/optimism/tree/v1.1.4/packages/contracts-bedrock/src) #### Fault Proof Optimistic Settlement diff --git a/pages/stack/design-principles.mdx b/pages/stack/design-principles.mdx index 89c2b22df..6ad39be75 100644 --- a/pages/stack/design-principles.mdx +++ b/pages/stack/design-principles.mdx @@ -90,7 +90,7 @@ Software that follows these principles is **USEful** software for the Optimism C For something to be part of the OP Stack, it should help power the Optimism Collective. This condition helps guide the type of software that can be included in the stack. -For instance, a powerful open-source block explorer that makes it easier for users to inspect [the Superchain](https://app.optimism.io/superchain/) would be a great addition to the OP Stack. +For instance, a powerful open-source block explorer that makes it easier for users to inspect [the Superchain](https://app.optimism.io/superchain/?utm_source=op-docs&utm_medium=docs) would be a great addition to the OP Stack. Although utility is important for inclusion in the OP Stack, you shouldn't be afraid to experiment. Do something crazy. @@ -126,4 +126,4 @@ Extensibility is a key design principle that unlocks the superpower of collabora The OP Stack is a decentralized software stack that anyone can contribute to. If you're interested in contributing to the OP Stack, check out [the Contributing section on our Community pages](https://community.optimism.io). -Of course, software that has an impact for the Optimism Collective is eligible to receive [Retroactive Public Goods Funding](https://app.optimism.io/retropgf). Build for the OP Stack — get rewarded for writing great open source software. What's not to love? +Of course, software that has an impact for the Optimism Collective is eligible to receive [Retroactive Public Goods Funding](https://app.optimism.io/retropgf?utm_source=op-docs&utm_medium=docs). Build for the OP Stack — get rewarded for writing great open source software. What's not to love? diff --git a/pages/stack/differences.mdx b/pages/stack/differences.mdx index efbb41252..e6dcc95cf 100644 --- a/pages/stack/differences.mdx +++ b/pages/stack/differences.mdx @@ -103,4 +103,4 @@ There are various useful tools linked above. Here are a few more tools and links * [OP-viem](https://viem.sh/op-stack): JS framework that can handle many of these unique functions on OP Chains. It is similar to Ethers.js for OP Stack chains. -* [Specs](https://specs.optimism.io/root.html): For more in-depth technical explanations and examples. +* [Specs](https://specs.optimism.io/root.html?utm_source=op-docs&utm_medium=docs): For more in-depth technical explanations and examples. diff --git a/pages/stack/fact-sheet.mdx b/pages/stack/fact-sheet.mdx index e965e979e..945295baf 100644 --- a/pages/stack/fact-sheet.mdx +++ b/pages/stack/fact-sheet.mdx @@ -36,7 +36,7 @@ While the OP Stack allows for full customization, chains in the Superchain adher 1Data for Superchain from [Base](https://etherscan.io/address/0x73a79Fab69143498Ed3712e519A88a918e1f4072#readProxyContract#F14). Data for OP Stack from [opBNB](https://docs.bnbchain.org/bnb-opbnb/core-concepts/opbnb-metrics/). -2The standard blockspace charter has a max gas limit of [200m](https://specs.optimism.io/protocol/configurability.html#gas-limit). Both gas limit and gas target can be configured through the system config. +2The standard blockspace charter has a max gas limit of [200m](https://specs.optimism.io/protocol/configurability.html?utm_source=op-docs&utm_medium=docs#gas-limit). Both gas limit and gas target can be configured through the system config. 3While protocol blocktimes can be lowered to 1 second, subsecond blocktimes can be achieved using [Rollup Boost and Flashblocks](https://writings.flashbots.net/introducing-rollup-boost). diff --git a/pages/stack/fault-proofs/cannon.mdx b/pages/stack/fault-proofs/cannon.mdx index bdecf2bb4..dece7cce0 100644 --- a/pages/stack/fault-proofs/cannon.mdx +++ b/pages/stack/fault-proofs/cannon.mdx @@ -219,17 +219,17 @@ The PreimageOracle Server connection is instantiated in `run.go`, where the serv `mips.go` communicates with the PreimageOracle Server when reading and writing Pre-images as part of MIPS syscall instructions, as well as hinting to the PreimageOracle Server. -The OP-stack fault-proof [Pre-image Oracle specs](https://specs.optimism.io/experimental/fault-proof/index.html#pre-image-oracle) +The OP-stack fault-proof [Pre-image Oracle specs](https://specs.optimism.io/experimental/fault-proof/index.html?utm_source=op-docs&utm_medium=docs#pre-image-oracle) define the ABI for communicating pre-images. -This ABI is implemented by the VM by intercepting the `read`/`write` syscalls to specific file descriptors. See [Cannon VM Specs](https://specs.optimism.io/experimental/fault-proof/cannon-fault-proof-vm.html#io) for more details. +This ABI is implemented by the VM by intercepting the `read`/`write` syscalls to specific file descriptors. See [Cannon VM Specs](https://specs.optimism.io/experimental/fault-proof/cannon-fault-proof-vm.html?utm_source=op-docs&utm_medium=docs#io) for more details. Note that although the oracle provides up to 32 bytes of the pre-image, Cannon only supports reading at most 4 bytes at a time, to unify the memory operations with 32-bit load/stores. ## Further Reading -* [Cannon FPVM Specification](https://specs.optimism.io/experimental/fault-proof/cannon-fault-proof-vm.html) +* [Cannon FPVM Specification](https://specs.optimism.io/experimental/fault-proof/cannon-fault-proof-vm.html?utm_source=op-docs&utm_medium=docs) * [Merkle Proofs Specification](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md) * [Executable and Linkable Format (ELF)](https://en.wikipedia.org/wiki/Executable_and_Linkable_Format) * [Keys in Mordor Summit: Cannon & Fault Proofs](https://www.youtube.com/watch?v=ASLMj70V0Ao) diff --git a/pages/stack/fault-proofs/challenger.mdx b/pages/stack/fault-proofs/challenger.mdx index ed5a9bb2b..06f6e7d1a 100644 --- a/pages/stack/fault-proofs/challenger.mdx +++ b/pages/stack/fault-proofs/challenger.mdx @@ -68,7 +68,7 @@ graph TD; ### Root claim -The root claim is considered to be an honest claim if and only if it has a [state witness Hash](https://specs.optimism.io/fault-proof/stage-one/fault-dispute-game.html#claims) that agrees with the honest challenger's state witness hash for the root claim. +The root claim is considered to be an honest claim if and only if it has a [state witness Hash](https://specs.optimism.io/fault-proof/stage-one/fault-dispute-game.html?utm_source=op-docs&utm_medium=docs#claims) that agrees with the honest challenger's state witness hash for the root claim. ### Counter claims @@ -83,7 +83,7 @@ When a new claim is made in a dispute game, the honest challenger processes it a ### Possible moves -The challenger monitors each game as new claims are added and reacts according to the [honest actor algorithm](https://specs.optimism.io/fault-proof/stage-one/honest-challenger-fdg.html) to defend valid proposals and invalidate invalid proposals. A **move** is a challenge against an existing claim and must include an alternate claim asserting a different trace (e.g., attack, defend, or step). +The challenger monitors each game as new claims are added and reacts according to the [honest actor algorithm](https://specs.optimism.io/fault-proof/stage-one/honest-challenger-fdg.html?utm_source=op-docs&utm_medium=docs) to defend valid proposals and invalidate invalid proposals. A **move** is a challenge against an existing claim and must include an alternate claim asserting a different trace (e.g., attack, defend, or step).
    @@ -102,7 +102,7 @@ The `FaultDisputeGame` does not put a time cap on resolution - because of the li ## Next steps * Ready to get started? Read our guide on how to [configure `op-challenger` on your OP Stack chain](/operators/chain-operators/tools/op-challenger). -* For more info about how `op-challenger` works under the hood, [check out the specs](https://specs.optimism.io/fault-proof/stage-one/honest-challenger-fdg.html). +* For more info about how `op-challenger` works under the hood, [check out the specs](https://specs.optimism.io/fault-proof/stage-one/honest-challenger-fdg.html?utm_source=op-docs&utm_medium=docs). ## FAQs diff --git a/pages/stack/fault-proofs/explainer.mdx b/pages/stack/fault-proofs/explainer.mdx index 74a311e3b..5960e3c11 100644 --- a/pages/stack/fault-proofs/explainer.mdx +++ b/pages/stack/fault-proofs/explainer.mdx @@ -72,7 +72,7 @@ Additionally, the following [security safeguards](/stack/fault-proofs/fp-securit * Ready to get started? Review the [FP Components](fp-components) to learn how the different components work together to enhance decentralization in the Optimism ecosystem. * See the [Fault Proof Mainnet Security](/stack/fault-proofs/fp-security) to understand changes to `OptimismPortal` and `FaultDisputeGame` contracts. -* For more info about how the FP system works under the hood, [check out the specs](https://specs.optimism.io/fault-proof/index.html). +* For more info about how the FP system works under the hood, [check out the specs](https://specs.optimism.io/fault-proof/index.html?utm_source=op-docs&utm_medium=docs). ## FAQs @@ -114,4 +114,4 @@ The list-claims subcommand of op-challenger can also provide a good view of the ./op-challenger/bin/op-challenger list-claims --l1-eth-rpc --game-address 0xcf8f181497DAD07277781517A76cb131C54A1BEE ``` -See the [specs](https://specs.optimism.io/experimental/fault-proof/stage-one/bond-incentives.html) for more details. +See the [specs](https://specs.optimism.io/experimental/fault-proof/stage-one/bond-incentives.html?utm_source=op-docs&utm_medium=docs) for more details. diff --git a/pages/stack/fault-proofs/fp-components.mdx b/pages/stack/fault-proofs/fp-components.mdx index a443ef1d5..2735ab229 100644 --- a/pages/stack/fault-proofs/fp-components.mdx +++ b/pages/stack/fault-proofs/fp-components.mdx @@ -55,7 +55,7 @@ The FPP is a combination of `op-node` and `op-geth`, so it has both the consensu The FPP is designed so that it can be run in a deterministic way such that two invocations with the same input data will result in not only the same output, but the same program execution trace. This allows it to be run in an onchain VM as part of the dispute resolution process. -All data is retrieved via the [Preimage Oracle API](https://specs.optimism.io/experimental/fault-proof/index.html#pre-image-oracle). The preimages could be provided via the FPVM when onchain or by a native "host" implementation that can download the required data from nodes via JSON-RPC requests. The native host implementation is also provided by `op-program` but doesn't run as part of the onchain execution. Basically, `op-program` has two halves: the "client" Fault Proof Program part covered in this section and the "host" part used to fetch required preimages. +All data is retrieved via the [Preimage Oracle API](https://specs.optimism.io/experimental/fault-proof/index.html#pre-image-oracle?utm_source=op-docs&utm_medium=docs). The preimages could be provided via the FPVM when onchain or by a native "host" implementation that can download the required data from nodes via JSON-RPC requests. The native host implementation is also provided by `op-program` but doesn't run as part of the onchain execution. Basically, `op-program` has two halves: the "client" Fault Proof Program part covered in this section and the "host" part used to fetch required preimages. ## Fault proof virtual machine @@ -94,4 +94,4 @@ The first full implementation of the VM generic in the bisection game includes a * For more detail on Cannon and its default operation as part of Optimism's Fault Proof Virtual Machine, see [Cannon FPVM](cannon). * For a detailed walk-thru of significant changes to Fault Proof Mainnet, see [FP Mainnet Security](fp-security). -* For detailed information about the entire FP program, FP virtual machine, and dispute game, see the [specs](https://specs.optimism.io/fault-proof/index.html). +* For detailed information about the entire FP program, FP virtual machine, and dispute game, see the [specs](https://specs.optimism.io/fault-proof/index.html?utm_source=op-docs&utm_medium=docs). diff --git a/pages/stack/fault-proofs/fp-security.mdx b/pages/stack/fault-proofs/fp-security.mdx index 89607f4d0..9b53f6910 100644 --- a/pages/stack/fault-proofs/fp-security.mdx +++ b/pages/stack/fault-proofs/fp-security.mdx @@ -72,4 +72,4 @@ With the introduction of Fault Proof Mainnet, The most significant change in the ## Next steps * See the [FP Components](fp-components) for an overview of FP system components and how they work together to enhance decentralization in the Optimism ecosystem. -* See the [specs](https://specs.optimism.io/fault-proof/index.html) for detailed information about the entire FP program, FP virtual machine, and dispute game. +* See the [specs](https://specs.optimism.io/fault-proof/index.html?utm_source=op-docs&utm_medium=docs) for detailed information about the entire FP program, FP virtual machine, and dispute game. diff --git a/pages/stack/fault-proofs/mips.mdx b/pages/stack/fault-proofs/mips.mdx index 83ea28474..cb250eb28 100644 --- a/pages/stack/fault-proofs/mips.mdx +++ b/pages/stack/fault-proofs/mips.mdx @@ -65,7 +65,7 @@ Thus, even when the instruction run onchain does not explicitly read from `Preim In order to execute a MIPS instruction onchain, the `MIPS.sol` contract needs to know important state information such as the instruction to run, the values in each of the general purpose registers, etc. More specifically, a tightly-packed `State` struct contains all the relevant information that the `MIPS.sol` contract needs to know. This struct is passed to the contract from the `FaultDisputeGame.sol` contract when it invokes the `step` function in `MIPS.sol` (which in-turn executes a single MIPS instruction onchain). -The following information is stored in the `State` struct. See [doc reference](https://specs.optimism.io/experimental/fault-proof/cannon-fault-proof-vm.html#state) and [code reference](https://github.com/ethereum-optimism/optimism/blob/546fb2c7a5796b7fe50b0b7edc7666d3bd281d6f/packages/contracts-bedrock/src/cannon/MIPS.sol#L26) for details: +The following information is stored in the `State` struct. See [doc reference](https://specs.optimism.io/experimental/fault-proof/cannon-fault-proof-vm.html?utm_source=op-docs&utm_medium=docs#state) and [code reference](https://github.com/ethereum-optimism/optimism/blob/546fb2c7a5796b7fe50b0b7edc7666d3bd281d6f/packages/contracts-bedrock/src/cannon/MIPS.sol#L26) for details: 1. `memRoot` - The merkle root hash of the binary merkle tree that represents the MIPS VM's monolithic 32-bit memory space. 2. `preimageKey` - Key that uniquely identifies the Pre-image data to be read (if applicable) from the `PreimageOracle.sol` contract. @@ -270,7 +270,7 @@ The internal pure [`execute`](https://github.com/ethereum-optimism/optimism/blob ## Further reading * [Cannon Overview](https://github.com/ethereum-optimism/optimism/blob/546fb2c7a5796b7fe50b0b7edc7666d3bd281d6f/cannon/docs/README.md) -* [Cannon FPVM Specification](https://specs.optimism.io/experimental/fault-proof/cannon-fault-proof-vm.html) +* [Cannon FPVM Specification](https://specs.optimism.io/experimental/fault-proof/cannon-fault-proof-vm.html?utm_source=op-docs&utm_medium=docs) * [MIPS IV ISA Specification](https://www.cs.cmu.edu/afs/cs/academic/class/15740-f97/public/doc/mips-isa.pdf) * [MIPS32 Architecture For Programmers Volume II (for SPECIAL2 opcodes)](https://www.cs.cornell.edu/courses/cs3410/2008fa/MIPS_Vol2.pdf) * [MIPS Assembly Wiki Book](https://en.wikibooks.org/wiki/MIPS_Assembly) diff --git a/pages/stack/interop/explainer.mdx b/pages/stack/interop/explainer.mdx index 8d009203e..b4f1f6355 100644 --- a/pages/stack/interop/explainer.mdx +++ b/pages/stack/interop/explainer.mdx @@ -113,7 +113,7 @@ This executing message could result in a contract function being executed on the The initiating message is simply a log event. Any log event on any chain that interoperates with the destination can initiate a cross-domain message. -The transaction that receives the message on the destination chain calls a contract called [`CrossL2Inbox`](https://specs.optimism.io/interop/predeploys.html#crossl2inbox). +The transaction that receives the message on the destination chain calls a contract called [`CrossL2Inbox`](https://specs.optimism.io/interop/predeploys.html?utm_source=op-docs&utm_medium=docs#crossl2inbox). This call can be at the top level, directly from the externally owned account, or come through a smart contract. The call to `CrossL2Inbox`, also known as the *executing message*, needs to [identify the initiating message uniquely](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/CrossL2Inbox.sol#L35-L42), using the chain ID of the source chain, the block number, and the index of the log event within that block, as well as a few other fields as a sanity check. diff --git a/pages/stack/opcm.mdx b/pages/stack/opcm.mdx index 306365f89..88b5ac791 100644 --- a/pages/stack/opcm.mdx +++ b/pages/stack/opcm.mdx @@ -38,5 +38,5 @@ Additionally, after the Upgrade 13 network upgrade, OPCM instances will be used ## Learn more -* Checkout the [OPCM specs](https://specs.optimism.io/experimental/op-contracts-manager.html) +* Checkout the [OPCM specs](https://specs.optimism.io/experimental/op-contracts-manager.html?utm_source=op-docs&utm_medium=docs) * Checkout the [OPCM design document](https://github.com/ethereum-optimism/design-docs/blob/main/protocol/op-contracts-manager-arch.md) diff --git a/pages/stack/public-devnets.mdx b/pages/stack/public-devnets.mdx index 85acc82c0..ff117f944 100644 --- a/pages/stack/public-devnets.mdx +++ b/pages/stack/public-devnets.mdx @@ -65,4 +65,4 @@ Features must be included on a betanet before they can be deployed on a testnet. ## Current devnets -A full list of active alpha and betanets is available at [https://devnets.optimism.io/](https://devnets.optimism.io/). +A full list of active alpha and betanets is available at [devnets](https://devnets.optimism.io/?utm_source=op-docs&utm_medium=docs). diff --git a/pages/stack/smart-contracts.mdx b/pages/stack/smart-contracts.mdx index cf17deb2f..3c6152bce 100644 --- a/pages/stack/smart-contracts.mdx +++ b/pages/stack/smart-contracts.mdx @@ -303,7 +303,7 @@ future hardforks, not the activation of said hardforks. The Protocol Version only applies to the Protocol specifications with the - [Superchain Targets](https://specs.optimism.io/protocol/superchain-upgrades.html#superchain-target) + [Superchain Targets](https://specs.optimism.io/protocol/superchain-upgrades.html?utm_source=op-docs&utm_medium=docs#superchain-target) specified within. This versioning is independent of the Semver versioning used in OP Stack smart contracts, and the Semver-versioned reference software of the OP-Stack. This is an optional feature. @@ -678,7 +678,7 @@ The `SchemaRegistry` predeploy implements the global attestation schemas for the * **Deprecated:** no * **Proxied:** yes -The SchemaRegistry works alongside the Ethereum Attestation Service (EAS) to enable attestations. See [Build Decentralized Identity Apps with Attestations](https://community.optimism.io/identity/about-attestations) for more details on schemas and usage. +The SchemaRegistry works alongside the Ethereum Attestation Service (EAS) to enable attestations. See [Build Decentralized Identity Apps with Attestations](https://community.optimism.io/identity/about-attestations?utm_source=op-docs&utm_medium=docs) for more details on schemas and usage. ### EAS (Ethereum Attestation Service) @@ -722,7 +722,7 @@ Attestations made via EAS can be indexed through the following tools: * [Ponder Graph](https://github.com/ethereum-attestation-service/eas-ponder-graph) * [Open Source Indexer](https://github.com/ethereum-attestation-service/eas-indexing-service) -For more information on working with attestations, see [Build Decentralized Identity Apps with Attestations](https://community.optimism.io/identity/about-attestations). +For more information on working with attestations, see [Build Decentralized Identity Apps with Attestations](https://community.optimism.io/identity/about-attestations?utm_source=op-docs&utm_medium=docs). ### BeaconBlockRoot From 9c93b42acf02e40ac7c6301f9b6849f7d41c911e Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Mon, 7 Apr 2025 20:38:43 +0100 Subject: [PATCH 2/5] fix lint issues --- pages/app-developers/get-started.mdx | 16 ++++++++-------- .../node-operators/management/snapshots.mdx | 14 +++++++------- .../node-operators/network-upgrades.mdx | 18 +++++++++--------- 3 files changed, 24 insertions(+), 24 deletions(-) diff --git a/pages/app-developers/get-started.mdx b/pages/app-developers/get-started.mdx index 7cf0619da..b981fafad 100644 --- a/pages/app-developers/get-started.mdx +++ b/pages/app-developers/get-started.mdx @@ -44,14 +44,14 @@ The SuperchainERC20 Starter Kit allows you to focus on what to deploy, not how t ## Tools & resources for building interoperable apps -| Tool | Description | -| ----------------------------------------------------------------------------- | ----------------------------------------------------------------------- | -| [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) | One stop shop to grab testnet ETH for any Superchain network. | -| [Supersim](tools/supersim) | Local multi-chain testing environment for smart contracts. | -| [Super CLI](https://github.com/ethereum-optimism/super-cli) | Command-line tool for seamless multichain app deployment and testing. | -| [Superchain Relayer](https://github.com/ethereum-optimism/superchain-relayer) | UI for monitoring and managing cross-chain transactions. | -| [Interop Docs](/stack/interop) | Comprehensive Interop information in the Optimism Docs. | -| [Superchain Dev Console](https://console.optimism.io/?utm_source=op-docs&utm_medium=docs) | Comprensive tool to build, launch, and grow your app on the Superchain. | +| Tool | Description | +| ------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | +| [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs\&utm_medium=docs) | One stop shop to grab testnet ETH for any Superchain network. | +| [Supersim](tools/supersim) | Local multi-chain testing environment for smart contracts. | +| [Super CLI](https://github.com/ethereum-optimism/super-cli) | Command-line tool for seamless multichain app deployment and testing. | +| [Superchain Relayer](https://github.com/ethereum-optimism/superchain-relayer) | UI for monitoring and managing cross-chain transactions. | +| [Interop Docs](/stack/interop) | Comprehensive Interop information in the Optimism Docs. | +| [Superchain Dev Console](https://console.optimism.io/?utm_source=op-docs\&utm_medium=docs) | Comprensive tool to build, launch, and grow your app on the Superchain. | ## Handy step-by-step guides diff --git a/pages/operators/node-operators/management/snapshots.mdx b/pages/operators/node-operators/management/snapshots.mdx index 1db29ee2e..c0e7ea492 100644 --- a/pages/operators/node-operators/management/snapshots.mdx +++ b/pages/operators/node-operators/management/snapshots.mdx @@ -60,15 +60,15 @@ Migrated OP Mainnet databases can be generated manually or pre-migrated database ### OP Mainnet (archive node) - You can also download access the [Optimism Foundation datadir explorer](https://datadirs.optimism.io/?utm_source=op-docs&utm_medium=docs) to find other snapshots. + You can also download access the [Optimism Foundation datadir explorer](https://datadirs.optimism.io/?utm_source=op-docs\&utm_medium=docs) to find other snapshots. -| Snapshot Date | Size | Download Link | sha256sum | -| ----------------------------- | ---- | ------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------- | -| Latest by Optimism Foundation | >4TB | [Mirror 1](https://datadirs.optimism.io/latest?utm_source=op-docs&utm_medium=docs)
    [Mirror 2 (torrent)](https://datadirs.optimism.io/latest.torrent?utm_source=op-docs&utm_medium=docs) | [sha256sum](https://datadirs.optimism.io/latest.sha256sum/?utm_source=op-docs&utm_medium=docs) | +| Snapshot Date | Size | Download Link | sha256sum | +| ----------------------------- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------- | +| Latest by Optimism Foundation | >4TB | [Mirror 1](https://datadirs.optimism.io/latest?utm_source=op-docs&utm_medium=docs)
    [Mirror 2 (torrent)](https://datadirs.optimism.io/latest.torrent?utm_source=op-docs&utm_medium=docs) | [sha256sum](https://datadirs.optimism.io/latest.sha256sum/?utm_source=op-docs&utm_medium=docs) | ### OP Mainnet (legacy) -| Snapshot Date | Size | Download Link | sha256sum | -| ------------- | ----- | ------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- | -| 2023-06-06 | 2.9TB | [Mirror 1](https://datadirs.optimism.io/mainnet-legacy-archival.tar.zst?utm_source=op-docs&utm_medium=docs) | `4adedb61125b81b55f9bdccc2e85092050c65ef2253c86e2b79569732b772829` | +| Snapshot Date | Size | Download Link | sha256sum | +| ------------- | ----- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- | +| 2023-06-06 | 2.9TB | [Mirror 1](https://datadirs.optimism.io/mainnet-legacy-archival.tar.zst?utm_source=op-docs&utm_medium=docs) | `4adedb61125b81b55f9bdccc2e85092050c65ef2253c86e2b79569732b772829` | diff --git a/pages/operators/node-operators/network-upgrades.mdx b/pages/operators/node-operators/network-upgrades.mdx index c4df0b1df..c24769869 100644 --- a/pages/operators/node-operators/network-upgrades.mdx +++ b/pages/operators/node-operators/network-upgrades.mdx @@ -30,15 +30,15 @@ The network upgrade naming scheme after the Bedrock upgrade follows a geology th Network upgrades are activated by timestamps. Failing to upgrade your OP Stack software before the timestamp will cause a chain divergence and you will need to resync the chain. Optimistic activation times refer to times that are pending governance approval. -| Upgrade | Governance Approval | [Mainnet Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml) | [Sepolia Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/sepolia/superchain.toml) | -| --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | -| [Holocene](https://specs.optimism.io/protocol/holocene/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515) | Thu Jan 9 18:00:01 UTC 2025 (`1736445601`) | Tue Nov 26 15:00:00 UTC 2024 (`1732633200`) | -| [Granite](https://specs.optimism.io/protocol/granite/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | -| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | -| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | -| [Delta](https://specs.optimism.io/protocol/delta/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | -| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | -| Bedrock | [approved](https://gov.optimism.io/t/final-upgrade-1-bedrock-protocol-upgrade-v2/5548) | Tue Jun 06 2023 16:28:23 UTC (`1686079703`) at block `105235063` | N/A | +| Upgrade | Governance Approval | [Mainnet Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml) | [Sepolia Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/sepolia/superchain.toml) | +| --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | +| [Holocene](https://specs.optimism.io/protocol/holocene/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515) | Thu Jan 9 18:00:01 UTC 2025 (`1736445601`) | Tue Nov 26 15:00:00 UTC 2024 (`1732633200`) | +| [Granite](https://specs.optimism.io/protocol/granite/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | +| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | +| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | +| [Delta](https://specs.optimism.io/protocol/delta/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | +| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | +| Bedrock | [approved](https://gov.optimism.io/t/final-upgrade-1-bedrock-protocol-upgrade-v2/5548) | Tue Jun 06 2023 16:28:23 UTC (`1686079703`) at block `105235063` | N/A | ## Upgrade process From 324b7fb7fb576b863ae6c69a8d4e1cc962533056 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Mon, 7 Apr 2025 20:39:08 +0100 Subject: [PATCH 3/5] Auto-fix: Update breadcrumbs, spelling dictionary and other automated fixes --- .../node-operators/management/snapshots.mdx | 4 ++-- .../operators/node-operators/network-upgrades.mdx | 14 +++++++------- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/pages/operators/node-operators/management/snapshots.mdx b/pages/operators/node-operators/management/snapshots.mdx index c0e7ea492..0bb8d7730 100644 --- a/pages/operators/node-operators/management/snapshots.mdx +++ b/pages/operators/node-operators/management/snapshots.mdx @@ -65,10 +65,10 @@ Migrated OP Mainnet databases can be generated manually or pre-migrated database | Snapshot Date | Size | Download Link | sha256sum | | ----------------------------- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------- | -| Latest by Optimism Foundation | >4TB | [Mirror 1](https://datadirs.optimism.io/latest?utm_source=op-docs&utm_medium=docs)
    [Mirror 2 (torrent)](https://datadirs.optimism.io/latest.torrent?utm_source=op-docs&utm_medium=docs) | [sha256sum](https://datadirs.optimism.io/latest.sha256sum/?utm_source=op-docs&utm_medium=docs) | +| Latest by Optimism Foundation | >4TB | [Mirror 1](https://datadirs.optimism.io/latest?utm_source=op-docs\&utm_medium=docs)
    [Mirror 2 (torrent)](https://datadirs.optimism.io/latest.torrent?utm_source=op-docs\&utm_medium=docs) | [sha256sum](https://datadirs.optimism.io/latest.sha256sum/?utm_source=op-docs\&utm_medium=docs) | ### OP Mainnet (legacy) | Snapshot Date | Size | Download Link | sha256sum | | ------------- | ----- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- | -| 2023-06-06 | 2.9TB | [Mirror 1](https://datadirs.optimism.io/mainnet-legacy-archival.tar.zst?utm_source=op-docs&utm_medium=docs) | `4adedb61125b81b55f9bdccc2e85092050c65ef2253c86e2b79569732b772829` | +| 2023-06-06 | 2.9TB | [Mirror 1](https://datadirs.optimism.io/mainnet-legacy-archival.tar.zst?utm_source=op-docs\&utm_medium=docs) | `4adedb61125b81b55f9bdccc2e85092050c65ef2253c86e2b79569732b772829` | diff --git a/pages/operators/node-operators/network-upgrades.mdx b/pages/operators/node-operators/network-upgrades.mdx index c24769869..2045251e1 100644 --- a/pages/operators/node-operators/network-upgrades.mdx +++ b/pages/operators/node-operators/network-upgrades.mdx @@ -32,12 +32,12 @@ Network upgrades are activated by timestamps. Failing to upgrade your OP Stack s | Upgrade | Governance Approval | [Mainnet Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml) | [Sepolia Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/sepolia/superchain.toml) | | --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | -| [Holocene](https://specs.optimism.io/protocol/holocene/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515) | Thu Jan 9 18:00:01 UTC 2025 (`1736445601`) | Tue Nov 26 15:00:00 UTC 2024 (`1732633200`) | -| [Granite](https://specs.optimism.io/protocol/granite/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | -| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | -| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | -| [Delta](https://specs.optimism.io/protocol/delta/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | -| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | +| [Holocene](https://specs.optimism.io/protocol/holocene/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515) | Thu Jan 9 18:00:01 UTC 2025 (`1736445601`) | Tue Nov 26 15:00:00 UTC 2024 (`1732633200`) | +| [Granite](https://specs.optimism.io/protocol/granite/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | +| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | +| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | +| [Delta](https://specs.optimism.io/protocol/delta/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | +| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | | Bedrock | [approved](https://gov.optimism.io/t/final-upgrade-1-bedrock-protocol-upgrade-v2/5548) | Tue Jun 06 2023 16:28:23 UTC (`1686079703`) at block `105235063` | N/A | ## Upgrade process @@ -86,4 +86,4 @@ then the software is deployed on production networks. ## More information * To check for the latest node software, see the [Software Releases](/operators/node-operators/releases). -* For more information on the governance process see the [governance documentation](https://community.optimism.io/docs/governance/?utm_source=op-docs&utm_medium=docs). +* For more information on the governance process see the [governance documentation](https://community.optimism.io/docs/governance/?utm_source=op-docs\&utm_medium=docs). From 7d3e6376db8c4ad19a5fa59b6d81d37454242b59 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Tue, 8 Apr 2025 17:04:40 +0100 Subject: [PATCH 4/5] added utm source to more pages --- .../transactions/troubleshooting.mdx | 2 +- .../tutorials/supersim/chain-env/chain-a.mdx | 2 +- .../tutorials/supersim/chain-env/chain-b.mdx | 2 +- .../supersim/chain-env/included-contracts.mdx | 4 ++-- .../tutorials/supersim/deposit-transactions.mdx | 2 +- .../chain-operators/configuration/rollup.mdx | 2 +- .../tutorials/integrating-da-layer.mdx | 2 +- .../node-operators/management/snapshots.mdx | 6 +++--- .../node-operators/network-upgrades.mdx | 14 +++++++------- pages/stack/interop/interop-security.mdx | 4 ++-- pages/stack/interop/op-supervisor.mdx | 2 +- pages/stack/interop/predeploy.mdx | 6 +++--- pages/stack/interop/tools/devnet.mdx | 4 ++-- pages/stack/interop/tools/rc-alpha.mdx | 2 +- .../tutorials/deploy-superchain-erc20.mdx | 2 +- pages/stack/interop/tutorials/event-contests.mdx | 2 +- pages/stack/interop/tutorials/event-reads.mdx | 2 +- .../interop/tutorials/relay-messages-cast.mdx | 4 ++-- pages/stack/rollup/derivation-pipeline.mdx | 2 +- pages/stack/rollup/outages.mdx | 6 +++--- pages/stack/rollup/overview.mdx | 16 ++++++++-------- pages/stack/security/faq-sec-model.mdx | 2 +- pages/stack/transactions/deposit-flow.mdx | 2 +- pages/stack/transactions/fees.mdx | 2 +- pages/stack/transactions/transaction-flow.mdx | 4 ++-- pages/superchain/standard-configuration.mdx | 8 ++++---- pages/superchain/superchain-upgrades.mdx | 10 +++++----- 27 files changed, 58 insertions(+), 58 deletions(-) diff --git a/pages/app-developers/transactions/troubleshooting.mdx b/pages/app-developers/transactions/troubleshooting.mdx index 51986acfd..57f0ebe3b 100644 --- a/pages/app-developers/transactions/troubleshooting.mdx +++ b/pages/app-developers/transactions/troubleshooting.mdx @@ -54,7 +54,7 @@ As a user, you are the final authority on transaction fields. Sometimes when sub ## Deposit transactions don't have a chainId on L2 - [Deposit transactions](https://specs.optimism.io/protocol/deposits.html#the-deposited-transaction-type) are transactions added to the L2 blockchain as part of the block derivation process. + [Deposit transactions](https://specs.optimism.io/protocol/deposits.html?utm_source=op-docs&utm_medium=docs#the-deposited-transaction-type) are transactions added to the L2 blockchain as part of the block derivation process. These transactions come from a dummy address and don't have a signature. Because in Ethereum the chainID is encoded as part of the signature, this means there is no recoverable chainID for these transactions. diff --git a/pages/app-developers/tutorials/supersim/chain-env/chain-a.mdx b/pages/app-developers/tutorials/supersim/chain-env/chain-a.mdx index 7c964e927..2b9c105f3 100644 --- a/pages/app-developers/tutorials/supersim/chain-env/chain-a.mdx +++ b/pages/app-developers/tutorials/supersim/chain-env/chain-a.mdx @@ -102,4 +102,4 @@ This guide provides network details and contract addresses for OPChainA (chainID ## Next steps * Learn how to [deposit transactions](/app-developers/tutorials/supersim/deposit-transactions) with Supersim, using a much simpler approach that bypasses the derivation pipeline. -* For more info about how Superchain interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html). +* For more info about how Superchain interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html?utm_source=op-docs&utm_medium=docs). diff --git a/pages/app-developers/tutorials/supersim/chain-env/chain-b.mdx b/pages/app-developers/tutorials/supersim/chain-env/chain-b.mdx index e6ea7e13f..39cb9b521 100644 --- a/pages/app-developers/tutorials/supersim/chain-env/chain-b.mdx +++ b/pages/app-developers/tutorials/supersim/chain-env/chain-b.mdx @@ -102,4 +102,4 @@ This guide provides network details and contract addresses for OPChainB (chainID ## Next steps * Learn how to [deposit transactions](/app-developers/tutorials/supersim/deposit-transactions) with Supersim, using a much simpler approach that bypasses the derivation pipeline. -* For more info about how Superchain interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html). +* For more info about how Superchain interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html?utm_source=op-docs&utm_medium=docs). diff --git a/pages/app-developers/tutorials/supersim/chain-env/included-contracts.mdx b/pages/app-developers/tutorials/supersim/chain-env/included-contracts.mdx index 137fe275b..11bae1c64 100644 --- a/pages/app-developers/tutorials/supersim/chain-env/included-contracts.mdx +++ b/pages/app-developers/tutorials/supersim/chain-env/included-contracts.mdx @@ -31,8 +31,8 @@ For more details, see [example contracts](/superchain/addresses#ethereum-l1) or The OP Stack system contracts on the L2 are included at the standard addresses by default. * [Standard OP Stack predeploys (L2)](https://specs.optimism.io/protocol/predeploys.html) -* [Interoperability predeploys (*experimental*) (L2)](https://specs.optimism.io/interop/predeploys.html) -* [OP Stack preinstalls (L2)](https://specs.optimism.io/protocol/preinstalls.html) +* [Interoperability predeploys (*experimental*) (L2)](https://specs.optimism.io/interop/predeploys.html?utm_source=op-docs&utm_medium=docs) +* [OP Stack preinstalls (L2)](https://specs.optimism.io/protocol/preinstalls.html?utm_source=op-docs&utm_medium=docs) ## Periphery contracts (L2) diff --git a/pages/app-developers/tutorials/supersim/deposit-transactions.mdx b/pages/app-developers/tutorials/supersim/deposit-transactions.mdx index 6c8a35607..eb78db734 100644 --- a/pages/app-developers/tutorials/supersim/deposit-transactions.mdx +++ b/pages/app-developers/tutorials/supersim/deposit-transactions.mdx @@ -108,4 +108,4 @@ We'll run through a sample deposit directly with the `OptimismPortal` using cast * See the [transaction guides](/app-developers/transactions) for more detailed information. * Questions about Interop? Check out collection of [interop guides](/stack/interop) or check out this [Superchain interop design video walk-thru](https://www.youtube.com/watch?v=FKc5RgjtGes). -* For more info about how Superchain interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html). +* For more info about how Superchain interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html?utm_source=op-docs&utm_medium=docs). diff --git a/pages/operators/chain-operators/configuration/rollup.mdx b/pages/operators/chain-operators/configuration/rollup.mdx index 51b846f22..55e5cce09 100644 --- a/pages/operators/chain-operators/configuration/rollup.mdx +++ b/pages/operators/chain-operators/configuration/rollup.mdx @@ -454,7 +454,7 @@ SuperchainConfig. Has the ability to pause withdrawals. * **Recommended value:** * **Notes:** Must not be `address(0)` * **Standard Config Requirement:** [0x09f7150D8c019BeF34450d6920f6B3608ceFdAf2](https://etherscan.io/address/0x09f7150D8c019BeF34450d6920f6B3608ceFdAf2) -A 1/1 Safe owned by the Security Council Safe, with the [Deputy Guardian Module](https://specs.optimism.io/protocol/safe-extensions.html#deputy-guardian-module?utm_source=op-docs&utm_medium=docs) +A 1/1 Safe owned by the Security Council Safe, with the [Deputy Guardian Module](https://specs.optimism.io/protocol/safe-extensions.html?utm_source=op-docs&utm_medium=docs#deputy-guardian-module) enabled to allow the Optimism Foundation to act as Guardian. *** diff --git a/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx b/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx index c6bb231b1..85e21418f 100644 --- a/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx +++ b/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx @@ -38,7 +38,7 @@ Our suggestion is for every DA Layer to build and maintain their own DA Server, * It must be able to validate the data returned from the data (i.e., include a cryptographic commitment to the data like a hash, merkle proof, or polynomial commitment, this could be done against the block hash with a complex proof). - See the [specs](https://specs.optimism.io/experimental/alt-da.html?highlight=input-commitment-submission#input-commitment-submission) for more info on commitment submission. + See the [specs](https://specs.optimism.io/experimental/alt-da.html?highlight=input-commitment-submission?utm_source=op-docs&utm_medium=docs#input-commitment-submission) for more info on commitment submission. ### Claim your da\_layer byte diff --git a/pages/operators/node-operators/management/snapshots.mdx b/pages/operators/node-operators/management/snapshots.mdx index 0bb8d7730..b0dff75d6 100644 --- a/pages/operators/node-operators/management/snapshots.mdx +++ b/pages/operators/node-operators/management/snapshots.mdx @@ -60,15 +60,15 @@ Migrated OP Mainnet databases can be generated manually or pre-migrated database ### OP Mainnet (archive node) - You can also download access the [Optimism Foundation datadir explorer](https://datadirs.optimism.io/?utm_source=op-docs\&utm_medium=docs) to find other snapshots. + You can also download access the [Optimism Foundation datadir explorer](https://datadirs.optimism.io/?utm_source=op-docs&utm_medium=docs) to find other snapshots. | Snapshot Date | Size | Download Link | sha256sum | | ----------------------------- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------- | -| Latest by Optimism Foundation | >4TB | [Mirror 1](https://datadirs.optimism.io/latest?utm_source=op-docs\&utm_medium=docs)
    [Mirror 2 (torrent)](https://datadirs.optimism.io/latest.torrent?utm_source=op-docs\&utm_medium=docs) | [sha256sum](https://datadirs.optimism.io/latest.sha256sum/?utm_source=op-docs\&utm_medium=docs) | +| Latest by Optimism Foundation | >4TB | [Mirror 1](https://datadirs.optimism.io/latest?utm_source=op-docs&utm_medium=docs)
    [Mirror 2 (torrent)](https://datadirs.optimism.io/latest.torrent?utm_source=op-docs&utm_medium=docs) | [sha256sum](https://datadirs.optimism.io/latest.sha256sum/?utm_source=op-docs&utm_medium=docs) | ### OP Mainnet (legacy) | Snapshot Date | Size | Download Link | sha256sum | | ------------- | ----- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- | -| 2023-06-06 | 2.9TB | [Mirror 1](https://datadirs.optimism.io/mainnet-legacy-archival.tar.zst?utm_source=op-docs\&utm_medium=docs) | `4adedb61125b81b55f9bdccc2e85092050c65ef2253c86e2b79569732b772829` | +| 2023-06-06 | 2.9TB | [Mirror 1](https://datadirs.optimism.io/mainnet-legacy-archival.tar.zst?utm_source=op-docs&utm_medium=docs) | `4adedb61125b81b55f9bdccc2e85092050c65ef2253c86e2b79569732b772829` | diff --git a/pages/operators/node-operators/network-upgrades.mdx b/pages/operators/node-operators/network-upgrades.mdx index 2045251e1..c24769869 100644 --- a/pages/operators/node-operators/network-upgrades.mdx +++ b/pages/operators/node-operators/network-upgrades.mdx @@ -32,12 +32,12 @@ Network upgrades are activated by timestamps. Failing to upgrade your OP Stack s | Upgrade | Governance Approval | [Mainnet Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml) | [Sepolia Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/sepolia/superchain.toml) | | --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | -| [Holocene](https://specs.optimism.io/protocol/holocene/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515) | Thu Jan 9 18:00:01 UTC 2025 (`1736445601`) | Tue Nov 26 15:00:00 UTC 2024 (`1732633200`) | -| [Granite](https://specs.optimism.io/protocol/granite/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | -| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | -| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | -| [Delta](https://specs.optimism.io/protocol/delta/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | -| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | +| [Holocene](https://specs.optimism.io/protocol/holocene/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515) | Thu Jan 9 18:00:01 UTC 2025 (`1736445601`) | Tue Nov 26 15:00:00 UTC 2024 (`1732633200`) | +| [Granite](https://specs.optimism.io/protocol/granite/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | +| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | +| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | +| [Delta](https://specs.optimism.io/protocol/delta/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | +| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | | Bedrock | [approved](https://gov.optimism.io/t/final-upgrade-1-bedrock-protocol-upgrade-v2/5548) | Tue Jun 06 2023 16:28:23 UTC (`1686079703`) at block `105235063` | N/A | ## Upgrade process @@ -86,4 +86,4 @@ then the software is deployed on production networks. ## More information * To check for the latest node software, see the [Software Releases](/operators/node-operators/releases). -* For more information on the governance process see the [governance documentation](https://community.optimism.io/docs/governance/?utm_source=op-docs\&utm_medium=docs). +* For more information on the governance process see the [governance documentation](https://community.optimism.io/docs/governance/?utm_source=op-docs&utm_medium=docs). diff --git a/pages/stack/interop/interop-security.mdx b/pages/stack/interop/interop-security.mdx index f249d964d..4f0ae5c1d 100644 --- a/pages/stack/interop/interop-security.mdx +++ b/pages/stack/interop/interop-security.mdx @@ -60,7 +60,7 @@ Excluding L1 reorgs, this can happen in two ways: A deposit only block only contains the deposit transactions and some internal transactions, not the sequencer transactions. - For more information about this process, [see the technical specifications](https://specs.optimism.io/protocol/derivation.html#deriving-the-transaction-list). + For more information about this process, [see the technical specifications](https://specs.optimism.io/protocol/derivation.html?utm_source=op-docs&utm_medium=docs#deriving-the-transaction-list). ## The latency/security tradeoff @@ -170,5 +170,5 @@ The protocol enforces the fact that all executing messages are valid. It does th * Build a [revolutionary app](/app-developers/get-started) that uses multiple blockchains within the Superchain * Deploy a [SuperchainERC20](/stack/interop/tutorials/deploy-superchain-erc20) to the Superchain -* For more info about how Superchain interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html) +* For more info about how Superchain interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html?utm_source=op-docs&utm_medium=docs) * View more [interop tutorials](/stack/interop/tutorials) diff --git a/pages/stack/interop/op-supervisor.mdx b/pages/stack/interop/op-supervisor.mdx index 6ae585b64..fca718441 100644 --- a/pages/stack/interop/op-supervisor.mdx +++ b/pages/stack/interop/op-supervisor.mdx @@ -95,4 +95,4 @@ For a full listing of API names, see the [source code](https://github.com/ethere * Build a [revolutionary app](/app-developers/get-started) that uses multiple blockchains within the Superchain * Deploy a [SuperchainERC20](/stack/interop/tutorials/deploy-superchain-erc20) to the Superchain * Learn [how ETH can move across chains](https://docs.optimism.io/stack/interop/superchain-weth) -* For more info about how Superchain interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html). +* For more info about how Superchain interoperability works under the hood, [check out the specs](https://specs.optimism.io/interop/overview.html?utm_source=op-docs&utm_medium=docs). diff --git a/pages/stack/interop/predeploy.mdx b/pages/stack/interop/predeploy.mdx index 733287d6b..cd784ef9b 100644 --- a/pages/stack/interop/predeploy.mdx +++ b/pages/stack/interop/predeploy.mdx @@ -38,7 +38,7 @@ The `CrossL2Inbox` is the system predeploy for cross chain messaging. Anyone can trigger the execution or validation of cross chain messages, on behalf of any user. * **Address:** `0x4200000000000000000000000000000000000022` -* **Specs:** [`CrossL2Inbox`](https://specs.optimism.io/interop/predeploys.html#crossl2inbox) +* **Specs:** [`CrossL2Inbox`](https://specs.optimism.io/interop/predeploys.html?utm_source=op-docs&utm_medium=docs#crossl2inbox) * **Source code:** [`CrossL2Inbox`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/CrossL2Inbox.sol) ## L2ToL2CrossDomainMessenger @@ -48,7 +48,7 @@ It's utilized for secure ERC20 token transfers between L2 chains. Messages sent through the `L2ToL2CrossDomainMessenger` on the source chain receive both replay protection and domain binding (the executing transaction can only be valid on a single chain). * **Address:** `0x4200000000000000000000000000000000000023` -* **Specs:** [`L2ToL2CrossDomainMessenger`](https://specs.optimism.io/interop/predeploys.html#l2tol2crossdomainmessenger) +* **Specs:** [`L2ToL2CrossDomainMessenger`](https://specs.optimism.io/interop/predeploys.html?utm_source=op-docs&utm_medium=docs#l2tol2crossdomainmessenger) * **Source code:** [`L2ToL2CrossDomainMessenger`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/L2ToL2CrossDomainMessenger.sol) {/* @@ -76,7 +76,7 @@ This contract is the `Beacon` part, which provides the implementation address fo The `SuperchainTokenBridge` is an abstraction on top of the `L2ToL2CrossDomainMessenger` that facilitates token bridging using interop. It has mint and burn rights over `SuperchainERC20` tokens, as described in the [token bridging spec](https://specs.optimism.io/interop/token-bridging.html). * **Address:** `0x4200000000000000000000000000000000000028` -* **Specs:** [`SuperchainTokenBridge`](https://specs.optimism.io/interop/predeploys.html#superchainerc20bridge) +* **Specs:** [`SuperchainTokenBridge`](https://specs.optimism.io/interop/predeploys.html?utm_source=op-docs&utm_medium=docs#superchainerc20bridge) * **Source code:** [`SuperchainTokenBridge`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/SuperchainTokenBridge.sol) diff --git a/pages/stack/interop/tools/devnet.mdx b/pages/stack/interop/tools/devnet.mdx index 15948880c..d7a37e303 100644 --- a/pages/stack/interop/tools/devnet.mdx +++ b/pages/stack/interop/tools/devnet.mdx @@ -84,7 +84,7 @@ To support Superchain Interop and DeFi experimentation, Uni V4 has been deployed ### Get testnet ETH from the Superchain Faucet - You can utilize the [Superchain Faucet](https://console.optimism.io/faucet) to get `ETH` on `interop-alpha-0` and `interop-alpha-1`. + You can utilize the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) to get `ETH` on `interop-alpha-0` and `interop-alpha-1`. ## Bridging ETH to the interop devnet @@ -92,7 +92,7 @@ To support Superchain Interop and DeFi experimentation, Uni V4 has been deployed ### Get Sepolia ETH from the Superchain Faucet - You can utilize the [Superchain Faucet](https://console.optimism.io/faucet) to get `ETH` on Sepolia. + You can utilize the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) to get `ETH` on Sepolia. ### Send the Sepolia ETH to the devnet diff --git a/pages/stack/interop/tools/rc-alpha.mdx b/pages/stack/interop/tools/rc-alpha.mdx index baf3fd89b..3461b91cc 100644 --- a/pages/stack/interop/tools/rc-alpha.mdx +++ b/pages/stack/interop/tools/rc-alpha.mdx @@ -62,7 +62,7 @@ import { Callout, Tabs, Steps } from 'nextra/components' ### Get Sepolia ETH from the Superchain Faucet - You can utilize the [Superchain Faucet](https://console.optimism.io/faucet) to get `ETH` on Sepolia. + You can utilize the [Superchain Faucet](https://console.optimism.io/faucet?utm_source=op-docs&utm_medium=docs) to get `ETH` on Sepolia. ### Send the Sepolia ETH to the devnet diff --git a/pages/stack/interop/tutorials/deploy-superchain-erc20.mdx b/pages/stack/interop/tutorials/deploy-superchain-erc20.mdx index 4b12c6e42..daab75827 100644 --- a/pages/stack/interop/tutorials/deploy-superchain-erc20.mdx +++ b/pages/stack/interop/tutorials/deploy-superchain-erc20.mdx @@ -192,5 +192,5 @@ The tutorial uses these primary tools: * Learn how to [transfer tokens between chains inside the Superchain](transfer-superchainERC20). * Use the [SuperchainERC20 Starter Kit](/app-developers/starter-kit) to deploy your token across the Superchain. -* Explore the [SuperchainERC20 specifications](https://specs.optimism.io/interop/token-bridging.html) for in-depth implementation details. +* Explore the [SuperchainERC20 specifications](https://specs.optimism.io/interop/token-bridging.html?utm_source=op-docs&utm_medium=docs) for in-depth implementation details. * Review the [Superchain Interop Explainer](/stack/interop/explainer) for answers to common questions about interoperability. diff --git a/pages/stack/interop/tutorials/event-contests.mdx b/pages/stack/interop/tutorials/event-contests.mdx index b15df8eea..705ff0a49 100644 --- a/pages/stack/interop/tutorials/event-contests.mdx +++ b/pages/stack/interop/tutorials/event-contests.mdx @@ -41,7 +41,7 @@ Unlike [TicTacToe](/stack/interop/tutorials/event-reads) which is deployed on ev ### Read cross-chain events - The system predeploy that enables pulling in validated cross-chain events is the [CrossL2Inbox](https://specs.optimism.io/interop/predeploys.html#crossl2inbox). + The system predeploy that enables pulling in validated cross-chain events is the [CrossL2Inbox](https://specs.optimism.io/interop/predeploys.html?utm_source=op-docs&utm_medium=docs#crossl2inbox). ```solidity contract ICrossL2Inbox { diff --git a/pages/stack/interop/tutorials/event-reads.mdx b/pages/stack/interop/tutorials/event-reads.mdx index ba24580f2..b91c0372d 100644 --- a/pages/stack/interop/tutorials/event-reads.mdx +++ b/pages/stack/interop/tutorials/event-reads.mdx @@ -34,7 +34,7 @@ This guide reviews a horizontally scalable implementation of TicTacToe. This [im We use events to define the ordering of a game with players only maintaining a local view. By default, a chain is also a part of its own interoperable dependency set, which means players on the same chain can also play each other **with no code changes**! -The system predeploy that enables pulling in validated cross-chain events is the [CrossL2Inbox](https://specs.optimism.io/interop/predeploys.html#crossl2inbox). +The system predeploy that enables pulling in validated cross-chain events is the [CrossL2Inbox](https://specs.optimism.io/interop/predeploys.html?utm_source=op-docs&utm_medium=docs#crossl2inbox). ```solidity contract ICrossL2Inbox { diff --git a/pages/stack/interop/tutorials/relay-messages-cast.mdx b/pages/stack/interop/tutorials/relay-messages-cast.mdx index 0c9a0dcf6..40d7e4dc2 100644 --- a/pages/stack/interop/tutorials/relay-messages-cast.mdx +++ b/pages/stack/interop/tutorials/relay-messages-cast.mdx @@ -30,7 +30,7 @@ Please note that the OP Stack interoperability upgrade, required for crosschain # Relaying interop messages using `cast` -This tutorial walks through how to form a [message identifier](https://specs.optimism.io/interop/messaging.html#message-identifier) to relay a [L2ToL2CrossDomainMessenger](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/L2ToL2CrossDomainMessenger.sol) cross-chain call. +This tutorial walks through how to form a [message identifier](https://specs.optimism.io/interop/messaging.html?utm_source=op-docs&utm_medium=docs#message-identifier) to relay a [L2ToL2CrossDomainMessenger](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L2/L2ToL2CrossDomainMessenger.sol) cross-chain call. We'll perform the SuperchainERC20 interop transfer in [Supersim first steps](/app-developers/tutorials/supersim/getting-started/first-steps##send-an-interoperable-superchainerc20-token-from-chain-901-to-902-l2-to-l2-message-passing) by manually relaying the message without the autorelayer. @@ -59,7 +59,7 @@ Sending an interop message using the `L2ToL2CrossDomainMessenger`: ## Message identifier A message identifier uniquely identifies a log emitted on a chain. -The sequencer and smart contracts (CrossL2Inbox) use the identifier to perform [invariant checks](https://specs.optimism.io/interop/messaging.html#messaging-invariants) to confirm that the message is valid. +The sequencer and smart contracts (CrossL2Inbox) use the identifier to perform [invariant checks](https://specs.optimism.io/interop/messaging.html?utm_source=op-docs&utm_medium=docs#messaging-invariants) to confirm that the message is valid. ```solidity struct Identifier { diff --git a/pages/stack/rollup/derivation-pipeline.mdx b/pages/stack/rollup/derivation-pipeline.mdx index 691130825..ca1266036 100644 --- a/pages/stack/rollup/derivation-pipeline.mdx +++ b/pages/stack/rollup/derivation-pipeline.mdx @@ -46,5 +46,5 @@ The `sequencerWindowSize` parameter is set during the deployment configurations ## Next steps -* For more detailed information, refer to the [derivation pipeline specification](https://specs.optimism.io/protocol/derivation.html). +* For more detailed information, refer to the [derivation pipeline specification](https://specs.optimism.io/protocol/derivation.html?utm_source=op-docs&utm_medium=docs). * Have questions? You can ask a question in the [developer support forum](https://github.com/ethereum-optimism/developers/discussions). diff --git a/pages/stack/rollup/outages.mdx b/pages/stack/rollup/outages.mdx index 558fcaf43..f76326d86 100644 --- a/pages/stack/rollup/outages.mdx +++ b/pages/stack/rollup/outages.mdx @@ -108,14 +108,14 @@ It's important to understand these rules in detail to properly mitigate the effe For all transactions sent to the `OptimismPortal`: 1. Transactions sent within a specific L1 block are processed together. -2. Transactions are given a timestamp no more than [`max_sequencer_drift`](https://specs.optimism.io/protocol/derivation.html#overview) in the future. +2. Transactions are given a timestamp no more than [`max_sequencer_drift`](https://specs.optimism.io/protocol/derivation.html?utm_source=op-docs&utm_medium=docs#overview) in the future. 3. Transactions are processed in the order they are received. -4. Transactions are processed within the [`sequencer_window`](https://specs.optimism.io/glossary.html#sequencing-window). +4. Transactions are processed within the [`sequencer_window`](https://specs.optimism.io/glossary.html?utm_source=op-docs&utm_medium=docs#sequencing-window). In practice, this means that transactions sent to the `OptimismPortal` contract will always be processed in the order they are received and within a maximum delay of the `sequencer_window` (set to 12 hours by default but may differ from chain to chain). If the Sequencer is unavailable or transactions are not published to L1 within this `sequencer_window`, OP Stack chains will automatically reorganize themselves to guarantee that these transactions are included in the L2 chain. -Refer to the [L2 Chain Derivation Specification](https://specs.optimism.io/protocol/derivation.html) for a much more detailed explanation of how transactions sent to the `OptimismPortal` contract are processed. +Refer to the [L2 Chain Derivation Specification](https://specs.optimism.io/protocol/derivation.html?utm_source=op-docs&utm_medium=docs) for a much more detailed explanation of how transactions sent to the `OptimismPortal` contract are processed. ### Inclusion scenarios diff --git a/pages/stack/rollup/overview.mdx b/pages/stack/rollup/overview.mdx index 3f9cc775b..5a1571394 100644 --- a/pages/stack/rollup/overview.mdx +++ b/pages/stack/rollup/overview.mdx @@ -23,7 +23,7 @@ is_imported_content: 'false' The big idea that makes Optimism possible is the Optimistic Rollup. We'll go through a brief explainer of *how* Optimistic Rollups work at a high level. Then we'll explain *why* Optimism is built as an Optimistic Rollup and why we believe it's the best option for a system that addresses all of our design goals. -Check out the [protocol specs](https://specs.optimism.io/), if you want more details about the rollup protocol. +Check out the [protocol specs](https://specs.optimism.io/?utm_source=op-docs&utm_medium=docs), if you want more details about the rollup protocol. ## Optimistic rollups TL;DR @@ -38,7 +38,7 @@ In Bedrock, L2 blocks are saved to the Ethereum blockchain using a non-contract As these blocks are submitted as transactions using EIP-4844 [blobs](/operators/chain-operators/management/blobs), there is no way to modify or censor them after the "transaction" is included in a block that has enough attestations. This is the way that OP Mainnet inherits the availability and integrity guarantees of Ethereum. -Blocks are written to L1 in [a compressed format](https://specs.optimism.io/protocol/derivation.html#batch-submission-wire-format) to reduce costs. +Blocks are written to L1 in [a compressed format](https://specs.optimism.io/protocol/derivation.html?utm_source=op-docs&utm_medium=docs#batch-submission-wire-format) to reduce costs. This is important because writing to L1 is [the major cost of OP Mainnet transactions](/stack/transactions/fees). ## Block production @@ -62,7 +62,7 @@ Transactions get to the sequencer in two ways: The first block of the epoch includes all the deposits that happened in the L1 block to which it corresponds. If the sequencer attempts to ignore a legitimate L1 transaction, it ends up with a state that is inconsistent with the verifiers, same as if the sequencer tried to fake the state by other means. This provides OP Mainnet with L1 Ethereum level censorship resistance. - You can read more about this mechanism [in the protocol specifications](https://specs.optimism.io/protocol/derivation.html#deriving-the-transaction-list). + You can read more about this mechanism [in the protocol specifications](https://specs.optimism.io/protocol/derivation.html?utm_source=op-docs&utm_medium=docs#deriving-the-transaction-list). For the moment, [The Optimism Foundation](https://www.optimism.io/) runs the only block producer on OP Mainnet. @@ -72,11 +72,11 @@ The execution engine (implemented as the `op-geth` component) receives blocks us 1. The execution engine can update itself using a peer-to-peer network with other execution engines. This operates in the same way that the L1 execution clients synchronize the state across the network. - You can read more about it [in the specs](https://specs.optimism.io/protocol/exec-engine.html#happy-path-sync). + You can read more about it [in the specs](https://specs.optimism.io/protocol/exec-engine.html?utm_source=op-docs&utm_medium=docs#happy-path-sync). 2. The rollup node (implemented as the `op-node` component) derives the L2 blocks from L1. This mechanism is slower, but censorship resistant. - You can read more about it [in the specs](https://specs.optimism.io/protocol/exec-engine.html#worst-case-sync). + You can read more about it [in the specs](https://specs.optimism.io/protocol/exec-engine.html?utm_source=op-docs&utm_medium=docs#worst-case-sync). ## Bridging ETH or tokens between layers @@ -94,7 +94,7 @@ In Optimism terminology, transactions going from Ethereum (L1) to OP Mainnet (L2 You use [`L1CrossDomainMessenger`](https://github.com/ethereum-optimism/optimism/blob/v1.1.4/packages/contracts-bedrock/src/L1/L1CrossDomainMessenger.sol) or [`L1StandardBridge`](https://github.com/ethereum-optimism/optimism/blob/v1.1.4/packages/contracts-bedrock/src/L1/L1StandardBridge.sol). Deposit transactions become part of the canonical blockchain in the first L2 block of the "epoch" corresponding to the L1 block where the deposits were made. This L2 block will usually be created a few minutes after the corresponding L1 block. -You can read more about this [in the specs](https://specs.optimism.io/protocol/deposits.html). +You can read more about this [in the specs](https://specs.optimism.io/protocol/deposits.html?utm_source=op-docs&utm_medium=docs). ### Moving from OP Mainnet to Ethereum @@ -108,7 +108,7 @@ Withdrawals (the term is used for any OP Mainnet to Ethereum message) have three 3. After the fault challenge period ends (a week on mainnet, less than that on the test network), finalize the withdrawal. -[You can read the full withdrawal specifications here](https://specs.optimism.io/protocol/withdrawals.html) +[You can read the full withdrawal specifications here](https://specs.optimism.io/protocol/withdrawals.html?utm_source=op-docs&utm_medium=docs) ## Fault proofs @@ -117,7 +117,7 @@ Instead, these commitments are considered pending for a period of time (called t If a proposed state commitment goes unchallenged for the duration of the challenge window (currently set to 7 days), then it is considered final. Once a commitment is considered final, smart contracts on Ethereum can safely accept withdrawal proofs about the state of OP Mainnet based on that commitment. -When a state commitment is challenged, it can be invalidated through a "fault proof" ([formerly known as a "fraud proof"](https://specs.optimism.io/experimental/fault-proof/index.html)) process. +When a state commitment is challenged, it can be invalidated through a "fault proof" ([formerly known as a "fraud proof"](https://specs.optimism.io/experimental/fault-proof/index.html?utm_source=op-docs&utm_medium=docs)) process. If the commitment is successfully challenged, then it is removed from the `StateCommitmentChain` to eventually be replaced by another proposed commitment. It's important to note that a successful challenge does not roll back OP Mainnet itself, only the published commitments about the state of the chain. The ordering of transactions and the state of OP Mainnet is unchanged by a fault proof challenge. diff --git a/pages/stack/security/faq-sec-model.mdx b/pages/stack/security/faq-sec-model.mdx index 5a04855a6..e7370de22 100644 --- a/pages/stack/security/faq-sec-model.mdx +++ b/pages/stack/security/faq-sec-model.mdx @@ -24,7 +24,7 @@ import { Callout } from 'nextra/components' # OP Stack security model Many OP Stack chains, such as OP Mainnet, are a work in progress. -Constant, iterative improvement of the security mechanisms that safeguard OP Stack users is a top priority for the entire [Optimism Collective](https://community.optimism.io/docs/governance/). +Constant, iterative improvement of the security mechanisms that safeguard OP Stack users is a top priority for the entire [Optimism Collective](https://community.optimism.io/docs/governance/?utm_source=op-docs&utm_medium=docs). The Optimism Collective strives to be clear and transparent about the security of OP Stack chains and the OP Stack as a whole. ## Bottom line diff --git a/pages/stack/transactions/deposit-flow.mdx b/pages/stack/transactions/deposit-flow.mdx index 93903728a..71ba3d7e6 100644 --- a/pages/stack/transactions/deposit-flow.mdx +++ b/pages/stack/transactions/deposit-flow.mdx @@ -66,7 +66,7 @@ Information is encapsulated in lower layer packets on the sending side and then 1. The `op-node` component [looks for `TransactionDeposited` events on L1](https://github.com/ethereum-optimism/optimism/blob/62c7f3b05a70027b30054d4c8974f44000606fb7/op-node/rollup/derive/deposits.go#L13-L33). If it sees any such events, it [parses](https://github.com/ethereum-optimism/optimism/blob/62c7f3b05a70027b30054d4c8974f44000606fb7/op-node/rollup/derive/deposit_log.go) them. -2. Next, `op-node` [converts](https://github.com/ethereum-optimism/optimism/blob/62c7f3b05a70027b30054d4c8974f44000606fb7/op-node/rollup/derive/deposits.go#L35-L51) those `TransactionDeposited` events into [deposit transactions](https://specs.optimism.io/protocol/deposits.html#user-deposited-transactions). +2. Next, `op-node` [converts](https://github.com/ethereum-optimism/optimism/blob/62c7f3b05a70027b30054d4c8974f44000606fb7/op-node/rollup/derive/deposits.go#L35-L51) those `TransactionDeposited` events into [deposit transactions](https://specs.optimism.io/protocol/deposits.html?utm_source=op-docs&utm_medium=docs#user-deposited-transactions). 3. In most cases, user deposit transactions call the [`relayMessage`](https://github.com/ethereum-optimism/optimism/blob/62c7f3b05a70027b30054d4c8974f44000606fb7/packages/contracts-bedrock/contracts/universal/CrossDomainMessenger.sol#L291-L413) function of [`L2CrossDomainMessenger`](https://github.com/ethereum-optimism/optimism/blob/62c7f3b05a70027b30054d4c8974f44000606fb7/packages/contracts-bedrock/contracts/universal/CrossDomainMessenger.sol). diff --git a/pages/stack/transactions/fees.mdx b/pages/stack/transactions/fees.mdx index 532ded72a..bcd878248 100644 --- a/pages/stack/transactions/fees.mdx +++ b/pages/stack/transactions/fees.mdx @@ -26,7 +26,7 @@ import { Callout } from 'nextra/components' The OP Stack maintains a distinct gas limit compared to the Ethereum mainnet. While both chains use the same underlying transaction formats, Optimism's gas limits are tailored for optimal Layer 2 performance and scalability. As a result, transactions on Optimism may behave differently from the mainnet regarding gas usage and fee estimation. - For a detailed comparison of gas limits between Optimism and Ethereum, see the [Optimism Chain Differences documentation](https://docs.optimism.io/chain/differences#transaction-fees). + For a detailed comparison of gas limits between Optimism and Ethereum, see the [Optimism Chain Differences documentation](https://docs.optimism.io/chain/differences?utm_source=op-docs&utm_medium=docs#transaction-fees).     # Transaction fees on OP Mainnet diff --git a/pages/stack/transactions/transaction-flow.mdx b/pages/stack/transactions/transaction-flow.mdx index af55a19bf..0d87749f7 100644 --- a/pages/stack/transactions/transaction-flow.mdx +++ b/pages/stack/transactions/transaction-flow.mdx @@ -44,9 +44,9 @@ This guide explains the transaction flow process for rollup transactions. The pr ### Compression -The batcher aggregates [sequencer batches](https://specs.optimism.io/glossary.html#sequencer-batch) into [channels](https://specs.optimism.io/glossary.html#channel). +The batcher aggregates [sequencer batches](https://specs.optimism.io/glossary.html?utm_source=op-docs&utm_medium=docs#sequencer-batch) into [channels](https://specs.optimism.io/glossary.html?utm_source=op-docs&utm_medium=docs#channel). This allows for more data per compression frame, and therefore a better compression ratio. -You can read more about this process [in the specs](https://specs.optimism.io/protocol/derivation.html#batch-submission). +You can read more about this process [in the specs](https://specs.optimism.io/protocol/derivation.html?utm_source=op-docs&utm_medium=docs#batch-submission). When a channel is full or times out it is compressed and written. diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index b6fdcc6c7..e169ae770 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 1. **Technical conformance:** * Compliance with the consensus parameters, policy parameters, admin roles, and service roles defined in the specifications. - For more details, please see 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?utm_source=op-docs&utm_medium=docs). * Utilization of officially supported features and modules of the OP Stack. 2. **Governance alignment:** @@ -107,7 +107,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?utm_source=op-docs&utm_medium=docs) and the Blockspace Charter. 2. **Use op-deployer:** Leverage [op-deployer](/operators/chain-operators/tools/op-deployer) to ensure your chain aligns with standard configurations. @@ -119,10 +119,10 @@ 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. 5. **Contribute to the ecosystem:** - Engage with the [Optimism Collective](https://community.optimism.io/) to share feedback and propose improvements. + Engage with the [Optimism Collective](https://community.optimism.io/?utm_source=op-docs&utm_medium=docs) to share feedback and propose improvements. ## References -* [OP Stack Specifications](https://specs.optimism.io/protocol/configurability.html) +* [OP Stack Specifications](https://specs.optimism.io/protocol/configurability.html?utm_source=op-docs&utm_medium=docs) * [Blockspace Charter](/superchain/blockspace-charter) * [Superchain Registry](https://github.com/ethereum-optimism/superchain-registry) diff --git a/pages/superchain/superchain-upgrades.mdx b/pages/superchain/superchain-upgrades.mdx index 79f66d41b..ce78f9b4b 100644 --- a/pages/superchain/superchain-upgrades.mdx +++ b/pages/superchain/superchain-upgrades.mdx @@ -25,19 +25,19 @@ This document provides a high-level overview of the key components and processes ## Superchain target -In the context of Superchain upgrades, the **[Superchain target](https://specs.optimism.io/protocol/superchain-upgrades.html#superchain-target)** refers to a set of upgrade parameters that multiple chains in the Superchain should adhere to, enabling synchronized network upgrades. +In the context of Superchain upgrades, the **[Superchain target](https://specs.optimism.io/protocol/superchain-upgrades.html?utm_source=op-docs&utm_medium=docs#superchain-target)** refers to a set of upgrade parameters that multiple chains in the Superchain should adhere to, enabling synchronized network upgrades. By aligning with a common Superchain target, chains can implement consensus-breaking changes simultaneously, maintaining compatibility and coherence across the Superchain ecosystem. This approach streamlines the upgrade process and reduces fragmentation within the Superchain. ## ProtocolVersion L1 smart contract -The **[ProtocolVersion](https://specs.optimism.io/protocol/superchain-upgrades.html#protocolversions-l1-contract)** L1 smart contract serves as an on-chain registry that records the protocol versions supported by various chains within the Superchain. +The **[ProtocolVersion](https://specs.optimism.io/protocol/superchain-upgrades.html?utm_source=op-docs&utm_medium=docs#protocolversions-l1-contract)** L1 smart contract serves as an on-chain registry that records the protocol versions supported by various chains within the Superchain. It provides a standardized mechanism for chains to signal their current protocol version, facilitating coordination and compatibility checks among different chains. This contract is instrumental in managing and tracking the progression of protocol versions across the Superchain. ## Superchain version signaling -**[Superchain version signaling](https://specs.optimism.io/protocol/superchain-upgrades.html#superchain-version-signaling)** is a mechanism that allows nodes and clients to be aware of and prepare for upcoming protocol changes. +**[Superchain version signaling](https://specs.optimism.io/protocol/superchain-upgrades.html?utm_source=op-docs&utm_medium=docs#superchain-version-signaling)** is a mechanism that allows nodes and clients to be aware of and prepare for upcoming protocol changes. This signaling is achieved through the **ProtocolVersion smart contract**, allowing chains to indicate their readiness for upcoming upgrades and ensuring that all participating chains are synchronized. If the node see's a versioning signal onchain before the node software has been updated for a hardfork, the node will [halt](/superchain/superchain-upgrades#rolluphalt-flags-on-node-binaries) to prevent chain divergence Through this signaling: @@ -46,7 +46,7 @@ Through this signaling: ## Activation rules -**[Activation rules](https://specs.optimism.io/protocol/superchain-upgrades.html#activation-rules)** define the conditions under which a network upgrade or hardfork becomes active within the Superchain. +**[Activation rules](https://specs.optimism.io/protocol/superchain-upgrades.html?utm_source=op-docs&utm_medium=docs#activation-rules)** define the conditions under which a network upgrade or hardfork becomes active within the Superchain. These rules are based on specific timestamps, dictating when the new protocol changes take effect. * **Block Height Activation:** The upgrade activates at a predetermined block number. @@ -71,4 +71,4 @@ Ensure you understand its implications before applying it to your node configura Coordinated upgrades within the Superchain are essential for maintaining network integrity and performance. By understanding and implementing all the components mentioned in this guide, network participants can ensure smooth transitions during protocol upgrades. -For comprehensive guidelines and technical specifications, refer to the [Superchain upgrades spec](https://specs.optimism.io/protocol/superchain-upgrades.html). +For comprehensive guidelines and technical specifications, refer to the [Superchain upgrades spec](https://specs.optimism.io/protocol/superchain-upgrades.html?utm_source=op-docs&utm_medium=docs). From b01e9c6ff1e63020f4b6a3731017227ed3f885e8 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Tue, 8 Apr 2025 17:05:28 +0100 Subject: [PATCH 5/5] Auto-fix: Update breadcrumbs, spelling dictionary and other automated fixes --- .../node-operators/management/snapshots.mdx | 6 +++--- .../operators/node-operators/network-upgrades.mdx | 14 +++++++------- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/pages/operators/node-operators/management/snapshots.mdx b/pages/operators/node-operators/management/snapshots.mdx index b0dff75d6..0bb8d7730 100644 --- a/pages/operators/node-operators/management/snapshots.mdx +++ b/pages/operators/node-operators/management/snapshots.mdx @@ -60,15 +60,15 @@ Migrated OP Mainnet databases can be generated manually or pre-migrated database ### OP Mainnet (archive node) - You can also download access the [Optimism Foundation datadir explorer](https://datadirs.optimism.io/?utm_source=op-docs&utm_medium=docs) to find other snapshots. + You can also download access the [Optimism Foundation datadir explorer](https://datadirs.optimism.io/?utm_source=op-docs\&utm_medium=docs) to find other snapshots. | Snapshot Date | Size | Download Link | sha256sum | | ----------------------------- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------- | -| Latest by Optimism Foundation | >4TB | [Mirror 1](https://datadirs.optimism.io/latest?utm_source=op-docs&utm_medium=docs)
    [Mirror 2 (torrent)](https://datadirs.optimism.io/latest.torrent?utm_source=op-docs&utm_medium=docs) | [sha256sum](https://datadirs.optimism.io/latest.sha256sum/?utm_source=op-docs&utm_medium=docs) | +| Latest by Optimism Foundation | >4TB | [Mirror 1](https://datadirs.optimism.io/latest?utm_source=op-docs\&utm_medium=docs)
    [Mirror 2 (torrent)](https://datadirs.optimism.io/latest.torrent?utm_source=op-docs\&utm_medium=docs) | [sha256sum](https://datadirs.optimism.io/latest.sha256sum/?utm_source=op-docs\&utm_medium=docs) | ### OP Mainnet (legacy) | Snapshot Date | Size | Download Link | sha256sum | | ------------- | ----- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- | -| 2023-06-06 | 2.9TB | [Mirror 1](https://datadirs.optimism.io/mainnet-legacy-archival.tar.zst?utm_source=op-docs&utm_medium=docs) | `4adedb61125b81b55f9bdccc2e85092050c65ef2253c86e2b79569732b772829` | +| 2023-06-06 | 2.9TB | [Mirror 1](https://datadirs.optimism.io/mainnet-legacy-archival.tar.zst?utm_source=op-docs\&utm_medium=docs) | `4adedb61125b81b55f9bdccc2e85092050c65ef2253c86e2b79569732b772829` | diff --git a/pages/operators/node-operators/network-upgrades.mdx b/pages/operators/node-operators/network-upgrades.mdx index c24769869..2045251e1 100644 --- a/pages/operators/node-operators/network-upgrades.mdx +++ b/pages/operators/node-operators/network-upgrades.mdx @@ -32,12 +32,12 @@ Network upgrades are activated by timestamps. Failing to upgrade your OP Stack s | Upgrade | Governance Approval | [Mainnet Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml) | [Sepolia Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/sepolia/superchain.toml) | | --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | -| [Holocene](https://specs.optimism.io/protocol/holocene/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515) | Thu Jan 9 18:00:01 UTC 2025 (`1736445601`) | Tue Nov 26 15:00:00 UTC 2024 (`1732633200`) | -| [Granite](https://specs.optimism.io/protocol/granite/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | -| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | -| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | -| [Delta](https://specs.optimism.io/protocol/delta/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | -| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html?utm_source=op-docs&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | +| [Holocene](https://specs.optimism.io/protocol/holocene/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515) | Thu Jan 9 18:00:01 UTC 2025 (`1736445601`) | Tue Nov 26 15:00:00 UTC 2024 (`1732633200`) | +| [Granite](https://specs.optimism.io/protocol/granite/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | +| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | +| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | +| [Delta](https://specs.optimism.io/protocol/delta/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | +| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html?utm_source=op-docs\&utm_medium=docs) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | | Bedrock | [approved](https://gov.optimism.io/t/final-upgrade-1-bedrock-protocol-upgrade-v2/5548) | Tue Jun 06 2023 16:28:23 UTC (`1686079703`) at block `105235063` | N/A | ## Upgrade process @@ -86,4 +86,4 @@ then the software is deployed on production networks. ## More information * To check for the latest node software, see the [Software Releases](/operators/node-operators/releases). -* For more information on the governance process see the [governance documentation](https://community.optimism.io/docs/governance/?utm_source=op-docs&utm_medium=docs). +* For more information on the governance process see the [governance documentation](https://community.optimism.io/docs/governance/?utm_source=op-docs\&utm_medium=docs).