From c923552bf52f36498281ed852646e0a48885c959 Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 18 Oct 2024 17:28:25 -0600 Subject: [PATCH 1/9] taking the protocol section up a level --- components/WipCallout.tsx | 21 +++++++++++++++ next-env.d.ts | 2 +- .../builders/chain-operators/tools/_meta.json | 10 ++++--- .../chain-operators/tools}/op-txproxy.mdx | 0 .../chain-operators/tools}/proxyd.mdx | 0 pages/stack/_meta.json | 13 ++++++---- pages/stack/beta-features/_meta.json | 4 +++ .../alt-da-mode.mdx | 0 .../custom-gas-token.mdx | 3 +++ .../{protocol => }/fault-proofs/_meta.json | 0 .../{protocol => }/fault-proofs/cannon.mdx | 0 .../fault-proofs/challenger.mdx | 0 .../{protocol => }/fault-proofs/explainer.mdx | 0 .../fault-proofs/fp-components.mdx | 0 .../fault-proofs/fp-security.mdx | 0 .../{protocol => }/fault-proofs/mips.mdx | 0 pages/stack/features/_meta.json | 3 +++ .../send-raw-transaction-conditional.mdx | 0 pages/stack/{protocol => }/interop/_meta.json | 0 .../interop/cross-chain-message.mdx | 0 .../{protocol => }/interop/explainer.mdx | 0 .../interop/superchain-erc20.mdx | 0 .../stack/{protocol => }/interop/supersim.mdx | 0 pages/stack/operators/_meta.json | 3 --- pages/stack/operators/features/_meta.json | 4 --- pages/stack/protocol/_meta.json | 8 ------ pages/stack/protocol/features/_meta.json | 5 ---- pages/stack/protocol/rollup/_meta.json | 7 ----- pages/stack/rollup/_meta.json | 5 ++++ .../derivation-pipeline.mdx | 0 pages/stack/{protocol => rollup}/outages.mdx | 0 .../stack/{protocol => }/rollup/overview.mdx | 0 pages/stack/transactions/_meta.json | 6 ++++- .../rollup => transactions}/deposit-flow.mdx | 0 .../forced-transaction.mdx | 0 .../transaction-flow.mdx | 0 .../withdrawal-flow.mdx | 0 public/_redirects | 26 +++++++++++++++++-- 38 files changed, 80 insertions(+), 40 deletions(-) rename pages/{stack/operators/features => builders/chain-operators/tools}/op-txproxy.mdx (100%) rename pages/{stack/operators/features => builders/chain-operators/tools}/proxyd.mdx (100%) create mode 100644 pages/stack/beta-features/_meta.json rename pages/stack/{protocol/features => beta-features}/alt-da-mode.mdx (100%) rename pages/stack/{protocol/features => beta-features}/custom-gas-token.mdx (98%) rename pages/stack/{protocol => }/fault-proofs/_meta.json (100%) rename pages/stack/{protocol => }/fault-proofs/cannon.mdx (100%) rename pages/stack/{protocol => }/fault-proofs/challenger.mdx (100%) rename pages/stack/{protocol => }/fault-proofs/explainer.mdx (100%) rename pages/stack/{protocol => }/fault-proofs/fp-components.mdx (100%) rename pages/stack/{protocol => }/fault-proofs/fp-security.mdx (100%) rename pages/stack/{protocol => }/fault-proofs/mips.mdx (100%) create mode 100644 pages/stack/features/_meta.json rename pages/stack/{protocol => }/features/send-raw-transaction-conditional.mdx (100%) rename pages/stack/{protocol => }/interop/_meta.json (100%) rename pages/stack/{protocol => }/interop/cross-chain-message.mdx (100%) rename pages/stack/{protocol => }/interop/explainer.mdx (100%) rename pages/stack/{protocol => }/interop/superchain-erc20.mdx (100%) rename pages/stack/{protocol => }/interop/supersim.mdx (100%) delete mode 100644 pages/stack/operators/_meta.json delete mode 100644 pages/stack/operators/features/_meta.json delete mode 100644 pages/stack/protocol/_meta.json delete mode 100644 pages/stack/protocol/features/_meta.json delete mode 100644 pages/stack/protocol/rollup/_meta.json create mode 100644 pages/stack/rollup/_meta.json rename pages/stack/{protocol => rollup}/derivation-pipeline.mdx (100%) rename pages/stack/{protocol => rollup}/outages.mdx (100%) rename pages/stack/{protocol => }/rollup/overview.mdx (100%) rename pages/stack/{protocol/rollup => transactions}/deposit-flow.mdx (100%) rename pages/stack/{protocol/rollup => transactions}/forced-transaction.mdx (100%) rename pages/stack/{protocol/rollup => transactions}/transaction-flow.mdx (100%) rename pages/stack/{protocol/rollup => transactions}/withdrawal-flow.mdx (100%) diff --git a/components/WipCallout.tsx b/components/WipCallout.tsx index c64f397cb..85ae4a870 100644 --- a/components/WipCallout.tsx +++ b/components/WipCallout.tsx @@ -93,3 +93,24 @@ export function AltCallout({ context }: Props): ReactElement { ); } + +export function CGTCallout({ context }: Props): ReactElement { + return ( +
+
+ {context ? ( + context + ) : ( +
+ The Custom Gas Token feature is currently in Beta within + the MIT-licensed OP Stack. Beta features are built and reviewed by + the Optimism Collective’s core contributors, and provide developers + with early access to highly requested configurations. These features + may experience stability issues, and we encourage feedback from our + early users. +
+ )} +
+
+ ); +} diff --git a/next-env.d.ts b/next-env.d.ts index a4a7b3f5c..4f11a03dc 100644 --- a/next-env.d.ts +++ b/next-env.d.ts @@ -2,4 +2,4 @@ /// // NOTE: This file should not be edited -// see https://nextjs.org/docs/pages/building-your-application/configuring/typescript for more information. +// see https://nextjs.org/docs/basic-features/typescript for more information. diff --git a/pages/builders/chain-operators/tools/_meta.json b/pages/builders/chain-operators/tools/_meta.json index 4c5077834..0779e410c 100644 --- a/pages/builders/chain-operators/tools/_meta.json +++ b/pages/builders/chain-operators/tools/_meta.json @@ -1,7 +1,9 @@ { "chain-monitoring": "Chain Monitoring", - "op-challenger": "Configure Challenger For Your Chain", - "op-conductor": "Conductor", - "op-deployer": "Deployer", - "explorer": "Block Explorer" + "explorer": "Block Explorer", + "op-challenger": "op-challenger", + "op-conductor": "op-conductor", + "op-deployer": "op-deployer", + "op-txproxy": "op-txproxy", + "proxyd": "proxyd" } diff --git a/pages/stack/operators/features/op-txproxy.mdx b/pages/builders/chain-operators/tools/op-txproxy.mdx similarity index 100% rename from pages/stack/operators/features/op-txproxy.mdx rename to pages/builders/chain-operators/tools/op-txproxy.mdx diff --git a/pages/stack/operators/features/proxyd.mdx b/pages/builders/chain-operators/tools/proxyd.mdx similarity index 100% rename from pages/stack/operators/features/proxyd.mdx rename to pages/builders/chain-operators/tools/proxyd.mdx diff --git a/pages/stack/_meta.json b/pages/stack/_meta.json index e2e98fa27..47b2dd20d 100644 --- a/pages/stack/_meta.json +++ b/pages/stack/_meta.json @@ -1,17 +1,20 @@ { "getting-started": "Getting Started: OP Stack", "differences": "Differences Between Ethereum and OP Stack Chains", - "components": "OP Stack Components", - "smart-contracts": "Smart Contracts", "explainer": "Superchain Explainer", "design-principles": "Design Philosophy & Principles", - "protocol": "Protocol", + "components": "OP Stack Components", + "smart-contracts": "Smart Contracts", + "rollup": "Rollup", + "fault-proofs": "Fault Proofs", "transactions": "Transactions", + "features": "Features", "security": "Security", - "operators": "Operators", "--- Experimental": { "title": "Experimental", "type": "separator" }, - "opcm": "OP Contracts Manager" + "opcm": "OP Contracts Manager", + "interop": "Interoperability", + "beta-features": "Beta Features" } diff --git a/pages/stack/beta-features/_meta.json b/pages/stack/beta-features/_meta.json new file mode 100644 index 000000000..22af59364 --- /dev/null +++ b/pages/stack/beta-features/_meta.json @@ -0,0 +1,4 @@ +{ + "custom-gas-token": "Custom Gas Token", + "alt-da-mode": "Alt-DA Mode" +} diff --git a/pages/stack/protocol/features/alt-da-mode.mdx b/pages/stack/beta-features/alt-da-mode.mdx similarity index 100% rename from pages/stack/protocol/features/alt-da-mode.mdx rename to pages/stack/beta-features/alt-da-mode.mdx diff --git a/pages/stack/protocol/features/custom-gas-token.mdx b/pages/stack/beta-features/custom-gas-token.mdx similarity index 98% rename from pages/stack/protocol/features/custom-gas-token.mdx rename to pages/stack/beta-features/custom-gas-token.mdx index b673f6dd0..1b5ca9bd8 100644 --- a/pages/stack/protocol/features/custom-gas-token.mdx +++ b/pages/stack/beta-features/custom-gas-token.mdx @@ -5,6 +5,9 @@ description: Learn the basic process, benefits, and considerations for running a --- import { Callout } from 'nextra/components' +import { CGTCallout } from '@/components/WipCallout' + + # Custom Gas Token Explainer diff --git a/pages/stack/protocol/fault-proofs/_meta.json b/pages/stack/fault-proofs/_meta.json similarity index 100% rename from pages/stack/protocol/fault-proofs/_meta.json rename to pages/stack/fault-proofs/_meta.json diff --git a/pages/stack/protocol/fault-proofs/cannon.mdx b/pages/stack/fault-proofs/cannon.mdx similarity index 100% rename from pages/stack/protocol/fault-proofs/cannon.mdx rename to pages/stack/fault-proofs/cannon.mdx diff --git a/pages/stack/protocol/fault-proofs/challenger.mdx b/pages/stack/fault-proofs/challenger.mdx similarity index 100% rename from pages/stack/protocol/fault-proofs/challenger.mdx rename to pages/stack/fault-proofs/challenger.mdx diff --git a/pages/stack/protocol/fault-proofs/explainer.mdx b/pages/stack/fault-proofs/explainer.mdx similarity index 100% rename from pages/stack/protocol/fault-proofs/explainer.mdx rename to pages/stack/fault-proofs/explainer.mdx diff --git a/pages/stack/protocol/fault-proofs/fp-components.mdx b/pages/stack/fault-proofs/fp-components.mdx similarity index 100% rename from pages/stack/protocol/fault-proofs/fp-components.mdx rename to pages/stack/fault-proofs/fp-components.mdx diff --git a/pages/stack/protocol/fault-proofs/fp-security.mdx b/pages/stack/fault-proofs/fp-security.mdx similarity index 100% rename from pages/stack/protocol/fault-proofs/fp-security.mdx rename to pages/stack/fault-proofs/fp-security.mdx diff --git a/pages/stack/protocol/fault-proofs/mips.mdx b/pages/stack/fault-proofs/mips.mdx similarity index 100% rename from pages/stack/protocol/fault-proofs/mips.mdx rename to pages/stack/fault-proofs/mips.mdx diff --git a/pages/stack/features/_meta.json b/pages/stack/features/_meta.json new file mode 100644 index 000000000..1d8a795f7 --- /dev/null +++ b/pages/stack/features/_meta.json @@ -0,0 +1,3 @@ +{ + "send-raw-transaction-conditional": "SendRawTransactionConditional" +} diff --git a/pages/stack/protocol/features/send-raw-transaction-conditional.mdx b/pages/stack/features/send-raw-transaction-conditional.mdx similarity index 100% rename from pages/stack/protocol/features/send-raw-transaction-conditional.mdx rename to pages/stack/features/send-raw-transaction-conditional.mdx diff --git a/pages/stack/protocol/interop/_meta.json b/pages/stack/interop/_meta.json similarity index 100% rename from pages/stack/protocol/interop/_meta.json rename to pages/stack/interop/_meta.json diff --git a/pages/stack/protocol/interop/cross-chain-message.mdx b/pages/stack/interop/cross-chain-message.mdx similarity index 100% rename from pages/stack/protocol/interop/cross-chain-message.mdx rename to pages/stack/interop/cross-chain-message.mdx diff --git a/pages/stack/protocol/interop/explainer.mdx b/pages/stack/interop/explainer.mdx similarity index 100% rename from pages/stack/protocol/interop/explainer.mdx rename to pages/stack/interop/explainer.mdx diff --git a/pages/stack/protocol/interop/superchain-erc20.mdx b/pages/stack/interop/superchain-erc20.mdx similarity index 100% rename from pages/stack/protocol/interop/superchain-erc20.mdx rename to pages/stack/interop/superchain-erc20.mdx diff --git a/pages/stack/protocol/interop/supersim.mdx b/pages/stack/interop/supersim.mdx similarity index 100% rename from pages/stack/protocol/interop/supersim.mdx rename to pages/stack/interop/supersim.mdx diff --git a/pages/stack/operators/_meta.json b/pages/stack/operators/_meta.json deleted file mode 100644 index 274405469..000000000 --- a/pages/stack/operators/_meta.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "features": "Features" -} \ No newline at end of file diff --git a/pages/stack/operators/features/_meta.json b/pages/stack/operators/features/_meta.json deleted file mode 100644 index 754729f73..000000000 --- a/pages/stack/operators/features/_meta.json +++ /dev/null @@ -1,4 +0,0 @@ -{ - "proxyd": "proxyd", - "op-txproxy": "op-txproxy" -} diff --git a/pages/stack/protocol/_meta.json b/pages/stack/protocol/_meta.json deleted file mode 100644 index fb4113973..000000000 --- a/pages/stack/protocol/_meta.json +++ /dev/null @@ -1,8 +0,0 @@ -{ - "rollup": "Rollup", - "fault-proofs": "Fault Proofs", - "interop": "Interoperability", - "features": "Features", - "outages": "Sequencer Outages", - "derivation-pipeline":"Derivation Pipeline" -} \ No newline at end of file diff --git a/pages/stack/protocol/features/_meta.json b/pages/stack/protocol/features/_meta.json deleted file mode 100644 index b9221d748..000000000 --- a/pages/stack/protocol/features/_meta.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "custom-gas-token": "Custom Gas Token", - "alt-da-mode": "Alt-DA Mode", - "send-raw-transaction-conditional": "SendRawTransactionConditional" -} diff --git a/pages/stack/protocol/rollup/_meta.json b/pages/stack/protocol/rollup/_meta.json deleted file mode 100644 index bf5f987a5..000000000 --- a/pages/stack/protocol/rollup/_meta.json +++ /dev/null @@ -1,7 +0,0 @@ -{ - "overview": "Rollup Overview", - "deposit-flow": "Deposit Flow", - "transaction-flow": "Transaction Flow", - "withdrawal-flow": "Withdrawal Flow", - "forced-transaction": "Forced Transaction" -} \ No newline at end of file diff --git a/pages/stack/rollup/_meta.json b/pages/stack/rollup/_meta.json new file mode 100644 index 000000000..a0e4ff047 --- /dev/null +++ b/pages/stack/rollup/_meta.json @@ -0,0 +1,5 @@ +{ + "overview": "Rollup Overview", + "derivation-pipeline": "Derivation Pipeline", + "outages": "Sequencer Outages" +} \ No newline at end of file diff --git a/pages/stack/protocol/derivation-pipeline.mdx b/pages/stack/rollup/derivation-pipeline.mdx similarity index 100% rename from pages/stack/protocol/derivation-pipeline.mdx rename to pages/stack/rollup/derivation-pipeline.mdx diff --git a/pages/stack/protocol/outages.mdx b/pages/stack/rollup/outages.mdx similarity index 100% rename from pages/stack/protocol/outages.mdx rename to pages/stack/rollup/outages.mdx diff --git a/pages/stack/protocol/rollup/overview.mdx b/pages/stack/rollup/overview.mdx similarity index 100% rename from pages/stack/protocol/rollup/overview.mdx rename to pages/stack/rollup/overview.mdx diff --git a/pages/stack/transactions/_meta.json b/pages/stack/transactions/_meta.json index 8f79b3007..20f41a7f2 100644 --- a/pages/stack/transactions/_meta.json +++ b/pages/stack/transactions/_meta.json @@ -1,3 +1,7 @@ { - "fees": "Transaction Fees" + "fees": "Transaction Fees", + "transaction-flow": "Transaction Flow", + "deposit-flow": "Deposit Flow", + "withdrawal-flow": "Withdrawal Flow", + "forced-transaction": "Forced Transaction" } diff --git a/pages/stack/protocol/rollup/deposit-flow.mdx b/pages/stack/transactions/deposit-flow.mdx similarity index 100% rename from pages/stack/protocol/rollup/deposit-flow.mdx rename to pages/stack/transactions/deposit-flow.mdx diff --git a/pages/stack/protocol/rollup/forced-transaction.mdx b/pages/stack/transactions/forced-transaction.mdx similarity index 100% rename from pages/stack/protocol/rollup/forced-transaction.mdx rename to pages/stack/transactions/forced-transaction.mdx diff --git a/pages/stack/protocol/rollup/transaction-flow.mdx b/pages/stack/transactions/transaction-flow.mdx similarity index 100% rename from pages/stack/protocol/rollup/transaction-flow.mdx rename to pages/stack/transactions/transaction-flow.mdx diff --git a/pages/stack/protocol/rollup/withdrawal-flow.mdx b/pages/stack/transactions/withdrawal-flow.mdx similarity index 100% rename from pages/stack/protocol/rollup/withdrawal-flow.mdx rename to pages/stack/transactions/withdrawal-flow.mdx diff --git a/public/_redirects b/public/_redirects index 89f0ac83c..d5dd6e606 100644 --- a/public/_redirects +++ b/public/_redirects @@ -76,7 +76,29 @@ /stack/protocol/design-principles /stack/design-principles /builders/node-operators/overview /builders/node-operators/rollup-node /builders/notices/ecotone-changes /stack/transactions/fees#ecotone -/stack/protocol/fault-proofs/overview /stack/protocol/fault-proofs/explainer +/stack/protocol/fault-proofs/overview /stack/fault-proofs/explainer /builders/chain-operators/management/configuration /builders/chain-operators/configuration/overview /builders/chain-operators/management/custom-gas-token /builders/chain-operators/features/custom-gas-token -/stack/protocol/rollup/smart-contracts /stack/smart-contracts \ No newline at end of file +/stack/protocol/rollup/smart-contracts /stack/smart-contracts +/stack/protocol/fault-proofs/challenger /stack/fault-proofs/challenger +/stack/protocol/fault-proofs/fp-security /stack/fault-proofs/fp-security +/stack/protocol/fault-proofs/mips /stack/fault-proofs/mips +/stack/protocol/fault-proofs/fp-components /stack/fault-proofs/fp-components +/stack/protocol/fault-proofs/explainer /stack/fault-proofs/explainer +/stack/protocol/fault-proofs/cannon /stack/fault-proofs/cannon +/stack/protocol/interop/supersim /stack/interop/supersim +/stack/protocol/interop/superchain-erc20 /stack/interop/superchain-erc20 +/stack/protocol/interop/explainer /stack/interop/explainer +/stack/protocol/interop/cross-chain-message /stack/interop/cross-chain-message +/stack/protocol/features/alt-da-mode +/stack/protocol/features/custom-gas-token +/stack/protocol/features/send-raw-transaction-conditional /stack/features/send-raw-transaction-conditional +/stack/protocol/derivation-pipeline /stack/rollup/derivation-pipeline +/stack/protocol/rollup/overview /stack/rollup/overview +/stack/protocol/rollup/withdrawal-flow /stack/transactions/withdrawal-flow +/stack/protocol/rollup/forced-transaction /stack/transactions/forced-transaction +/stack/protocol/rollup/transaction-flow /stack/transactions/transaction-flow +/stack/protocol/rollup/deposit-flow /stack/transactions/deposit-flow +/stack/protocol/outages /stack/rollup/outages +/stack/operators/features/op-txproxy /builders/chain-operators/tools/op-txproxy +/stack/operators/features/proxyd /builders/chain-operators/tools/proxyd \ No newline at end of file From 68f23e543940c0614d01396547e6f34aa6167554 Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 18 Oct 2024 17:34:35 -0600 Subject: [PATCH 2/9] fixing build issue? --- pages/builders/app-developers/contracts/superchain-erc20.mdx | 2 +- pages/builders/app-developers/tools/supersim.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/builders/app-developers/contracts/superchain-erc20.mdx b/pages/builders/app-developers/contracts/superchain-erc20.mdx index e966aac46..dfaf8f84e 100644 --- a/pages/builders/app-developers/contracts/superchain-erc20.mdx +++ b/pages/builders/app-developers/contracts/superchain-erc20.mdx @@ -1,6 +1,6 @@ --- --- -import SuperchainERC20 from '@/pages/stack/protocol/interop/superchain-erc20.mdx' +import SuperchainERC20 from '@/pages/stack/interop/superchain-erc20.mdx' diff --git a/pages/builders/app-developers/tools/supersim.mdx b/pages/builders/app-developers/tools/supersim.mdx index f25adb1bc..dc60c54ac 100644 --- a/pages/builders/app-developers/tools/supersim.mdx +++ b/pages/builders/app-developers/tools/supersim.mdx @@ -1,6 +1,6 @@ --- --- -import Supersim from '@/pages/stack/protocol/interop/supersim.mdx' +import Supersim from '@/pages/stack/interop/supersim.mdx' From 9771f62a03644a63a648cbf76a0cb3d6f2a3a36d Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 18 Oct 2024 19:05:30 -0600 Subject: [PATCH 3/9] fixing some internal links --- pages/builders/app-developers/bridging/messaging.mdx | 2 +- pages/builders/chain-operators/configuration/rollup.mdx | 4 ++-- pages/builders/chain-operators/features/alt-da-mode.mdx | 4 ++-- .../chain-operators/features/custom-gas-token.mdx | 4 ++-- pages/builders/chain-operators/tools/chain-monitoring.mdx | 2 +- pages/builders/chain-operators/tools/op-challenger.mdx | 4 ++-- pages/builders/chain-operators/tools/op-txproxy.mdx | 2 +- .../chain-operators/tutorials/integrating-da-layer.mdx | 2 +- pages/builders/notices/fp-changes.mdx | 6 +++--- pages/builders/notices/granite-changes.mdx | 2 +- pages/builders/tools/build/account-abstraction.mdx | 2 +- pages/chain/security/faq.mdx | 2 +- pages/stack/fault-proofs/cannon.mdx | 2 +- pages/stack/fault-proofs/challenger.mdx | 2 +- pages/stack/fault-proofs/explainer.mdx | 8 ++++---- pages/stack/interop/supersim.mdx | 2 +- pages/stack/transactions/withdrawal-flow.mdx | 4 ++-- 17 files changed, 27 insertions(+), 27 deletions(-) diff --git a/pages/builders/app-developers/bridging/messaging.mdx b/pages/builders/app-developers/bridging/messaging.mdx index 0d8cd9e6a..2b03591f4 100644 --- a/pages/builders/app-developers/bridging/messaging.mdx +++ b/pages/builders/app-developers/bridging/messaging.mdx @@ -215,7 +215,7 @@ The L1 proof and finalization transactions are typically significantly more expe One of the most important things to understand about L1 ⇔ L2 interaction is that **mainnet messages sent from Layer 2 to Layer 1 cannot be relayed for at least 7 days**. This means that any messages you send from Layer 2 will only be received on Layer 1 after this one week period has elapsed. -We call this period of time the "challenge period" because it is the time during which a transaction can be challenged with a [fault proof](/stack/protocol/rollup/overview#fault-proofs). +We call this period of time the "challenge period" because it is the time during which a transaction can be challenged with a [fault proof](/stack/rollup/overview#fault-proofs). Optimistic Rollups are "optimistic" because they're based around the idea of publishing the *result* of a transaction to Ethereum without actually executing the transaction on Ethereum. In the "optimistic" case, this transaction result is correct and one can completely avoid the need to perform complicated (and expensive) logic on Ethereum. diff --git a/pages/builders/chain-operators/configuration/rollup.mdx b/pages/builders/chain-operators/configuration/rollup.mdx index 6dd615624..2ba6cd795 100644 --- a/pages/builders/chain-operators/configuration/rollup.mdx +++ b/pages/builders/chain-operators/configuration/rollup.mdx @@ -973,7 +973,7 @@ instead of the older output oracle mechanism. The Custom Gas Token configuration lets OP Stack chain operators deploy their chain allowing a specific ERC-20 token to be deposited in as the native token -to pay for gas fees. Learn more [here](/stack/protocol/features/custom-gas-token). +to pay for gas fees. Learn more [here](/stack/features/custom-gas-token). *** @@ -1005,7 +1005,7 @@ gas on L2. Alt-DA Mode enables seamless integration of various Data Availability (DA) Layers, regardless of their commitment type, into the OP Stack. This allows any chain operator to launch an OP Stack chain using their favorite DA Layer -for sustainably low costs. Lean more [here](/stack/protocol/features/alt-da-mode). +for sustainably low costs. Lean more [here](/stack/features/alt-da-mode). *** diff --git a/pages/builders/chain-operators/features/alt-da-mode.mdx b/pages/builders/chain-operators/features/alt-da-mode.mdx index e6f6397c7..4ea569197 100644 --- a/pages/builders/chain-operators/features/alt-da-mode.mdx +++ b/pages/builders/chain-operators/features/alt-da-mode.mdx @@ -13,7 +13,7 @@ import { Callout, Steps } from 'nextra/components' These features may experience stability issues, and we encourage feedback from our early users. -This guide provides a walkthrough for chain operators who want to run an Alt-DA Mode chain. See the [Alt-DA Mode Explainer](/stack/protocol/features/alt-da-mode) for a general overview of this OP Stack configuration. +This guide provides a walkthrough for chain operators who want to run an Alt-DA Mode chain. See the [Alt-DA Mode Explainer](/stack/features/alt-da-mode) for a general overview of this OP Stack configuration. An Alt-DA Mode OP Stack chain enables a chain operator to post and read data to any alternative data availability layer that has built a functioning OP Stack DA Server. @@ -224,6 +224,6 @@ 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/protocol/features/alt-da-mode#faqs). +* Additional questions? See the FAQ section in the [Alt-DA Mode Explainer](/stack/features/alt-da-mode#faqs). * For more detailed info on Alt-DA Mode, see the [specs](https://specs.optimism.io/experimental/alt-da.html). * If you experience any problems, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). diff --git a/pages/builders/chain-operators/features/custom-gas-token.mdx b/pages/builders/chain-operators/features/custom-gas-token.mdx index f2a42c986..1a3869063 100644 --- a/pages/builders/chain-operators/features/custom-gas-token.mdx +++ b/pages/builders/chain-operators/features/custom-gas-token.mdx @@ -12,7 +12,7 @@ import { Callout, Steps } from 'nextra/components' The Custom Gas Token feature is a Beta feature of the MIT licensed OP Stack. While it has received initial review from core contributors, it is still undergoing testing, and may have bugs or other issues. -This guide provides a walkthrough for chain operators who want to run a custom gas token chain. See the [Custom Gas Token Explainer](/stack/protocol/features/custom-gas-token) for a general overview of this OP Stack feature. +This guide provides a walkthrough for chain operators who want to run a custom gas token chain. See the [Custom Gas Token Explainer](/stack/beta-features/custom-gas-token) for a general overview of this OP Stack feature. An OP Stack chain that uses the custom gas token feature enables an end user to deposit an L1 native ERC20 token into L2 where that asset is minted as the native L2 asset and can be used to pay for gas on L2. @@ -156,6 +156,6 @@ section of the docs. ## Next Steps -* Additional questions? See the FAQ section in the [Custom Gas Token Explainer](/stack/protocol/features/custom-gas-token#faqs). +* Additional questions? See the FAQ section in the [Custom Gas Token Explainer](/stack/beta-features/custom-gas-token#faqs). * For more detailed info on custom gas tokens, see the [specs](https://specs.optimism.io/experimental/custom-gas-token.html). * If you experience any problems, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). diff --git a/pages/builders/chain-operators/tools/chain-monitoring.mdx b/pages/builders/chain-operators/tools/chain-monitoring.mdx index c97183443..3efb4ceba 100644 --- a/pages/builders/chain-operators/tools/chain-monitoring.mdx +++ b/pages/builders/chain-operators/tools/chain-monitoring.mdx @@ -108,7 +108,7 @@ You can find more information about these flags in our [Batcher configuration do ### `op-challenger` The `op-challenger` operates as the *honest actor* in the fault dispute system and defends the chain by securing the `OptimismPortal` and ensuring the game always resolves to the correct state of the chain. -For verifying the legitimacy of claims, `op-challenger` relies on a synced, trusted rollup node as well as a trace provider (e.g., [Cannon](/stack/protocol/fault-proofs/cannon)). See the [OP-Challenger Explainer](/stack/protocol/fault-proofs/challenger) for more information on this service. +For verifying the legitimacy of claims, `op-challenger` relies on a synced, trusted rollup node as well as a trace provider (e.g., [Cannon](/stack/fault-proofs/cannon)). See the [OP-Challenger Explainer](/stack/fault-proofs/challenger) for more information on this service. To enable metrics, pass the `--metrics.enabled` flag to `op-challenger` and follow the steps above for customization options. diff --git a/pages/builders/chain-operators/tools/op-challenger.mdx b/pages/builders/chain-operators/tools/op-challenger.mdx index 760af2647..da1283b9c 100644 --- a/pages/builders/chain-operators/tools/op-challenger.mdx +++ b/pages/builders/chain-operators/tools/op-challenger.mdx @@ -8,7 +8,7 @@ import { Callout, Steps } from 'nextra/components' # How to Configure Challenger For Your Chain -This guide provides a walkthrough of setting up the configuration and monitoring options for `op-challenger`. See the [OP-Challenger Explainer](/stack/protocol/fault-proofs/challenger) for a general overview of this fault proofs feature. +This guide provides a walkthrough of setting up the configuration and monitoring options for `op-challenger`. See the [OP-Challenger Explainer](/stack/fault-proofs/challenger) for a general overview of this fault proofs feature. ### Build the Executable @@ -218,6 +218,6 @@ 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/protocol/fault-proofs/challenger). +* 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). * If you experience any problems, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). diff --git a/pages/builders/chain-operators/tools/op-txproxy.mdx b/pages/builders/chain-operators/tools/op-txproxy.mdx index 525519dbe..c3e75653c 100644 --- a/pages/builders/chain-operators/tools/op-txproxy.mdx +++ b/pages/builders/chain-operators/tools/op-txproxy.mdx @@ -61,7 +61,7 @@ When the request passes validation, it is passed through to the configured backe - Per the [specification](/stack/protocol/features/send-raw-transaction-conditional), conditional transactions are not gossiped between peers. Thus, if you use replicas in an active/passive sequencer setup, this request must be broadcasted to all replicas. + Per the [specification](/stack/features/send-raw-transaction-conditional), conditional transactions are not gossiped between peers. Thus, if you use replicas in an active/passive sequencer setup, this request must be broadcasted to all replicas. [proxyd](./proxyd) as an egress router for this method supports this broadcasting functionality. diff --git a/pages/builders/chain-operators/tutorials/integrating-da-layer.mdx b/pages/builders/chain-operators/tutorials/integrating-da-layer.mdx index a1dbc7c99..51fb0300d 100644 --- a/pages/builders/chain-operators/tutorials/integrating-da-layer.mdx +++ b/pages/builders/chain-operators/tutorials/integrating-da-layer.mdx @@ -13,7 +13,7 @@ import { Callout, Steps } from 'nextra/components' These features may experience stability issues, and we encourage feedback from our early users. -[Alt-DA Mode](/stack/protocol/features/alt-da-mode) enables seamless integration of any DA Layer, regardless of their commitment type, into the OP Stack. After a DA Server is built for a DA Layer, any chain operator can launch an OP Stack chain using that DA Layer for sustainably low costs. +[Alt-DA Mode](/stack/beta-features/alt-da-mode) enables seamless integration of any DA Layer, regardless of their commitment type, into the OP Stack. After a DA Server is built for a DA Layer, any chain operator can launch an OP Stack chain using that DA Layer for sustainably low costs. ## Build Your DA Server diff --git a/pages/builders/notices/fp-changes.mdx b/pages/builders/notices/fp-changes.mdx index 4f7a34d81..c5a6c60af 100644 --- a/pages/builders/notices/fp-changes.mdx +++ b/pages/builders/notices/fp-changes.mdx @@ -17,7 +17,7 @@ If you experience difficulty at any stage of this process, please reach out to [ **ALL** withdrawals that are not finalized before the Fault Proofs upgrade executes will need to be reproven after the upgrade is complete. - * Reproving simply requires that you execute the [withdrawal proving flow](https://docs.optimism.io/stack/protocol/rollup/withdrawal-flow) again. + * Reproving simply requires that you execute the [withdrawal proving flow](https://docs.optimism.io/stack/rollup/withdrawal-flow) again. * Withdrawals prior to the Fault Proofs upgrade must wait a 7-day challenge period before finalization. As a result, any withdrawal initiated less than 7 days before the upgrade cannot be finalized before the upgrade is executed. You may want to consider waiting until after the upgrade is complete to begin a withdrawal during this 7-day window. @@ -96,5 +96,5 @@ The proposed Fault Proof upgrade requires developers to enable Fault Proof chang ## Next Steps -* See the [Fault Proofs Explainer](/stack/protocol/fault-proofs/explainer) to learn more about the three main components of the Fault Proof System. -* You can also read more about [Cannon FPVM](/stack/protocol/fault-proofs/cannon) and [Mips.sol](/stack/protocol/fault-proofs/mips), the onchain smart contract implementation of Cannon. +* See the [Fault Proofs Explainer](/stack/fault-proofs/explainer) to learn more about the three main components of the Fault Proof System. +* You can also read more about [Cannon FPVM](/stack/fault-proofs/cannon) and [Mips.sol](/stack/fault-proofs/mips), the onchain smart contract implementation of Cannon. diff --git a/pages/builders/notices/granite-changes.mdx b/pages/builders/notices/granite-changes.mdx index b0eaa9871..ccbb10ee8 100644 --- a/pages/builders/notices/granite-changes.mdx +++ b/pages/builders/notices/granite-changes.mdx @@ -17,7 +17,7 @@ If you experience difficulty at any stage of this process, please reach out to [ ## What's Included in Granite -This upgrade is proposed in response to security vulnerabilities identified during a series of third-party security audits by Spearbit, Cantina, and Code4rena. None of the vulnerabilities have been exploited, and user assets are not and were never at risk. However, out of an abundance of caution, the permissioned fallback mechanism has been activated in order to avoid any potential instability while the vulnerabilities are patched. For more information on the permissioned fallback mechanism and the OP Stack's defense-in-depth approach to Fault Proof security, see the [fault proof documentation](https://docs.optimism.io/stack/protocol/fault-proofs/fp-security). +This upgrade is proposed in response to security vulnerabilities identified during a series of third-party security audits by Spearbit, Cantina, and Code4rena. None of the vulnerabilities have been exploited, and user assets are not and were never at risk. However, out of an abundance of caution, the permissioned fallback mechanism has been activated in order to avoid any potential instability while the vulnerabilities are patched. For more information on the permissioned fallback mechanism and the OP Stack's defense-in-depth approach to Fault Proof security, see the [fault proof documentation](https://docs.optimism.io/stack/fault-proofs/fp-security). The upgrade includes both a set of smart contract upgrades to fix the vulnerabilities identified in the audit as well as an L2 hardfork to improve the stability and performance of the fault proof system. In addition, we propose extending the capabilities of the Guardian and DeputyGuardian to set the anchor state for the fault proof system in order to prevent referencing invalid anchor states. Aside from implementing these fixes, the primary impact of this upgrade would be to reset user withdrawals at the planned time, similar to the initial Fault Proof upgrade. diff --git a/pages/builders/tools/build/account-abstraction.mdx b/pages/builders/tools/build/account-abstraction.mdx index 7cebf8eb5..de6cffa86 100644 --- a/pages/builders/tools/build/account-abstraction.mdx +++ b/pages/builders/tools/build/account-abstraction.mdx @@ -21,7 +21,7 @@ import { Callout } from 'nextra/components' ## Bundlers -The OP Stack includes support for the `eth_sendRawTransactionConditional` RPC method to assist bundlers on shared 4337 mempools. See the [specification](/stack/protocol/features/send-raw-transaction-conditional) for how this method is implemented in op-geth. +The OP Stack includes support for the `eth_sendRawTransactionConditional` RPC method to assist bundlers on shared 4337 mempools. See the [specification](/stack/features/send-raw-transaction-conditional) for how this method is implemented in op-geth. If enabled by the chain operator, also see the supplemental [op-txproxy](/stack/operators/features/op-txproxy) service, if applied, as this enforces request authentication for this method. diff --git a/pages/chain/security/faq.mdx b/pages/chain/security/faq.mdx index b000bb446..fe0f37327 100644 --- a/pages/chain/security/faq.mdx +++ b/pages/chain/security/faq.mdx @@ -38,7 +38,7 @@ Withdrawals are proven against proposals about the state of OP Mainnet that are Proposals can be submitted to the `DisputeGameFactory` contract by any user and submissions do not require any special permissions. Each submitted proposal creates a [`FaultDisputeGame`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/dispute/FaultDisputeGame.sol) contract that allows any other user to challenge the validity of a proposal by participating in a "fault proof" process. -A more detailed explanation of the fault proof game can be found in the [Fault Proofs Explainer](/stack/protocol/fault-proofs/explainer). +A more detailed explanation of the fault proof game can be found in the [Fault Proofs Explainer](/stack/fault-proofs/explainer). Although the fault proof game is permissionless, the Optimism Security Council acting as the [Guardian](/chain/security/privileged-roles#guardian) role provides a backstop in case of a failure in the fault proof game. Each proposal must wait for a delay period during which the Guardian can prevent invalid proposals from being used to withdraw ETH or tokens through a number of safety hatches. diff --git a/pages/stack/fault-proofs/cannon.mdx b/pages/stack/fault-proofs/cannon.mdx index 4a86b4ce6..e5685632c 100644 --- a/pages/stack/fault-proofs/cannon.mdx +++ b/pages/stack/fault-proofs/cannon.mdx @@ -35,7 +35,7 @@ single L2 block state transition that they disagree on. ### OP-Challenger \<> Cannon -Once an active fault dispute game reaches a depth below attacking / defending L2 block state transitions, [OP-Challenger](/stack/protocol/fault-proofs/challenger) will run +Once an active fault dispute game reaches a depth below attacking / defending L2 block state transitions, [OP-Challenger](/stack/fault-proofs/challenger) will run Cannon to begin processing MIPS instructions within the FPVM. As part of processing MIPS instructions, Cannon will generate state witness hashes, which are the commitment to the results of the MIPS instructions' computation within the FPVM. Now, in the bisection game, OP-Challenger will provide the generated hashes until a single MIPS instruction is identified as the root disagreement between participants in the active dispute. Cannon will then diff --git a/pages/stack/fault-proofs/challenger.mdx b/pages/stack/fault-proofs/challenger.mdx index 3f23d83f3..c7b715a14 100644 --- a/pages/stack/fault-proofs/challenger.mdx +++ b/pages/stack/fault-proofs/challenger.mdx @@ -9,7 +9,7 @@ import Image from 'next/image' # OP-Challenger Explainer -The `op-challenger` operates as the *honest actor* in the fault dispute system and defends the chain by securing the `OptimismPortal` and ensuring the game always resolves to the correct state of the chain. For verifying the legitimacy of claims, `op-challenger` relies on a synced, trusted rollup node as well as a trace provider (e.g., [Cannon](/stack/protocol/fault-proofs/cannon)). +The `op-challenger` operates as the *honest actor* in the fault dispute system and defends the chain by securing the `OptimismPortal` and ensuring the game always resolves to the correct state of the chain. For verifying the legitimacy of claims, `op-challenger` relies on a synced, trusted rollup node as well as a trace provider (e.g., [Cannon](/stack/fault-proofs/cannon)). Specifically, `op-challenger` performs the following actions: diff --git a/pages/stack/fault-proofs/explainer.mdx b/pages/stack/fault-proofs/explainer.mdx index 7b1299aa4..fd5665555 100644 --- a/pages/stack/fault-proofs/explainer.mdx +++ b/pages/stack/fault-proofs/explainer.mdx @@ -39,16 +39,16 @@ See the permissionless fault proofs diagram below for more details: ## Permissionless Challenges Because anyone can submit a proposal, it's important that invalid proposals can be challenged. -In [Optimistic Rollups like OP Stack Chains](/stack/protocol/rollup/overview) there is a \~1 week challenge period during which users can challenge a proposal if they believe it to be incorrect. +In [Optimistic Rollups like OP Stack Chains](/stack/rollup/overview) there is a \~1 week challenge period during which users can challenge a proposal if they believe it to be incorrect. With the Fault Proofs upgrade to the OP Stack, challenges become permissionless and can be submitted by anyone. Any user can run a node for the OP Stack chain in question and use the `op-challenger` tool to participate in the dispute process. ## Modular Design and Multi-layer Security -The OP Stack Fault Proof system is [modular in design](/stack/protocol/fault-proofs/fp-components#system-design--modularity) and lays the groundwork for achieving a "multi-proof" system. This allows the OP Stack to support multiple proof systems alongside the initial [Cannon](/stack/protocol/fault-proofs/cannon) proof system. +The OP Stack Fault Proof system is [modular in design](/stack/fault-proofs/fp-components#system-design--modularity) and lays the groundwork for achieving a "multi-proof" system. This allows the OP Stack to support multiple proof systems alongside the initial [Cannon](/stack/fault-proofs/cannon) proof system. With multiple proof systems in place, the OP Stack can be more resilient to potential attacks and bugs in any one proof system. -Additionally, the following [security safeguards](/stack/protocol/fault-proofs/fp-security) have been built around the game, as follows: +Additionally, the following [security safeguards](/stack/fault-proofs/fp-security) have been built around the game, as follows: * An off chain monitoring system has been set up to monitor all proposed roots and ensure they align with the correct state. See [`op-dispute-mon`](https://github.com/ethereum-optimism/optimism/blob/develop/op-dispute-mon/README.md?plain=1) for more details. * After a root is finalized through a game, an additional delay called the "airgap window" has been added before withdrawals can occur. During this period, the `GUARDIAN` role can reject the root. @@ -57,7 +57,7 @@ Additionally, the following [security safeguards](/stack/protocol/fault-proofs/f ## Next Steps * 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/protocol/fault-proofs/fp-security) to understand changes to `OptimismPortal` and `FaultDisputeGame` contracts. +* 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). ## FAQs diff --git a/pages/stack/interop/supersim.mdx b/pages/stack/interop/supersim.mdx index 10b88e8fe..0d628e48b 100644 --- a/pages/stack/interop/supersim.mdx +++ b/pages/stack/interop/supersim.mdx @@ -57,5 +57,5 @@ This diagram illustrates how developers interact with Supersim through the CLI, ## Next steps * Check out the dedicated [Supersim docs](https://Supersim.pages.dev/) for tutorials and specific use cases. -* Questions about Interop? Check out the FAQ section in the [Superchain Interop Explainer](/stack/protocol/interop/explainer#faqs) or check out this [Superchain interop design video walk-thru](https://www.youtube.com/watch?v=FKc5RgjtGes). +* Questions about Interop? Check out the FAQ section in the [Superchain Interop Explainer](/stack/interop/explainer#faqs) 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). diff --git a/pages/stack/transactions/withdrawal-flow.mdx b/pages/stack/transactions/withdrawal-flow.mdx index dd2ae78b6..ef49eb6c6 100644 --- a/pages/stack/transactions/withdrawal-flow.mdx +++ b/pages/stack/transactions/withdrawal-flow.mdx @@ -97,8 +97,8 @@ The Chugsplash Proxy operates differently than standard proxies. During a withdr For more information about the withdrawal process and how it works on Optimism, refer to the following resources: -* [Smart Contracts Overview](https://docs.optimism.io/stack/protocol/rollup/smart-contracts) -* [Withdrawal Flow](https://docs.optimism.io/stack/protocol/rollup/withdrawal-flow#withdrawal-initiating-transaction) +* [Smart Contracts Overview](https://docs.optimism.io/stack/rollup/smart-contracts) +* [Withdrawal Flow](https://docs.optimism.io/stack/rollup/withdrawal-flow#withdrawal-initiating-transaction) ### Offchain processing From 17e723d4f5510eb5a8e4a496423da2243a2a2898 Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 18 Oct 2024 19:17:11 -0600 Subject: [PATCH 4/9] fixing internal links and redirects --- .../chain-operators/configuration/rollup.mdx | 2 +- .../chain-operators/features/alt-da-mode.mdx | 4 +-- pages/builders/notices/sdk-deprecation.mdx | 29 ------------------- .../tools/build/account-abstraction.mdx | 2 +- public/_redirects | 4 +-- 5 files changed, 6 insertions(+), 35 deletions(-) diff --git a/pages/builders/chain-operators/configuration/rollup.mdx b/pages/builders/chain-operators/configuration/rollup.mdx index 2ba6cd795..a82ed3167 100644 --- a/pages/builders/chain-operators/configuration/rollup.mdx +++ b/pages/builders/chain-operators/configuration/rollup.mdx @@ -1005,7 +1005,7 @@ gas on L2. Alt-DA Mode enables seamless integration of various Data Availability (DA) Layers, regardless of their commitment type, into the OP Stack. This allows any chain operator to launch an OP Stack chain using their favorite DA Layer -for sustainably low costs. Lean more [here](/stack/features/alt-da-mode). +for sustainably low costs. Lean more [here](/stack/beta-features/alt-da-mode). *** diff --git a/pages/builders/chain-operators/features/alt-da-mode.mdx b/pages/builders/chain-operators/features/alt-da-mode.mdx index 4ea569197..c64ab3829 100644 --- a/pages/builders/chain-operators/features/alt-da-mode.mdx +++ b/pages/builders/chain-operators/features/alt-da-mode.mdx @@ -13,7 +13,7 @@ import { Callout, Steps } from 'nextra/components' These features may experience stability issues, and we encourage feedback from our early users. -This guide provides a walkthrough for chain operators who want to run an Alt-DA Mode chain. See the [Alt-DA Mode Explainer](/stack/features/alt-da-mode) for a general overview of this OP Stack configuration. +This guide provides a walkthrough for chain operators who want to run an Alt-DA Mode chain. See the [Alt-DA Mode Explainer](/stack/beta-features/alt-da-mode) for a general overview of this OP Stack configuration. An Alt-DA Mode OP Stack chain enables a chain operator to post and read data to any alternative data availability layer that has built a functioning OP Stack DA Server. @@ -224,6 +224,6 @@ 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/features/alt-da-mode#faqs). +* 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). * If you experience any problems, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). diff --git a/pages/builders/notices/sdk-deprecation.mdx b/pages/builders/notices/sdk-deprecation.mdx index 302f4afba..4b509005e 100644 --- a/pages/builders/notices/sdk-deprecation.mdx +++ b/pages/builders/notices/sdk-deprecation.mdx @@ -23,35 +23,6 @@ Developers and users are strongly encouraged to transition to `viem` before the We are updating our tutorials to use the `viem` library. - {/* Below, you'll find links to the updated versions of popular tutorials: - -* [Estimating Transaction Costs on OP Mainnet](../tutorials/transaction-cost-estimation)\ - Estimation of transaction costs now uses the `viem` gas estimation utilities. - -* [Triggering OP Mainnet Transactions from Ethereum](../tutorials/trigger-op-transactions)\ - Learn how to trigger transactions using `viem` to interact with the OP Mainnet. - -* [Tracing Deposits and Withdrawals](../tutorials/tracing-deposits-withdrawals)\ - The tracing functionalities have been adapted to use `opstack` for efficient results. - -* [Viewing Deposits and Withdrawals by Address](../tutorials/view-deposits-withdrawals)\ - This tutorial outlines updated methods in `viem` for querying deposits and withdrawals by address. - -* [Bridging Your Standard ERC-20 Token Using the Standard Bridge](../tutorials/bridge-standard-erc20)\ - The standard bridge tutorial now uses `opstack` for token transfers between Ethereum and OP Mainnet. - -* [Bridging Your Custom ERC-20 Token Using the Standard Bridge](../tutorials/bridge-custom-erc20)\ - Custom ERC-20 tokens can now be bridged via `opstack`, making the process more streamlined. - -* [Bridging ERC-20 Tokens to OP Mainnet With the Optimism SDK](../tutorials/bridge-sdk-erc20)\ - **Deprecated** – please use [Bridging Your Custom ERC-20 Token Using the Standard Bridge](../tutorials/bridge-custom-erc20). - -* [Bridging ETH to OP Mainnet With the Optimism SDK](../tutorials/bridge-sdk-eth)\ - **Deprecated** – please use [Estimating Transaction Costs on OP Mainnet](../tutorials/transaction-cost-estimation). - -* [Communicating Between OP Mainnet and Ethereum in Solidity](../tutorials/cross-chain-solidity)\ - Cross-chain communication now leverages `opstack` for all messaging. */} - ### For app developers If your application currently depends on the Optimism SDK, you will need to migrate to using the `viem` library. diff --git a/pages/builders/tools/build/account-abstraction.mdx b/pages/builders/tools/build/account-abstraction.mdx index de6cffa86..efa52e673 100644 --- a/pages/builders/tools/build/account-abstraction.mdx +++ b/pages/builders/tools/build/account-abstraction.mdx @@ -23,7 +23,7 @@ import { Callout } from 'nextra/components' The OP Stack includes support for the `eth_sendRawTransactionConditional` RPC method to assist bundlers on shared 4337 mempools. See the [specification](/stack/features/send-raw-transaction-conditional) for how this method is implemented in op-geth. -If enabled by the chain operator, also see the supplemental [op-txproxy](/stack/operators/features/op-txproxy) service, if applied, as this enforces request authentication for this method. +If enabled by the chain operator, also see the supplemental [op-txproxy](/builders/chain-operators/tools/op-txproxy) service, if applied, as this enforces request authentication for this method. As of today, this endpoint is not enabled by default in the stack. The operator must explicitly configure this. diff --git a/public/_redirects b/public/_redirects index d5dd6e606..59f07d98b 100644 --- a/public/_redirects +++ b/public/_redirects @@ -90,8 +90,8 @@ /stack/protocol/interop/superchain-erc20 /stack/interop/superchain-erc20 /stack/protocol/interop/explainer /stack/interop/explainer /stack/protocol/interop/cross-chain-message /stack/interop/cross-chain-message -/stack/protocol/features/alt-da-mode -/stack/protocol/features/custom-gas-token +/stack/protocol/features/alt-da-mode /stack/beta-features/alt-da-mode +/stack/protocol/features/custom-gas-token /stack/beta-features/custom-gas-token /stack/protocol/features/send-raw-transaction-conditional /stack/features/send-raw-transaction-conditional /stack/protocol/derivation-pipeline /stack/rollup/derivation-pipeline /stack/protocol/rollup/overview /stack/rollup/overview From 6f3f1f85825c60fd83df75eb95cdad096d55d1e2 Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 18 Oct 2024 19:21:19 -0600 Subject: [PATCH 5/9] refactoring component --- components/WipCallout.tsx | 39 +++++++++++++++------------------------ 1 file changed, 15 insertions(+), 24 deletions(-) diff --git a/components/WipCallout.tsx b/components/WipCallout.tsx index 85ae4a870..72dd73d5c 100644 --- a/components/WipCallout.tsx +++ b/components/WipCallout.tsx @@ -73,38 +73,21 @@ export function InfoCallout({ context }: Props): ReactElement { ); } -export function AltCallout({ context }: Props): ReactElement { - return ( -
-
- {context ? ( - context - ) : ( -
- The Alt-DA Mode feature is currently in Beta within - the MIT-licensed OP Stack. Beta features are built and reviewed by - the Optimism Collective’s core contributors, and provide developers - with early access to highly requested configurations. These features - may experience stability issues, and we encourage feedback from our - early users. -
- )} -
-
- ); +interface BetaCalloutProps extends Props { + featureName: string; } -export function CGTCallout({ context }: Props): ReactElement { +function BetaCallout({ context, featureName }: BetaCalloutProps): ReactElement { return (
-
+
{context ? ( context ) : ( -
- The Custom Gas Token feature is currently in Beta within +
+ The {featureName} feature is currently in Beta within the MIT-licensed OP Stack. Beta features are built and reviewed by - the Optimism Collective’s core contributors, and provide developers + the Optimism Collective's core contributors, and provide developers with early access to highly requested configurations. These features may experience stability issues, and we encourage feedback from our early users. @@ -114,3 +97,11 @@ export function CGTCallout({ context }: Props): ReactElement {
); } + +export function AltCallout(props: Props): ReactElement { + return ; +} + +export function CGTCallout(props: Props): ReactElement { + return ; +} \ No newline at end of file From fbbf7de98dfd30c82da79a52af62b4083aff6d79 Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 18 Oct 2024 20:10:30 -0600 Subject: [PATCH 6/9] fixing more broken links --- pages/builders/chain-operators/configuration/rollup.mdx | 2 +- pages/builders/chain-operators/features/alt-da-mode.mdx | 2 +- pages/builders/chain-operators/tools/chain-monitoring.mdx | 2 +- pages/builders/chain-operators/tools/op-deployer.mdx | 2 +- pages/builders/notices/fp-changes.mdx | 2 +- pages/builders/notices/granite-changes.mdx | 2 +- pages/builders/tools/build/account-abstraction.mdx | 2 +- pages/builders/tools/build/nft-tools.mdx | 4 ---- pages/connect/contribute/style-guide.mdx | 2 +- pages/stack/transactions/withdrawal-flow.mdx | 2 +- words.txt | 1 - 11 files changed, 9 insertions(+), 14 deletions(-) diff --git a/pages/builders/chain-operators/configuration/rollup.mdx b/pages/builders/chain-operators/configuration/rollup.mdx index a82ed3167..b6e93b803 100644 --- a/pages/builders/chain-operators/configuration/rollup.mdx +++ b/pages/builders/chain-operators/configuration/rollup.mdx @@ -973,7 +973,7 @@ instead of the older output oracle mechanism. The Custom Gas Token configuration lets OP Stack chain operators deploy their chain allowing a specific ERC-20 token to be deposited in as the native token -to pay for gas fees. Learn more [here](/stack/features/custom-gas-token). +to pay for gas fees. Learn more [here](/stack/beta-features/custom-gas-token). *** diff --git a/pages/builders/chain-operators/features/alt-da-mode.mdx b/pages/builders/chain-operators/features/alt-da-mode.mdx index c64ab3829..39d8fd93c 100644 --- a/pages/builders/chain-operators/features/alt-da-mode.mdx +++ b/pages/builders/chain-operators/features/alt-da-mode.mdx @@ -224,6 +224,6 @@ 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). +* Additional questions? See the FAQ section in the [Alt-DA Mode Explainer](/stack/bet/alt-da-mode#faqs). * For more detailed info on Alt-DA Mode, see the [specs](https://specs.optimism.io/experimental/alt-da.html). * If you experience any problems, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). diff --git a/pages/builders/chain-operators/tools/chain-monitoring.mdx b/pages/builders/chain-operators/tools/chain-monitoring.mdx index 3efb4ceba..c5ea3410c 100644 --- a/pages/builders/chain-operators/tools/chain-monitoring.mdx +++ b/pages/builders/chain-operators/tools/chain-monitoring.mdx @@ -71,7 +71,7 @@ Additional flags: You can find more info on `op-dispute-mon` on [the repo](https://github.com/ethereum-optimism/optimism/tree/develop/op-dispute-mon). -Chain operators can easily create their grafana dashboard for Dispute Monitor using the following json file: [Download the Dispute Monitor JSON](/grafana/dispute-monitor-1718214549035.json). +Chain operators can easily create their grafana dashboard for Dispute Monitor using the following json file: [Download the Dispute Monitor JSON](/resources/grafana/dispute-monitor-1718214549035.json). ## Offchain Component Monitoring diff --git a/pages/builders/chain-operators/tools/op-deployer.mdx b/pages/builders/chain-operators/tools/op-deployer.mdx index 4d8edb21b..85794f497 100644 --- a/pages/builders/chain-operators/tools/op-deployer.mdx +++ b/pages/builders/chain-operators/tools/op-deployer.mdx @@ -123,5 +123,5 @@ else. You can run another member of the `inspect` family, `rollup`, to get the ` ## Next Steps -* For more details, check out the tool and documentation in the [op-deployer repository](https://github.com/ethereum-optimism/optimism/tree/develop/op-chain-ops/cmd/op-deployer). +* For more details, check out the tool and documentation in the [op-deployer repository](https://github.com/ethereum-optimism/optimism/tree/develop/op-deployer/cmd/op-deployer). * For more information on OP Contracts Manager, refer to the [OPCM documentation](/stack/opcm). diff --git a/pages/builders/notices/fp-changes.mdx b/pages/builders/notices/fp-changes.mdx index c5a6c60af..853263134 100644 --- a/pages/builders/notices/fp-changes.mdx +++ b/pages/builders/notices/fp-changes.mdx @@ -17,7 +17,7 @@ If you experience difficulty at any stage of this process, please reach out to [ **ALL** withdrawals that are not finalized before the Fault Proofs upgrade executes will need to be reproven after the upgrade is complete. - * Reproving simply requires that you execute the [withdrawal proving flow](https://docs.optimism.io/stack/rollup/withdrawal-flow) again. + * Reproving simply requires that you execute the [withdrawal proving flow](https://docs.optimism.io/stack/transactions/withdrawal-flow) again. * Withdrawals prior to the Fault Proofs upgrade must wait a 7-day challenge period before finalization. As a result, any withdrawal initiated less than 7 days before the upgrade cannot be finalized before the upgrade is executed. You may want to consider waiting until after the upgrade is complete to begin a withdrawal during this 7-day window. diff --git a/pages/builders/notices/granite-changes.mdx b/pages/builders/notices/granite-changes.mdx index ccbb10ee8..2b4605676 100644 --- a/pages/builders/notices/granite-changes.mdx +++ b/pages/builders/notices/granite-changes.mdx @@ -17,7 +17,7 @@ If you experience difficulty at any stage of this process, please reach out to [ ## What's Included in Granite -This upgrade is proposed in response to security vulnerabilities identified during a series of third-party security audits by Spearbit, Cantina, and Code4rena. None of the vulnerabilities have been exploited, and user assets are not and were never at risk. However, out of an abundance of caution, the permissioned fallback mechanism has been activated in order to avoid any potential instability while the vulnerabilities are patched. For more information on the permissioned fallback mechanism and the OP Stack's defense-in-depth approach to Fault Proof security, see the [fault proof documentation](https://docs.optimism.io/stack/fault-proofs/fp-security). +This upgrade is proposed in response to security vulnerabilities identified during a series of third-party security audits by Spearbit, Cantina, and Code4rena. None of the vulnerabilities have been exploited, and user assets are not and were never at risk. However, out of an abundance of caution, the permissioned fallback mechanism has been activated in order to avoid any potential instability while the vulnerabilities are patched. For more information on the permissioned fallback mechanism and the OP Stack's defense-in-depth approach to Fault Proof security, see the [fault proof documentation](/stack/fault-proofs/fp-security). The upgrade includes both a set of smart contract upgrades to fix the vulnerabilities identified in the audit as well as an L2 hardfork to improve the stability and performance of the fault proof system. In addition, we propose extending the capabilities of the Guardian and DeputyGuardian to set the anchor state for the fault proof system in order to prevent referencing invalid anchor states. Aside from implementing these fixes, the primary impact of this upgrade would be to reset user withdrawals at the planned time, similar to the initial Fault Proof upgrade. diff --git a/pages/builders/tools/build/account-abstraction.mdx b/pages/builders/tools/build/account-abstraction.mdx index efa52e673..4ca1d1cf9 100644 --- a/pages/builders/tools/build/account-abstraction.mdx +++ b/pages/builders/tools/build/account-abstraction.mdx @@ -31,7 +31,7 @@ If enabled by the chain operator, also see the supplemental [op-txproxy](/builde ## Superchain Paymaster -The Superchain paymaster is an ERC-4337 verifying paymaster that sponsors transactions for smart accounts on the Superchain. Use the Superchain Paymaster to get your transactions sponsored to remove friction from your app experience. [View the implementation guide and tutorials here.](https://github.com/ethereum-optimism/ecosystem/tree/main/docs/superchain-paymaster) +The Superchain paymaster is an ERC-4337 verifying paymaster that sponsors transactions for smart accounts on the Superchain. Use the Superchain Paymaster to get your transactions sponsored to remove friction from your app experience. ## Account Abstraction Tools diff --git a/pages/builders/tools/build/nft-tools.mdx b/pages/builders/tools/build/nft-tools.mdx index 270f3f636..9a9bd9bc2 100644 --- a/pages/builders/tools/build/nft-tools.mdx +++ b/pages/builders/tools/build/nft-tools.mdx @@ -59,7 +59,3 @@ These tools are available on OP Mainnet: * [Tofu](https://tofunft.com/optimism) * [OptiMarket](https://optimarket.io/) * [Circular Art](https://www.circularart.xyz/) - -## Marketplace aggregators - -* [Bluesweep](https://www.bluesweep.xyz/) diff --git a/pages/connect/contribute/style-guide.mdx b/pages/connect/contribute/style-guide.mdx index ddeead204..853aad9f8 100644 --- a/pages/connect/contribute/style-guide.mdx +++ b/pages/connect/contribute/style-guide.mdx @@ -298,7 +298,7 @@ Developers trust that we will lead them to sites or pages related to their readi * Use absolute or relative links when linking across pages in the site. Absolute links are cleaner and easier to work with when pages are nested, so they are the recommended option. - **Examples**: absolute link `(/protocol/deposit-flow)` versus relative link `(../../protocol/deposit-flow)` + **Examples**: absolute link `(/stack/transactions/deposit-flow)` versus relative link `(../../protocol/deposit-flow)` * Use the exact title of the page when linking to it in a sentence, whenever possible, and display it in title case. The link should use default styling with no other formatting (bold, italics, quotations). diff --git a/pages/stack/transactions/withdrawal-flow.mdx b/pages/stack/transactions/withdrawal-flow.mdx index ef49eb6c6..57cbf85f9 100644 --- a/pages/stack/transactions/withdrawal-flow.mdx +++ b/pages/stack/transactions/withdrawal-flow.mdx @@ -98,7 +98,7 @@ The Chugsplash Proxy operates differently than standard proxies. During a withdr For more information about the withdrawal process and how it works on Optimism, refer to the following resources: * [Smart Contracts Overview](https://docs.optimism.io/stack/rollup/smart-contracts) -* [Withdrawal Flow](https://docs.optimism.io/stack/rollup/withdrawal-flow#withdrawal-initiating-transaction) +* [Withdrawal Flow](https://docs.optimism.io/stack/transactions/withdrawal-flow#withdrawal-initiating-transaction) ### Offchain processing diff --git a/words.txt b/words.txt index 21cc95118..93c865012 100644 --- a/words.txt +++ b/words.txt @@ -38,7 +38,6 @@ blocktime BLOOMFILTER bloomfilter BLTZ -Bluesweep Bootcamp BOOTNODES Bootnodes From f489068926707b77bca0e4035490100905d2592a Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 18 Oct 2024 22:18:48 -0600 Subject: [PATCH 7/9] fixing more broken links --- pages/builders/chain-operators/features/alt-da-mode.mdx | 4 ++-- pages/builders/notices/fp-changes.mdx | 2 +- pages/stack/transactions/withdrawal-flow.mdx | 5 ----- 3 files changed, 3 insertions(+), 8 deletions(-) diff --git a/pages/builders/chain-operators/features/alt-da-mode.mdx b/pages/builders/chain-operators/features/alt-da-mode.mdx index 39d8fd93c..8df26f52f 100644 --- a/pages/builders/chain-operators/features/alt-da-mode.mdx +++ b/pages/builders/chain-operators/features/alt-da-mode.mdx @@ -44,7 +44,7 @@ You should use at least the following compatible op\* versions when running your * Celestia's docs on how to run the [Celestia DA server](https://github.com/celestiaorg/op-plasma-celestia/blob/main/README.md) * EigenDA's docs on how to run the [EigenDA DA server](https://github.com/Layr-Labs/op-plasma-eigenda/blob/main/README.md) * Avail's docs on how to run the [AvailDA DA Server](https://docs.availproject.org/docs/build-with-avail/Optimium/op-stack/op-stack#setup-avail-da-server) - * 0gDA's docs on how to run the [0gDA DA Server](https://github.com/0glabs/0g-da-op-plasma/blob/op0g/README.md) + * 0gDA's docs on how to run the [0gDA DA Server](https://github.com/0glabs/0g-da-op-plasma) * Near DA's docs on how to run the [Near DA Server](https://github.com/Nuffle-Labs/data-availability/blob/84b484de98f58a91bf12c8abe8df27f5e753f63a/docs/OP-Alt-DA.md) ### Configure Your `op-node` @@ -224,6 +224,6 @@ 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/bet/alt-da-mode#faqs). +* 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). * If you experience any problems, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). diff --git a/pages/builders/notices/fp-changes.mdx b/pages/builders/notices/fp-changes.mdx index 853263134..90502bf5f 100644 --- a/pages/builders/notices/fp-changes.mdx +++ b/pages/builders/notices/fp-changes.mdx @@ -17,7 +17,7 @@ If you experience difficulty at any stage of this process, please reach out to [ **ALL** withdrawals that are not finalized before the Fault Proofs upgrade executes will need to be reproven after the upgrade is complete. - * Reproving simply requires that you execute the [withdrawal proving flow](https://docs.optimism.io/stack/transactions/withdrawal-flow) again. + * Reproving simply requires that you execute the [withdrawal proving flow](/stack/transactions/withdrawal-flow) again. * Withdrawals prior to the Fault Proofs upgrade must wait a 7-day challenge period before finalization. As a result, any withdrawal initiated less than 7 days before the upgrade cannot be finalized before the upgrade is executed. You may want to consider waiting until after the upgrade is complete to begin a withdrawal during this 7-day window. diff --git a/pages/stack/transactions/withdrawal-flow.mdx b/pages/stack/transactions/withdrawal-flow.mdx index 57cbf85f9..7de98ea75 100644 --- a/pages/stack/transactions/withdrawal-flow.mdx +++ b/pages/stack/transactions/withdrawal-flow.mdx @@ -95,11 +95,6 @@ The Chugsplash Proxy operates differently than standard proxies. During a withdr * **No Cause for Concern**: Although Etherscan highlights these reverts, they do not affect the final success of the transaction. * **User Assurance**: If you encounter these reverts during a withdrawal transaction, rest assured that the withdrawal will still finalize as expected. -For more information about the withdrawal process and how it works on Optimism, refer to the following resources: - -* [Smart Contracts Overview](https://docs.optimism.io/stack/rollup/smart-contracts) -* [Withdrawal Flow](https://docs.optimism.io/stack/transactions/withdrawal-flow#withdrawal-initiating-transaction) - ### Offchain processing 1. A user calls the SDK's [`CrossDomainMessenger.finalizeMessage()`](https://github.com/ethereum-optimism/optimism/blob/62c7f3b05a70027b30054d4c8974f44000606fb7/packages/sdk/src/cross-chain-messenger.ts#L1473-L1493) with the hash of the L1 message. From 7214836d378713d48c4ca09f57f25eaaf397d842 Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 18 Oct 2024 22:48:35 -0600 Subject: [PATCH 8/9] last broken links? --- pages/stack/rollup/overview.mdx | 4 ++-- public/_redirects | 12 ++++++------ 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/pages/stack/rollup/overview.mdx b/pages/stack/rollup/overview.mdx index a275be581..e71405711 100644 --- a/pages/stack/rollup/overview.mdx +++ b/pages/stack/rollup/overview.mdx @@ -50,7 +50,7 @@ Transactions get to the sequencer in two ways: 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). -For the moment, [The Optimism Foundation](https://www.optimism.io/) runs the only block producer on OP Mainnet. Refer to [Protocol specs](overview) section for more information about how we plan to decentralize the Sequencer role in the future. +For the moment, [The Optimism Foundation](https://www.optimism.io/) runs the only block producer on OP Mainnet. ## Block Execution @@ -112,5 +112,5 @@ The fault proof process is currently undergoing major redevelopment as a side-ef ## Next Steps -* If you want to learn more about rollup protocol, check out the guides on [deposit flow](deposit-flow), [withdrawal flow](withdrawal-flow), or [transaction flow](transaction-flow). +* If you want to learn more about rollup protocol, check out the guides on [deposit flow](/stack/transactions/deposit-flow), [withdrawal flow](/stack/transactions/withdrawal-flow), or [transaction flow](/stack/transactions/transaction-flow). * To learn about operating your own L2 rollup, see the guide on [starting a self-hosted chain](/builders/chain-operators/self-hosted) or go directly to the tutorial on [creating your own L2 rollup](/builders/chain-operators/tutorials/create-l2-rollup). diff --git a/public/_redirects b/public/_redirects index 59f07d98b..d586cee18 100644 --- a/public/_redirects +++ b/public/_redirects @@ -62,17 +62,17 @@ /transaction-fees/overview /builders/app-developers/transactions/fees /dapp-developers/contracts/meta-tx /builders/app-developers/contracts/optimization /builders/tools/build/overview /builders/tools/overview -/protocol-specifications/optimistic-rollup/block-production /stack/protocol/rollup/overview#block-production +/protocol-specifications/optimistic-rollup/block-production /stack/rollup/overview#block-production /builders/node-operators/metrics /builders/node-operators/management/metrics /stack /stack/getting-started /chain/sec /chain/security/faq /builders/chain-operators/management/tools/explorer /builders/chain-operators/tools/explorer /builders/node-operators/management/configuration /builders/node-operators/configuration/base-config -/stack/protocol/deposit-flow /stack/protocol/rollup/deposit-flow -/stack/protocol/transaction-flow /stack/protocol/rollup/transaction-flow -/stack/protocol/withdrawal-flow /stack/protocol/rollup/withdrawal-flow -/stack/protocol/smart-contracts /stack/protocol/rollup/smart-contracts -/stack/protocol/overview /stack/protocol/rollup/overview +/stack/protocol/deposit-flow /stack/transactions/deposit-flow +/stack/protocol/transaction-flow /stack/transactions/transaction-flow +/stack/protocol/withdrawal-flow /stack/transactions/withdrawal-flow +/stack/protocol/smart-contracts /stack/smart-contracts +/stack/protocol/overview /stack/rollup/overview /stack/protocol/design-principles /stack/design-principles /builders/node-operators/overview /builders/node-operators/rollup-node /builders/notices/ecotone-changes /stack/transactions/fees#ecotone From 72ae27c8ae00f0d2a7d421f2a874c11f4f2157aa Mon Sep 17 00:00:00 2001 From: soyboy Date: Sat, 19 Oct 2024 15:57:53 -0600 Subject: [PATCH 9/9] fixing internal link --- pages/stack/interop/explainer.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/stack/interop/explainer.mdx b/pages/stack/interop/explainer.mdx index 53afe4cbd..f4d5c17bd 100644 --- a/pages/stack/interop/explainer.mdx +++ b/pages/stack/interop/explainer.mdx @@ -25,7 +25,7 @@ Native OP Stack interoperability provides the ability to read messages and trans Superchain interop includes both the protocol layer message passing and the Superchain ERC20 token specification. * **Message passing protocol:** the initial + finalizing/executing [message](https://specs.optimism.io/interop/messaging.html) that fire events to be consumed by the chains in the [dependency set](https://specs.optimism.io/interop/dependency-set.html) -* **SuperchainERC20 token specification**: the [SuperchainERC20](https://specs.optimism.io/interop/token-bridging.html) turns message passing into asset transfer between chains in the interop set. Learn more about how the SuperchainERC20 token standard enables asset interoperability in the Superchain [here](/stack/protocol/interop/superchain-erc20) +* **SuperchainERC20 token specification**: the [SuperchainERC20](https://specs.optimism.io/interop/token-bridging.html) turns message passing into asset transfer between chains in the interop set. Learn more about how the SuperchainERC20 token standard enables asset interoperability in the Superchain [here](/stack/interop/superchain-erc20) This means ETH and ERC-20s can seamlessly and securely move across L2s, and intent-based protocols (i.e., bridges) can build better experiences on top of the message passing protocol.