From 75b79ab577a4c1476060ce4981b8f07f14546cdc Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Mon, 27 Jan 2025 23:16:02 -0800 Subject: [PATCH 01/49] nav prototype --- next-env.d.ts | 2 +- pages/_meta.json | 92 ++++++------ .../{builders => }/app-developers/_meta.json | 4 + .../app-developers/bridging.mdx | 5 + .../app-developers/bridging/_meta.json | 0 .../app-developers/bridging/basics.mdx | 0 .../app-developers/bridging/custom-bridge.mdx | 0 .../app-developers/bridging/messaging.mdx | 0 .../bridging/standard-bridge.mdx | 0 .../app-developers/overview.mdx | 0 .../app-developers/quick-start.mdx | 0 pages/{builders => }/app-developers/tools.mdx | 8 ++ .../tools/_meta.json | 3 +- .../tools/build.mdx | 0 .../tools/build/_meta.json | 0 .../tools/build/account-abstraction.mdx | 0 .../tools/build/block-explorers.mdx | 0 .../tools/build/faucets.mdx | 0 .../tools/build/nft-tools.mdx | 0 .../tools/build/oracles.mdx | 0 .../tools/connect.mdx | 0 .../tools/connect/_meta.json | 0 .../tools/connect/networks.mdx | 0 .../tools/connect/rpc-providers.mdx | 0 .../tools/ecosystem-overview.mdx | 0 .../tools/monitor.mdx | 0 .../tools/monitor/_meta.json | 0 .../tools/monitor/analytics-tools.mdx | 0 .../tools/monitor/regenesis-history.mdx | 0 .../tools/op-tools.mdx | 0 .../tools/op-tools/_meta.json | 0 .../tools/overview.mdx | 0 .../app-developers/tools/supersim.mdx | 0 .../app-developers/transactions.mdx | 6 + .../app-developers/transactions/_meta.json | 0 .../app-developers/transactions/estimates.mdx | 0 .../app-developers/transactions/fees.mdx | 0 .../transactions/parameters.mdx | 0 .../app-developers/transactions/statuses.mdx | 0 .../transactions/troubleshooting.mdx | 0 .../app-developers/tutorials.mdx | 10 ++ .../app-developers/tutorials/_meta.json | 0 .../tutorials/cross-dom-bridge-erc20.mdx | 0 .../tutorials/cross-dom-bridge-eth.mdx | 0 .../tutorials/cross-dom-solidity.mdx | 0 .../tutorials/sdk-estimate-costs.mdx | 0 .../tutorials/sdk-trace-txns.mdx | 0 .../tutorials/sdk-view-txns.mdx | 0 .../tutorials/send-tx-from-eth.mdx | 0 .../standard-bridge-custom-token.mdx | 0 .../standard-bridge-standard-token.mdx | 0 pages/builders.mdx | 20 --- pages/builders/_meta.json | 7 - pages/builders/app-developers.mdx | 25 ---- .../builders/app-developers/tools/_meta.json | 9 -- pages/builders/chain-operators.mdx | 31 ----- pages/builders/node-operators.mdx | 29 ---- pages/builders/notices.mdx | 19 --- pages/builders/tools.mdx | 25 ---- pages/index.mdx | 2 +- pages/{builders => }/notices/_meta.json | 0 .../notices/holocene-changes.mdx | 0 .../{builders => }/notices/pectra-changes.mdx | 0 .../notices/sdk-deprecation.mdx | 0 pages/operators/_meta.json | 22 +++ pages/operators/chain-operators.mdx | 23 +++ .../chain-operators/_meta.json | 0 .../chain-operators/architecture.mdx | 0 .../chain-operators/configuration.mdx | 0 .../chain-operators/configuration/_meta.json | 0 .../chain-operators/configuration/batcher.mdx | 0 .../configuration/overview.mdx | 0 .../configuration/proposer.mdx | 0 .../chain-operators/configuration/rollup.mdx | 0 .../chain-operators/deploy.mdx | 0 .../chain-operators/deploy/_meta.json | 0 .../chain-operators/deploy/genesis.mdx | 0 .../chain-operators/deploy/overview.mdx | 0 .../deploy/smart-contracts.mdx | 0 .../chain-operators/features.mdx | 0 .../chain-operators/features/_meta.json | 0 .../chain-operators/features/alt-da-mode.mdx | 0 .../features/bridged-usdc-standard.mdx | 0 .../features/custom-gas-token.mdx | 0 .../chain-operators/features/preinstalls.mdx | 0 .../chain-operators/features/span-batches.mdx | 0 .../chain-operators/hacks.mdx | 0 .../chain-operators/hacks/_meta.json | 0 .../hacks/data-availability.mdx | 0 .../chain-operators/hacks/derivation.mdx | 0 .../chain-operators/hacks/execution.mdx | 0 .../chain-operators/hacks/featured-hacks.mdx | 0 .../chain-operators/hacks/overview.mdx | 0 .../chain-operators/hacks/settlement.mdx | 0 .../chain-operators/management.mdx | 0 .../chain-operators/management/_meta.json | 0 .../management/best-practices.mdx | 0 .../chain-operators/management/blobs.mdx | 0 .../management/key-management.mdx | 0 .../chain-operators/management/operations.mdx | 0 .../chain-operators/management/snap-sync.mdx | 0 .../management/troubleshooting.mdx | 0 .../chain-operators/self-hosted.mdx | 0 .../chain-operators/tools.mdx | 0 .../chain-operators/tools/_meta.json | 3 +- .../tools/chain-monitoring.mdx | 0 .../chain-operators/tools/explorer.mdx | 0 .../chain-operators}/tools/fee-calculator.mdx | 0 .../chain-operators/tools/op-challenger.mdx | 0 .../chain-operators/tools/op-conductor.mdx | 0 .../chain-operators/tools/op-deployer.mdx | 0 .../chain-operators/tools/op-txproxy.mdx | 0 .../chain-operators/tools/proxyd.mdx | 0 .../chain-operators/tutorials.mdx | 0 .../chain-operators/tutorials/_meta.json | 0 .../adding-derivation-attributes.mdx | 0 .../tutorials/adding-precompiles.mdx | 0 .../tutorials/create-l2-rollup.mdx | 0 .../tutorials/integrating-da-layer.mdx | 0 .../tutorials/modifying-predeploys.mdx | 0 pages/operators/node-operators.mdx | 22 +++ .../node-operators/_meta.json | 0 .../node-operators/architecture.mdx | 0 .../node-operators/configuration.mdx | 0 .../node-operators/configuration/_meta.json | 0 .../configuration/base-config.mdx | 0 .../configuration/consensus-config.mdx | 0 .../configuration/execution-config.mdx | 0 .../node-operators/json-rpc.mdx | 0 .../node-operators/management.mdx | 0 .../node-operators/management/_meta.json | 0 .../node-operators/management/blobs.mdx | 0 .../node-operators/management/metrics.mdx | 0 .../node-operators/management/snap-sync.mdx | 0 .../node-operators/management/snapshots.mdx | 0 .../management/troubleshooting.mdx | 0 .../node-operators/network-upgrades.mdx | 0 .../node-operators/releases.mdx | 0 .../node-operators/rollup-node.mdx | 0 .../node-operators/tutorials.mdx | 0 .../node-operators/tutorials/_meta.json | 0 .../node-operators/tutorials/mainnet.mdx | 0 .../tutorials/node-from-docker.mdx | 0 .../tutorials/node-from-source.mdx | 0 .../node-operators/tutorials/testnet.mdx | 0 pages/stack/_meta.json | 10 +- pages/stack/chain.mdx | 20 +++ pages/{ => stack}/chain/_meta.json | 0 pages/{ => stack}/chain/addresses.mdx | 0 pages/{ => stack}/chain/getting-started.mdx | 0 pages/{ => stack}/chain/networks.mdx | 0 pages/{ => stack}/chain/security.mdx | 0 pages/{ => stack}/chain/security/_meta.json | 0 pages/{ => stack}/chain/security/faq.mdx | 0 .../chain/security/privileged-roles.mdx | 0 .../chain/security/security-policy.mdx | 0 pages/{ => stack}/chain/testing.mdx | 0 pages/{ => stack}/chain/testing/_meta.json | 0 pages/{ => stack}/chain/testing/dev-node.mdx | 0 .../chain/testing/testing-apps.mdx | 0 pages/{ => stack}/chain/tokenlist.mdx | 0 pages/superchain/_meta.json | 4 + public/_redirects | 131 +++++++++--------- utils/breadcrumbs.ts | 2 +- utils/create-breadcrumbs.ts | 2 +- 165 files changed, 247 insertions(+), 289 deletions(-) rename pages/{builders => }/app-developers/_meta.json (67%) rename pages/{builders => }/app-developers/bridging.mdx (71%) rename pages/{builders => }/app-developers/bridging/_meta.json (100%) rename pages/{builders => }/app-developers/bridging/basics.mdx (100%) rename pages/{builders => }/app-developers/bridging/custom-bridge.mdx (100%) rename pages/{builders => }/app-developers/bridging/messaging.mdx (100%) rename pages/{builders => }/app-developers/bridging/standard-bridge.mdx (100%) rename pages/{builders => }/app-developers/overview.mdx (100%) rename pages/{builders => }/app-developers/quick-start.mdx (100%) rename pages/{builders => }/app-developers/tools.mdx (54%) rename pages/{builders => app-developers}/tools/_meta.json (62%) rename pages/{builders => app-developers}/tools/build.mdx (100%) rename pages/{builders => app-developers}/tools/build/_meta.json (100%) rename pages/{builders => app-developers}/tools/build/account-abstraction.mdx (100%) rename pages/{builders => app-developers}/tools/build/block-explorers.mdx (100%) rename pages/{builders => app-developers}/tools/build/faucets.mdx (100%) rename pages/{builders => app-developers}/tools/build/nft-tools.mdx (100%) rename pages/{builders => app-developers}/tools/build/oracles.mdx (100%) rename pages/{builders => app-developers}/tools/connect.mdx (100%) rename pages/{builders => app-developers}/tools/connect/_meta.json (100%) rename pages/{builders => app-developers}/tools/connect/networks.mdx (100%) rename pages/{builders => app-developers}/tools/connect/rpc-providers.mdx (100%) rename pages/{builders => }/app-developers/tools/ecosystem-overview.mdx (100%) rename pages/{builders => app-developers}/tools/monitor.mdx (100%) rename pages/{builders => app-developers}/tools/monitor/_meta.json (100%) rename pages/{builders => app-developers}/tools/monitor/analytics-tools.mdx (100%) rename pages/{builders => app-developers}/tools/monitor/regenesis-history.mdx (100%) rename pages/{builders => app-developers}/tools/op-tools.mdx (100%) rename pages/{builders => app-developers}/tools/op-tools/_meta.json (100%) rename pages/{builders => app-developers}/tools/overview.mdx (100%) rename pages/{builders => }/app-developers/tools/supersim.mdx (100%) rename pages/{builders => }/app-developers/transactions.mdx (68%) rename pages/{builders => }/app-developers/transactions/_meta.json (100%) rename pages/{builders => }/app-developers/transactions/estimates.mdx (100%) rename pages/{builders => }/app-developers/transactions/fees.mdx (100%) rename pages/{builders => }/app-developers/transactions/parameters.mdx (100%) rename pages/{builders => }/app-developers/transactions/statuses.mdx (100%) rename pages/{builders => }/app-developers/transactions/troubleshooting.mdx (100%) rename pages/{builders => }/app-developers/tutorials.mdx (65%) rename pages/{builders => }/app-developers/tutorials/_meta.json (100%) rename pages/{builders => }/app-developers/tutorials/cross-dom-bridge-erc20.mdx (100%) rename pages/{builders => }/app-developers/tutorials/cross-dom-bridge-eth.mdx (100%) rename pages/{builders => }/app-developers/tutorials/cross-dom-solidity.mdx (100%) rename pages/{builders => }/app-developers/tutorials/sdk-estimate-costs.mdx (100%) rename pages/{builders => }/app-developers/tutorials/sdk-trace-txns.mdx (100%) rename pages/{builders => }/app-developers/tutorials/sdk-view-txns.mdx (100%) rename pages/{builders => }/app-developers/tutorials/send-tx-from-eth.mdx (100%) rename pages/{builders => }/app-developers/tutorials/standard-bridge-custom-token.mdx (100%) rename pages/{builders => }/app-developers/tutorials/standard-bridge-standard-token.mdx (100%) delete mode 100644 pages/builders.mdx delete mode 100644 pages/builders/_meta.json delete mode 100644 pages/builders/app-developers.mdx delete mode 100644 pages/builders/app-developers/tools/_meta.json delete mode 100644 pages/builders/chain-operators.mdx delete mode 100644 pages/builders/node-operators.mdx delete mode 100644 pages/builders/notices.mdx delete mode 100644 pages/builders/tools.mdx rename pages/{builders => }/notices/_meta.json (100%) rename pages/{builders => }/notices/holocene-changes.mdx (100%) rename pages/{builders => }/notices/pectra-changes.mdx (100%) rename pages/{builders => }/notices/sdk-deprecation.mdx (100%) create mode 100644 pages/operators/_meta.json create mode 100644 pages/operators/chain-operators.mdx rename pages/{builders => operators}/chain-operators/_meta.json (100%) rename pages/{builders => operators}/chain-operators/architecture.mdx (100%) rename pages/{builders => operators}/chain-operators/configuration.mdx (100%) rename pages/{builders => operators}/chain-operators/configuration/_meta.json (100%) rename pages/{builders => operators}/chain-operators/configuration/batcher.mdx (100%) rename pages/{builders => operators}/chain-operators/configuration/overview.mdx (100%) rename pages/{builders => operators}/chain-operators/configuration/proposer.mdx (100%) rename pages/{builders => operators}/chain-operators/configuration/rollup.mdx (100%) rename pages/{builders => operators}/chain-operators/deploy.mdx (100%) rename pages/{builders => operators}/chain-operators/deploy/_meta.json (100%) rename pages/{builders => operators}/chain-operators/deploy/genesis.mdx (100%) rename pages/{builders => operators}/chain-operators/deploy/overview.mdx (100%) rename pages/{builders => operators}/chain-operators/deploy/smart-contracts.mdx (100%) rename pages/{builders => operators}/chain-operators/features.mdx (100%) rename pages/{builders => operators}/chain-operators/features/_meta.json (100%) rename pages/{builders => operators}/chain-operators/features/alt-da-mode.mdx (100%) rename pages/{builders => operators}/chain-operators/features/bridged-usdc-standard.mdx (100%) rename pages/{builders => operators}/chain-operators/features/custom-gas-token.mdx (100%) rename pages/{builders => operators}/chain-operators/features/preinstalls.mdx (100%) rename pages/{builders => operators}/chain-operators/features/span-batches.mdx (100%) rename pages/{builders => operators}/chain-operators/hacks.mdx (100%) rename pages/{builders => operators}/chain-operators/hacks/_meta.json (100%) rename pages/{builders => operators}/chain-operators/hacks/data-availability.mdx (100%) rename pages/{builders => operators}/chain-operators/hacks/derivation.mdx (100%) rename pages/{builders => operators}/chain-operators/hacks/execution.mdx (100%) rename pages/{builders => operators}/chain-operators/hacks/featured-hacks.mdx (100%) rename pages/{builders => operators}/chain-operators/hacks/overview.mdx (100%) rename pages/{builders => operators}/chain-operators/hacks/settlement.mdx (100%) rename pages/{builders => operators}/chain-operators/management.mdx (100%) rename pages/{builders => operators}/chain-operators/management/_meta.json (100%) rename pages/{builders => operators}/chain-operators/management/best-practices.mdx (100%) rename pages/{builders => operators}/chain-operators/management/blobs.mdx (100%) rename pages/{builders => operators}/chain-operators/management/key-management.mdx (100%) rename pages/{builders => operators}/chain-operators/management/operations.mdx (100%) rename pages/{builders => operators}/chain-operators/management/snap-sync.mdx (100%) rename pages/{builders => operators}/chain-operators/management/troubleshooting.mdx (100%) rename pages/{builders => operators}/chain-operators/self-hosted.mdx (100%) rename pages/{builders => operators}/chain-operators/tools.mdx (100%) rename pages/{builders => operators}/chain-operators/tools/_meta.json (78%) rename pages/{builders => operators}/chain-operators/tools/chain-monitoring.mdx (100%) rename pages/{builders => operators}/chain-operators/tools/explorer.mdx (100%) rename pages/{builders => operators/chain-operators}/tools/fee-calculator.mdx (100%) rename pages/{builders => operators}/chain-operators/tools/op-challenger.mdx (100%) rename pages/{builders => operators}/chain-operators/tools/op-conductor.mdx (100%) rename pages/{builders => operators}/chain-operators/tools/op-deployer.mdx (100%) rename pages/{builders => operators}/chain-operators/tools/op-txproxy.mdx (100%) rename pages/{builders => operators}/chain-operators/tools/proxyd.mdx (100%) rename pages/{builders => operators}/chain-operators/tutorials.mdx (100%) rename pages/{builders => operators}/chain-operators/tutorials/_meta.json (100%) rename pages/{builders => operators}/chain-operators/tutorials/adding-derivation-attributes.mdx (100%) rename pages/{builders => operators}/chain-operators/tutorials/adding-precompiles.mdx (100%) rename pages/{builders => operators}/chain-operators/tutorials/create-l2-rollup.mdx (100%) rename pages/{builders => operators}/chain-operators/tutorials/integrating-da-layer.mdx (100%) rename pages/{builders => operators}/chain-operators/tutorials/modifying-predeploys.mdx (100%) create mode 100644 pages/operators/node-operators.mdx rename pages/{builders => operators}/node-operators/_meta.json (100%) rename pages/{builders => operators}/node-operators/architecture.mdx (100%) rename pages/{builders => operators}/node-operators/configuration.mdx (100%) rename pages/{builders => operators}/node-operators/configuration/_meta.json (100%) rename pages/{builders => operators}/node-operators/configuration/base-config.mdx (100%) rename pages/{builders => operators}/node-operators/configuration/consensus-config.mdx (100%) rename pages/{builders => operators}/node-operators/configuration/execution-config.mdx (100%) rename pages/{builders => operators}/node-operators/json-rpc.mdx (100%) rename pages/{builders => operators}/node-operators/management.mdx (100%) rename pages/{builders => operators}/node-operators/management/_meta.json (100%) rename pages/{builders => operators}/node-operators/management/blobs.mdx (100%) rename pages/{builders => operators}/node-operators/management/metrics.mdx (100%) rename pages/{builders => operators}/node-operators/management/snap-sync.mdx (100%) rename pages/{builders => operators}/node-operators/management/snapshots.mdx (100%) rename pages/{builders => operators}/node-operators/management/troubleshooting.mdx (100%) rename pages/{builders => operators}/node-operators/network-upgrades.mdx (100%) rename pages/{builders => operators}/node-operators/releases.mdx (100%) rename pages/{builders => operators}/node-operators/rollup-node.mdx (100%) rename pages/{builders => operators}/node-operators/tutorials.mdx (100%) rename pages/{builders => operators}/node-operators/tutorials/_meta.json (100%) rename pages/{builders => operators}/node-operators/tutorials/mainnet.mdx (100%) rename pages/{builders => operators}/node-operators/tutorials/node-from-docker.mdx (100%) rename pages/{builders => operators}/node-operators/tutorials/node-from-source.mdx (100%) rename pages/{builders => operators}/node-operators/tutorials/testnet.mdx (100%) create mode 100644 pages/stack/chain.mdx rename pages/{ => stack}/chain/_meta.json (100%) rename pages/{ => stack}/chain/addresses.mdx (100%) rename pages/{ => stack}/chain/getting-started.mdx (100%) rename pages/{ => stack}/chain/networks.mdx (100%) rename pages/{ => stack}/chain/security.mdx (100%) rename pages/{ => stack}/chain/security/_meta.json (100%) rename pages/{ => stack}/chain/security/faq.mdx (100%) rename pages/{ => stack}/chain/security/privileged-roles.mdx (100%) rename pages/{ => stack}/chain/security/security-policy.mdx (100%) rename pages/{ => stack}/chain/testing.mdx (100%) rename pages/{ => stack}/chain/testing/_meta.json (100%) rename pages/{ => stack}/chain/testing/dev-node.mdx (100%) rename pages/{ => stack}/chain/testing/testing-apps.mdx (100%) rename pages/{ => stack}/chain/tokenlist.mdx (100%) diff --git a/next-env.d.ts b/next-env.d.ts index 4f11a03dc..a4a7b3f5c 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/basic-features/typescript for more information. +// see https://nextjs.org/docs/pages/building-your-application/configuring/typescript for more information. diff --git a/pages/_meta.json b/pages/_meta.json index 26f362e32..af0cf1fa8 100644 --- a/pages/_meta.json +++ b/pages/_meta.json @@ -1,12 +1,12 @@ { "index": { - "title": "Getting started", + "title": "Get started", "display": "hidden", "theme": { "breadcrumb": false, "footer": true, "sidebar": true, - "toc": true, + "toc": false, "pagination": false } }, @@ -37,73 +37,63 @@ } }, - "faucet": { - "title": "Superchain faucet", - "type": "page", - "href": "https://console.optimism.io/faucet?utm_source=docs", - "newWindow": true - }, - "gas": { - "title": "Gas tracker", - "type": "page", - "href": "https://optimistic.grafana.net/public-dashboards/c84a5a9924fe4e14b270a42a8651ceb8?orgId=1&refresh=5m", - "newWindow": true - }, - "status": { - "title": "Status", - "type": "page", - "href": "https://status.optimism.io/", - "newWindow": true - }, - - "--- BUILDERS": { - "title": "BUILDERS", - "type": "separator" - }, - "builders": { - "title": "Builders", - "display": "children" - }, - - "+++ THE SUPERCHAIN": { - "title": "", - "type": "separator" - }, - "--- THE SUPERCHAIN": { - "title": "THE SUPERCHAIN", - "type": "separator" - }, "superchain": { "title": "The Superchain", + "type":"page", + "theme": { + "navbar": true, + "sidebar": true, + "toc": true, + "pagination": true + }, "display": "children" }, - - "+++ OP STACK": { - "title": "", - "type": "separator" + "app-developers": { + "title": "App Devs", + "type": "page", + "theme": { + "navbar": true, + "sidebar": true, + "toc": true, + "pagination": true + }, + "display": "children" }, - "--- OP STACK": { - "title": "OP STACK", - "type": "separator" + "operators": { + "title": "Operators", + "type": "page", + "theme": { + "navbar": true, + "sidebar": true, + "toc": true, + "pagination": true + }, + "display": "children" }, "stack": { "title": "OP Stack", + "type": "page", + "theme": { + "navbar": true, + "sidebar": true, + "toc": true, + "pagination": true + }, "display": "children" }, - "+++ OP MAINNET": { + "+++ NOTICES": { "title": "", "type": "separator" }, - "--- OP MAINNET": { - "title": "OP MAINNET", + "--- NOTICES": { + "title": "NOTICES", "type": "separator" }, - "chain": { - "title": "OP Mainnet", + "notices": { + "title": "Notices", "display": "children" }, - "+++ CONNECT": { "title": "", "type": "separator" diff --git a/pages/builders/app-developers/_meta.json b/pages/app-developers/_meta.json similarity index 67% rename from pages/builders/app-developers/_meta.json rename to pages/app-developers/_meta.json index b2cbaa949..f00e7d62b 100644 --- a/pages/builders/app-developers/_meta.json +++ b/pages/app-developers/_meta.json @@ -1,4 +1,8 @@ { + "--- APP DEVS": { + "title": "APP DEVELOPERS", + "type": "separator" + }, "overview": "Overview", "quick-start": "Superchain app quick start", "tutorials": "Tutorials", diff --git a/pages/builders/app-developers/bridging.mdx b/pages/app-developers/bridging.mdx similarity index 71% rename from pages/builders/app-developers/bridging.mdx rename to pages/app-developers/bridging.mdx index 893cb6db6..3cf4fefbc 100644 --- a/pages/builders/app-developers/bridging.mdx +++ b/pages/app-developers/bridging.mdx @@ -18,4 +18,9 @@ This section provides information on bridging basics, custom bridges, sending da + + + + + diff --git a/pages/builders/app-developers/bridging/_meta.json b/pages/app-developers/bridging/_meta.json similarity index 100% rename from pages/builders/app-developers/bridging/_meta.json rename to pages/app-developers/bridging/_meta.json diff --git a/pages/builders/app-developers/bridging/basics.mdx b/pages/app-developers/bridging/basics.mdx similarity index 100% rename from pages/builders/app-developers/bridging/basics.mdx rename to pages/app-developers/bridging/basics.mdx diff --git a/pages/builders/app-developers/bridging/custom-bridge.mdx b/pages/app-developers/bridging/custom-bridge.mdx similarity index 100% rename from pages/builders/app-developers/bridging/custom-bridge.mdx rename to pages/app-developers/bridging/custom-bridge.mdx diff --git a/pages/builders/app-developers/bridging/messaging.mdx b/pages/app-developers/bridging/messaging.mdx similarity index 100% rename from pages/builders/app-developers/bridging/messaging.mdx rename to pages/app-developers/bridging/messaging.mdx diff --git a/pages/builders/app-developers/bridging/standard-bridge.mdx b/pages/app-developers/bridging/standard-bridge.mdx similarity index 100% rename from pages/builders/app-developers/bridging/standard-bridge.mdx rename to pages/app-developers/bridging/standard-bridge.mdx diff --git a/pages/builders/app-developers/overview.mdx b/pages/app-developers/overview.mdx similarity index 100% rename from pages/builders/app-developers/overview.mdx rename to pages/app-developers/overview.mdx diff --git a/pages/builders/app-developers/quick-start.mdx b/pages/app-developers/quick-start.mdx similarity index 100% rename from pages/builders/app-developers/quick-start.mdx rename to pages/app-developers/quick-start.mdx diff --git a/pages/builders/app-developers/tools.mdx b/pages/app-developers/tools.mdx similarity index 54% rename from pages/builders/app-developers/tools.mdx rename to pages/app-developers/tools.mdx index 7aeb81f23..03cbd5c63 100644 --- a/pages/builders/app-developers/tools.mdx +++ b/pages/app-developers/tools.mdx @@ -14,4 +14,12 @@ This section provides information on open-source code repositories for OP Stack + + + + + + + + diff --git a/pages/builders/tools/_meta.json b/pages/app-developers/tools/_meta.json similarity index 62% rename from pages/builders/tools/_meta.json rename to pages/app-developers/tools/_meta.json index 440d418b9..c194edc71 100644 --- a/pages/builders/tools/_meta.json +++ b/pages/app-developers/tools/_meta.json @@ -3,6 +3,5 @@ "connect": "Connecting", "build": "Building", "monitor": "Monitoring", - "op-tools": "OP tools", - "fee-calculator": "Fee calculator" + "op-tools": "OP tools" } diff --git a/pages/builders/tools/build.mdx b/pages/app-developers/tools/build.mdx similarity index 100% rename from pages/builders/tools/build.mdx rename to pages/app-developers/tools/build.mdx diff --git a/pages/builders/tools/build/_meta.json b/pages/app-developers/tools/build/_meta.json similarity index 100% rename from pages/builders/tools/build/_meta.json rename to pages/app-developers/tools/build/_meta.json diff --git a/pages/builders/tools/build/account-abstraction.mdx b/pages/app-developers/tools/build/account-abstraction.mdx similarity index 100% rename from pages/builders/tools/build/account-abstraction.mdx rename to pages/app-developers/tools/build/account-abstraction.mdx diff --git a/pages/builders/tools/build/block-explorers.mdx b/pages/app-developers/tools/build/block-explorers.mdx similarity index 100% rename from pages/builders/tools/build/block-explorers.mdx rename to pages/app-developers/tools/build/block-explorers.mdx diff --git a/pages/builders/tools/build/faucets.mdx b/pages/app-developers/tools/build/faucets.mdx similarity index 100% rename from pages/builders/tools/build/faucets.mdx rename to pages/app-developers/tools/build/faucets.mdx diff --git a/pages/builders/tools/build/nft-tools.mdx b/pages/app-developers/tools/build/nft-tools.mdx similarity index 100% rename from pages/builders/tools/build/nft-tools.mdx rename to pages/app-developers/tools/build/nft-tools.mdx diff --git a/pages/builders/tools/build/oracles.mdx b/pages/app-developers/tools/build/oracles.mdx similarity index 100% rename from pages/builders/tools/build/oracles.mdx rename to pages/app-developers/tools/build/oracles.mdx diff --git a/pages/builders/tools/connect.mdx b/pages/app-developers/tools/connect.mdx similarity index 100% rename from pages/builders/tools/connect.mdx rename to pages/app-developers/tools/connect.mdx diff --git a/pages/builders/tools/connect/_meta.json b/pages/app-developers/tools/connect/_meta.json similarity index 100% rename from pages/builders/tools/connect/_meta.json rename to pages/app-developers/tools/connect/_meta.json diff --git a/pages/builders/tools/connect/networks.mdx b/pages/app-developers/tools/connect/networks.mdx similarity index 100% rename from pages/builders/tools/connect/networks.mdx rename to pages/app-developers/tools/connect/networks.mdx diff --git a/pages/builders/tools/connect/rpc-providers.mdx b/pages/app-developers/tools/connect/rpc-providers.mdx similarity index 100% rename from pages/builders/tools/connect/rpc-providers.mdx rename to pages/app-developers/tools/connect/rpc-providers.mdx diff --git a/pages/builders/app-developers/tools/ecosystem-overview.mdx b/pages/app-developers/tools/ecosystem-overview.mdx similarity index 100% rename from pages/builders/app-developers/tools/ecosystem-overview.mdx rename to pages/app-developers/tools/ecosystem-overview.mdx diff --git a/pages/builders/tools/monitor.mdx b/pages/app-developers/tools/monitor.mdx similarity index 100% rename from pages/builders/tools/monitor.mdx rename to pages/app-developers/tools/monitor.mdx diff --git a/pages/builders/tools/monitor/_meta.json b/pages/app-developers/tools/monitor/_meta.json similarity index 100% rename from pages/builders/tools/monitor/_meta.json rename to pages/app-developers/tools/monitor/_meta.json diff --git a/pages/builders/tools/monitor/analytics-tools.mdx b/pages/app-developers/tools/monitor/analytics-tools.mdx similarity index 100% rename from pages/builders/tools/monitor/analytics-tools.mdx rename to pages/app-developers/tools/monitor/analytics-tools.mdx diff --git a/pages/builders/tools/monitor/regenesis-history.mdx b/pages/app-developers/tools/monitor/regenesis-history.mdx similarity index 100% rename from pages/builders/tools/monitor/regenesis-history.mdx rename to pages/app-developers/tools/monitor/regenesis-history.mdx diff --git a/pages/builders/tools/op-tools.mdx b/pages/app-developers/tools/op-tools.mdx similarity index 100% rename from pages/builders/tools/op-tools.mdx rename to pages/app-developers/tools/op-tools.mdx diff --git a/pages/builders/tools/op-tools/_meta.json b/pages/app-developers/tools/op-tools/_meta.json similarity index 100% rename from pages/builders/tools/op-tools/_meta.json rename to pages/app-developers/tools/op-tools/_meta.json diff --git a/pages/builders/tools/overview.mdx b/pages/app-developers/tools/overview.mdx similarity index 100% rename from pages/builders/tools/overview.mdx rename to pages/app-developers/tools/overview.mdx diff --git a/pages/builders/app-developers/tools/supersim.mdx b/pages/app-developers/tools/supersim.mdx similarity index 100% rename from pages/builders/app-developers/tools/supersim.mdx rename to pages/app-developers/tools/supersim.mdx diff --git a/pages/builders/app-developers/transactions.mdx b/pages/app-developers/transactions.mdx similarity index 68% rename from pages/builders/app-developers/transactions.mdx rename to pages/app-developers/transactions.mdx index e845de2d1..d2bb9fdf5 100644 --- a/pages/builders/app-developers/transactions.mdx +++ b/pages/app-developers/transactions.mdx @@ -22,4 +22,10 @@ This section provides information on transactions in OP Mainnet, including fee e + + + + + + diff --git a/pages/builders/app-developers/transactions/_meta.json b/pages/app-developers/transactions/_meta.json similarity index 100% rename from pages/builders/app-developers/transactions/_meta.json rename to pages/app-developers/transactions/_meta.json diff --git a/pages/builders/app-developers/transactions/estimates.mdx b/pages/app-developers/transactions/estimates.mdx similarity index 100% rename from pages/builders/app-developers/transactions/estimates.mdx rename to pages/app-developers/transactions/estimates.mdx diff --git a/pages/builders/app-developers/transactions/fees.mdx b/pages/app-developers/transactions/fees.mdx similarity index 100% rename from pages/builders/app-developers/transactions/fees.mdx rename to pages/app-developers/transactions/fees.mdx diff --git a/pages/builders/app-developers/transactions/parameters.mdx b/pages/app-developers/transactions/parameters.mdx similarity index 100% rename from pages/builders/app-developers/transactions/parameters.mdx rename to pages/app-developers/transactions/parameters.mdx diff --git a/pages/builders/app-developers/transactions/statuses.mdx b/pages/app-developers/transactions/statuses.mdx similarity index 100% rename from pages/builders/app-developers/transactions/statuses.mdx rename to pages/app-developers/transactions/statuses.mdx diff --git a/pages/builders/app-developers/transactions/troubleshooting.mdx b/pages/app-developers/transactions/troubleshooting.mdx similarity index 100% rename from pages/builders/app-developers/transactions/troubleshooting.mdx rename to pages/app-developers/transactions/troubleshooting.mdx diff --git a/pages/builders/app-developers/tutorials.mdx b/pages/app-developers/tutorials.mdx similarity index 65% rename from pages/builders/app-developers/tutorials.mdx rename to pages/app-developers/tutorials.mdx index 34a2f40e4..e2f51eb26 100644 --- a/pages/builders/app-developers/tutorials.mdx +++ b/pages/app-developers/tutorials.mdx @@ -28,4 +28,14 @@ This section provides information on bridging erc 20 tokens to op mainnet with v + + + + + + + + + + diff --git a/pages/builders/app-developers/tutorials/_meta.json b/pages/app-developers/tutorials/_meta.json similarity index 100% rename from pages/builders/app-developers/tutorials/_meta.json rename to pages/app-developers/tutorials/_meta.json diff --git a/pages/builders/app-developers/tutorials/cross-dom-bridge-erc20.mdx b/pages/app-developers/tutorials/cross-dom-bridge-erc20.mdx similarity index 100% rename from pages/builders/app-developers/tutorials/cross-dom-bridge-erc20.mdx rename to pages/app-developers/tutorials/cross-dom-bridge-erc20.mdx diff --git a/pages/builders/app-developers/tutorials/cross-dom-bridge-eth.mdx b/pages/app-developers/tutorials/cross-dom-bridge-eth.mdx similarity index 100% rename from pages/builders/app-developers/tutorials/cross-dom-bridge-eth.mdx rename to pages/app-developers/tutorials/cross-dom-bridge-eth.mdx diff --git a/pages/builders/app-developers/tutorials/cross-dom-solidity.mdx b/pages/app-developers/tutorials/cross-dom-solidity.mdx similarity index 100% rename from pages/builders/app-developers/tutorials/cross-dom-solidity.mdx rename to pages/app-developers/tutorials/cross-dom-solidity.mdx diff --git a/pages/builders/app-developers/tutorials/sdk-estimate-costs.mdx b/pages/app-developers/tutorials/sdk-estimate-costs.mdx similarity index 100% rename from pages/builders/app-developers/tutorials/sdk-estimate-costs.mdx rename to pages/app-developers/tutorials/sdk-estimate-costs.mdx diff --git a/pages/builders/app-developers/tutorials/sdk-trace-txns.mdx b/pages/app-developers/tutorials/sdk-trace-txns.mdx similarity index 100% rename from pages/builders/app-developers/tutorials/sdk-trace-txns.mdx rename to pages/app-developers/tutorials/sdk-trace-txns.mdx diff --git a/pages/builders/app-developers/tutorials/sdk-view-txns.mdx b/pages/app-developers/tutorials/sdk-view-txns.mdx similarity index 100% rename from pages/builders/app-developers/tutorials/sdk-view-txns.mdx rename to pages/app-developers/tutorials/sdk-view-txns.mdx diff --git a/pages/builders/app-developers/tutorials/send-tx-from-eth.mdx b/pages/app-developers/tutorials/send-tx-from-eth.mdx similarity index 100% rename from pages/builders/app-developers/tutorials/send-tx-from-eth.mdx rename to pages/app-developers/tutorials/send-tx-from-eth.mdx diff --git a/pages/builders/app-developers/tutorials/standard-bridge-custom-token.mdx b/pages/app-developers/tutorials/standard-bridge-custom-token.mdx similarity index 100% rename from pages/builders/app-developers/tutorials/standard-bridge-custom-token.mdx rename to pages/app-developers/tutorials/standard-bridge-custom-token.mdx diff --git a/pages/builders/app-developers/tutorials/standard-bridge-standard-token.mdx b/pages/app-developers/tutorials/standard-bridge-standard-token.mdx similarity index 100% rename from pages/builders/app-developers/tutorials/standard-bridge-standard-token.mdx rename to pages/app-developers/tutorials/standard-bridge-standard-token.mdx diff --git a/pages/builders.mdx b/pages/builders.mdx deleted file mode 100644 index 98f4178cf..000000000 --- a/pages/builders.mdx +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Builders -lang: en-US -description: Learn about deploying contracts, cross-chain messaging, and tutorials to help you build applications on OP Mainnet. ---- - -import { Card, Cards } from 'nextra/components' - -# Builders - -Welcome to the Builders section. Here you'll find resources and guides for developers, operators, and other stakeholders involved in building on OP Stack. Explore the categories below to find the information you need. - - - - - - - - - diff --git a/pages/builders/_meta.json b/pages/builders/_meta.json deleted file mode 100644 index 17ea9b121..000000000 --- a/pages/builders/_meta.json +++ /dev/null @@ -1,7 +0,0 @@ -{ - "notices": "Notices (README)", - "app-developers": "App developers", - "chain-operators": "Chain operators", - "node-operators": "Node operators", - "tools": "Developer tools" -} diff --git a/pages/builders/app-developers.mdx b/pages/builders/app-developers.mdx deleted file mode 100644 index ea242737a..000000000 --- a/pages/builders/app-developers.mdx +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: App Developers -description: If you're a developer looking to build on OP Stack, you've come to the right place. In this area of the Optimism Docs you'll find everything you ... -lang: en-US ---- - -import { Card, Cards } from 'nextra/components' - -# App Developers - -If you're a developer looking to build on OP Mainnet, you've come to the right place. In this area of the Optimism Docs you'll find everything you ... - - - - - - - - - - - - - - diff --git a/pages/builders/app-developers/tools/_meta.json b/pages/builders/app-developers/tools/_meta.json deleted file mode 100644 index f751e54e9..000000000 --- a/pages/builders/app-developers/tools/_meta.json +++ /dev/null @@ -1,9 +0,0 @@ -{ - "ecosystem-overview": "Open source code repo", - "supersim": "Supersim Multichain Development Environment", - "console": { - "title": "Superchain Dev Console", - "href": "https://console.optimism.io/?utm_source=docs", - "newWindow": true - } -} diff --git a/pages/builders/chain-operators.mdx b/pages/builders/chain-operators.mdx deleted file mode 100644 index 73c0e4bb9..000000000 --- a/pages/builders/chain-operators.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Chain Operators -description: Documentation covering Architecture, Configuration, Deploy, Features, Hacks, Management, Self Hosted, Tools, Tutorials in the Chain Operators section of the OP Stack ecosystem. -lang: en-US ---- - -import { Card, Cards } from 'nextra/components' - -# Chain Operators - -Documentation covering Architecture, Configuration, Deploy, Features, Hacks, Management, Self Hosted, Tools, Tutorials in the Chain Operators section of the OP Stack ecosystem. - - - - - - - - - - - - - - - - - - - - diff --git a/pages/builders/node-operators.mdx b/pages/builders/node-operators.mdx deleted file mode 100644 index 537743b2f..000000000 --- a/pages/builders/node-operators.mdx +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Node Operators -description: Documentation covering Architecture, Configuration, Json Rpc, Management, Network Upgrades, Releases, Rollup Node, Tutorials in the Node Operators section of the OP Stack ecosystem. -lang: en-US ---- - -import { Card, Cards } from 'nextra/components' - -# Node Operators - -Documentation covering Architecture, Configuration, Json Rpc, Management, Network Upgrades, Releases, Rollup Node, Tutorials in the Node Operators section of the OP Stack ecosystem. - - - - - - - - - - - - - - - - - - diff --git a/pages/builders/notices.mdx b/pages/builders/notices.mdx deleted file mode 100644 index 746de9e0f..000000000 --- a/pages/builders/notices.mdx +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Notices -description: Documentation covering Sdk Deprecation in the Notices section of the OP Stack ecosystem. -lang: en-US ---- - -import { Card, Cards } from 'nextra/components' - -# Notices - -Documentation covering Sdk Deprecation in the Notices section of the OP Stack ecosystem. - - - - - - - - diff --git a/pages/builders/tools.mdx b/pages/builders/tools.mdx deleted file mode 100644 index 354ca94dd..000000000 --- a/pages/builders/tools.mdx +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Tools -description: Welcome to the Optimism developer tools! -lang: en-US ---- - -import { Card, Cards } from 'nextra/components' - -# Tools - -Welcome to the Optimism developer tools! - - - - - - - - - - - - - - diff --git a/pages/index.mdx b/pages/index.mdx index 103e7d984..eeaa2d14b 100644 --- a/pages/index.mdx +++ b/pages/index.mdx @@ -41,7 +41,7 @@ Check out these amazing tools, so you can get building with Optimism. } /> - } /> + } /> diff --git a/pages/builders/notices/_meta.json b/pages/notices/_meta.json similarity index 100% rename from pages/builders/notices/_meta.json rename to pages/notices/_meta.json diff --git a/pages/builders/notices/holocene-changes.mdx b/pages/notices/holocene-changes.mdx similarity index 100% rename from pages/builders/notices/holocene-changes.mdx rename to pages/notices/holocene-changes.mdx diff --git a/pages/builders/notices/pectra-changes.mdx b/pages/notices/pectra-changes.mdx similarity index 100% rename from pages/builders/notices/pectra-changes.mdx rename to pages/notices/pectra-changes.mdx diff --git a/pages/builders/notices/sdk-deprecation.mdx b/pages/notices/sdk-deprecation.mdx similarity index 100% rename from pages/builders/notices/sdk-deprecation.mdx rename to pages/notices/sdk-deprecation.mdx diff --git a/pages/operators/_meta.json b/pages/operators/_meta.json new file mode 100644 index 000000000..113ad9d1c --- /dev/null +++ b/pages/operators/_meta.json @@ -0,0 +1,22 @@ +{ + "--- CHAINS": { + "title": "CHAIN OPERATORS", + "type": "separator" + }, + "chain-operators": { + "title": "Chains", + "display": "children" + }, + "+++ NODES": { + "title": "", + "type": "separator" + }, + "--- NODES": { + "title": "NODE OPERATORS", + "type": "separator" + }, + "node-operators": { + "title": "Nodes", + "display": "children" + } + } \ No newline at end of file diff --git a/pages/operators/chain-operators.mdx b/pages/operators/chain-operators.mdx new file mode 100644 index 000000000..497ec5248 --- /dev/null +++ b/pages/operators/chain-operators.mdx @@ -0,0 +1,23 @@ +--- +title: Chain Operators +description: Documentation covering Architecture, Configuration, Deploy, Features, Hacks, Management, Self Hosted, Tools, Tutorials in the Chain Operators section of the OP Stack ecosystem. +lang: en-US +--- + +import { Card, Cards } from 'nextra/components' + +# Chain Operators + +Documentation covering Architecture, Configuration, Deploy, Features, Hacks, Management, Self Hosted, Tools, Tutorials in the Chain Operators section of the OP Stack ecosystem. + + + + + + + + + + + + \ No newline at end of file diff --git a/pages/builders/chain-operators/_meta.json b/pages/operators/chain-operators/_meta.json similarity index 100% rename from pages/builders/chain-operators/_meta.json rename to pages/operators/chain-operators/_meta.json diff --git a/pages/builders/chain-operators/architecture.mdx b/pages/operators/chain-operators/architecture.mdx similarity index 100% rename from pages/builders/chain-operators/architecture.mdx rename to pages/operators/chain-operators/architecture.mdx diff --git a/pages/builders/chain-operators/configuration.mdx b/pages/operators/chain-operators/configuration.mdx similarity index 100% rename from pages/builders/chain-operators/configuration.mdx rename to pages/operators/chain-operators/configuration.mdx diff --git a/pages/builders/chain-operators/configuration/_meta.json b/pages/operators/chain-operators/configuration/_meta.json similarity index 100% rename from pages/builders/chain-operators/configuration/_meta.json rename to pages/operators/chain-operators/configuration/_meta.json diff --git a/pages/builders/chain-operators/configuration/batcher.mdx b/pages/operators/chain-operators/configuration/batcher.mdx similarity index 100% rename from pages/builders/chain-operators/configuration/batcher.mdx rename to pages/operators/chain-operators/configuration/batcher.mdx diff --git a/pages/builders/chain-operators/configuration/overview.mdx b/pages/operators/chain-operators/configuration/overview.mdx similarity index 100% rename from pages/builders/chain-operators/configuration/overview.mdx rename to pages/operators/chain-operators/configuration/overview.mdx diff --git a/pages/builders/chain-operators/configuration/proposer.mdx b/pages/operators/chain-operators/configuration/proposer.mdx similarity index 100% rename from pages/builders/chain-operators/configuration/proposer.mdx rename to pages/operators/chain-operators/configuration/proposer.mdx diff --git a/pages/builders/chain-operators/configuration/rollup.mdx b/pages/operators/chain-operators/configuration/rollup.mdx similarity index 100% rename from pages/builders/chain-operators/configuration/rollup.mdx rename to pages/operators/chain-operators/configuration/rollup.mdx diff --git a/pages/builders/chain-operators/deploy.mdx b/pages/operators/chain-operators/deploy.mdx similarity index 100% rename from pages/builders/chain-operators/deploy.mdx rename to pages/operators/chain-operators/deploy.mdx diff --git a/pages/builders/chain-operators/deploy/_meta.json b/pages/operators/chain-operators/deploy/_meta.json similarity index 100% rename from pages/builders/chain-operators/deploy/_meta.json rename to pages/operators/chain-operators/deploy/_meta.json diff --git a/pages/builders/chain-operators/deploy/genesis.mdx b/pages/operators/chain-operators/deploy/genesis.mdx similarity index 100% rename from pages/builders/chain-operators/deploy/genesis.mdx rename to pages/operators/chain-operators/deploy/genesis.mdx diff --git a/pages/builders/chain-operators/deploy/overview.mdx b/pages/operators/chain-operators/deploy/overview.mdx similarity index 100% rename from pages/builders/chain-operators/deploy/overview.mdx rename to pages/operators/chain-operators/deploy/overview.mdx diff --git a/pages/builders/chain-operators/deploy/smart-contracts.mdx b/pages/operators/chain-operators/deploy/smart-contracts.mdx similarity index 100% rename from pages/builders/chain-operators/deploy/smart-contracts.mdx rename to pages/operators/chain-operators/deploy/smart-contracts.mdx diff --git a/pages/builders/chain-operators/features.mdx b/pages/operators/chain-operators/features.mdx similarity index 100% rename from pages/builders/chain-operators/features.mdx rename to pages/operators/chain-operators/features.mdx diff --git a/pages/builders/chain-operators/features/_meta.json b/pages/operators/chain-operators/features/_meta.json similarity index 100% rename from pages/builders/chain-operators/features/_meta.json rename to pages/operators/chain-operators/features/_meta.json diff --git a/pages/builders/chain-operators/features/alt-da-mode.mdx b/pages/operators/chain-operators/features/alt-da-mode.mdx similarity index 100% rename from pages/builders/chain-operators/features/alt-da-mode.mdx rename to pages/operators/chain-operators/features/alt-da-mode.mdx diff --git a/pages/builders/chain-operators/features/bridged-usdc-standard.mdx b/pages/operators/chain-operators/features/bridged-usdc-standard.mdx similarity index 100% rename from pages/builders/chain-operators/features/bridged-usdc-standard.mdx rename to pages/operators/chain-operators/features/bridged-usdc-standard.mdx diff --git a/pages/builders/chain-operators/features/custom-gas-token.mdx b/pages/operators/chain-operators/features/custom-gas-token.mdx similarity index 100% rename from pages/builders/chain-operators/features/custom-gas-token.mdx rename to pages/operators/chain-operators/features/custom-gas-token.mdx diff --git a/pages/builders/chain-operators/features/preinstalls.mdx b/pages/operators/chain-operators/features/preinstalls.mdx similarity index 100% rename from pages/builders/chain-operators/features/preinstalls.mdx rename to pages/operators/chain-operators/features/preinstalls.mdx diff --git a/pages/builders/chain-operators/features/span-batches.mdx b/pages/operators/chain-operators/features/span-batches.mdx similarity index 100% rename from pages/builders/chain-operators/features/span-batches.mdx rename to pages/operators/chain-operators/features/span-batches.mdx diff --git a/pages/builders/chain-operators/hacks.mdx b/pages/operators/chain-operators/hacks.mdx similarity index 100% rename from pages/builders/chain-operators/hacks.mdx rename to pages/operators/chain-operators/hacks.mdx diff --git a/pages/builders/chain-operators/hacks/_meta.json b/pages/operators/chain-operators/hacks/_meta.json similarity index 100% rename from pages/builders/chain-operators/hacks/_meta.json rename to pages/operators/chain-operators/hacks/_meta.json diff --git a/pages/builders/chain-operators/hacks/data-availability.mdx b/pages/operators/chain-operators/hacks/data-availability.mdx similarity index 100% rename from pages/builders/chain-operators/hacks/data-availability.mdx rename to pages/operators/chain-operators/hacks/data-availability.mdx diff --git a/pages/builders/chain-operators/hacks/derivation.mdx b/pages/operators/chain-operators/hacks/derivation.mdx similarity index 100% rename from pages/builders/chain-operators/hacks/derivation.mdx rename to pages/operators/chain-operators/hacks/derivation.mdx diff --git a/pages/builders/chain-operators/hacks/execution.mdx b/pages/operators/chain-operators/hacks/execution.mdx similarity index 100% rename from pages/builders/chain-operators/hacks/execution.mdx rename to pages/operators/chain-operators/hacks/execution.mdx diff --git a/pages/builders/chain-operators/hacks/featured-hacks.mdx b/pages/operators/chain-operators/hacks/featured-hacks.mdx similarity index 100% rename from pages/builders/chain-operators/hacks/featured-hacks.mdx rename to pages/operators/chain-operators/hacks/featured-hacks.mdx diff --git a/pages/builders/chain-operators/hacks/overview.mdx b/pages/operators/chain-operators/hacks/overview.mdx similarity index 100% rename from pages/builders/chain-operators/hacks/overview.mdx rename to pages/operators/chain-operators/hacks/overview.mdx diff --git a/pages/builders/chain-operators/hacks/settlement.mdx b/pages/operators/chain-operators/hacks/settlement.mdx similarity index 100% rename from pages/builders/chain-operators/hacks/settlement.mdx rename to pages/operators/chain-operators/hacks/settlement.mdx diff --git a/pages/builders/chain-operators/management.mdx b/pages/operators/chain-operators/management.mdx similarity index 100% rename from pages/builders/chain-operators/management.mdx rename to pages/operators/chain-operators/management.mdx diff --git a/pages/builders/chain-operators/management/_meta.json b/pages/operators/chain-operators/management/_meta.json similarity index 100% rename from pages/builders/chain-operators/management/_meta.json rename to pages/operators/chain-operators/management/_meta.json diff --git a/pages/builders/chain-operators/management/best-practices.mdx b/pages/operators/chain-operators/management/best-practices.mdx similarity index 100% rename from pages/builders/chain-operators/management/best-practices.mdx rename to pages/operators/chain-operators/management/best-practices.mdx diff --git a/pages/builders/chain-operators/management/blobs.mdx b/pages/operators/chain-operators/management/blobs.mdx similarity index 100% rename from pages/builders/chain-operators/management/blobs.mdx rename to pages/operators/chain-operators/management/blobs.mdx diff --git a/pages/builders/chain-operators/management/key-management.mdx b/pages/operators/chain-operators/management/key-management.mdx similarity index 100% rename from pages/builders/chain-operators/management/key-management.mdx rename to pages/operators/chain-operators/management/key-management.mdx diff --git a/pages/builders/chain-operators/management/operations.mdx b/pages/operators/chain-operators/management/operations.mdx similarity index 100% rename from pages/builders/chain-operators/management/operations.mdx rename to pages/operators/chain-operators/management/operations.mdx diff --git a/pages/builders/chain-operators/management/snap-sync.mdx b/pages/operators/chain-operators/management/snap-sync.mdx similarity index 100% rename from pages/builders/chain-operators/management/snap-sync.mdx rename to pages/operators/chain-operators/management/snap-sync.mdx diff --git a/pages/builders/chain-operators/management/troubleshooting.mdx b/pages/operators/chain-operators/management/troubleshooting.mdx similarity index 100% rename from pages/builders/chain-operators/management/troubleshooting.mdx rename to pages/operators/chain-operators/management/troubleshooting.mdx diff --git a/pages/builders/chain-operators/self-hosted.mdx b/pages/operators/chain-operators/self-hosted.mdx similarity index 100% rename from pages/builders/chain-operators/self-hosted.mdx rename to pages/operators/chain-operators/self-hosted.mdx diff --git a/pages/builders/chain-operators/tools.mdx b/pages/operators/chain-operators/tools.mdx similarity index 100% rename from pages/builders/chain-operators/tools.mdx rename to pages/operators/chain-operators/tools.mdx diff --git a/pages/builders/chain-operators/tools/_meta.json b/pages/operators/chain-operators/tools/_meta.json similarity index 78% rename from pages/builders/chain-operators/tools/_meta.json rename to pages/operators/chain-operators/tools/_meta.json index 990ea87a2..40fdb8480 100644 --- a/pages/builders/chain-operators/tools/_meta.json +++ b/pages/operators/chain-operators/tools/_meta.json @@ -5,5 +5,6 @@ "op-conductor": "op-conductor", "op-deployer": "op-deployer", "op-txproxy": "op-txproxy", - "proxyd": "proxyd" + "proxyd": "proxyd", + "fee-calculator": "Fee calculator" } diff --git a/pages/builders/chain-operators/tools/chain-monitoring.mdx b/pages/operators/chain-operators/tools/chain-monitoring.mdx similarity index 100% rename from pages/builders/chain-operators/tools/chain-monitoring.mdx rename to pages/operators/chain-operators/tools/chain-monitoring.mdx diff --git a/pages/builders/chain-operators/tools/explorer.mdx b/pages/operators/chain-operators/tools/explorer.mdx similarity index 100% rename from pages/builders/chain-operators/tools/explorer.mdx rename to pages/operators/chain-operators/tools/explorer.mdx diff --git a/pages/builders/tools/fee-calculator.mdx b/pages/operators/chain-operators/tools/fee-calculator.mdx similarity index 100% rename from pages/builders/tools/fee-calculator.mdx rename to pages/operators/chain-operators/tools/fee-calculator.mdx diff --git a/pages/builders/chain-operators/tools/op-challenger.mdx b/pages/operators/chain-operators/tools/op-challenger.mdx similarity index 100% rename from pages/builders/chain-operators/tools/op-challenger.mdx rename to pages/operators/chain-operators/tools/op-challenger.mdx diff --git a/pages/builders/chain-operators/tools/op-conductor.mdx b/pages/operators/chain-operators/tools/op-conductor.mdx similarity index 100% rename from pages/builders/chain-operators/tools/op-conductor.mdx rename to pages/operators/chain-operators/tools/op-conductor.mdx diff --git a/pages/builders/chain-operators/tools/op-deployer.mdx b/pages/operators/chain-operators/tools/op-deployer.mdx similarity index 100% rename from pages/builders/chain-operators/tools/op-deployer.mdx rename to pages/operators/chain-operators/tools/op-deployer.mdx diff --git a/pages/builders/chain-operators/tools/op-txproxy.mdx b/pages/operators/chain-operators/tools/op-txproxy.mdx similarity index 100% rename from pages/builders/chain-operators/tools/op-txproxy.mdx rename to pages/operators/chain-operators/tools/op-txproxy.mdx diff --git a/pages/builders/chain-operators/tools/proxyd.mdx b/pages/operators/chain-operators/tools/proxyd.mdx similarity index 100% rename from pages/builders/chain-operators/tools/proxyd.mdx rename to pages/operators/chain-operators/tools/proxyd.mdx diff --git a/pages/builders/chain-operators/tutorials.mdx b/pages/operators/chain-operators/tutorials.mdx similarity index 100% rename from pages/builders/chain-operators/tutorials.mdx rename to pages/operators/chain-operators/tutorials.mdx diff --git a/pages/builders/chain-operators/tutorials/_meta.json b/pages/operators/chain-operators/tutorials/_meta.json similarity index 100% rename from pages/builders/chain-operators/tutorials/_meta.json rename to pages/operators/chain-operators/tutorials/_meta.json diff --git a/pages/builders/chain-operators/tutorials/adding-derivation-attributes.mdx b/pages/operators/chain-operators/tutorials/adding-derivation-attributes.mdx similarity index 100% rename from pages/builders/chain-operators/tutorials/adding-derivation-attributes.mdx rename to pages/operators/chain-operators/tutorials/adding-derivation-attributes.mdx diff --git a/pages/builders/chain-operators/tutorials/adding-precompiles.mdx b/pages/operators/chain-operators/tutorials/adding-precompiles.mdx similarity index 100% rename from pages/builders/chain-operators/tutorials/adding-precompiles.mdx rename to pages/operators/chain-operators/tutorials/adding-precompiles.mdx diff --git a/pages/builders/chain-operators/tutorials/create-l2-rollup.mdx b/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx similarity index 100% rename from pages/builders/chain-operators/tutorials/create-l2-rollup.mdx rename to pages/operators/chain-operators/tutorials/create-l2-rollup.mdx diff --git a/pages/builders/chain-operators/tutorials/integrating-da-layer.mdx b/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx similarity index 100% rename from pages/builders/chain-operators/tutorials/integrating-da-layer.mdx rename to pages/operators/chain-operators/tutorials/integrating-da-layer.mdx diff --git a/pages/builders/chain-operators/tutorials/modifying-predeploys.mdx b/pages/operators/chain-operators/tutorials/modifying-predeploys.mdx similarity index 100% rename from pages/builders/chain-operators/tutorials/modifying-predeploys.mdx rename to pages/operators/chain-operators/tutorials/modifying-predeploys.mdx diff --git a/pages/operators/node-operators.mdx b/pages/operators/node-operators.mdx new file mode 100644 index 000000000..a43522b41 --- /dev/null +++ b/pages/operators/node-operators.mdx @@ -0,0 +1,22 @@ +--- +title: Node Operators +description: Documentation covering Architecture, Configuration, Json Rpc, Management, Network Upgrades, Releases, Rollup Node, Tutorials in the Node Operators section of the OP Stack ecosystem. +lang: en-US +--- + +import { Card, Cards } from 'nextra/components' + +# Node Operators + +Documentation covering Architecture, Configuration, Json Rpc, Management, Network Upgrades, Releases, Rollup Node, Tutorials in the Node Operators section of the OP Stack ecosystem. + + + + + + + + + + + \ No newline at end of file diff --git a/pages/builders/node-operators/_meta.json b/pages/operators/node-operators/_meta.json similarity index 100% rename from pages/builders/node-operators/_meta.json rename to pages/operators/node-operators/_meta.json diff --git a/pages/builders/node-operators/architecture.mdx b/pages/operators/node-operators/architecture.mdx similarity index 100% rename from pages/builders/node-operators/architecture.mdx rename to pages/operators/node-operators/architecture.mdx diff --git a/pages/builders/node-operators/configuration.mdx b/pages/operators/node-operators/configuration.mdx similarity index 100% rename from pages/builders/node-operators/configuration.mdx rename to pages/operators/node-operators/configuration.mdx diff --git a/pages/builders/node-operators/configuration/_meta.json b/pages/operators/node-operators/configuration/_meta.json similarity index 100% rename from pages/builders/node-operators/configuration/_meta.json rename to pages/operators/node-operators/configuration/_meta.json diff --git a/pages/builders/node-operators/configuration/base-config.mdx b/pages/operators/node-operators/configuration/base-config.mdx similarity index 100% rename from pages/builders/node-operators/configuration/base-config.mdx rename to pages/operators/node-operators/configuration/base-config.mdx diff --git a/pages/builders/node-operators/configuration/consensus-config.mdx b/pages/operators/node-operators/configuration/consensus-config.mdx similarity index 100% rename from pages/builders/node-operators/configuration/consensus-config.mdx rename to pages/operators/node-operators/configuration/consensus-config.mdx diff --git a/pages/builders/node-operators/configuration/execution-config.mdx b/pages/operators/node-operators/configuration/execution-config.mdx similarity index 100% rename from pages/builders/node-operators/configuration/execution-config.mdx rename to pages/operators/node-operators/configuration/execution-config.mdx diff --git a/pages/builders/node-operators/json-rpc.mdx b/pages/operators/node-operators/json-rpc.mdx similarity index 100% rename from pages/builders/node-operators/json-rpc.mdx rename to pages/operators/node-operators/json-rpc.mdx diff --git a/pages/builders/node-operators/management.mdx b/pages/operators/node-operators/management.mdx similarity index 100% rename from pages/builders/node-operators/management.mdx rename to pages/operators/node-operators/management.mdx diff --git a/pages/builders/node-operators/management/_meta.json b/pages/operators/node-operators/management/_meta.json similarity index 100% rename from pages/builders/node-operators/management/_meta.json rename to pages/operators/node-operators/management/_meta.json diff --git a/pages/builders/node-operators/management/blobs.mdx b/pages/operators/node-operators/management/blobs.mdx similarity index 100% rename from pages/builders/node-operators/management/blobs.mdx rename to pages/operators/node-operators/management/blobs.mdx diff --git a/pages/builders/node-operators/management/metrics.mdx b/pages/operators/node-operators/management/metrics.mdx similarity index 100% rename from pages/builders/node-operators/management/metrics.mdx rename to pages/operators/node-operators/management/metrics.mdx diff --git a/pages/builders/node-operators/management/snap-sync.mdx b/pages/operators/node-operators/management/snap-sync.mdx similarity index 100% rename from pages/builders/node-operators/management/snap-sync.mdx rename to pages/operators/node-operators/management/snap-sync.mdx diff --git a/pages/builders/node-operators/management/snapshots.mdx b/pages/operators/node-operators/management/snapshots.mdx similarity index 100% rename from pages/builders/node-operators/management/snapshots.mdx rename to pages/operators/node-operators/management/snapshots.mdx diff --git a/pages/builders/node-operators/management/troubleshooting.mdx b/pages/operators/node-operators/management/troubleshooting.mdx similarity index 100% rename from pages/builders/node-operators/management/troubleshooting.mdx rename to pages/operators/node-operators/management/troubleshooting.mdx diff --git a/pages/builders/node-operators/network-upgrades.mdx b/pages/operators/node-operators/network-upgrades.mdx similarity index 100% rename from pages/builders/node-operators/network-upgrades.mdx rename to pages/operators/node-operators/network-upgrades.mdx diff --git a/pages/builders/node-operators/releases.mdx b/pages/operators/node-operators/releases.mdx similarity index 100% rename from pages/builders/node-operators/releases.mdx rename to pages/operators/node-operators/releases.mdx diff --git a/pages/builders/node-operators/rollup-node.mdx b/pages/operators/node-operators/rollup-node.mdx similarity index 100% rename from pages/builders/node-operators/rollup-node.mdx rename to pages/operators/node-operators/rollup-node.mdx diff --git a/pages/builders/node-operators/tutorials.mdx b/pages/operators/node-operators/tutorials.mdx similarity index 100% rename from pages/builders/node-operators/tutorials.mdx rename to pages/operators/node-operators/tutorials.mdx diff --git a/pages/builders/node-operators/tutorials/_meta.json b/pages/operators/node-operators/tutorials/_meta.json similarity index 100% rename from pages/builders/node-operators/tutorials/_meta.json rename to pages/operators/node-operators/tutorials/_meta.json diff --git a/pages/builders/node-operators/tutorials/mainnet.mdx b/pages/operators/node-operators/tutorials/mainnet.mdx similarity index 100% rename from pages/builders/node-operators/tutorials/mainnet.mdx rename to pages/operators/node-operators/tutorials/mainnet.mdx diff --git a/pages/builders/node-operators/tutorials/node-from-docker.mdx b/pages/operators/node-operators/tutorials/node-from-docker.mdx similarity index 100% rename from pages/builders/node-operators/tutorials/node-from-docker.mdx rename to pages/operators/node-operators/tutorials/node-from-docker.mdx diff --git a/pages/builders/node-operators/tutorials/node-from-source.mdx b/pages/operators/node-operators/tutorials/node-from-source.mdx similarity index 100% rename from pages/builders/node-operators/tutorials/node-from-source.mdx rename to pages/operators/node-operators/tutorials/node-from-source.mdx diff --git a/pages/builders/node-operators/tutorials/testnet.mdx b/pages/operators/node-operators/tutorials/testnet.mdx similarity index 100% rename from pages/builders/node-operators/tutorials/testnet.mdx rename to pages/operators/node-operators/tutorials/testnet.mdx diff --git a/pages/stack/_meta.json b/pages/stack/_meta.json index 83c33a773..24d7967c8 100644 --- a/pages/stack/_meta.json +++ b/pages/stack/_meta.json @@ -1,5 +1,9 @@ { - "getting-started": "Getting started: OP Stack", + "--- OP STACK": { + "title": "OP STACK", + "type": "separator" + }, + "getting-started": "Getting Started with OP Stack", "fact-sheet": "Fact sheet", "differences": "Differences between Ethereum and OP Stack chains", "design-principles": "Design philosophy & principles", @@ -11,6 +15,10 @@ "transactions": "Transactions", "features": "Features", "security": "Security", + "chain": { + "title": "OP Mainnet", + "display": "hidden" + }, "--- EXPERIMENTAL": { "title": "EXPERIMENTAL", "type": "separator" diff --git a/pages/stack/chain.mdx b/pages/stack/chain.mdx new file mode 100644 index 000000000..5f83f808c --- /dev/null +++ b/pages/stack/chain.mdx @@ -0,0 +1,20 @@ +--- +title: Chain +description: Documentation covering Addresses, Getting Started, Networks, Security, Testing, Tokenlist in the Chain section of the OP Stack ecosystem. +lang: en-US +--- + +import { Card, Cards } from 'nextra/components' + +# Chain + +Documentation covering Addresses, Getting Started, Networks, Security, Testing, Tokenlist in the Chain section of the OP Stack ecosystem. + + + + + + + + + \ No newline at end of file diff --git a/pages/chain/_meta.json b/pages/stack/chain/_meta.json similarity index 100% rename from pages/chain/_meta.json rename to pages/stack/chain/_meta.json diff --git a/pages/chain/addresses.mdx b/pages/stack/chain/addresses.mdx similarity index 100% rename from pages/chain/addresses.mdx rename to pages/stack/chain/addresses.mdx diff --git a/pages/chain/getting-started.mdx b/pages/stack/chain/getting-started.mdx similarity index 100% rename from pages/chain/getting-started.mdx rename to pages/stack/chain/getting-started.mdx diff --git a/pages/chain/networks.mdx b/pages/stack/chain/networks.mdx similarity index 100% rename from pages/chain/networks.mdx rename to pages/stack/chain/networks.mdx diff --git a/pages/chain/security.mdx b/pages/stack/chain/security.mdx similarity index 100% rename from pages/chain/security.mdx rename to pages/stack/chain/security.mdx diff --git a/pages/chain/security/_meta.json b/pages/stack/chain/security/_meta.json similarity index 100% rename from pages/chain/security/_meta.json rename to pages/stack/chain/security/_meta.json diff --git a/pages/chain/security/faq.mdx b/pages/stack/chain/security/faq.mdx similarity index 100% rename from pages/chain/security/faq.mdx rename to pages/stack/chain/security/faq.mdx diff --git a/pages/chain/security/privileged-roles.mdx b/pages/stack/chain/security/privileged-roles.mdx similarity index 100% rename from pages/chain/security/privileged-roles.mdx rename to pages/stack/chain/security/privileged-roles.mdx diff --git a/pages/chain/security/security-policy.mdx b/pages/stack/chain/security/security-policy.mdx similarity index 100% rename from pages/chain/security/security-policy.mdx rename to pages/stack/chain/security/security-policy.mdx diff --git a/pages/chain/testing.mdx b/pages/stack/chain/testing.mdx similarity index 100% rename from pages/chain/testing.mdx rename to pages/stack/chain/testing.mdx diff --git a/pages/chain/testing/_meta.json b/pages/stack/chain/testing/_meta.json similarity index 100% rename from pages/chain/testing/_meta.json rename to pages/stack/chain/testing/_meta.json diff --git a/pages/chain/testing/dev-node.mdx b/pages/stack/chain/testing/dev-node.mdx similarity index 100% rename from pages/chain/testing/dev-node.mdx rename to pages/stack/chain/testing/dev-node.mdx diff --git a/pages/chain/testing/testing-apps.mdx b/pages/stack/chain/testing/testing-apps.mdx similarity index 100% rename from pages/chain/testing/testing-apps.mdx rename to pages/stack/chain/testing/testing-apps.mdx diff --git a/pages/chain/tokenlist.mdx b/pages/stack/chain/tokenlist.mdx similarity index 100% rename from pages/chain/tokenlist.mdx rename to pages/stack/chain/tokenlist.mdx diff --git a/pages/superchain/_meta.json b/pages/superchain/_meta.json index 47b18a2f5..ee551b1fe 100644 --- a/pages/superchain/_meta.json +++ b/pages/superchain/_meta.json @@ -1,4 +1,8 @@ { + "--- SUPERCHAIN": { + "title": "THE SUPERCHAIN", + "type": "separator" + }, "superchain-explainer": "The Superchain explainer", "superchain-registry": "The Superchain Registry", "blockspace-charter": "Blockspace Charters and the Standard Rollup Charter", diff --git a/public/_redirects b/public/_redirects index 476db7624..f8cb5646d 100644 --- a/public/_redirects +++ b/public/_redirects @@ -1,84 +1,84 @@ # Redirects from what the browser requests to what we serve -/builders/tools/rpc-providers /builders/tools/connect/rpc-providers -/builders/tools/block-explorers /builders/tools/build/block-explorers -/builders/tools/faucets /builders/tools/build/faucets -/builders/tools/oracles /builders/tools/build/oracles -/builders/tools/nft-tools /builders/tools/build/nft-tools -/builders/tools/account-abstraction /builders/tools/build/account-abstraction -/builders/tools/analytics-tools /builders/tools/monitor/analytics-tools -/builders/tools/regenesis-history /builders/tools/monitor/regenesis-history -/builders/dapp-developers/contracts/account-abstraction /builders/tools/build/account-abstraction +/builders/tools/rpc-providers /app-developers/tools/connect/rpc-providers +/builders/tools/block-explorers /app-developers/tools/build/block-explorers +/builders/tools/faucets /app-developers/tools/build/faucets +/builders/tools/oracles /app-developers/tools/build/oracles +/builders/tools/nft-tools /app-developers/tools/build/nft-tools +/builders/tools/account-abstraction /app-developers/tools/build/account-abstraction +/builders/tools/analytics-tools /app-developers/tools/monitor/analytics-tools +/builders/tools/regenesis-history /app-developers/tools/monitor/regenesis-history +/builders/dapp-developers/contracts/account-abstraction /app-developers/tools/build/account-abstraction /stack/security/forced-transfers /stack/security/faq -/builders/dapp-developers/dapp-developer-overview /builders/app-developers/overview +/builders/dapp-developers/dapp-developer-overview /app-developers/overview /tokenlist /chain/tokenlist /addresses /chain/addresses /identity/optimist-profile /chain/identity/overview /chain/identity/optimist-profile /chain/identity/overview /stack/transactions/transaction-fees /stack/transactions/fees -/builders/tools/monitoring/regenesis-history /builders/tools/monitor/regenesis-history -/builders/dapp-developers/bridging/basics /builders/app-developers/bridging/basics +/builders/tools/monitoring/regenesis-history /app-developers/tools/monitor/regenesis-history +/builders/dapp-developers/bridging/basics /app-developers/bridging/basics /resources/glossary /connect/resources/glossary /differences-op-stack /stack/differences /differences /chain/differences -/chain-operators/sample-hacks/modifying-predeploys /builders/chain-operators/tutorials/modifying-predeploys +/chain-operators/sample-hacks/modifying-predeploys /operators/chain-operators/tutorials/modifying-predeploys /chain/testing/testing-dapps /chain/testing/testing-apps -/chain-operators/hacks/derivation /builders/chain-operators/hacks/derivation -/chain-operators/hacks/overview /builders/chain-operators/hacks/overview +/chain-operators/hacks/derivation /operators/chain-operators/hacks/derivation +/chain-operators/hacks/overview /operators/chain-operators/hacks/overview /getting-started-op-stack /stack/getting-started -/builders/tools/javascript/sdk /builders/chain-operators/tutorials/sdk -/builders/tools/monitoring/analytics-tools /builders/tools/monitor/analytics-tools -/builders/chain-operators/operations /builders/chain-operators/management/operations -/builders/dapp-developers/contracts/cheap-dapp /builders/app-developers/contracts/optimization -/builders/dapp-developers/contracts/compatibility /builders/app-developers/contracts/compatibility -/builders/dapp-developers/contracts/system-contracts /builders/app-developers/contracts/system-contracts -/dapp-developers/creating-a-nft /builders/tools/build/nft-tools -/chain-operators/chain-troubleshooting /builders/chain-operators/management/troubleshooting +/builders/tools/javascript/sdk /operators/chain-operators/tutorials/sdk +/builders/tools/monitoring/analytics-tools /app-developers/tools/monitor/analytics-tools +/builders/chain-operators/operations /operators/chain-operators/management/operations +/builders/dapp-developers/contracts/cheap-dapp /app-developers/contracts/optimization +/builders/dapp-developers/contracts/compatibility /app-developers/contracts/compatibility +/builders/dapp-developers/contracts/system-contracts /app-developers/contracts/system-contracts +/dapp-developers/creating-a-nft /app-developers/tools/build/nft-tools +/chain-operators/chain-troubleshooting /operators/chain-operators/management/troubleshooting /builders/notices/ecotone-fee-changes /stack/transactions/fees#ecotone -/builders/node-operators/network-upgrades/overview /builders/node-operators/network-upgrades -/builders/node-operators/network-upgrades/canyon /builders/node-operators/network-upgrades -/builders/node-operators/network-upgrades/delta /builders/node-operators/network-upgrades -/builders/node-operators/network-upgrades/ecotone /builders/node-operators/network-upgrades -/builders/dapp-developers/code-examples/ecosystem-overview /builders/app-developers/tools/ecosystem-overview -/builders/dapp-developers/quick-start /builders/app-developers/quick-start -/builders/dapp-developers/bridging/messaging /builders/app-developers/bridging/messaging -/builders/dapp-developers/bridging/standard-bridge /builders/app-developers/bridging/standard-bridge -/builders/dapp-developers/bridging/custom-bridge /builders/app-developers/bridging/custom-bridge -/builders/dapp-developers/tutorials/first-contract /builders/app-developers/tutorials/first-contract -/builders/dapp-developers/tutorials/cross-dom-bridge-eth /builders/app-developers/tutorials/cross-dom-bridge-eth -/builders/dapp-developers/tutorials/cross-dom-bridge-erc20 /builders/app-developers/tutorials/cross-dom-bridge-erc20 -/builders/dapp-developers/tutorials/sdk-estimate-costs /builders/app-developers/tutorials/sdk-estimate-costs -/builders/dapp-developers/tutorials/sdk-view-txns /builders/app-developers/tutorials/sdk-view-txns -/builders/dapp-developers/tutorials/sdk-trace-txns /builders/app-developers/tutorials/sdk-trace-txns -/builders/dapp-developers/tutorials/send-tx-from-eth /builders/app-developers/tutorials/send-tx-from-eth -/builders/dapp-developers/tutorials/cross-dom-solidity /builders/app-developers/tutorials/cross-dom-solidity -/builders/dapp-developers/tutorials/standard-bridge-standard-token /builders/app-developers/tutorials/standard-bridge-standard-token -/builders/dapp-developers/tutorials/standard-bridge-custom-token /builders/app-developers/tutorials/standard-bridge-custom-token -/builders/dapp-developers/transactions/estimates /builders/app-developers/transactions/estimates -/builders/dapp-developers/transactions/fees /builders/app-developers/transactions/fees -/builders/dapp-developers/transactions/transactions/parameters /builders/app-developers/transactions/parameters -/builders/dapp-developers/transactions/statuses /builders/app-developers/transactions/statuses -/builders/dapp-developers/transactions/troubleshooting /builders/app-developers/transactions/troubleshooting -/builders/chain-operators/overview /builders/chain-operators/self-hosted -/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 +/builders/node-operators/network-upgrades/overview /operators/node-operators/network-upgrades +/builders/node-operators/network-upgrades/canyon /operators/node-operators/network-upgrades +/builders/node-operators/network-upgrades/delta /operators/node-operators/network-upgrades +/builders/node-operators/network-upgrades/ecotone /operators/node-operators/network-upgrades +/builders/dapp-developers/code-examples/ecosystem-overview /app-developers/tools/ecosystem-overview +/builders/dapp-developers/quick-start /app-developers/quick-start +/builders/dapp-developers/bridging/messaging /app-developers/bridging/messaging +/builders/dapp-developers/bridging/standard-bridge /app-developers/bridging/standard-bridge +/builders/dapp-developers/bridging/custom-bridge /app-developers/bridging/custom-bridge +/builders/dapp-developers/tutorials/first-contract /app-developers/tutorials/first-contract +/builders/dapp-developers/tutorials/cross-dom-bridge-eth /app-developers/tutorials/cross-dom-bridge-eth +/builders/dapp-developers/tutorials/cross-dom-bridge-erc20 /app-developers/tutorials/cross-dom-bridge-erc20 +/builders/dapp-developers/tutorials/sdk-estimate-costs /app-developers/tutorials/sdk-estimate-costs +/builders/dapp-developers/tutorials/sdk-view-txns /app-developers/tutorials/sdk-view-txns +/builders/dapp-developers/tutorials/sdk-trace-txns /app-developers/tutorials/sdk-trace-txns +/builders/dapp-developers/tutorials/send-tx-from-eth /app-developers/tutorials/send-tx-from-eth +/builders/dapp-developers/tutorials/cross-dom-solidity /app-developers/tutorials/cross-dom-solidity +/builders/dapp-developers/tutorials/standard-bridge-standard-token /app-developers/tutorials/standard-bridge-standard-token +/builders/dapp-developers/tutorials/standard-bridge-custom-token /app-developers/tutorials/standard-bridge-custom-token +/builders/dapp-developers/transactions/estimates /app-developers/transactions/estimates +/builders/dapp-developers/transactions/fees /app-developers/transactions/fees +/builders/dapp-developers/transactions/transactions/parameters /app-developers/transactions/parameters +/builders/dapp-developers/transactions/statuses /app-developers/transactions/statuses +/builders/dapp-developers/transactions/troubleshooting /app-developers/transactions/troubleshooting +/builders/chain-operators/overview /operators/chain-operators/self-hosted +/transaction-fees/overview /app-developers/transactions/fees +/dapp-developers/contracts/meta-tx /app-developers/contracts/optimization +/builders/tools/build/overview /app-developers/tools/overview /protocol-specifications/optimistic-rollup/block-production /stack/rollup/overview#block-production -/builders/node-operators/metrics /builders/node-operators/management/metrics +/builders/node-operators/metrics /operators/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 +/builders/chain-operators/management/tools/explorer /operators/chain-operators/tools/explorer +/builders/node-operators/management/configuration /operators/node-operators/configuration/base-config /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/node-operators/overview /operators/node-operators/rollup-node /builders/notices/ecotone-changes /stack/transactions/fees#ecotone /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 +/builders/chain-operators/management/configuration /operators/chain-operators/configuration/overview +/builders/chain-operators/management/custom-gas-token /operators/chain-operators/features/custom-gas-token /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 @@ -100,25 +100,25 @@ /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 +/stack/operators/features/op-txproxy /operators/chain-operators/tools/op-txproxy +/stack/operators/features/proxyd /operators/chain-operators/tools/proxyd /builders/notices/granite-changes https://github.com/ethereum-optimism/docs/blob/ef619668ae44276edecdfd657157254b9809e2d6/pages/builders/notices/granite-changes.mdx /builders/notices/fp-changes https://github.com/ethereum-optimism/docs/blob/ef619668ae44276edecdfd657157254b9809e2d6/pages/builders/notices/fp-changes.mdx /chain/differences /stack/differences -/builders/app-developers/contracts/optimization /builders/app-developers/overview +/builders/app-developers/contracts/optimization /app-developers/overview /builders/app-developers/contracts/system-contracts /stack/smart-contracts /builders/app-developers/contracts/compatibility /stack/differences -/builders/app-developers/tutorials/first-contract /builders/app-developers/overview -/builders/cex-wallet-developers/cex-support /builders/app-developers/overview -/builders/cex-wallet-developers/wallet-support /builders/app-developers/overview -/builders/cex-wallet-developers /builders/app-developers/overview +/builders/app-developers/tutorials/first-contract /app-developers/overview +/builders/cex-wallet-developers/cex-support /app-developers/overview +/builders/cex-wallet-developers/wallet-support /app-developers/overview +/builders/cex-wallet-developers /app-developers/overview /stack/interop/assets/superchain-erc20 /stack/interop/superchain-erc20 /stack/interop/assets/superchain-weth /stack/interop/superchain-weth /stack/interop/transfer-superchainERC20 /stack/interop/tutorials/transfer-superchainERC20 /stack/interop/assets/transfer-superchainERC20 /stack/interop/tutorials/transfer-superchainERC20 /stack/interop/assets/deploy-superchain-erc20 /stack/interop/tutorials/deploy-superchain-erc20 /builders/app-developers/contracts/superchain-erc20 /stack/interop/superchain-erc20 -/builders/chain-operators/tutorials/sdk /builders/app-developers/overview +/builders/chain-operators/tutorials/sdk /app-developers/overview /stack/explainer /superchain/superchain-explainer /stack/interop/architecture /stack/interop/explainer#interoperability-architecture /stack/interop/cross-chain-message /stack/interop/explainer#how-messages-get-from-one-chain-to-the-other @@ -131,3 +131,4 @@ /chain/identity/overview https://community.optimism.io/identity/overview /chain/identity/projects https://community.optimism.io/identity/projects /chain/identity/schemas https://community.optimism.io/identity/schemas +/builders/tools/fee-calculator /operators/chain-operators/tools/fee-calculator diff --git a/utils/breadcrumbs.ts b/utils/breadcrumbs.ts index ff00309d7..12aeb33c9 100644 --- a/utils/breadcrumbs.ts +++ b/utils/breadcrumbs.ts @@ -123,7 +123,7 @@ async function main() { try { // Process main sections: builders, chain, connect, stack - const mainSections = ['builders', 'chain', 'connect', 'stack']; + const mainSections = ['app-developers', 'operators', 'connect', 'stack']; for (const section of mainSections) { const sectionPath = path.join(rootDir, section); try { diff --git a/utils/create-breadcrumbs.ts b/utils/create-breadcrumbs.ts index 370e44bc4..61054ce7e 100644 --- a/utils/create-breadcrumbs.ts +++ b/utils/create-breadcrumbs.ts @@ -235,7 +235,7 @@ const main = async (): Promise => { try { // Process main sections: builders, chain, connect, stack - const mainSections = ['builders', 'chain', 'connect', 'stack']; + const mainSections = ['app-developers', 'operators', 'connect', 'stack']; for (const section of mainSections) { const sectionPath = path.join(rootDir, section); try { From a49be67c37d3eb09f472da32249d5b6cbdea8f68 Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Mon, 27 Jan 2025 23:26:47 -0800 Subject: [PATCH 02/49] llint fixes --- pages/operators/chain-operators.mdx | 10 +++++++++- pages/operators/node-operators.mdx | 9 ++++++++- pages/stack/chain.mdx | 7 ++++++- words.txt | 8 +++----- 4 files changed, 26 insertions(+), 8 deletions(-) diff --git a/pages/operators/chain-operators.mdx b/pages/operators/chain-operators.mdx index 497ec5248..94684f3c9 100644 --- a/pages/operators/chain-operators.mdx +++ b/pages/operators/chain-operators.mdx @@ -12,12 +12,20 @@ Documentation covering Architecture, Configuration, Deploy, Features, Hacks, Man + + + + + + + + - \ No newline at end of file + diff --git a/pages/operators/node-operators.mdx b/pages/operators/node-operators.mdx index a43522b41..81a4b9a03 100644 --- a/pages/operators/node-operators.mdx +++ b/pages/operators/node-operators.mdx @@ -12,11 +12,18 @@ Documentation covering Architecture, Configuration, Json Rpc, Management, Networ + + + + + + + - \ No newline at end of file + diff --git a/pages/stack/chain.mdx b/pages/stack/chain.mdx index 5f83f808c..640d93076 100644 --- a/pages/stack/chain.mdx +++ b/pages/stack/chain.mdx @@ -12,9 +12,14 @@ Documentation covering Addresses, Getting Started, Networks, Security, Testing, + + + + + - \ No newline at end of file + diff --git a/words.txt b/words.txt index e1b28a20a..f1621434a 100644 --- a/words.txt +++ b/words.txt @@ -95,6 +95,7 @@ DISABLETXPOOLGOSSIP disabletxpoolgossip Discv discv +disincentivize DIVU Drand dripcheck @@ -123,7 +124,6 @@ Farcaster Faultproof FDLIMIT fdlimit -featureset Flashblocks Flashbots forkable @@ -263,7 +263,6 @@ Pausability pausable pcscdpath Pectra -pectra Pectra's Peerstore peerstore @@ -282,7 +281,6 @@ pprof Precommitments precommitments preconfigured -Preconfigured predeploy Predeployed predeployed @@ -378,7 +376,6 @@ Superchain superchain Superchain's Superchainerc -superchainerc Superchains Superscan Supersim @@ -393,6 +390,8 @@ thirdweb threadcreate tility timeseries +Tokenlist +tokenlist triggerable trustlessly trustrpc @@ -411,7 +410,6 @@ unmetered Unprotect unsubmitted UPNP -usafe VERKLE verkle VHOSTS From 6b39f43cd73a02b35a7655373a3837096bb78a45 Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Mon, 27 Jan 2025 23:43:37 -0800 Subject: [PATCH 03/49] fix breadcrumbs --- pages/app-developers/tools/build.mdx | 25 ------------------------- pages/app-developers/tools/connect.mdx | 19 ------------------- pages/app-developers/tools/monitor.mdx | 19 ------------------- 3 files changed, 63 deletions(-) delete mode 100644 pages/app-developers/tools/build.mdx delete mode 100644 pages/app-developers/tools/connect.mdx delete mode 100644 pages/app-developers/tools/monitor.mdx diff --git a/pages/app-developers/tools/build.mdx b/pages/app-developers/tools/build.mdx deleted file mode 100644 index 0d039842e..000000000 --- a/pages/app-developers/tools/build.mdx +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Build -lang: en-US -description: >- - Learn about build in the Optimism ecosystem. This guide provides detailed - information and resources about build. ---- - -import { Card, Cards } from 'nextra/components' - -# Build - -This section provides information on account abstraction, block explorers, testnet faucets, op mainnet nft tools and oracles. You'll find guide, reference, tool, api to help you understand and work with these topics. - - - - - - - - - - - - diff --git a/pages/app-developers/tools/connect.mdx b/pages/app-developers/tools/connect.mdx deleted file mode 100644 index 50154b1f4..000000000 --- a/pages/app-developers/tools/connect.mdx +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Connect -lang: en-US -description: >- - Learn about connect in the Optimism ecosystem. This guide provides detailed - information and resources about connect. ---- - -import { Card, Cards } from 'nextra/components' - -# Connect - -This section provides information on networks and rpc & node providers. You'll find reference to help you understand and work with these topics. - - - - - - diff --git a/pages/app-developers/tools/monitor.mdx b/pages/app-developers/tools/monitor.mdx deleted file mode 100644 index 848483480..000000000 --- a/pages/app-developers/tools/monitor.mdx +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Monitor -lang: en-US -description: >- - Learn about monitor in the Optimism ecosystem. This guide provides detailed - information and resources about monitor. ---- - -import { Card, Cards } from 'nextra/components' - -# Monitor - -This section provides information on analytics tools and accessing pre regenesis history. You'll find guide, tool to help you understand and work with these topics. - - - - - - From c75b40afb3787b20fbe8d1a8c07ba8b496416954 Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Mon, 27 Jan 2025 23:52:10 -0800 Subject: [PATCH 04/49] adding pages back --- pages/app-developers/tools/build.mdx | 25 +++++++++++++++++++++++++ pages/app-developers/tools/connect.mdx | 19 +++++++++++++++++++ pages/app-developers/tools/monitor.mdx | 19 +++++++++++++++++++ 3 files changed, 63 insertions(+) create mode 100644 pages/app-developers/tools/build.mdx create mode 100644 pages/app-developers/tools/connect.mdx create mode 100644 pages/app-developers/tools/monitor.mdx diff --git a/pages/app-developers/tools/build.mdx b/pages/app-developers/tools/build.mdx new file mode 100644 index 000000000..c0875fb8c --- /dev/null +++ b/pages/app-developers/tools/build.mdx @@ -0,0 +1,25 @@ +--- +title: Build +lang: en-US +description: >- + Learn about build in the Optimism ecosystem. This guide provides detailed + information and resources about build. +--- + +import { Card, Cards } from 'nextra/components' + +# Build + +This section provides information on account abstraction, block explorers, testnet faucets, op mainnet nft tools and oracles. You'll find guide, reference, tool, api to help you understand and work with these topics. + + + + + + + + + + + + \ No newline at end of file diff --git a/pages/app-developers/tools/connect.mdx b/pages/app-developers/tools/connect.mdx new file mode 100644 index 000000000..69580e7cb --- /dev/null +++ b/pages/app-developers/tools/connect.mdx @@ -0,0 +1,19 @@ +--- +title: Connect +lang: en-US +description: >- + Learn about connect in the Optimism ecosystem. This guide provides detailed + information and resources about connect. +--- + +import { Card, Cards } from 'nextra/components' + +# Connect + +This section provides information on networks and rpc & node providers. You'll find reference to help you understand and work with these topics. + + + + + + \ No newline at end of file diff --git a/pages/app-developers/tools/monitor.mdx b/pages/app-developers/tools/monitor.mdx new file mode 100644 index 000000000..dea98e87f --- /dev/null +++ b/pages/app-developers/tools/monitor.mdx @@ -0,0 +1,19 @@ +--- +title: Monitor +lang: en-US +description: >- + Learn about monitor in the Optimism ecosystem. This guide provides detailed + information and resources about monitor. +--- + +import { Card, Cards } from 'nextra/components' + +# Monitor + +This section provides information on analytics tools and accessing pre regenesis history. You'll find guide, tool to help you understand and work with these topics. + + + + + + \ No newline at end of file From a5a5ba504ac017991270255446c21fa4a8a47e84 Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Tue, 28 Jan 2025 00:18:33 -0800 Subject: [PATCH 05/49] redirects and breadcrumbs --- pages/app-developers/bridging.mdx | 8 -------- pages/app-developers/overview.mdx | 14 +++++++------- pages/app-developers/tools.mdx | 8 ++------ pages/app-developers/tools/build.mdx | 10 +++++----- pages/app-developers/tools/connect.mdx | 4 ++-- pages/app-developers/tools/monitor.mdx | 4 ++-- pages/app-developers/tools/op-tools.mdx | 2 +- pages/app-developers/tools/overview.mdx | 20 ++++++++++---------- pages/app-developers/transactions.mdx | 10 ---------- pages/app-developers/tutorials.mdx | 18 ------------------ public/_redirects | 2 ++ 11 files changed, 31 insertions(+), 69 deletions(-) diff --git a/pages/app-developers/bridging.mdx b/pages/app-developers/bridging.mdx index 3cf4fefbc..4bec707f9 100644 --- a/pages/app-developers/bridging.mdx +++ b/pages/app-developers/bridging.mdx @@ -11,14 +11,6 @@ import { Card, Cards } from 'nextra/components' This section provides information on bridging basics, custom bridges, sending data between l1 and l2 and using the standard bridge. You'll find guide, overview to help you understand and work with these topics. - - - - - - - - diff --git a/pages/app-developers/overview.mdx b/pages/app-developers/overview.mdx index e38817e46..60c59480d 100644 --- a/pages/app-developers/overview.mdx +++ b/pages/app-developers/overview.mdx @@ -13,19 +13,19 @@ In this area of the Optimism Docs you'll find everything you need to know about ## Getting started -If you're brand new to OP Mainnet, try starting with the guide on [deploying a basic contract](/chain/getting-started). +If you're brand new to OP Mainnet, try starting with the guide on [deploying a basic contract](/stack/chain/getting-started). It'll get you familiar with the basic steps required to get a contract deployed to the network. OP Mainnet is [EVM equivalent](https://web.archive.org/web/20231127160757/https://medium.com/ethereum-optimism/introducing-evm-equivalence-5c2021deb306) so you can feel confident that your existing Ethereum smart contract skills will carry over to OP Mainnet. Just make sure to be aware of the few small [differences between Ethereum and OP Mainnet](/stack/differences). -You might also want to check out the [testing on OP Networks guide](/chain/testing/testing-apps) and the tutorial on [running a local development environment](/chain/testing/dev-node) to help you feel totally confident in your OP Mainnet deployment. +You might also want to check out the [testing on OP Networks guide](/chain/testing/testing-apps) and the tutorial on [running a local development environment](/stack/chain/testing/dev-node) to help you feel totally confident in your OP Mainnet deployment. - } /> + } /> } /> - } /> + } /> ## Bridging and messaging @@ -39,11 +39,11 @@ Contracts on one chain can trigger contract functions on the other chain, it's p The Standard Token Bridge for OP Mainnet even uses this same message-passing infrastructure under the hood. - } /> + } /> - } /> + } /> - } /> + } /> ## Tutorials diff --git a/pages/app-developers/tools.mdx b/pages/app-developers/tools.mdx index 03cbd5c63..fd20891c6 100644 --- a/pages/app-developers/tools.mdx +++ b/pages/app-developers/tools.mdx @@ -11,15 +11,11 @@ import { Card, Cards } from 'nextra/components' This section provides information on open-source code repositories for OP Stack builders and SuperSim. Users will find references to help understand and work with these topics. - - - - + + - - diff --git a/pages/app-developers/tools/build.mdx b/pages/app-developers/tools/build.mdx index c0875fb8c..0d2c493c3 100644 --- a/pages/app-developers/tools/build.mdx +++ b/pages/app-developers/tools/build.mdx @@ -13,13 +13,13 @@ import { Card, Cards } from 'nextra/components' This section provides information on account abstraction, block explorers, testnet faucets, op mainnet nft tools and oracles. You'll find guide, reference, tool, api to help you understand and work with these topics. - + - + - + - + - + \ No newline at end of file diff --git a/pages/app-developers/tools/connect.mdx b/pages/app-developers/tools/connect.mdx index 69580e7cb..dfc271d0a 100644 --- a/pages/app-developers/tools/connect.mdx +++ b/pages/app-developers/tools/connect.mdx @@ -13,7 +13,7 @@ import { Card, Cards } from 'nextra/components' This section provides information on networks and rpc & node providers. You'll find reference to help you understand and work with these topics. - + - + \ No newline at end of file diff --git a/pages/app-developers/tools/monitor.mdx b/pages/app-developers/tools/monitor.mdx index dea98e87f..065b05f7d 100644 --- a/pages/app-developers/tools/monitor.mdx +++ b/pages/app-developers/tools/monitor.mdx @@ -13,7 +13,7 @@ import { Card, Cards } from 'nextra/components' This section provides information on analytics tools and accessing pre regenesis history. You'll find guide, tool to help you understand and work with these topics. - + - + \ No newline at end of file diff --git a/pages/app-developers/tools/op-tools.mdx b/pages/app-developers/tools/op-tools.mdx index 6b074eb92..0d1e79319 100644 --- a/pages/app-developers/tools/op-tools.mdx +++ b/pages/app-developers/tools/op-tools.mdx @@ -10,7 +10,7 @@ import { Card, Cards } from 'nextra/components' # Op Tools -This section provides information on . +This section provides information on OP-specific tooling. diff --git a/pages/app-developers/tools/overview.mdx b/pages/app-developers/tools/overview.mdx index c3069e116..f7db715c2 100644 --- a/pages/app-developers/tools/overview.mdx +++ b/pages/app-developers/tools/overview.mdx @@ -15,32 +15,32 @@ If you are already familiar with [building on OP Mainnet](/chain/getting-started ## Connecting - } /> + } /> - } /> + } /> ## Building - } /> + } /> - } /> + } /> - } /> + } /> - } /> + } /> - } /> + } /> ## Monitoring - } /> + } /> - } /> + } /> ## OP tools @@ -58,6 +58,6 @@ If you are already familiar with [building on OP Mainnet](/chain/getting-started } /> - } /> + } /> diff --git a/pages/app-developers/transactions.mdx b/pages/app-developers/transactions.mdx index d2bb9fdf5..1d633421a 100644 --- a/pages/app-developers/transactions.mdx +++ b/pages/app-developers/transactions.mdx @@ -13,16 +13,6 @@ import { Card, Cards } from 'nextra/components' This section provides information on transactions in OP Mainnet, including fee estimation, gas parameters, transaction statuses, and troubleshooting. You'll find guides to help you understand and work with these topics. - - - - - - - - - - diff --git a/pages/app-developers/tutorials.mdx b/pages/app-developers/tutorials.mdx index e2f51eb26..91bc57aad 100644 --- a/pages/app-developers/tutorials.mdx +++ b/pages/app-developers/tutorials.mdx @@ -11,24 +11,6 @@ import { Card, Cards } from 'nextra/components' This section provides information on bridging erc 20 tokens to op mainnet with viem, bridging eth to op mainnet with viem, communicating between op mainnet and ethereum in solidity, deploying your first contract on op mainnet, estimating transaction costs on op mainnet, tracing deposits and withdrawals, viewing deposits and withdrawals by address, triggering op mainnet transactions from ethereum, bridging your custom erc 20 token using the standard bridge and bridging your standard erc 20 token using the standard bridge. You'll find tutorial to help you understand and work with these topics. - - - - - - - - - - - - - - - - - - diff --git a/public/_redirects b/public/_redirects index f8cb5646d..7217f9a12 100644 --- a/public/_redirects +++ b/public/_redirects @@ -132,3 +132,5 @@ /chain/identity/projects https://community.optimism.io/identity/projects /chain/identity/schemas https://community.optimism.io/identity/schemas /builders/tools/fee-calculator /operators/chain-operators/tools/fee-calculator +/builders/app-developers/tools/supersim /app-developers/tools/supersim +/builders/app-developers/tools/ecosystem-overview /app-developers/tools/ecosystem-overview From 3827fd5f380b0110fee34c682472536d723068b0 Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Tue, 28 Jan 2025 00:38:44 -0800 Subject: [PATCH 06/49] fix breadcrumbs --- pages/app-developers/tools/build.mdx | 2 +- pages/app-developers/tools/connect.mdx | 2 +- pages/app-developers/tools/monitor.mdx | 2 +- .../operators/chain-operators/configuration.mdx | 8 ++++---- pages/operators/chain-operators/deploy.mdx | 6 +++--- pages/operators/chain-operators/features.mdx | 10 +++++----- pages/operators/chain-operators/hacks.mdx | 12 ++++++------ pages/operators/chain-operators/management.mdx | 12 ++++++------ pages/operators/chain-operators/tools.mdx | 16 +++++++++------- pages/operators/chain-operators/tutorials.mdx | 12 ++++++------ pages/operators/node-operators/configuration.mdx | 6 +++--- pages/operators/node-operators/management.mdx | 10 +++++----- pages/operators/node-operators/tutorials.mdx | 8 ++++---- pages/stack/chain/security.mdx | 6 +++--- pages/stack/chain/testing.mdx | 4 ++-- 15 files changed, 59 insertions(+), 57 deletions(-) diff --git a/pages/app-developers/tools/build.mdx b/pages/app-developers/tools/build.mdx index 0d2c493c3..7d3d47d24 100644 --- a/pages/app-developers/tools/build.mdx +++ b/pages/app-developers/tools/build.mdx @@ -22,4 +22,4 @@ This section provides information on account abstraction, block explorers, testn - \ No newline at end of file + diff --git a/pages/app-developers/tools/connect.mdx b/pages/app-developers/tools/connect.mdx index dfc271d0a..8be23f91b 100644 --- a/pages/app-developers/tools/connect.mdx +++ b/pages/app-developers/tools/connect.mdx @@ -16,4 +16,4 @@ This section provides information on networks and rpc & node providers. You'll f - \ No newline at end of file + diff --git a/pages/app-developers/tools/monitor.mdx b/pages/app-developers/tools/monitor.mdx index 065b05f7d..273430003 100644 --- a/pages/app-developers/tools/monitor.mdx +++ b/pages/app-developers/tools/monitor.mdx @@ -16,4 +16,4 @@ This section provides information on analytics tools and accessing pre regenesis - \ No newline at end of file + diff --git a/pages/operators/chain-operators/configuration.mdx b/pages/operators/chain-operators/configuration.mdx index f8ea320f4..46e9508c5 100644 --- a/pages/operators/chain-operators/configuration.mdx +++ b/pages/operators/chain-operators/configuration.mdx @@ -11,11 +11,11 @@ import { Card, Cards } from 'nextra/components' This section provides information on batcher configuration, chain operator configurations, proposer configuration, and rollup deployment configuration. Users will find API references and overviews to help understand and work with these topics. - + - + - + - + diff --git a/pages/operators/chain-operators/deploy.mdx b/pages/operators/chain-operators/deploy.mdx index 87e4184f6..369ad9942 100644 --- a/pages/operators/chain-operators/deploy.mdx +++ b/pages/operators/chain-operators/deploy.mdx @@ -11,9 +11,9 @@ import { Card, Cards } from 'nextra/components' This section provides information on OP Stack genesis creation, deployment overview, and smart contract deployment. You'll find guides and overviews to help you understand and work with these topics. - + - + - + diff --git a/pages/operators/chain-operators/features.mdx b/pages/operators/chain-operators/features.mdx index e2a22d516..e62458cb4 100644 --- a/pages/operators/chain-operators/features.mdx +++ b/pages/operators/chain-operators/features.mdx @@ -13,13 +13,13 @@ import { Card, Cards } from 'nextra/components' This section provides information on various features for chain operators. You'll find guides and overviews to help you understand and work with topics such as running an alternative data availability mode chain, implementing the bridged USDC standard on the OP Stack, running a custom gas token chain, OP Stack preinstalls, and span batches. - + - + - + - + - + diff --git a/pages/operators/chain-operators/hacks.mdx b/pages/operators/chain-operators/hacks.mdx index 5a30e8912..6ab68895a 100644 --- a/pages/operators/chain-operators/hacks.mdx +++ b/pages/operators/chain-operators/hacks.mdx @@ -13,15 +13,15 @@ import { Card, Cards } from 'nextra/components' This section provides information on various types of hacks related to OP Stack, including data availability, derivation, execution, and settlement. You'll find an overview and introduction to help you understand and work with these topics, as well as featured hacks for practical examples. - + - + - + - + - + - + diff --git a/pages/operators/chain-operators/management.mdx b/pages/operators/chain-operators/management.mdx index df32978e5..a8137ad97 100644 --- a/pages/operators/chain-operators/management.mdx +++ b/pages/operators/chain-operators/management.mdx @@ -13,15 +13,15 @@ import { Card, Cards } from 'nextra/components' This section provides information on chain operator best practices, using blobs, managing keys, rollup operations, using snap sync for chain operators, and troubleshooting chain operations. You'll find guides and tutorials to help you understand and work with these topics. - + - + - + - + - + - + diff --git a/pages/operators/chain-operators/tools.mdx b/pages/operators/chain-operators/tools.mdx index c8018d508..803484d19 100644 --- a/pages/operators/chain-operators/tools.mdx +++ b/pages/operators/chain-operators/tools.mdx @@ -13,17 +13,19 @@ import { Card, Cards } from 'nextra/components' This section provides information on chain monitoring options, deploying a block explorer, configuring a challenger for your chain, conductor, and deployer. You'll find guides, overviews, and tools to help you understand and work with these topics. - + - + - + - + - + - + - + + + Card title="Fjord fee parameter calculator" href="/operators/chain-operators/tools/fee-calculator" /> diff --git a/pages/operators/chain-operators/tutorials.mdx b/pages/operators/chain-operators/tutorials.mdx index 6b2387f7a..7de592e70 100644 --- a/pages/operators/chain-operators/tutorials.mdx +++ b/pages/operators/chain-operators/tutorials.mdx @@ -13,15 +13,15 @@ import { Card, Cards } from 'nextra/components' This section provides information on adding attributes to the derivation function, adding a precompile, creating your own l2 rollup testnet, integrating a new da layer with alt da, modifying predeployed contracts and using viem. You'll find overview, tutorial, guide to help you understand and work with these topics. - + - + - + - + - + - + diff --git a/pages/operators/node-operators/configuration.mdx b/pages/operators/node-operators/configuration.mdx index da2c8f8a8..12b895d1d 100644 --- a/pages/operators/node-operators/configuration.mdx +++ b/pages/operators/node-operators/configuration.mdx @@ -13,9 +13,9 @@ import { Card, Cards } from 'nextra/components' This section provides information on node base configuration, consensus layer configuration options (OP Node), and execution layer configuration options (OP Geth). You'll find information to help you understand and work with these topics. - + - + - + diff --git a/pages/operators/node-operators/management.mdx b/pages/operators/node-operators/management.mdx index 428a4593d..865817fd6 100644 --- a/pages/operators/node-operators/management.mdx +++ b/pages/operators/node-operators/management.mdx @@ -13,13 +13,13 @@ import { Card, Cards } from 'nextra/components' This section provides information on using blobs, node metrics and monitoring, snap sync for node operators, node snapshots, and troubleshooting. Users will find APIs, references, and guides to help understand and work with these topics. - + - + - + - + - + diff --git a/pages/operators/node-operators/tutorials.mdx b/pages/operators/node-operators/tutorials.mdx index de908fd0f..c2979638f 100644 --- a/pages/operators/node-operators/tutorials.mdx +++ b/pages/operators/node-operators/tutorials.mdx @@ -13,11 +13,11 @@ import { Card, Cards } from 'nextra/components' This section provides information on various node operations. It covers running an OP Mainnet node from source, running a node with Docker, building a node from source, and running an OP Sepolia node from source. You'll find tutorials and guides to help you understand and work with these topics. - + - + - + - + diff --git a/pages/stack/chain/security.mdx b/pages/stack/chain/security.mdx index e4f10a998..d9aa08693 100644 --- a/pages/stack/chain/security.mdx +++ b/pages/stack/chain/security.mdx @@ -11,9 +11,9 @@ import { Card, Cards } from 'nextra/components' Documentation covering Faq, Privileged Roles, Security Policy in the Security section of the OP Stack ecosystem. - + - + - + diff --git a/pages/stack/chain/testing.mdx b/pages/stack/chain/testing.mdx index fc2af6d47..ebdcca3a2 100644 --- a/pages/stack/chain/testing.mdx +++ b/pages/stack/chain/testing.mdx @@ -11,7 +11,7 @@ import { Card, Cards } from 'nextra/components' Documentation covering Dev Node, Testing Apps in the Testing section of the OP Stack ecosystem. - + - + From 81a8a2f7f8917f2a3402db8834e681009def57b5 Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Tue, 28 Jan 2025 00:42:03 -0800 Subject: [PATCH 07/49] Delete tools.mdx --- pages/operators/chain-operators/tools.mdx | 31 ----------------------- 1 file changed, 31 deletions(-) delete mode 100644 pages/operators/chain-operators/tools.mdx diff --git a/pages/operators/chain-operators/tools.mdx b/pages/operators/chain-operators/tools.mdx deleted file mode 100644 index 803484d19..000000000 --- a/pages/operators/chain-operators/tools.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Tools -lang: en-US -description: >- - Learn about tools in the Optimism ecosystem. This guide provides detailed - information and resources about tools. ---- - -import { Card, Cards } from 'nextra/components' - -# Tools - -This section provides information on chain monitoring options, deploying a block explorer, configuring a challenger for your chain, conductor, and deployer. You'll find guides, overviews, and tools to help you understand and work with these topics. - - - - - - - - - - - - - - - - - Card title="Fjord fee parameter calculator" href="/operators/chain-operators/tools/fee-calculator" /> - From b4d58684d18f8b51cc4548108f5c31d2c9191851 Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Tue, 28 Jan 2025 00:54:05 -0800 Subject: [PATCH 08/49] links and breadcrumbs --- pages/index.mdx | 16 +++++++------- pages/operators/chain-operators/tools.mdx | 27 +++++++++++++++++++++++ 2 files changed, 35 insertions(+), 8 deletions(-) create mode 100644 pages/operators/chain-operators/tools.mdx diff --git a/pages/index.mdx b/pages/index.mdx index eeaa2d14b..675bd5003 100644 --- a/pages/index.mdx +++ b/pages/index.mdx @@ -16,15 +16,15 @@ Information about the Optimism Collective's governance, community, and mission c Whether you're a developer building an app on OP Mainnet, a node operator running an OP Mainnet node, or a chain operator launching your own OP Stack chain, you'll find everything you need to get started right here. - } /> + } /> - } /> + } /> - } /> + } /> - } /> + } /> - } /> + } /> @@ -35,11 +35,11 @@ Check out these amazing tools, so you can get building with Optimism. } /> - } /> + } /> } /> - } /> + } /> } /> @@ -53,7 +53,7 @@ The Superchain is a network of OP Stack chains that share a bridging protocol, g We've got you covered with these detailed guides to help you learn all about Optimism's tech stack. - } /> + } /> } /> diff --git a/pages/operators/chain-operators/tools.mdx b/pages/operators/chain-operators/tools.mdx new file mode 100644 index 000000000..3238c2873 --- /dev/null +++ b/pages/operators/chain-operators/tools.mdx @@ -0,0 +1,27 @@ +--- +title: Tools +lang: en-US +description: >- + Learn about tools in the Optimism ecosystem. This guide provides detailed + information and resources about tools. +--- + +import { Card, Cards } from 'nextra/components' + +# Tools + +This section provides information on chain monitoring options, deploying a block explorer, configuring a challenger for your chain, conductor, and deployer. You'll find guides, overviews, and tools to help you understand and work with these topics. + + + + + + + + + + + + + + From 7707d0230a62bb987bce29e04948fd4d95ae05cc Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Tue, 28 Jan 2025 01:23:08 -0800 Subject: [PATCH 09/49] fix internal links --- .../suggest_troubleshooting_item.yaml | 2 +- components/calculator/ResultsTable.tsx | 2 +- pages/app-developers/bridging/basics.mdx | 8 ++--- .../app-developers/bridging/custom-bridge.mdx | 2 +- pages/app-developers/bridging/messaging.mdx | 2 +- .../bridging/standard-bridge.mdx | 8 ++--- pages/app-developers/quick-start.mdx | 2 +- .../tools/build/account-abstraction.mdx | 2 +- .../tools/build/block-explorers.mdx | 4 +-- pages/app-developers/tools/build/faucets.mdx | 2 +- pages/app-developers/tools/build/oracles.mdx | 2 +- .../tools/connect/rpc-providers.mdx | 2 +- .../app-developers/transactions/estimates.mdx | 2 +- .../tutorials/cross-dom-bridge-erc20.mdx | 6 ++-- .../tutorials/cross-dom-bridge-eth.mdx | 4 +-- .../tutorials/cross-dom-solidity.mdx | 4 +-- .../tutorials/sdk-estimate-costs.mdx | 4 +-- pages/connect/contribute/docs-contribute.mdx | 2 +- pages/connect/contribute/stack-contribute.mdx | 2 +- pages/connect/contribute/style-guide.mdx | 20 +++++------ .../chain-operators/architecture.mdx | 10 +++--- .../chain-operators/configuration/batcher.mdx | 2 +- .../configuration/overview.mdx | 8 ++--- .../chain-operators/configuration/rollup.mdx | 4 +-- .../chain-operators/deploy/genesis.mdx | 8 ++--- .../chain-operators/deploy/overview.mdx | 6 ++-- .../deploy/smart-contracts.mdx | 10 +++--- .../chain-operators/features/alt-da-mode.mdx | 4 +-- .../features/custom-gas-token.mdx | 2 +- .../chain-operators/hacks/derivation.mdx | 2 +- .../chain-operators/hacks/execution.mdx | 2 +- .../management/best-practices.mdx | 2 +- .../chain-operators/management/blobs.mdx | 10 +++--- .../chain-operators/management/operations.mdx | 2 +- .../chain-operators/management/snap-sync.mdx | 12 +++---- .../operators/chain-operators/self-hosted.mdx | 26 +++++++------- .../tools/chain-monitoring.mdx | 8 ++--- .../chain-operators/tools/op-conductor.mdx | 2 +- .../chain-operators/tools/proxyd.mdx | 6 ++-- .../tutorials/create-l2-rollup.mdx | 6 ++-- .../tutorials/integrating-da-layer.mdx | 2 +- .../operators/node-operators/architecture.mdx | 2 +- .../configuration/base-config.mdx | 10 +++--- .../configuration/consensus-config.mdx | 2 +- pages/operators/node-operators/json-rpc.mdx | 2 +- .../node-operators/management/blobs.mdx | 2 +- .../node-operators/management/snap-sync.mdx | 8 ++--- .../node-operators/network-upgrades.mdx | 2 +- .../operators/node-operators/rollup-node.mdx | 36 +++++++++---------- .../node-operators/tutorials/mainnet.mdx | 14 ++++---- .../node-operators/tutorials/testnet.mdx | 8 ++--- pages/stack/beta-features/alt-da-mode.mdx | 2 +- .../stack/beta-features/custom-gas-token.mdx | 2 +- pages/stack/chain/getting-started.mdx | 4 +-- pages/stack/chain/networks.mdx | 2 +- pages/stack/chain/testing/dev-node.mdx | 2 +- pages/stack/chain/testing/testing-apps.mdx | 2 +- pages/stack/components.mdx | 2 +- pages/stack/fault-proofs/challenger.mdx | 2 +- .../send-raw-transaction-conditional.mdx | 2 +- pages/stack/getting-started.mdx | 4 +-- pages/stack/interop/explainer.mdx | 4 +-- pages/stack/research/block-time-research.mdx | 2 +- pages/stack/rollup/overview.mdx | 6 ++-- pages/stack/smart-contracts.mdx | 2 +- pages/stack/transactions/fees.mdx | 10 +++--- .../transactions/transaction-finality.mdx | 2 +- pages/stack/transactions/withdrawal-flow.mdx | 2 +- pages/superchain/standard-configuration.mdx | 4 +-- pages/superchain/superchain-registry.mdx | 2 +- theme.config.tsx | 2 +- 71 files changed, 181 insertions(+), 181 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/suggest_troubleshooting_item.yaml b/.github/ISSUE_TEMPLATE/suggest_troubleshooting_item.yaml index 287ed464d..16b983b60 100644 --- a/.github/ISSUE_TEMPLATE/suggest_troubleshooting_item.yaml +++ b/.github/ISSUE_TEMPLATE/suggest_troubleshooting_item.yaml @@ -6,7 +6,7 @@ body: - type: markdown attributes: value: | - Before submitting this suggestion, be sure to read our expectations for [troubleshooting content](https://docs.optimism.io/contribute/style-guide#troubleshooting-guides).
For an example troubleshooting guide with problem+solution pairs, see [Troubleshooting: L2 Rollup](https://docs.optimism.io/builders/chain-operators/management/troubleshooting). + Before submitting this suggestion, be sure to read our expectations for [troubleshooting content](https://docs.optimism.io/contribute/style-guide#troubleshooting-guides).
For an example troubleshooting guide with problem+solution pairs, see [Troubleshooting: L2 Rollup](https://docs.optimism.io/operators/chain-operators/management/troubleshooting). - type: markdown id: project_info attributes: diff --git a/components/calculator/ResultsTable.tsx b/components/calculator/ResultsTable.tsx index e20a0d7f8..3613dafcc 100644 --- a/components/calculator/ResultsTable.tsx +++ b/components/calculator/ResultsTable.tsx @@ -108,7 +108,7 @@ export function ResultsTable({

Note: This is an estimation,{" "} read how to determine scalar values using blobs diff --git a/pages/app-developers/bridging/basics.mdx b/pages/app-developers/bridging/basics.mdx index f2085f5fe..33af955f9 100644 --- a/pages/app-developers/bridging/basics.mdx +++ b/pages/app-developers/bridging/basics.mdx @@ -28,7 +28,7 @@ All of this is easily accessible with a simple, clean API. Ready to start bridging? Check out these tutorials to get up to speed fast. -* [Learn how to bridge ERC-20 tokens with viem](/builders/app-developers/tutorials/cross-dom-bridge-erc20) -* [Learn how to bridge ETH with viem](/builders/app-developers/tutorials/cross-dom-bridge-eth) -* [Learn how to create a standard bridged token](/builders/app-developers/tutorials/standard-bridge-standard-token) -* [Learn how to create a custom bridged token](/builders/app-developers/tutorials/standard-bridge-custom-token) +* [Learn how to bridge ERC-20 tokens with viem](/app-developers/tutorials/cross-dom-bridge-erc20) +* [Learn how to bridge ETH with viem](/app-developers/tutorials/cross-dom-bridge-eth) +* [Learn how to create a standard bridged token](/app-developers/tutorials/standard-bridge-standard-token) +* [Learn how to create a custom bridged token](/app-developers/tutorials/standard-bridge-custom-token) diff --git a/pages/app-developers/bridging/custom-bridge.mdx b/pages/app-developers/bridging/custom-bridge.mdx index e0e60e2c4..ab5b02a0f 100644 --- a/pages/app-developers/bridging/custom-bridge.mdx +++ b/pages/app-developers/bridging/custom-bridge.mdx @@ -15,7 +15,7 @@ This guide provides important information you should be aware of when building a Custom bridges can bring a significant amount of complexity and risk to any project. Before you commit to a custom bridge, be sure that the [Standard Bridge](./standard-bridge) definitely does not support your use case. - [Building a custom bridged token](/builders/app-developers/tutorials/standard-bridge-custom-token) is often sufficient for projects that need more flexibility. + [Building a custom bridged token](/app-developers/tutorials/standard-bridge-custom-token) is often sufficient for projects that need more flexibility. ## Guidelines diff --git a/pages/app-developers/bridging/messaging.mdx b/pages/app-developers/bridging/messaging.mdx index 796339862..61213733f 100644 --- a/pages/app-developers/bridging/messaging.mdx +++ b/pages/app-developers/bridging/messaging.mdx @@ -13,7 +13,7 @@ This page explains how bridging works, how to use it, and what to watch out for. This is a high-level overview of the bridging process. - For a step-by-step tutorial on how to send data between L1 and L2, check out the [Solidity tutorial](/builders/app-developers/tutorials/cross-dom-solidity). + For a step-by-step tutorial on how to send data between L1 and L2, check out the [Solidity tutorial](/app-developers/tutorials/cross-dom-solidity). ## Understanding contract calls diff --git a/pages/app-developers/bridging/standard-bridge.mdx b/pages/app-developers/bridging/standard-bridge.mdx index ff9d7c467..6777721df 100644 --- a/pages/app-developers/bridging/standard-bridge.mdx +++ b/pages/app-developers/bridging/standard-bridge.mdx @@ -199,10 +199,10 @@ Users simply need to trigger and send ETH to the [`bridgeETH`](https://github.co ## Tutorials -* [Learn how to bridge ERC-20 tokens with viem](/builders/app-developers/tutorials/cross-dom-bridge-erc20) -* [Learn how to bridge ETH with viem](/builders/app-developers/tutorials/cross-dom-bridge-eth) -* [Learn how to create a standard bridged token](/builders/app-developers/tutorials/standard-bridge-standard-token) -* [Learn how to create a custom bridged token](/builders/app-developers/tutorials/standard-bridge-custom-token) +* [Learn how to bridge ERC-20 tokens with viem](/app-developers/tutorials/cross-dom-bridge-erc20) +* [Learn how to bridge ETH with viem](/app-developers/tutorials/cross-dom-bridge-eth) +* [Learn how to create a standard bridged token](/app-developers/tutorials/standard-bridge-standard-token) +* [Learn how to create a custom bridged token](/app-developers/tutorials/standard-bridge-custom-token) ## Superchain Token List diff --git a/pages/app-developers/quick-start.mdx b/pages/app-developers/quick-start.mdx index 98cc91da0..621ae28fd 100644 --- a/pages/app-developers/quick-start.mdx +++ b/pages/app-developers/quick-start.mdx @@ -26,7 +26,7 @@ You can request testnet ETH from the Superchain Faucet in one of two ways: **con Looking for more faucets? - You can also try using [other available OP Sepolia faucets](/builders/tools/build/faucets). + You can also try using [other available OP Sepolia faucets](/app-developers/tools/build/faucets). ## Step 2: Build a basic app with Scaffold-OP diff --git a/pages/app-developers/tools/build/account-abstraction.mdx b/pages/app-developers/tools/build/account-abstraction.mdx index a5a1cbec8..f73fb004d 100644 --- a/pages/app-developers/tools/build/account-abstraction.mdx +++ b/pages/app-developers/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 used by the chain operator, also see the supplemental [op-txproxy](/builders/chain-operators/tools/op-txproxy) service which may apply additional restrictions prior to reaching the block builder. +If used by the chain operator, also see the supplemental [op-txproxy](/operators/chain-operators/tools/op-txproxy) service which may apply additional restrictions prior to reaching the block builder. As of today, this endpoint is not enabled by default in the stack. The operator must explicitly configure this. diff --git a/pages/app-developers/tools/build/block-explorers.mdx b/pages/app-developers/tools/build/block-explorers.mdx index cd179fc87..2da83f348 100644 --- a/pages/app-developers/tools/build/block-explorers.mdx +++ b/pages/app-developers/tools/build/block-explorers.mdx @@ -68,7 +68,7 @@ Once Upon currently supports: ## 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/). -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](/builders/tools/monitor/regenesis-history). +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](/app-developers/tools/monitor/regenesis-history). ## Inclusion criteria @@ -84,4 +84,4 @@ You can also promote your tool in the [developer forum](https://github.com/ether ## Next Steps * Please visit the [community block explorers page](https://github.com/ethereum-optimism/developers/blob/main/community/tools/block-explorers.md) for a listing of third-party block explorers used by the Optimism developer community. -* Looking for other developer tools? See [developer tools overview](/builders/tools/overview) to explore more options! +* Looking for other developer tools? See [developer tools overview](/app-developers/tools/overview) to explore more options! diff --git a/pages/app-developers/tools/build/faucets.mdx b/pages/app-developers/tools/build/faucets.mdx index 8c815513a..2850701c7 100644 --- a/pages/app-developers/tools/build/faucets.mdx +++ b/pages/app-developers/tools/build/faucets.mdx @@ -61,4 +61,4 @@ You can also promote your tool in the [developer forum](https://github.com/ether * If you're new to onchain development, check out [Optimism Unleashed](https://cryptozombies.io/en/optimism) by CryptoZombies and [Superchain Builder NFT](https://web.archive.org/web/20231218203510/https://blog.thirdweb.com/guides/optimism-superchain-faucet-nft/) by ThirdWeb. * If you're familiar with onchain development, check out the [Optimism Ecosystem's Contributions Dashboard](https://github.com/ethereum-optimism/ecosystem-contributions) for project ideas that the Optimism Collective is looking for. -* Looking for other developer tools? See [developer tools overview](/builders/tools/overview) to explore more options! +* Looking for other developer tools? See [developer tools overview](/app-developers/tools/overview) to explore more options! diff --git a/pages/app-developers/tools/build/oracles.mdx b/pages/app-developers/tools/build/oracles.mdx index d9802c4a6..f70207126 100644 --- a/pages/app-developers/tools/build/oracles.mdx +++ b/pages/app-developers/tools/build/oracles.mdx @@ -147,4 +147,4 @@ You can also promote your tool in the [developer forum](https://github.com/ether ## Next steps * Please visit the [community oracles page](https://github.com/ethereum-optimism/developers/blob/main/community/tools/oracles.md) for a listing of third-party Oracles used by the Optimism developer community. -* Looking for other developer tools? See [developer tools overview](/builders/tools/overview) to explore more options! +* Looking for other developer tools? See [developer tools overview](/app-developers/tools/overview) to explore more options! diff --git a/pages/app-developers/tools/connect/rpc-providers.mdx b/pages/app-developers/tools/connect/rpc-providers.mdx index 4ea661d26..bf99edc6a 100644 --- a/pages/app-developers/tools/connect/rpc-providers.mdx +++ b/pages/app-developers/tools/connect/rpc-providers.mdx @@ -148,4 +148,4 @@ You can also promote your tool in the [developer forum](https://github.com/ether ## Next steps * Please visit the [community node providers page](https://github.com/ethereum-optimism/developers/blob/main/community/tools/node-providers.md) for a listing of third-party node providers used by the Optimism developer community. -* Looking for other developer tools? See [developer tools overview](/builders/tools/overview) to explore more options! +* Looking for other developer tools? See [developer tools overview](/app-developers/tools/overview) to explore more options! diff --git a/pages/app-developers/transactions/estimates.mdx b/pages/app-developers/transactions/estimates.mdx index 8f7bcf99c..dcb5cf5ab 100644 --- a/pages/app-developers/transactions/estimates.mdx +++ b/pages/app-developers/transactions/estimates.mdx @@ -51,7 +51,7 @@ Make sure to check out the guide on [Setting Transaction Gas Parameters on OP Ma The Viem library provides a convenient method for estimating the L1 data fee for a transaction. -Check out the tutorial on [Estimating Transaction Costs on OP Mainnet](/builders/app-developers/tutorials/sdk-estimate-costs) to learn how to use the Viem library to estimate the L1 data fee for your transaction. +Check out the tutorial on [Estimating Transaction Costs on OP Mainnet](/app-developers/tutorials/sdk-estimate-costs) to learn how to use the Viem library to estimate the L1 data fee for your transaction. Keep reading if you'd like to learn how to estimate the L1 data fee without the Viem library. diff --git a/pages/app-developers/tutorials/cross-dom-bridge-erc20.mdx b/pages/app-developers/tutorials/cross-dom-bridge-erc20.mdx index 883e4908c..f57f39877 100644 --- a/pages/app-developers/tutorials/cross-dom-bridge-erc20.mdx +++ b/pages/app-developers/tutorials/cross-dom-bridge-erc20.mdx @@ -17,8 +17,8 @@ This tutorial explains how you can use the [Optimism SDK](https://sdk.optimism.i The Optimism SDK is an easy way to add bridging functionality to your javascript-based application. It also provides some safety rails to prevent common mistakes that could cause tokens to be made inaccessible. -Behind the scenes, the Optimism SDK uses the [Standard Bridge](/builders/app-developers/bridging/standard-bridge) contracts to transfer tokens. -Make sure to check out the [Standard Bridge guide](/builders/app-developers/bridging/standard-bridge) if you want to learn more about how the bridge works under the hood. +Behind the scenes, the Optimism SDK uses the [Standard Bridge](/app-developers/bridging/standard-bridge) contracts to transfer tokens. +Make sure to check out the [Standard Bridge guide](/app-developers/bridging/standard-bridge) if you want to learn more about how the bridge works under the hood. The Standard Bridge **does not** support [**fee on transfer @@ -31,7 +31,7 @@ Make sure to check out the [Standard Bridge guide](/builders/app-developers/brid The Optimism SDK supports any of the [Superchain networks](/chain/networks). [Some Superchain networks](https://sdk.optimism.io/enums/l2chainid) are already included in the SDK by default. -If you want to use a network that isn't included by default, you can simply [instantiate the SDK with the appropriate contract addresses](/builders/app-developers/overview). +If you want to use a network that isn't included by default, you can simply [instantiate the SDK with the appropriate contract addresses](/app-developers/overview). ## Dependencies diff --git a/pages/app-developers/tutorials/cross-dom-bridge-eth.mdx b/pages/app-developers/tutorials/cross-dom-bridge-eth.mdx index 3cbe5253e..6acfefeeb 100644 --- a/pages/app-developers/tutorials/cross-dom-bridge-eth.mdx +++ b/pages/app-developers/tutorials/cross-dom-bridge-eth.mdx @@ -12,8 +12,8 @@ This tutorial explains how you can use [Viem](https://viem.sh) to bridge ETH fro Viem is a TypeScript interface for Ethereum that provides low-level stateless primitives for interacting with Ethereum. It offers an easy way to add bridging functionality to your JavaScript-based application. -Behind the scenes, Viem uses the [Standard Bridge](/builders/app-developers/bridging/standard-bridge) contracts to transfer ETH and ERC-20 tokens. -Make sure to check out the [Standard Bridge guide](/builders/app-developers/bridging/standard-bridge) if you want to learn more about how the bridge works under the hood. +Behind the scenes, Viem uses the [Standard Bridge](/app-developers/bridging/standard-bridge) contracts to transfer ETH and ERC-20 tokens. +Make sure to check out the [Standard Bridge guide](/app-developers/bridging/standard-bridge) if you want to learn more about how the bridge works under the hood. ## Supported networks diff --git a/pages/app-developers/tutorials/cross-dom-solidity.mdx b/pages/app-developers/tutorials/cross-dom-solidity.mdx index 1aa33fb07..feb22428b 100644 --- a/pages/app-developers/tutorials/cross-dom-solidity.mdx +++ b/pages/app-developers/tutorials/cross-dom-solidity.mdx @@ -27,7 +27,7 @@ OP Stack uses a smart contract called the `CrossDomainMessenger` to pass message Both chains have a version of this contract (the `L1CrossDomainMessenger` and the `L2CrossDomainMessenger`). Messages sent from Ethereum to OP Stack are automatically relayed behind the scenes. Messages sent from OP Stack to Ethereum must be explicitly relayed with a second transaction on Ethereum. -Read more about message passing in the guide to [Sending Data Between L1 and L2](/builders/app-developers/bridging/messaging). +Read more about message passing in the guide to [Sending Data Between L1 and L2](/app-developers/bridging/messaging). ## Dependencies @@ -321,7 +321,7 @@ You just learned how you can write Solidity contracts on Sepolia and OP Sepolia You can follow the same pattern to write contracts that can talk to each other on Ethereum and OP Stack. This sort of cross-chain communication is useful for a variety of reasons. -For example, the [Standard Bridge](/builders/app-developers/bridging/standard-bridge) contracts use this same system to bridge ETH and ERC-20 tokens between Ethereum and OP Stack. +For example, the [Standard Bridge](/app-developers/bridging/standard-bridge) contracts use this same system to bridge ETH and ERC-20 tokens between Ethereum and OP Stack. One cool way to take advantage of cross-chain communication is to do most of your heavy lifting on OP Stack and then send a message to Ethereum only when you have important results to share. This way you can take advantage of the low gas costs on OP Stack while still being able to use Ethereum when you need it. diff --git a/pages/app-developers/tutorials/sdk-estimate-costs.mdx b/pages/app-developers/tutorials/sdk-estimate-costs.mdx index 8b47d81c4..6fce2ccdb 100644 --- a/pages/app-developers/tutorials/sdk-estimate-costs.mdx +++ b/pages/app-developers/tutorials/sdk-estimate-costs.mdx @@ -9,11 +9,11 @@ import { Callout, Steps, Tabs } from 'nextra/components' # Estimating transaction costs on OP Stack In this tutorial, you'll learn how to use [viem](https://viem.sh/op-stack/) to estimate the cost of a transaction on OP Mainnet. -You'll learn how to estimate the [execution gas fee](/builders/app-developers/transactions/fees#execution-gas-fee) and the [L1 data fee](/builders/app-developers/transactions/fees#l1-data-fee) independently. +You'll learn how to estimate the [execution gas fee](/app-developers/transactions/fees#execution-gas-fee) and the [L1 data fee](/app-developers/transactions/fees#l1-data-fee) independently. You'll also learn how to estimate the total cost of the transaction all at once. - Check out the full explainer on [OP Stack transaction fees](/builders/app-developers/transactions/fees) for more information on how OP Mainnet charges fees under the hood. + Check out the full explainer on [OP Stack transaction fees](/app-developers/transactions/fees) for more information on how OP Mainnet charges fees under the hood. ## Supported networks diff --git a/pages/connect/contribute/docs-contribute.mdx b/pages/connect/contribute/docs-contribute.mdx index d29189de3..d1472fcdd 100644 --- a/pages/connect/contribute/docs-contribute.mdx +++ b/pages/connect/contribute/docs-contribute.mdx @@ -22,7 +22,7 @@ Optimism Docs (docs.optimism.io) is an open-source project, and we welcome your * [Add or update an FAQ item](https://github.com/ethereum-optimism/docs/issues/new?assignees=\&labels=documentation%2Cfaq%2Ccommunity-request\&projects=\&template=suggest_faq_item.yaml\&title=Suggest+an+FAQ+item): add a new FAQ (question+answer set) to an [existing page](/chain/security/faq#security-model-faq), create a new FAQ page, or update an existing FAQ question/answer set. * [Add or update a troubleshooting item](https://github.com/ethereum-optimism/docs/issues/new?assignees=\&labels=documentation%2Ctroubleshooting%2Ccommunity-request\&projects=\&template=suggest_troubleshooting_item.yaml\&title=Suggest+a+troubleshooting+item): - add a new troubleshooting item (problem+solution set) to an [existing page](/builders/chain-operators/management/troubleshooting), create a new troubleshooting page, or update an existing troubleshooting problem/solution set. + add a new troubleshooting item (problem+solution set) to an [existing page](/operators/chain-operators/management/troubleshooting), create a new troubleshooting page, or update an existing troubleshooting problem/solution set. * [Add a glossary term](https://github.com/ethereum-optimism/docs/issues/new?assignees=\&labels=glossary%2Cdocumentation%2Ccommunity-request\&projects=\&template=suggest_glossary_term.yaml\&title=Suggest+a+glossary+term): help us continue to expand the Optimism [glossary](/connect/resources/glossary). * [Add a faucet to the developer community](https://github.com/ethereum-optimism/developers/tree/main/community): diff --git a/pages/connect/contribute/stack-contribute.mdx b/pages/connect/contribute/stack-contribute.mdx index 22fec79f0..a53ff01ca 100644 --- a/pages/connect/contribute/stack-contribute.mdx +++ b/pages/connect/contribute/stack-contribute.mdx @@ -29,7 +29,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 are considered [OP Stack Hacks](/builders/chain-operators/hacks/overview) — 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 are considered [OP Stack Hacks](/operators/chain-operators/hacks/overview) — 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/). Developer support for OP Stack Hacks is limited — when in doubt, stick to the capabilities of the current release! diff --git a/pages/connect/contribute/style-guide.mdx b/pages/connect/contribute/style-guide.mdx index de6691ba6..ff400ebc8 100644 --- a/pages/connect/contribute/style-guide.mdx +++ b/pages/connect/contribute/style-guide.mdx @@ -84,7 +84,7 @@ See below for when to use title or sentence case. * Use sentence case for body content and short phrases, even when the content is a link. Sentence case means you only capitalize the first letter of the sentence.
- **Example:** If you're trying to figure out how to do something specific as a node operator, you might search our collection of [tutorials](/builders/node-operators/rollup-node) or [suggest a new one](https://github.com/ethereum-optimism/docs/issues). + **Example:** If you're trying to figure out how to do something specific as a node operator, you might search our collection of [tutorials](/operators/node-operators/rollup-node) or [suggest a new one](https://github.com/ethereum-optimism/docs/issues). * Use lowercase in code snippets by default, unless the code block uses capitalization (e.g., for the name of a function or variable) and you are referring to the function or variable elsewhere within the technical documentation.
**Examples**: Run `git add` or Import `useState` @@ -306,15 +306,15 @@ Developers trust that we will lead them to sites or pages related to their readi * Use sentence case when linking to an article without using the exact article title. This causes minimal disruption to the flow of the sentence. The link should use default styling. - **Example**: For something more advanced, we recommend reading through our page on [sending data between L1 and L2](/builders/app-developers/bridging/messaging). + **Example**: For something more advanced, we recommend reading through our page on [sending data between L1 and L2](/app-developers/bridging/messaging). * Use `detailed instructions` link format to refer users to another article with detailed instructions that are important for completing the current task. - **Example**: For detailed instructions, see [Article Title](/builders/app-developers/bridging/standard-bridge). + **Example**: For detailed instructions, see [Article Title](/app-developers/bridging/standard-bridge). * Use the `more information` link format to guide users to a suggested reading that the user may find helpful because it is related to the task/topic, but not essential for completing the current task. - **Example**: For more information, see [Article Title](/builders/app-developers/bridging/standard-bridge). + **Example**: For more information, see [Article Title](/app-developers/bridging/standard-bridge). ## Content types @@ -323,16 +323,16 @@ Content types help manage technical content by defining the purpose and common s | Document type | Purpose | Examples | | ------------------ | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------- | | Overviews | General introduction to a product or feature, provides a happy-path for readers | [Smart Contract Overview](/stack/smart-contracts) | -| Guides | Explain what things are and how they work | [Standard Bridge Guide](/builders/app-developers/bridging/standard-bridge) | -| Quick Start Guides | Briefly explain how to "minimally" get started with a product, often in 30 minutes or less | [Superchain App Quick Start](/builders/app-developers/quick-start) | -| Tutorials | Provide task-oriented guidance with step-by-step "learn by doing" instructions | [Bridging ERC-20 tokens with viem](/builders/app-developers/tutorials/cross-dom-bridge-erc20) | +| Guides | Explain what things are and how they work | [Standard Bridge Guide](/app-developers/bridging/standard-bridge) | +| Quick Start Guides | Briefly explain how to "minimally" get started with a product, often in 30 minutes or less | [Superchain App Quick Start](/app-developers/quick-start) | +| Tutorials | Provide task-oriented guidance with step-by-step "learn by doing" instructions | [Bridging ERC-20 tokens with viem](/app-developers/tutorials/cross-dom-bridge-erc20) | | FAQs | Address frequently asked questions | [FAQ: OP Mainnet Security Model](/chain/security/faq) | -| Troubleshooting | List common troubleshooting scenarios and solutions | [Troubleshooting: Run a Node](/builders/node-operators/management/troubleshooting) | -| Reference | Provide deep, theoretical knowledge of the internal workings of a system, such as API endpoints and specifications | [Node and RPC Providers](/builders/tools/connect/rpc-providers) | +| Troubleshooting | List common troubleshooting scenarios and solutions | [Troubleshooting: Run a Node](/operators/node-operators/management/troubleshooting) | +| Reference | Provide deep, theoretical knowledge of the internal workings of a system, such as API endpoints and specifications | [Node and RPC Providers](/app-developers/tools/connect/rpc-providers) | ### Overviews -Overviews provide a general introduction to a product or service and a happy path for readers on how to navigate a particular set of docs or related features; often used at the top-level of a directory, such as `/builders/app-developers/overview`. When done well, overviews accomplish two essential tasks for users: +Overviews provide a general introduction to a product or service and a happy path for readers on how to navigate a particular set of docs or related features; often used at the top-level of a directory, such as `/app-developers/overview`. When done well, overviews accomplish two essential tasks for users: 1. **organize** the related set of documentation pages to keep developers from getting overloaded by too much information, and 2. **establish a 'happy path'** to direct developers to the right pages in the documentation set based on their user scenario or use case. diff --git a/pages/operators/chain-operators/architecture.mdx b/pages/operators/chain-operators/architecture.mdx index 60f2d2528..5bc5b42ef 100644 --- a/pages/operators/chain-operators/architecture.mdx +++ b/pages/operators/chain-operators/architecture.mdx @@ -123,7 +123,7 @@ Bootnodes facilitate peer discovery for network nodes. They help initialize peer ### Archive RPC Nodes -We recommend setting up some archive nodes for internal RPC usage, primary used by the challenger, proposer and security monitoring tools like [monitorism](/builders/chain-operators/tools/chain-monitoring#monitorism). +We recommend setting up some archive nodes for internal RPC usage, primary used by the challenger, proposer and security monitoring tools like [monitorism](/operators/chain-operators/tools/chain-monitoring#monitorism). ```yaml GETH_GCMODE: "archive" @@ -160,11 +160,11 @@ In addition to the core protocol components, the following offchain services are ### op-conductor -The [op-conductor](/builders/chain-operators/tools/op-conductor) RPC can act as a leader-aware rpc proxy for op-batcher (proxies the necessary op-geth / op-node RPC methods if the node is the leader). +The [op-conductor](/operators/chain-operators/tools/op-conductor) RPC can act as a leader-aware rpc proxy for op-batcher (proxies the necessary op-geth / op-node RPC methods if the node is the leader). ### op-challenger -The [op-challenger](/builders/chain-operators/tools/op-challenger) verifies the correctness of the L2 state by challenging invalid state transitions. This ensures the network's security and validity. +The [op-challenger](/operators/chain-operators/tools/op-challenger) verifies the correctness of the L2 state by challenging invalid state transitions. This ensures the network's security and validity. ### Ethereum L1 nodes @@ -201,7 +201,7 @@ This tool is an RPC request router and proxy. It does the following things: ## Next steps -* Find out how you can support [snap sync](/builders/chain-operators/management/snap-sync) +* Find out how you can support [snap sync](/operators/chain-operators/management/snap-sync) on your chain. -* Find out how you can utilize [blob space](/builders/chain-operators/management/blobs) +* Find out how you can utilize [blob space](/operators/chain-operators/management/blobs) to reduce the transaction fee cost on your chain. diff --git a/pages/operators/chain-operators/configuration/batcher.mdx b/pages/operators/chain-operators/configuration/batcher.mdx index b06ab603b..e3f0bcf8b 100644 --- a/pages/operators/chain-operators/configuration/batcher.mdx +++ b/pages/operators/chain-operators/configuration/batcher.mdx @@ -86,7 +86,7 @@ The minimum tip cap and base fee are also lifted to 2 gwei because it is uncerta The resubmission timeout is increased to a few minutes to give more time for inclusion before bumping the fees because current transaction pool implementations require a doubling of fees for blob transaction replacements. Multi-blob transactions are particularly useful for medium to high-throughput chains, where enough transaction volume exists to fill up 6 blobs in a reasonable amount of time. -You can use [this calculator](https://docs.google.com/spreadsheets/d/12VIiXHaVECG2RUunDSVJpn67IQp9NHFJqUsma2PndpE/edit) for your chain to determine what number of blobs are right for you, and what gas scalar configuration to use. Please also refer to guide on [Using Blobs](/builders/chain-operators/management/blobs) for chain operators. +You can use [this calculator](https://docs.google.com/spreadsheets/d/12VIiXHaVECG2RUunDSVJpn67IQp9NHFJqUsma2PndpE/edit) for your chain to determine what number of blobs are right for you, and what gas scalar configuration to use. Please also refer to guide on [Using Blobs](/operators/chain-operators/management/blobs) for chain operators. ### Set your `--batch-type=1` to use span batches diff --git a/pages/operators/chain-operators/configuration/overview.mdx b/pages/operators/chain-operators/configuration/overview.mdx index e5976b068..cfa5b6e19 100644 --- a/pages/operators/chain-operators/configuration/overview.mdx +++ b/pages/operators/chain-operators/configuration/overview.mdx @@ -23,7 +23,7 @@ documentation for details on configuring each piece. * Be aware that many of these values cannot be changed after deployment or require a complex process to update. Carefully consider and validate all settings during configuration to avoid issues later. - * [Rollup Configuration Documentation](/builders/chain-operators/configuration/rollup) + * [Rollup Configuration Documentation](/operators/chain-operators/configuration/rollup) {

Batcher Configuration

} @@ -31,21 +31,21 @@ documentation for details on configuring each piece. it available for verifiers. These configurations determine the batcher's behavior. - * [Batcher Configuration Documentation](/builders/chain-operators/configuration/batcher) + * [Batcher Configuration Documentation](/operators/chain-operators/configuration/batcher) {

Proposer Configuration

} The proposer is the service that submits the output roots to the L1. These configurations determine the proposer's behavior. - * [Proposer Configuration Documentation](/builders/chain-operators/configuration/proposer) + * [Proposer Configuration Documentation](/operators/chain-operators/configuration/proposer) {

Node Configuration

} The rollup node has a wide array of configurations for both the consensus and execution clients. - * [Node Configuration Documentation](/builders/node-operators/configuration/base-config) + * [Node Configuration Documentation](/operators/node-operators/configuration/base-config) diff --git a/pages/operators/chain-operators/configuration/rollup.mdx b/pages/operators/chain-operators/configuration/rollup.mdx index 766faec29..0a846e0c9 100644 --- a/pages/operators/chain-operators/configuration/rollup.mdx +++ b/pages/operators/chain-operators/configuration/rollup.mdx @@ -275,7 +275,7 @@ How far the L2 timestamp can differ from the actual L1 timestamp. * **Default value:** None * **Recommended value:** 1800 * **Notes:** Must not be `0`. 1800 (30 minutes) is the constant that takes -effect with the [Fjord activation](/builders/node-operators/network-upgrades#fjord). +effect with the [Fjord activation](/operators/node-operators/network-upgrades#fjord). * **Standard Config Requirement:** *** @@ -306,7 +306,7 @@ transactions. After the timeout, the frame is dropped. * **Type:** Number of blocks * **Default value:** 50 * **Recommended value:** -* **Notes:** This default value was introduced in the [Granite network upgrade](/builders/node-operators/network-upgrades#granite) +* **Notes:** This default value was introduced in the [Granite network upgrade](/operators/node-operators/network-upgrades#granite) * **Standard Config Requirement:** *** diff --git a/pages/operators/chain-operators/deploy/genesis.mdx b/pages/operators/chain-operators/deploy/genesis.mdx index 7004e07d8..57148fa33 100644 --- a/pages/operators/chain-operators/deploy/genesis.mdx +++ b/pages/operators/chain-operators/deploy/genesis.mdx @@ -10,7 +10,7 @@ import { Callout } from 'nextra/components' This page is out of date and shows the legacy method for genesis file creation. -For the latest recommended method, use [op-deployer](/builders/chain-operators/tools/op-deployer). +For the latest recommended method, use [op-deployer](/operators/chain-operators/tools/op-deployer). The following guide shows you how to generate the L2 genesis file `genesis.json`. This is a JSON @@ -89,7 +89,7 @@ go run cmd/main.go genesis l2 \ ## Next steps -* Learn how to [initialize](/builders/node-operators/configuration/base-config#initialization-via-genesis-file) +* Learn how to [initialize](/operators/node-operators/configuration/base-config#initialization-via-genesis-file) `op-geth` with your `genesis.json` file. -* Learn how to [initialize](https://docs.optimism.io/builders/node-operators/configuration/base-config#configuring-op-node) `op-node` with your `rollup.json` file. -* Learn more about the off chain [architecture](/builders/chain-operators/architecture). +* Learn how to [initialize](https://docs.optimism.io/operators/node-operators/configuration/base-config#configuring-op-node) `op-node` with your `rollup.json` file. +* Learn more about the off chain [architecture](/operators/chain-operators/architecture). diff --git a/pages/operators/chain-operators/deploy/overview.mdx b/pages/operators/chain-operators/deploy/overview.mdx index 532c99b96..db4e5d3d8 100644 --- a/pages/operators/chain-operators/deploy/overview.mdx +++ b/pages/operators/chain-operators/deploy/overview.mdx @@ -102,6 +102,6 @@ process. ## Next steps -* Discover how to [deploy the smart contracts](/builders/chain-operators/deploy/smart-contracts). -* Find out how to create your [genesis file](/builders/chain-operators/deploy/genesis). -* Explore some chain operator [best practices](/builders/chain-operators/management/best-practices). +* Discover how to [deploy the smart contracts](/operators/chain-operators/deploy/smart-contracts). +* Find out how to create your [genesis file](/operators/chain-operators/deploy/genesis). +* Explore some chain operator [best practices](/operators/chain-operators/management/best-practices). diff --git a/pages/operators/chain-operators/deploy/smart-contracts.mdx b/pages/operators/chain-operators/deploy/smart-contracts.mdx index 2a26e2f10..9b357c6e7 100644 --- a/pages/operators/chain-operators/deploy/smart-contracts.mdx +++ b/pages/operators/chain-operators/deploy/smart-contracts.mdx @@ -10,7 +10,7 @@ import { Callout } from 'nextra/components' This page is out of date and shows the legacy method for smart contract deployment. -For the latest recommended method, use [op-deployer](/builders/chain-operators/tools/op-deployer). +For the latest recommended method, use [op-deployer](/operators/chain-operators/tools/op-deployer). The following guide shows you how to deploy the OP Stack L1 smart contracts. @@ -29,7 +29,7 @@ Deploying your OP Stack contracts requires creating a deployment configuration JSON file. You will create a new deployment configuration file in the following monorepo subdirectory: [packages/contracts-bedrock/deploy-config](https://github.com/ethereum-optimism/optimism/tree/develop/packages/contracts-bedrock/deploy-config) For the full set of deployment configuration options and their meanings, you -can see the [rollup deployment configuration page](/builders/chain-operators/configuration/rollup). +can see the [rollup deployment configuration page](/operators/chain-operators/configuration/rollup). ## Deployment script @@ -58,7 +58,7 @@ forge script -vvv scripts/deploy/Deploy.s.sol:Deploy --sig 'runWithStateDiff()' * `DEPLOY_CONFIG_PATH` is the path on the filesystem that points to a deployment config. The same deployment config JSON file should be used for L1 contracts deployment as when generating the L2 genesis allocs. See the [deploy-config](https://github.com/ethereum-optimism/optimism/tree/develop/packages/contracts-bedrock/deploy-config) - directory for examples and the [rollup configuration page](/builders/chain-operators/configuration/rollup) + directory for examples and the [rollup configuration page](/operators/chain-operators/configuration/rollup) for descriptions of the values. * `IMPL_SALT` env var can be used to set the create2 salt for deploying the implementation contracts. @@ -97,5 +97,5 @@ operators should have a firm understanding of. ## Next steps -* Learn how to [create your genesis file](/builders/chain-operators/deploy/genesis) -* See all [configuration options](/builders/chain-operators/configuration/rollup) and example configurations +* Learn how to [create your genesis file](/operators/chain-operators/deploy/genesis) +* See all [configuration options](/operators/chain-operators/configuration/rollup) and example configurations diff --git a/pages/operators/chain-operators/features/alt-da-mode.mdx b/pages/operators/chain-operators/features/alt-da-mode.mdx index 409190053..e182f58cd 100644 --- a/pages/operators/chain-operators/features/alt-da-mode.mdx +++ b/pages/operators/chain-operators/features/alt-da-mode.mdx @@ -31,7 +31,7 @@ You should use at least the following compatible op\* versions when running your - If you are trying to launch an Alt-DA Mode Chain using a custom gas token, follow the contract deployment instructions in our [Custom Gas Token docs](/builders/chain-operators/features/custom-gas-token.mdx). + If you are trying to launch an Alt-DA Mode Chain using a custom gas token, follow the contract deployment instructions in our [Custom Gas Token docs](/operators/chain-operators/features/custom-gas-token.mdx). @@ -92,7 +92,7 @@ You should use at least the following compatible op\* versions when running your * Chain operators are not posting everything to Ethereum, just commitments, so chain operators will need to determine fee scalars values to charge users. The fee scalar values are network throughput dependent, so values will need to be adjusted by chain operators as needed. * Cost structure for Alt-DA Mode: The transaction data is split up into 128kb chunks and then submitted to your DA Layer. Then, 32 byte commitments are submitted (goes to batch inbox address) to L1 for each 128kb chunk. Then, figure out how much that costs relative to the amount of transactions your chain is putting through. - * Set scalar values inside the deploy config. The example below shows some possible fee scalar values, calculated assuming negligible DA Layer costs, but will need to be adjusted up or down based on network throughput - as a reminder of how to set your scalar values, see [this section](https://docs.optimism.io/builders/chain-operators/management/blobs#update-your-scalar-values-for-blobs) of the docs. + * Set scalar values inside the deploy config. The example below shows some possible fee scalar values, calculated assuming negligible DA Layer costs, but will need to be adjusted up or down based on network throughput - as a reminder of how to set your scalar values, see [this section](https://docs.optimism.io/operators/chain-operators/management/blobs#update-your-scalar-values-for-blobs) of the docs. ``` // Set in Deploy Config diff --git a/pages/operators/chain-operators/features/custom-gas-token.mdx b/pages/operators/chain-operators/features/custom-gas-token.mdx index 59064c2ee..63cc02d1a 100644 --- a/pages/operators/chain-operators/features/custom-gas-token.mdx +++ b/pages/operators/chain-operators/features/custom-gas-token.mdx @@ -48,7 +48,7 @@ An OP Stack chain that uses the custom gas token feature enables an end user to * The [`v2.0.0-beta.3` release](https://github.com/ethereum-optimism/optimism/tree/op-contracts/v2.0.0-beta.3) -enables fee withdrawals to L1 and L2. For more details on these values, see the [Withdrawal Network](/builders/chain-operators/configuration/rollup#withdrawal-network) +enables fee withdrawals to L1 and L2. For more details on these values, see the [Withdrawal Network](/operators/chain-operators/configuration/rollup#withdrawal-network) section of the docs. * Deploy the L1 contracts from `contracts-bedrock` using the following command: diff --git a/pages/operators/chain-operators/hacks/derivation.mdx b/pages/operators/chain-operators/hacks/derivation.mdx index 47651c308..99f22e87a 100644 --- a/pages/operators/chain-operators/hacks/derivation.mdx +++ b/pages/operators/chain-operators/hacks/derivation.mdx @@ -40,4 +40,4 @@ Like with events, transactions on an OP Stack chain can be triggered whenever a The Derivation layer is one of the most flexible layers of the stack. Transactions can be generated from all sorts of raw input data and can be triggered from all sorts of conditions. You can derive transactions from any piece of data that can be found in the Data Availability layer modules! -[Tutorial: Adding attributes to the derivation function](/builders/chain-operators/tutorials/adding-derivation-attributes). +[Tutorial: Adding attributes to the derivation function](/operators/chain-operators/tutorials/adding-derivation-attributes). diff --git a/pages/operators/chain-operators/hacks/execution.mdx b/pages/operators/chain-operators/hacks/execution.mdx index 495ceb8a1..95c261b0c 100644 --- a/pages/operators/chain-operators/hacks/execution.mdx +++ b/pages/operators/chain-operators/hacks/execution.mdx @@ -38,4 +38,4 @@ It's also possible to create alternative execution client implementations to imp The OP Stack allows you to replace the EVM with *any* state transition function, as long as the transition can be triggered via the Engine API. This has, for example, been used to implement an OP Stack chain that runs a GameBoy emulator rather than the EVM. -[Tutorial: Adding a precompile](/builders/chain-operators/tutorials/adding-precompiles). +[Tutorial: Adding a precompile](/operators/chain-operators/tutorials/adding-precompiles). diff --git a/pages/operators/chain-operators/management/best-practices.mdx b/pages/operators/chain-operators/management/best-practices.mdx index d5bcd8ae6..ae9a80a28 100644 --- a/pages/operators/chain-operators/management/best-practices.mdx +++ b/pages/operators/chain-operators/management/best-practices.mdx @@ -80,7 +80,7 @@ GETH_TXPOOL_LIFETIME: "1h" GETH_TXPOOL_NOLOCALS: "true" ``` -For additional information about these flags, check out our [Execution Layer Configuration Options](/builders/node-operators/configuration/execution-config) doc. +For additional information about these flags, check out our [Execution Layer Configuration Options](/operators/node-operators/configuration/execution-config) doc. ## Write your own runbooks diff --git a/pages/operators/chain-operators/management/blobs.mdx b/pages/operators/chain-operators/management/blobs.mdx index 605e1b296..d84a3fd67 100644 --- a/pages/operators/chain-operators/management/blobs.mdx +++ b/pages/operators/chain-operators/management/blobs.mdx @@ -23,7 +23,7 @@ This guide walks you through how to switch to using blobs for your chain after E The first step to switching to submit data with Blobs is to calculate the scalar values you wish to set for the formula to charge users fees. To determine the scalar values to use for your chain, you can utilize this [fee parameter calculator](https://docs.google.com/spreadsheets/d/1V3CWpeUzXv5Iopw8lBSS8tWoSzyR4PDDwV9cu2kKOrs/edit) - to get a better estimate for scalar values on your chain. Input the average transaction per day your chain is processing, the types of transactions that occur on your chain, the [`OP_BATCHER_MAX_CHANNEL_DURATION`](/builders/chain-operators/configuration/batcher#setting-your--op_batcher_max_channel_duration) you have parameterized on your `op-batcher`, and the target margin you wish to charge users on top of your L1 costs. The following + to get a better estimate for scalar values on your chain. Input the average transaction per day your chain is processing, the types of transactions that occur on your chain, the [`OP_BATCHER_MAX_CHANNEL_DURATION`](/operators/chain-operators/configuration/batcher#setting-your--op_batcher_max_channel_duration) you have parameterized on your `op-batcher`, and the target margin you wish to charge users on top of your L1 costs. The following information is tuned to a network like OP Mainnet. For more details on fee scalar, see [Transaction Fees, Ecotone section](/stack/transactions/fees#ecotone). @@ -85,8 +85,8 @@ This guide walks you through how to switch to using blobs for your chain after E Steps to configure the batcher: * Configure `OP_BATCHER_DATA_AVAILABILITY_TYPE=blobs`. The batcher will have to be restarted for it to take effect. - * Ensure your `OP_BATCHER_MAX_CHANNEL_DURATION` is properly set to maximize your fee savings. See [OP Batcher Max Channel Configuration](/builders/chain-operators/configuration/batcher#set-your--op_batcher_max_channel_duration) for more details. - * Optionally, you can configure your batcher to support multi-blobs. See [Multi-Blob Batcher Configuration](/builders/chain-operators/configuration/batcher#configure-your-multi-blob-batcher) for more details. + * Ensure your `OP_BATCHER_MAX_CHANNEL_DURATION` is properly set to maximize your fee savings. See [OP Batcher Max Channel Configuration](/operators/chain-operators/configuration/batcher#set-your--op_batcher_max_channel_duration) for more details. + * Optionally, you can configure your batcher to support multi-blobs. See [Multi-Blob Batcher Configuration](/operators/chain-operators/configuration/batcher#configure-your-multi-blob-batcher) for more details. ## Switch back to using calldata @@ -128,10 +128,10 @@ blobs back to using calldata. * Configure `OP_BATCHER_DATA_AVAILABILITY_TYPE=calldata`. The batcher will have to be restarted for it to take effect. - * Ensure your `OP_BATCHER_MAX_CHANNEL_DURATION` is properly set to maximize savings. **NOTE:** While setting a high value here will lower costs, it will be less meaningful than for low throughput chains using blobs. See [OP Batcher Max Channel Configuration](/builders/chain-operators/configuration/batcher#set-your--op_batcher_max_channel_duration) for more details. + * Ensure your `OP_BATCHER_MAX_CHANNEL_DURATION` is properly set to maximize savings. **NOTE:** While setting a high value here will lower costs, it will be less meaningful than for low throughput chains using blobs. See [OP Batcher Max Channel Configuration](/operators/chain-operators/configuration/batcher#set-your--op_batcher_max_channel_duration) for more details. ## Other considerations * For information on L1 Data Fee changes related to the Ecotone upgrade, visit the [Transaction Fees page](/stack/transactions/fees#ecotone). -* If you want to enable archive nodes, you will need to access a blob archiver service. You can use [Optimism's](/builders/node-operators/management/snapshots#op-mainnet-archive-node) or [run your own](/builders/chain-operators/tools/explorer#create-an-archive-node). +* If you want to enable archive nodes, you will need to access a blob archiver service. You can use [Optimism's](/operators/node-operators/management/snapshots#op-mainnet-archive-node) or [run your own](/operators/chain-operators/tools/explorer#create-an-archive-node). diff --git a/pages/operators/chain-operators/management/operations.mdx b/pages/operators/chain-operators/management/operations.mdx index 0750d965d..3306c315d 100644 --- a/pages/operators/chain-operators/management/operations.mdx +++ b/pages/operators/chain-operators/management/operations.mdx @@ -193,5 +193,5 @@ If you do it this way, you won't have to wait until the transactions are written ## Next steps -* See the [Node Configuration](/builders/node-operators/configuration/base-config) guide for additional explanation or customization. +* See the [Node Configuration](/operators/node-operators/configuration/base-config) guide for additional explanation or customization. * If you experience difficulty at any stage of this process, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). diff --git a/pages/operators/chain-operators/management/snap-sync.mdx b/pages/operators/chain-operators/management/snap-sync.mdx index 97e372754..ee7175e0d 100644 --- a/pages/operators/chain-operators/management/snap-sync.mdx +++ b/pages/operators/chain-operators/management/snap-sync.mdx @@ -15,7 +15,7 @@ Snap sync works by downloading a snapshot of the state from other nodes on the n This means that performing a snap sync is significantly faster than performing a full sync. * Snap sync enables node operators on your network to sync faster. -* Snap sync removes the need for nodes on your post Ecotone network to run a [blob archiver](/builders/node-operators/management/blobs). +* Snap sync removes the need for nodes on your post Ecotone network to run a [blob archiver](/operators/node-operators/management/blobs). ## Enable snap sync for chains @@ -23,8 +23,8 @@ To enable snap sync, chain operators need to spin up a node which is exposed to For snap sync, all `op-geth` nodes should expose port `30303` TCP and `30303` UDP to easily find other op-geth nodes to sync from. - * If you set the port with [`--discovery.port`](/builders/node-operators/configuration/execution-config#discoveryport), then you must open the port specified for UDP. - * If you set [`--port`](/builders/node-operators/configuration/execution-config#port), then you must open the port specified for TCP. + * If you set the port with [`--discovery.port`](/operators/node-operators/configuration/execution-config#discoveryport), then you must open the port specified for UDP. + * If you set [`--port`](/operators/node-operators/configuration/execution-config#port), then you must open the port specified for TCP. * The only exception is for sequencers and transaction ingress nodes. @@ -32,14 +32,14 @@ For snap sync, all `op-geth` nodes should expose port `30303` TCP and `30303` UD ### Setup a snap sync node * Expose port `30303` (`op-geth`'s default discovery port) to the internet on TCP and UDP. - * Disable transaction gossip with the [`--rollup.disabletxpoolgossip`](/builders/node-operators/configuration/execution-config#rollupdisabletxpoolgossip) flag + * Disable transaction gossip with the [`--rollup.disabletxpoolgossip`](/operators/node-operators/configuration/execution-config#rollupdisabletxpoolgossip) flag ### Enable snap sync on your network - * Follow the [Node operator snap sync guide](/builders/node-operators/management/snap-sync#enable-snap-sync-for-your-node) to enable snap sync for your chain network. + * Follow the [Node operator snap sync guide](/operators/node-operators/management/snap-sync#enable-snap-sync-for-your-node) to enable snap sync for your chain network. ## Next Steps -* See the [Node configuration](/builders/node-operators/configuration/base-config#configuration) guide for additional explanation or customization. +* See the [Node configuration](/operators/node-operators/configuration/base-config#configuration) guide for additional explanation or customization. * If you experience difficulty at any stage of this process, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). diff --git a/pages/operators/chain-operators/self-hosted.mdx b/pages/operators/chain-operators/self-hosted.mdx index f206a840f..0edd8be4b 100644 --- a/pages/operators/chain-operators/self-hosted.mdx +++ b/pages/operators/chain-operators/self-hosted.mdx @@ -19,14 +19,14 @@ There are two main steps to get started building your own self-hosted OP Chain: To work with OP Chains, you'll need to understand the fundamental components of OP Chains. - * **Chain Architecture**: OP Chains use execution and consensus clients as well as the OP Stack's privileged roles. For more details, see the [Chain Architecture](/builders/chain-operators/architecture) guide. + * **Chain Architecture**: OP Chains use execution and consensus clients as well as the OP Stack's privileged roles. For more details, see the [Chain Architecture](/operators/chain-operators/architecture) guide. * **Smart Contracts**: OP Chains use several smart contracts on the L1 blockchain to manage aspects of the Rollup. Each OP Stack chain has its own set of [L1 smart contracts](/stack/smart-contracts), [L2 predeploy contracts](/stack/smart-contracts), - and [L2 preinstall contracts](/builders/chain-operators/features/preinstalls) + and [L2 preinstall contracts](/operators/chain-operators/features/preinstalls) that are deployed when the chain is created. - * **Preinstalls**: OP Chains come with [preinstalled core contracts](/builders/chain-operators/features/preinstalls), making them usable as soon as a chain is initialized on the OP Stack. + * **Preinstalls**: OP Chains come with [preinstalled core contracts](/operators/chain-operators/features/preinstalls), making them usable as soon as a chain is initialized on the OP Stack. You should only use governance approved and audited smart contracts. The monorepo has them tagged with the following pattern `op-contracts/vX.X.X` and you can review the release notes for details on the changes. @@ -35,7 +35,7 @@ There are two main steps to get started building your own self-hosted OP Chain: {

Launch Your OP Stack Testnet Chain

} * Now, you are ready to spin up your testnet chain. - * Just follow the [Creating Your Own L2 Rollup Testnet](/builders/chain-operators/tutorials/create-l2-rollup) tutorial to get started. + * Just follow the [Creating Your Own L2 Rollup Testnet](/operators/chain-operators/tutorials/create-l2-rollup) tutorial to get started. ## Configure your chain @@ -45,22 +45,22 @@ OP Chains can be configured for throughput, cost, and other decentralization tra {

Setup Key Management and Privileged Roles

} - * Configure hot wallets and cold wallets using the guide for [Managing Your Keys](/builders/chain-operators/management/key-management). + * Configure hot wallets and cold wallets using the guide for [Managing Your Keys](/operators/chain-operators/management/key-management). * Refer to the [Privileged Roles](/chain/security/privileged-roles) guide for detailed security information. {

Make Standard Chain Configurations

} - * Configure your [OP Chain parameters](/builders/chain-operators/configuration/overview) based on your particular tradeoffs. You'll need to configure the **rollup**, **batcher**, and **proposer** for optimal performance. - * Update your batcher to [post transaction data within blobs](/builders/chain-operators/management/blobs) instead of call data to maximize your fee savings. - * Enable [snap sync](/builders/chain-operators/management/snap-sync) on your OP Chain to significantly improve the experience and speed of syncing an OP Stack node. + * Configure your [OP Chain parameters](/operators/chain-operators/configuration/overview) based on your particular tradeoffs. You'll need to configure the **rollup**, **batcher**, and **proposer** for optimal performance. + * Update your batcher to [post transaction data within blobs](/operators/chain-operators/management/blobs) instead of call data to maximize your fee savings. + * Enable [snap sync](/operators/chain-operators/management/snap-sync) on your OP Chain to significantly improve the experience and speed of syncing an OP Stack node. {

Set Public RPC Endpoint

} - * Set the [public RPC Endpoint](/builders/chain-operators/architecture), so your OP Chain can handle large volumes of RPC requests from your users. + * Set the [public RPC Endpoint](/operators/chain-operators/architecture), so your OP Chain can handle large volumes of RPC requests from your users. {

Enable Analytics for Onchain Data

} - * Enable [analytics tracking for your OP Chain](/builders/node-operators/management/metrics), to immediately generate onchain metrics after mainnet launch. + * Enable [analytics tracking for your OP Chain](/operators/node-operators/management/metrics), to immediately generate onchain metrics after mainnet launch. ## Test your chain @@ -72,15 +72,15 @@ Before launching on Mainnet, thoroughly test and debug OP Chain contracts, featu Block explorers allow you to access transaction history and conduct chain debugging. - * Option 1: Select an [external block explorer](/builders/tools/build/block-explorers) to use with your OP Chain. - * Option 2: Deploy your own block explorer for your OP Chain, such as [Blockscout](/builders/chain-operators/tools/explorer). + * Option 1: Select an [external block explorer](/app-developers/tools/build/block-explorers) to use with your OP Chain. + * Option 2: Deploy your own block explorer for your OP Chain, such as [Blockscout](/operators/chain-operators/tools/explorer). {

Send Test Transactions

} As part of testing your OP Chain, you'll need to send test or example transactions to the new network. * Test [sending L2 transactions](https://github.com/ethereum-optimism/tx-overload) to understand how much load your new chain can handle. - * Trace [deposits and withdrawals](/builders/app-developers/tutorials/sdk-trace-txns) using the SDK or viem. + * Trace [deposits and withdrawals](/app-developers/tutorials/sdk-trace-txns) using the SDK or viem. * Run [basic transaction tests](https://metamask.io/) using Metamask. diff --git a/pages/operators/chain-operators/tools/chain-monitoring.mdx b/pages/operators/chain-operators/tools/chain-monitoring.mdx index 1dac6ef35..22e154211 100644 --- a/pages/operators/chain-operators/tools/chain-monitoring.mdx +++ b/pages/operators/chain-operators/tools/chain-monitoring.mdx @@ -86,8 +86,8 @@ The general steps for enabling offchain monitoring are pretty consistent for all ### `op-node` -`op-node` metrics and monitoring is detailed in the [Node Metrics and Monitoring](/builders/node-operators/management/metrics) guide. To enable metrics, pass the `--metrics.enabled` flag to `op-node` and follow the steps above for customization options. -See [this curated list](/builders/node-operators/management/metrics#important-metrics) for important metrics to track specifically for `op-node`. +`op-node` metrics and monitoring is detailed in the [Node Metrics and Monitoring](/operators/node-operators/management/metrics) guide. To enable metrics, pass the `--metrics.enabled` flag to `op-node` and follow the steps above for customization options. +See [this curated list](/operators/node-operators/management/metrics#important-metrics) for important metrics to track specifically for `op-node`. ### `op-geth` @@ -97,13 +97,13 @@ To enable metrics, pass the `--metrics.enabled` flag to the op-geth. You can cus To enable metrics, pass the `--metrics.enabled` flag to the op-proposer. You can customize the metrics port and address via the `--metrics.port` and `--metrics.addr` flags, respectively. -You can find more information about these flags in our [Proposer configuration doc](/builders/chain-operators/configuration/proposer#metricsenabled). +You can find more information about these flags in our [Proposer configuration doc](/operators/chain-operators/configuration/proposer#metricsenabled). ### `op-batcher` To enable metrics, pass the `--metrics.enabled` flag to the op-batcher. You can customize the metrics port and address via the `--metrics.port` and `--metrics.addr` flags, respectively. -You can find more information about these flags in our [Batcher configuration doc](/builders/chain-operators/configuration/proposer#metricsenabled). +You can find more information about these flags in our [Batcher configuration doc](/operators/chain-operators/configuration/proposer#metricsenabled). ### `op-challenger` diff --git a/pages/operators/chain-operators/tools/op-conductor.mdx b/pages/operators/chain-operators/tools/op-conductor.mdx index 50acf2fcb..2d3714ff5 100644 --- a/pages/operators/chain-operators/tools/op-conductor.mdx +++ b/pages/operators/chain-operators/tools/op-conductor.mdx @@ -36,7 +36,7 @@ The design of the `op-conductor` provides the following guarantees: ## Design -![op-conductor.](/img/builders/chain-operators/op-conductor.svg) +![op-conductor.](/img/operators/chain-operators/op-conductor.svg) **On a high level, `op-conductor` serves the following functions:** diff --git a/pages/operators/chain-operators/tools/proxyd.mdx b/pages/operators/chain-operators/tools/proxyd.mdx index e2b7cf6ef..51a43b7c4 100644 --- a/pages/operators/chain-operators/tools/proxyd.mdx +++ b/pages/operators/chain-operators/tools/proxyd.mdx @@ -69,8 +69,8 @@ Extensive metrics are available to monitor request latency, error rates, backend ## Next steps -* Read about the [OP Stack chain architecture](/builders/chain-operators/architecture). -* Find out how you can support [snap sync](/builders/chain-operators/management/snap-sync). +* Read about the [OP Stack chain architecture](/operators/chain-operators/architecture). +* Find out how you can support [snap sync](/operators/chain-operators/management/snap-sync). on your chain. -* Find out how you can utilize [blob space](/builders/chain-operators/management/blobs) +* Find out how you can utilize [blob space](/operators/chain-operators/management/blobs) to reduce the transaction fee cost on your chain. diff --git a/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx b/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx index 0090367f1..7179576a7 100644 --- a/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx +++ b/pages/operators/chain-operators/tutorials/create-l2-rollup.mdx @@ -22,7 +22,7 @@ You'll walk through the full deployment process and teach you all of the compone It's useful to understand what each of these components does before you start deploying your chain. To learn about the different components please -read the [deployment overview page](/builders/chain-operators/deploy/overview). +read the [deployment overview page](/operators/chain-operators/deploy/overview). You can use this testnet to experiment and perform tests, or you can choose to modify the chain to adapt it to your own needs. **The OP Stack is free and open source software licensed entirely under the MIT license**. @@ -635,7 +635,7 @@ You can add the following options to the `op-node` command to enable peer-to-pee --p2p.listen.udp=9003 \ ``` -You can alternatively also remove the [--p2p.static](/builders/node-operators/configuration/consensus-config#p2pstatic) option, but you may see failed requests from other chains using the same chain ID. +You can alternatively also remove the [--p2p.static](/operators/node-operators/configuration/consensus-config#p2pstatic) option, but you may see failed requests from other chains using the same chain ID. @@ -681,7 +681,7 @@ cd ~/optimism/op-batcher ``` -The [`--max-channel-duration=n`](/builders/chain-operators/configuration/batcher#set-your--op_batcher_max_channel_duration) setting tells the batcher to write all the data to L1 every `n` L1 blocks. +The [`--max-channel-duration=n`](/operators/chain-operators/configuration/batcher#set-your--op_batcher_max_channel_duration) setting tells the batcher to write all the data to L1 every `n` L1 blocks. When it is low, transactions are written to L1 frequently and other nodes can synchronize from L1 quickly. When it is high, transactions are written to L1 less frequently and the batcher spends less ETH. If you want to reduce costs, either set this value to 0 to disable it or increase it to a higher value. diff --git a/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx b/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx index 8627d4385..63ce7762a 100644 --- a/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx +++ b/pages/operators/chain-operators/tutorials/integrating-da-layer.mdx @@ -42,7 +42,7 @@ Our suggestion is for every DA Layer to build and maintain their own DA Server, ## Run Alt-DA -Follow our guide on [how to operate an Alt-DA Mode chain](/builders/chain-operators/features/alt-da-mode), except instead of using the S3 DA server, use the DA server that you built. +Follow our guide on [how to operate an Alt-DA Mode chain](/operators/chain-operators/features/alt-da-mode), except instead of using the S3 DA server, use the DA server that you built. ## Next steps diff --git a/pages/operators/node-operators/architecture.mdx b/pages/operators/node-operators/architecture.mdx index 014f7b8dc..d7de1dc35 100644 --- a/pages/operators/node-operators/architecture.mdx +++ b/pages/operators/node-operators/architecture.mdx @@ -37,6 +37,6 @@ Legacy Geth is **not** required and is typically only necessary if you want to m ## Next steps -* To get your node up and running, start with the [run a node from docker](/builders/node-operators/tutorials/node-from-docker) or [build a node from source](/builders/node-operators/tutorials/node-from-source) tutorial. +* To get your node up and running, start with the [run a node from docker](/operators/node-operators/tutorials/node-from-docker) or [build a node from source](/operators/node-operators/tutorials/node-from-source) tutorial. * If you've already got your node up and running, check out the [Node Metrics and Monitoring Guide](./management/metrics) to learn how to keep tabs on your node and make sure it keeps running smoothly. * If you run into any problems, please visit the [Node Troubleshooting Guide](./management/troubleshooting) for help. diff --git a/pages/operators/node-operators/configuration/base-config.mdx b/pages/operators/node-operators/configuration/base-config.mdx index 610fd7fe6..8bc79043d 100644 --- a/pages/operators/node-operators/configuration/base-config.mdx +++ b/pages/operators/node-operators/configuration/base-config.mdx @@ -30,7 +30,7 @@ Depending on the network you're running, initialization is done one of three way 1. **With Network Flags:** This initializes the genesis information and chain configuration from the [superchain-registry](https://github.com/ethereum-optimism/superchain-registry). 2. **With a Genesis File:** This is for deployments that are not migrated from a legacy network (i.e. OP Sepolia). In this case, you'll use a genesis file and initialize the data directory via `geth init`. -3. **With a Data Directory:** This is used for networks that are migrated from a legacy network. This currently **only** includes OP Mainnet. In this case, you'll download a preconfigured data directory and extract it. No further initialization is necessary in this case, because the data directory contains the network's genesis information. This method can be bypassed if you utilize [snap sync](/builders/node-operators/management/snap-sync). +3. **With a Data Directory:** This is used for networks that are migrated from a legacy network. This currently **only** includes OP Mainnet. In this case, you'll download a preconfigured data directory and extract it. No further initialization is necessary in this case, because the data directory contains the network's genesis information. This method can be bypassed if you utilize [snap sync](/operators/node-operators/management/snap-sync). Regardless of how `op-geth` is initialized, you'll need to ensure that you have sufficient disk space available to store the network's data. As of this writing, the OP Mainnet data directory is \~1.6TB for a full node and \~5TB for an archival node. @@ -138,8 +138,8 @@ Consult [Geth's documentation](https://geth.ethereum.org/docs/) for more informa `op-node` is a standalone, statically linked binary. It stores no state, and requires no initialization. It consumes configuration parameters either via the command line or environment variables. For some networks, the Rollup Node also requires a configuration file (called `rollup.json` or the "rollup config") that configures network-specific genesis parameters. For official networks like OP Sepolia and OP Mainnet, the genesis config is hardcoded in the `op-node` software and can be specified via a `--network` flag. -Following the [Ecotone upgrade](/builders/node-operators/network-upgrades#ecotone) -node operators must set an L1 beacon value to retrieve [blobs](/builders/node-operators/management/blobs) +Following the [Ecotone upgrade](/operators/node-operators/network-upgrades#ecotone) +node operators must set an L1 beacon value to retrieve [blobs](/operators/node-operators/management/blobs) from a Beacon node. @@ -217,6 +217,6 @@ The term *historical execution* refers to RPC methods that need to execute trans If you do not need these RPC methods for historical data, then you do not need to run Legacy Geth at all. ## Next steps -* See the [op-node configuration](/builders/node-operators/configuration/consensus-config) guide for additional configuration options for `op-node` and the Consensus-Layer. -* Similarly, visit the [op-geth configuration](/builders/node-operators/configuration/execution-config) guide for additional configuration options for `op-geth` and Execution-Layer. +* See the [op-node configuration](/operators/node-operators/configuration/consensus-config) guide for additional configuration options for `op-node` and the Consensus-Layer. +* Similarly, visit the [op-geth configuration](/operators/node-operators/configuration/execution-config) guide for additional configuration options for `op-geth` and Execution-Layer. * If you run into any problems, please reach out to our [developer support forum](https://github.com/ethereum-optimism/developers/discussions) for help. diff --git a/pages/operators/node-operators/configuration/consensus-config.mdx b/pages/operators/node-operators/configuration/consensus-config.mdx index 48246b162..246ed538b 100644 --- a/pages/operators/node-operators/configuration/consensus-config.mdx +++ b/pages/operators/node-operators/configuration/consensus-config.mdx @@ -592,7 +592,7 @@ Hex-encoded private key for signing off on p2p application messages as sequencer ### p2p.static -Comma-separated multiaddr-format(an unsigned address, containing: IP, TCP port, [PeerID](/builders/node-operators/json-rpc#opp2p_self)) peer list. Static connections to make and +Comma-separated multiaddr-format(an unsigned address, containing: IP, TCP port, [PeerID](/operators/node-operators/json-rpc#opp2p_self)) peer list. Static connections to make and maintain, these peers will be regarded as trusted. Addresses of the local peer are ignored. Duplicate/Alternative addresses for the same peer all apply, but only a single connection per peer is maintained. diff --git a/pages/operators/node-operators/json-rpc.mdx b/pages/operators/node-operators/json-rpc.mdx index 1f0ca452c..8131d9a9b 100644 --- a/pages/operators/node-operators/json-rpc.mdx +++ b/pages/operators/node-operators/json-rpc.mdx @@ -14,7 +14,7 @@ There are several OP Mainnet components with an RPC API, which are reviewed in t Use [`eth_gasPrice`](https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_gasprice) instead of `rollup_gasPrices` for the L2 gas price. For the L1 gas price, you can call the [`GasPriceOracle`'s `l1BaseFee` function](https://optimistic.etherscan.io/address/0x420000000000000000000000000000000000000F#readProxyContract#F11). - If you want to estimate the cost of a transaction, you can [use the SDK](/builders/app-developers/tutorials/sdk-estimate-costs). + If you want to estimate the cost of a transaction, you can [use the SDK](/app-developers/tutorials/sdk-estimate-costs). ## op-node diff --git a/pages/operators/node-operators/management/blobs.mdx b/pages/operators/node-operators/management/blobs.mdx index 5f738f79f..d80ca9353 100644 --- a/pages/operators/node-operators/management/blobs.mdx +++ b/pages/operators/node-operators/management/blobs.mdx @@ -22,7 +22,7 @@ These steps are necessary for EVERY node operator: ### Update to the latest release -See the [Software Releases](/builders/node-operators/releases) page for the minimum release version. +See the [Software Releases](/operators/node-operators/releases) page for the minimum release version. ### Configure the Ecotone activation date diff --git a/pages/operators/node-operators/management/snap-sync.mdx b/pages/operators/node-operators/management/snap-sync.mdx index 68bf869c9..bef6bbc91 100644 --- a/pages/operators/node-operators/management/snap-sync.mdx +++ b/pages/operators/node-operators/management/snap-sync.mdx @@ -23,8 +23,8 @@ This means that performing a Snap Sync is significantly faster than performing a For snap sync, all `op-geth` nodes should expose port `30303` TCP and `30303` UDP to easily find other op-geth nodes to sync from. - * If you set the port with [`--discovery.port`](/builders/node-operators/configuration/execution-config#discoveryport), then you must open the port specified for UDP. - * If you set [`--port`](/builders/node-operators/configuration/execution-config#port), then you must open the port specified for TCP. + * If you set the port with [`--discovery.port`](/operators/node-operators/configuration/execution-config#discoveryport), then you must open the port specified for UDP. + * If you set [`--port`](/operators/node-operators/configuration/execution-config#port), then you must open the port specified for TCP. * The only exception is for sequencers and transaction ingress nodes. @@ -102,6 +102,6 @@ To enable execution layer sync for these clients, set the following flags on `op ## Next steps -* See the [Node Configuration](/builders/node-operators/configuration/base-config#configuration) guide for additional explanation or customization. -* To enable snap sync for your chain, see [Using Snap Sync for Chain Operators](/builders/chain-operators/management/snap-sync). +* See the [Node Configuration](/operators/node-operators/configuration/base-config#configuration) guide for additional explanation or customization. +* To enable snap sync for your chain, see [Using Snap Sync for Chain Operators](/operators/chain-operators/management/snap-sync). * If you experience difficulty at any stage of this process, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). diff --git a/pages/operators/node-operators/network-upgrades.mdx b/pages/operators/node-operators/network-upgrades.mdx index 7e342318a..9ef8b8cc1 100644 --- a/pages/operators/node-operators/network-upgrades.mdx +++ b/pages/operators/node-operators/network-upgrades.mdx @@ -72,5 +72,5 @@ then the software is deployed on production networks. ## More information -* To check for the latest node software, see the [Software Releases](/builders/node-operators/releases). +* 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/). diff --git a/pages/operators/node-operators/rollup-node.mdx b/pages/operators/node-operators/rollup-node.mdx index 19c82347c..32bc050a1 100644 --- a/pages/operators/node-operators/rollup-node.mdx +++ b/pages/operators/node-operators/rollup-node.mdx @@ -19,19 +19,19 @@ Before building your node, you will learn fundamental aspects of OP Stack rollup These are the two fundamental components of an OP Stack rollup node: - * **Node Architecture**: OP Stack rollup nodes use the rollup node and execution client and can also support legacy geth for pre-bedrock historical execution requests. For more details, see the [Node Architecture](/builders/node-operators/architecture) guide. - * **Network Upgrades**: Network upgrades for OP Stack rollup nodes are generally [activated by timestamps](/builders/node-operators/network-upgrades#activations). Failing to upgrade your node before the timestamp causes a chain divergence, requiring you to resync your node to reconcile the chain. Follow the established [Node Upgrade Process](/builders/node-operators/network-upgrades#upgrade-process) to avoid chain divergence. + * **Node Architecture**: OP Stack rollup nodes use the rollup node and execution client and can also support legacy geth for pre-bedrock historical execution requests. For more details, see the [Node Architecture](/operators/node-operators/architecture) guide. + * **Network Upgrades**: Network upgrades for OP Stack rollup nodes are generally [activated by timestamps](/operators/node-operators/network-upgrades#activations). Failing to upgrade your node before the timestamp causes a chain divergence, requiring you to resync your node to reconcile the chain. Follow the established [Node Upgrade Process](/operators/node-operators/network-upgrades#upgrade-process) to avoid chain divergence. - If you are building an archive node on OP Mainnet, then you'll need a [node snapshot](/builders/node-operators/management/snapshots). This is **not required** for nodes using [snap sync](/builders/node-operators/management/snap-sync). + If you are building an archive node on OP Mainnet, then you'll need a [node snapshot](/operators/node-operators/management/snapshots). This is **not required** for nodes using [snap sync](/operators/node-operators/management/snap-sync). {

Build Your OP Stack Node

} Now, you are ready to build your OP Stack rollup node. You have two options for this: - * **Option 1:** Follow the [Running a Node with Docker](/builders/node-operators/tutorials/node-from-docker) tutorial, which gets your OP Stack rollup node up and running without having to build it from source. - * **Option 2:** Follow the [Building a Node from Source](/builders/node-operators/tutorials/node-from-source) tutorial, if you need to use a specific architecture or want to inspect the source code of your OP Stack rollup node. + * **Option 1:** Follow the [Running a Node with Docker](/operators/node-operators/tutorials/node-from-docker) tutorial, which gets your OP Stack rollup node up and running without having to build it from source. + * **Option 2:** Follow the [Building a Node from Source](/operators/node-operators/tutorials/node-from-source) tutorial, if you need to use a specific architecture or want to inspect the source code of your OP Stack rollup node. ## Configure your node @@ -41,17 +41,17 @@ OP Stack rollup nodes can be configured for individual needs. The following step {

Setup Your Working Base Configs

} - * Configure `op-geth` using the [base configuration](/builders/node-operators/configuration/base-config#working-base-configuration). - * Set the [recommended flags for `op-geth`](/builders/node-operators/configuration/base-config#recommended-flags-for-op-geth-configuration) to follow best practices for configuring OP Stack rollup nodes. - * Configure `op-node` using the [base configuration](/builders/node-operators/configuration/base-config#working-base-configuration-1). + * Configure `op-geth` using the [base configuration](/operators/node-operators/configuration/base-config#working-base-configuration). + * Set the [recommended flags for `op-geth`](/operators/node-operators/configuration/base-config#recommended-flags-for-op-geth-configuration) to follow best practices for configuring OP Stack rollup nodes. + * Configure `op-node` using the [base configuration](/operators/node-operators/configuration/base-config#working-base-configuration-1). {

Enable Snap Sync

} - * Enable [snap sync](/builders/node-operators/management/snap-sync) for your node to significantly improve the experience and speed of syncing an OP Stack node. + * Enable [snap sync](/operators/node-operators/management/snap-sync) for your node to significantly improve the experience and speed of syncing an OP Stack node. This is an **optional** feature but highly recommended for node providers. - Additional configuration options exist for [`op-geth`](/builders/node-operators/configuration/execution-config) and [`op-node`](/builders/node-operators/configuration/consensus-config), respectively. + Additional configuration options exist for [`op-geth`](/operators/node-operators/configuration/execution-config) and [`op-node`](/operators/node-operators/configuration/consensus-config), respectively. @@ -65,17 +65,17 @@ Now, you will run your node and set your node debugging log level for more granu You will now run your node from source for your Superchain network. Here are your options. - The tutorial [Building a Node from Source](/builders/node-operators/tutorials/node-from-source) is a **pre-requisite** to running your node from source and must be completed first. + The tutorial [Building a Node from Source](/operators/node-operators/tutorials/node-from-source) is a **pre-requisite** to running your node from source and must be completed first. - * **Option 1:** Follow the [Running an OP Sepolia Node from Source](/builders/node-operators/tutorials/testnet) tutorial. - * **Option 2:** Follow the [Running an OP Mainnet Node from Source](/builders/node-operators/tutorials/mainnet) tutorial, if you plan to run a full node or archive node. + * **Option 1:** Follow the [Running an OP Sepolia Node from Source](/operators/node-operators/tutorials/testnet) tutorial. + * **Option 2:** Follow the [Running an OP Mainnet Node from Source](/operators/node-operators/tutorials/mainnet) tutorial, if you plan to run a full node or archive node. {

Update Node Log Level

} As part of running your rollup node, you may want to adjust the log level for more or less granular feedback when debugging. - * Update node [log level](/builders/node-operators/configuration/consensus-config#loglevel) based on individual needs. For more details, see the guide on [Geth Logs](https://geth.ethereum.org/docs/fundamentals/logs). + * Update node [log level](/operators/node-operators/configuration/consensus-config#loglevel) based on individual needs. For more details, see the guide on [Geth Logs](https://geth.ethereum.org/docs/fundamentals/logs). ## Monitor your node @@ -85,7 +85,7 @@ It is important to regularly monitor your node, and you can optionally configure {

Enable the Metrics Port

} - * Enable the [metrics port](/builders/node-operators/management/metrics) for your node by passing the `--metrics.enabled` flag to `op-node`. + * Enable the [metrics port](/operators/node-operators/management/metrics) for your node by passing the `--metrics.enabled` flag to `op-node`. * Optionally, you can customize the metrics port and address via the `--metrics.port` and `--metrics.addr` flags, respectively. {

Setup Prometheus & Grafana

} @@ -103,7 +103,7 @@ It is important to regularly monitor your node, and you can optionally configure ## Follow node updates * It's important to keep your node software up to date. Software updates can also include important bug fixes and patches that can help keep your node stable. -* Refer to the [Software Releases](/builders/node-operators/releases) page for a detailed look at the latest releases of various rollup node and execution client implementations. +* Refer to the [Software Releases](/operators/node-operators/releases) page for a detailed look at the latest releases of various rollup node and execution client implementations. * Notifications are also posted to the Optimism Upgrade Announcement Channels on [**Discord**](https://discord.com/channels/667044843901681675/754090866435424270) and [**Telegram**](https://t.me/+LtAJL1Mt1PYyNjBh). ## Node operator tutorials @@ -123,5 +123,5 @@ It is important to regularly monitor your node, and you can optionally configure ## Next steps -* If you've already got your node up and running, check out the [Node Metrics and Monitoring Guide](/builders/node-operators/management/metrics) to learn how to keep tabs on your node and make sure it keeps running smoothly. -* If you run into any problems, please visit the [Node Troubleshooting Guide](/builders/node-operators/management/troubleshooting) for help. +* If you've already got your node up and running, check out the [Node Metrics and Monitoring Guide](/operators/node-operators/management/metrics) to learn how to keep tabs on your node and make sure it keeps running smoothly. +* If you run into any problems, please visit the [Node Troubleshooting Guide](/operators/node-operators/management/troubleshooting) for help. diff --git a/pages/operators/node-operators/tutorials/mainnet.mdx b/pages/operators/node-operators/tutorials/mainnet.mdx index 4ae527e4e..96fa233a4 100644 --- a/pages/operators/node-operators/tutorials/mainnet.mdx +++ b/pages/operators/node-operators/tutorials/mainnet.mdx @@ -44,7 +44,7 @@ Based on these trends, node operators should plan for future storage needs and c ### Assess blob archiver Assess if you need to configure a blob archiver service by reading the -[Configure a Blob Archiver documentation](/builders/node-operators/management/blobs#configure-a-blob-archiver-archive-nodes). +[Configure a Blob Archiver documentation](/operators/node-operators/management/blobs#configure-a-blob-archiver-archive-nodes). ### Create a JWT secret @@ -89,7 +89,7 @@ You can still start `op-geth` without yet running `op-node`, but the `op-geth` i Use the following command to start `op-geth` in a default configuration. The JSON-RPC API will become available on port 8545. - Refer to the `op-geth` [configuration documentation](/builders/node-operators/configuration/execution-config) for more detailed information about available options. + Refer to the `op-geth` [configuration documentation](/operators/node-operators/configuration/execution-config) for more detailed information about available options. ```bash ./build/bin/geth \ @@ -138,7 +138,7 @@ Once you've started `op-geth`, you can start `op-node`. {

Start op-node

} Use the following command to start `op-node` in a default configuration. - Refer to the `op-node` [configuration documentation](/builders/node-operators/configuration/consensus-config) for more detailed information about available options. + Refer to the `op-node` [configuration documentation](/operators/node-operators/configuration/consensus-config) for more detailed information about available options. The `op-node` RPC should not be exposed publicly. If left exposed, it could @@ -146,7 +146,7 @@ Once you've started `op-geth`, you can start `op-node`. - Sync mode is set to `--syncmode=execution-layer` to enable [snap sync](/builders/node-operators/management/snap-sync) + Sync mode is set to `--syncmode=execution-layer` to enable [snap sync](/operators/node-operators/management/snap-sync) and remove the need to initialize the node with a data directory. @@ -275,7 +275,7 @@ In this section, you'll learn how to download and verify the pre-migrated databa Click the link below to find the latest publicly available database snapshots for OP Mainnet. Snapshots are available for multiple dates and snapshots get larger as they get closer to the current date. Snapshots are large files and may take some time to download. - [OP Mainnet Snapshots](/builders/node-operators/management/snapshots#op-mainnet) + [OP Mainnet Snapshots](/operators/node-operators/management/snapshots#op-mainnet) {

Verify the Download

} @@ -300,7 +300,7 @@ In this section, you'll learn how to download and verify the pre-migrated databa ``` Your exact output will depend on the snapshot you've downloaded. - Check the [OP Mainnet Snapshots](/builders/node-operators/management/snapshots#op-mainnet) page for the correct checksum for the snapshot you've downloaded. + Check the [OP Mainnet Snapshots](/operators/node-operators/management/snapshots#op-mainnet) page for the correct checksum for the snapshot you've downloaded. {

Extract the Data Directory

} @@ -337,7 +337,7 @@ If you want to run a full node then you can safely skip this section. Click the link below to download the latest publicly available database snapshot for Legacy Geth. This is a very large file (2.9TB), so expect the download to take some time to complete. - [Legacy Geth Data Directory (2.9TB)](/builders/node-operators/management/snapshots#op-mainnet-legacy) + [Legacy Geth Data Directory (2.9TB)](/operators/node-operators/management/snapshots#op-mainnet-legacy) {

Verify the Download

} diff --git a/pages/operators/node-operators/tutorials/testnet.mdx b/pages/operators/node-operators/tutorials/testnet.mdx index bec9846dc..96b6bda28 100644 --- a/pages/operators/node-operators/tutorials/testnet.mdx +++ b/pages/operators/node-operators/tutorials/testnet.mdx @@ -29,7 +29,7 @@ Below are suggested minimum hardware requirements for each type of node. ## Assess blob archiver Assess if you need to configure a blob archiver service by reading the -[Configure a Blob Archiver documentation](/builders/node-operators/management/blobs#configure-a-blob-archiver-archive-nodes). +[Configure a Blob Archiver documentation](/operators/node-operators/management/blobs#configure-a-blob-archiver-archive-nodes). ## Create a JWT secret @@ -75,7 +75,7 @@ export DATADIR_PATH=... # Path to the folder where geth data will be stored Use the following command to start `op-geth` in a default configuration. The JSON-RPC API will become available on port 8545. -Refer to the `op-geth` [configuration documentation](/builders/node-operators/configuration/execution-config) for more detailed information about available options. +Refer to the `op-geth` [configuration documentation](/operators/node-operators/configuration/execution-config) for more detailed information about available options. * Set `--syncmode=execution-layer` on `op-node` if you don't set `--syncmode=full` here on op-geth. @@ -132,7 +132,7 @@ export L1_BEACON_URL=... # URL address for the L1 Beacon-node HTTP endpoint to u {

Start op-node

} Use the following command to start `op-node` in a default configuration. -Refer to the `op-node` [configuration documentation](/builders/node-operators/configuration/consensus-config) for more detailed information about available options. +Refer to the `op-node` [configuration documentation](/operators/node-operators/configuration/consensus-config) for more detailed information about available options. The `op-node` RPC should not be exposed publicly. If left exposed, it could @@ -140,7 +140,7 @@ Refer to the `op-node` [configuration documentation](/builders/node-operators/co -Sync mode is set to `--syncmode=execution-layer` to enable [snap sync](/builders/node-operators/management/snap-sync). +Sync mode is set to `--syncmode=execution-layer` to enable [snap sync](/operators/node-operators/management/snap-sync). ```bash diff --git a/pages/stack/beta-features/alt-da-mode.mdx b/pages/stack/beta-features/alt-da-mode.mdx index 61546d8e9..a72c26e02 100644 --- a/pages/stack/beta-features/alt-da-mode.mdx +++ b/pages/stack/beta-features/alt-da-mode.mdx @@ -41,7 +41,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](/builders/chain-operators/features/alt-da-mode). +* 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). ## FAQs diff --git a/pages/stack/beta-features/custom-gas-token.mdx b/pages/stack/beta-features/custom-gas-token.mdx index 3e25e1a86..f4afb9271 100644 --- a/pages/stack/beta-features/custom-gas-token.mdx +++ b/pages/stack/beta-features/custom-gas-token.mdx @@ -71,7 +71,7 @@ The custom token being used must adhere to the following constraints to be able ## Next steps -* Ready to get started? Read our guide on how to [deploy your custom gas token chain](/builders/chain-operators/features/custom-gas-token). +* Ready to get started? Read our guide on how to [deploy your custom gas token chain](/operators/chain-operators/features/custom-gas-token). * For more info about how the custom gas token feature works under the hood, [check out the specs](https://specs.optimism.io/experimental/custom-gas-token.html). ## FAQs diff --git a/pages/stack/chain/getting-started.mdx b/pages/stack/chain/getting-started.mdx index d4af9faea..2011b9014 100644 --- a/pages/stack/chain/getting-started.mdx +++ b/pages/stack/chain/getting-started.mdx @@ -15,7 +15,7 @@ But a few differences [do exist](/stack/differences). ## OP Mainnet and OP Sepolia endpoint URLs -To access any Ethereum type network you need an endpoint. [These providers](/builders/tools/connect/rpc-providers) support our networks. +To access any Ethereum type network you need an endpoint. [These providers](/app-developers/tools/connect/rpc-providers) support our networks. ### Network choice @@ -58,7 +58,7 @@ Only when you have a version that works well on a test network should you deploy ### Contract source verification -You don't have to upload your source code to [block explorers](/builders/tools/build/block-explorers), but it is a good idea. +You don't have to upload your source code to [block explorers](/app-developers/tools/build/block-explorers), but it is a good idea. 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. diff --git a/pages/stack/chain/networks.mdx b/pages/stack/chain/networks.mdx index a7e97799d..8f52706a2 100644 --- a/pages/stack/chain/networks.mdx +++ b/pages/stack/chain/networks.mdx @@ -12,7 +12,7 @@ This reference guide provides a listing of the different OP networks and public The public RPC URLs provided below are rate limited and do not support websocket connections. - If you are experiencing rate limiting issues or need websocket functionality, consider [running your own node](/builders/node-operators/rollup-node) or signing up for a [third-party RPC provider](/builders/tools/connect/rpc-providers). + If you are experiencing rate limiting issues or need websocket functionality, consider [running your own node](/operators/node-operators/rollup-node) or signing up for a [third-party RPC provider](/app-developers/tools/connect/rpc-providers). ## OP Mainnet diff --git a/pages/stack/chain/testing/dev-node.mdx b/pages/stack/chain/testing/dev-node.mdx index 228a1a803..434d6ae62 100644 --- a/pages/stack/chain/testing/dev-node.mdx +++ b/pages/stack/chain/testing/dev-node.mdx @@ -19,7 +19,7 @@ You'll perform the full deployment process, and **you'll end up with your very o It's useful to understand what each of these components does before you start deploying your chain. To learn about the different components please -read the [deployment overview page](/builders/chain-operators/deploy/overview). +read the [deployment overview page](/operators/chain-operators/deploy/overview). You can use this devnet to experiment and perform tests, or you can choose to modify the chain to adapt it to your own needs. **The OP Stack is free and open source software licensed entirely under the MIT license**. You don't need permission from diff --git a/pages/stack/chain/testing/testing-apps.mdx b/pages/stack/chain/testing/testing-apps.mdx index 2eac879a2..bf337c5ca 100644 --- a/pages/stack/chain/testing/testing-apps.mdx +++ b/pages/stack/chain/testing/testing-apps.mdx @@ -23,7 +23,7 @@ Running proper testing is key to identifying fringe cases where the equivalence ## Multilayer integration tests Some apps need OP Mainnet-specific features that aren't available as part of the development stack. -For example, if your decentralized application relies on [inter-domain communication](/builders/app-developers/bridging/messaging), the effort of developing a stub to let you debug it in a development stack is probably greater than the hassle of having the automated test go to [a local development environment](dev-node) each time. +For example, if your decentralized application relies on [inter-domain communication](/app-developers/bridging/messaging), the effort of developing a stub to let you debug it in a development stack is probably greater than the hassle of having the automated test go to [a local development environment](dev-node) each time. ## Integration with other products diff --git a/pages/stack/components.mdx b/pages/stack/components.mdx index bb658e97f..2c879bbef 100644 --- a/pages/stack/components.mdx +++ b/pages/stack/components.mdx @@ -83,7 +83,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](/builders/app-developers/bridging/messaging)) +* [Specifications](https://specs.optimism.io/protocol/withdrawals.html) (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/fault-proofs/challenger.mdx b/pages/stack/fault-proofs/challenger.mdx index d6e12aa17..d1d9b4480 100644 --- a/pages/stack/fault-proofs/challenger.mdx +++ b/pages/stack/fault-proofs/challenger.mdx @@ -84,7 +84,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](/builders/chain-operators/tools/op-challenger). +* 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). ## FAQs diff --git a/pages/stack/features/send-raw-transaction-conditional.mdx b/pages/stack/features/send-raw-transaction-conditional.mdx index f087ed935..b133d9a63 100644 --- a/pages/stack/features/send-raw-transaction-conditional.mdx +++ b/pages/stack/features/send-raw-transaction-conditional.mdx @@ -59,5 +59,5 @@ This feature can be enabled with the addition of a flag to op-geth. * `--rollup.sequencertxconditionalcostratelimit` (default: 5000) an integer flag that sets the rate limit for cost observable per second. - It is not advised to publicly expose this sequencer endpoint due to DoS concerns. This supplemental proxy, [op-txproxy](/builders/chain-operators/tools/op-txproxy), should be used to apply additional constraints on this endpoint prior to passing through to the sequencer. + It is not advised to publicly expose this sequencer endpoint due to DoS concerns. This supplemental proxy, [op-txproxy](/operators/chain-operators/tools/op-txproxy), should be used to apply additional constraints on this endpoint prior to passing through to the sequencer. diff --git a/pages/stack/getting-started.mdx b/pages/stack/getting-started.mdx index 624a33132..e7218b268 100644 --- a/pages/stack/getting-started.mdx +++ b/pages/stack/getting-started.mdx @@ -16,7 +16,7 @@ import { Callout } from 'nextra/components' The OP Stack consists of the many different software components managed and maintained by the Optimism Collective that, together, form the backbone of Optimism. The OP Stack is built as a public good for the Ethereum and Optimism ecosystems. -To understand how to operate an OP Stack chain, including roll-up and chain deployment basics, visit [Chain Operator guide](/builders/chain-operators/self-hosted). Check out these guides to get an overview of everything you need to know to properly support OP mainnet within your [exchange](/builders/app-developers/overview) and [wallet](/builders/app-developers/overview). +To understand how to operate an OP Stack chain, including roll-up and chain deployment basics, visit [Chain Operator guide](/operators/chain-operators/self-hosted). Check out these guides to get an overview of everything you need to know to properly support OP mainnet within your [exchange](/app-developers/overview) and [wallet](/app-developers/overview). ## The OP Stack powers Optimism @@ -46,7 +46,7 @@ The Bedrock release of the OP Stack makes it easy to spin up an L2 that will be If you'd like to launch a Superchain-ready L2, check out our guide for running a chain based on the Bedrock release of the OP Stack. It is possible to modify components of the OP Stack to build novel L2 systems. -If you're interested in experimenting with the OP Stack, check out [the OP Stack Hacks section of this site](/builders/chain-operators/hacks/overview). +If you're interested in experimenting with the OP Stack, check out [the OP Stack Hacks section of this site](/operators/chain-operators/hacks/overview). Please note that, as of the Bedrock release, the OP Stack is *not* designed to support these modifications and you will very much be *hacking* on the codebase. As a result, **you should, for the moment, expect limited (if any) developer support for OP Stack Hacks.** OP Stack Hacks will likely make your chain incompatible with the Optimism Superchain. diff --git a/pages/stack/interop/explainer.mdx b/pages/stack/interop/explainer.mdx index 759694683..2ad26b111 100644 --- a/pages/stack/interop/explainer.mdx +++ b/pages/stack/interop/explainer.mdx @@ -31,7 +31,7 @@ Interoperability provides the following benefits: A pre-interop OP Stack node consists of two pieces of software: a consensus client (e.g. op-node) and an execution client, which is responsible for processing user transactions and constructing blocks (e.g. op-geth). Interoperability among OP Stack chains is enabled via a new service called [*OP Supervisor*](/stack/interop/op-supervisor). -Every node operator is expected to run this service in addition to the [rollup node](/builders/node-operators/architecture#rollup-node) and [execution client](/builders/node-operators/architecture#execution-client). +Every node operator is expected to run this service in addition to the [rollup node](/operators/node-operators/architecture#rollup-node) and [execution client](/operators/node-operators/architecture#execution-client). ```mermaid @@ -138,7 +138,7 @@ flowchart LR B1 --> C0 ``` -Interop expands the scope of trust for unsafe blocks (blocks that are shared through [the gossip protocol](/builders/chain-operators/architecture#sequencer)). +Interop expands the scope of trust for unsafe blocks (blocks that are shared through [the gossip protocol](/operators/chain-operators/architecture#sequencer)). If a sequencer chooses to accept unsafe messages, the sequencer must trust the sequencer that produces the inbound message as well as any referenced unsafe messages produced from sequencers in the transitive dependency set.
diff --git a/pages/stack/research/block-time-research.mdx b/pages/stack/research/block-time-research.mdx index ca8678765..a5832a82b 100644 --- a/pages/stack/research/block-time-research.mdx +++ b/pages/stack/research/block-time-research.mdx @@ -59,7 +59,7 @@ As a result, we can learn that nodes can build the latest blocks of Base Mainnet ### Verifier -* Sync from genesis: If OP Chains' block time drops to one second, verifiers may need longer to sync the chain from the genesis with L1 derivation. However, we expect it won't be a notable issue for verifiers as OP Stack supports the [engine sync](/builders/node-operators/management/snap-sync). +* Sync from genesis: If OP Chains' block time drops to one second, verifiers may need longer to sync the chain from the genesis with L1 derivation. However, we expect it won't be a notable issue for verifiers as OP Stack supports the [engine sync](/operators/node-operators/management/snap-sync). * Following the tip: The research suggests that verifiers are less likely to have a problem following the tip because nodes could build a block under one second at the highest gas range, especially since most verifiers are full nodes. ### Sequencer diff --git a/pages/stack/rollup/overview.mdx b/pages/stack/rollup/overview.mdx index b29615ea6..e07ec94f6 100644 --- a/pages/stack/rollup/overview.mdx +++ b/pages/stack/rollup/overview.mdx @@ -21,7 +21,7 @@ Specifically, Optimistic Rollups leverage the consensus mechanism (like PoW or P ## Block storage In Bedrock, L2 blocks are saved to the Ethereum blockchain using a non-contract address ([`0xff00..0010` on Ethereum](https://etherscan.io/address/0xff00000000000000000000000000000000000010)) to minimize the L1 gas expense. -As these blocks are submitted as transactions using EIP-4844 [blobs](/builders/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. +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. @@ -71,7 +71,7 @@ This makes it possible to transfer ETH or tokens, including ERC20 tokens, betwee The exact mechanism by which this communication occurs differs depending on the direction in which messages are being sent. OP Mainnet uses this functionality in the Standard bridge to allow users to deposit tokens from Ethereum to OP Mainnet and also to allow withdrawals of the same tokens from OP Mainnet back to Ethereum. -See the [developer documentation and examples](/builders/app-developers/bridging/standard-bridge) for details on the inner workings of the Standard bridge. +See the [developer documentation and examples](/app-developers/bridging/standard-bridge) for details on the inner workings of the Standard bridge. ### Moving from Ethereum to OP Mainnet @@ -113,4 +113,4 @@ 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](/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). +* To learn about operating your own L2 rollup, see the guide on [starting a self-hosted chain](/operators/chain-operators/self-hosted) or go directly to the tutorial on [creating your own L2 rollup](/operators/chain-operators/tutorials/create-l2-rollup). diff --git a/pages/stack/smart-contracts.mdx b/pages/stack/smart-contracts.mdx index 9c5807c05..a5fde2e17 100644 --- a/pages/stack/smart-contracts.mdx +++ b/pages/stack/smart-contracts.mdx @@ -37,7 +37,7 @@ Contract releases have a component name of `op-contracts` and therefore are tagg The release fixes security vulnerabilities found in Fault Proof contracts. They were made 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. -The upgrade was coupled with the [Granite network upgrade](/builders/node-operators/network-upgrades#granite) to improve the stability and performance of the Fault Proof System. In addition, the capabilities of the Guardian and DeputyGuardian have been extended to set the anchor state for the Fault Proof System in order to prevent referencing invalid anchor states. +The upgrade was coupled with the [Granite network upgrade](/operators/node-operators/network-upgrades#granite) to improve the stability and performance of the Fault Proof System. In addition, the capabilities of the Guardian and DeputyGuardian have been extended to set the anchor state for the Fault Proof System in order to prevent referencing invalid anchor states. * [Official - Fault Proof Fixes Release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.6.0) * [Governance Post](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) diff --git a/pages/stack/transactions/fees.mdx b/pages/stack/transactions/fees.mdx index 4934845e4..ed669c52c 100644 --- a/pages/stack/transactions/fees.mdx +++ b/pages/stack/transactions/fees.mdx @@ -96,7 +96,7 @@ the L1 Data Fee are generally quite small and should not impact the average tran The L1 Data Fee formula changed with the Ecotone upgrade. - Refer to the [Network Upgrade Overview](/builders/node-operators/network-upgrades) for network upgrade activation timestamps for OP Sepolia and OP Mainnet. + Refer to the [Network Upgrade Overview](/operators/node-operators/network-upgrades) for network upgrade activation timestamps for OP Sepolia and OP Mainnet. Prior to the Ecotone upgrade, the L1 Data Fee is calculated based on the following parameters: @@ -130,7 +130,7 @@ l1_data_fee = tx_total_gas * ethereum_base_fee The L1 Data Fee formula changed with the Ecotone upgrade. - Refer to the [Network Upgrade Overview](/builders/node-operators/network-upgrades) for network upgrade activation timestamps for OP Sepolia and OP Mainnet. + Refer to the [Network Upgrade Overview](/operators/node-operators/network-upgrades) for network upgrade activation timestamps for OP Sepolia and OP Mainnet. The pricing function changes with Ecotone upgrade because of the introduction of the option to @@ -171,13 +171,13 @@ Recall that base\_fee\_scalar is set to dynamic\_overhead and blob\_base\_fee\_s following the upgrade. Because the old overhead parameter becomes ignored, new L1 data prices will be (slightly, since overhead is typically very small) lower than before the fork. Chain operators will likely want to retune the parameters appropriately after the fork, particularly if -they plan on [enabling blobs](/builders/chain-operators/management/blobs). +they plan on [enabling blobs](/operators/chain-operators/management/blobs). Chain operators can use the [Ecotone fee parameter calculator](https://docs.google.com/spreadsheets/d/12VIiXHaVECG2RUunDSVJpn67IQp9NHFJqUsma2PndpE/edit#gid=186414307) to get a better estimate of scalar values to use for your chain. #### Fjord - The L1 Data Fee formula changed with the Fjord upgrade. Refer to the [Network Upgrade Overview](/builders/node-operators/network-upgrades) for network upgrade activation timestamps for OP Sepolia and OP Mainnet. + The L1 Data Fee formula changed with the Fjord upgrade. Refer to the [Network Upgrade Overview](/operators/node-operators/network-upgrades) for network upgrade activation timestamps for OP Sepolia and OP Mainnet. The pricing function changes with the Fjord upgrade because of the FastLZ compression estimator, which more accurately charges for L1 data usage on a per-transaction basis. @@ -229,4 +229,4 @@ This system ensures effective fee management, maintaining the security and opera ## Next steps * Read the [differences between Ethereum and OP Stack Chains](/stack/differences) guide. -* Read the [L2 to L1 Transactions](/builders/app-developers/bridging/messaging#for-l1-to-l2-transactions) guide. +* Read the [L2 to L1 Transactions](/app-developers/bridging/messaging#for-l1-to-l2-transactions) guide. diff --git a/pages/stack/transactions/transaction-finality.mdx b/pages/stack/transactions/transaction-finality.mdx index 60b61d9b7..2d7eb6272 100644 --- a/pages/stack/transactions/transaction-finality.mdx +++ b/pages/stack/transactions/transaction-finality.mdx @@ -62,7 +62,7 @@ This misconception often arises due to the OP Stack's Standard Bridge, which inc Another misconception related to the belief that [finalization takes 7 days](#misconception-transactions-take-7-days-to-finalize) is that **Fault Proof challenges** created in response to withdrawals in the Standard Bridge can reorganize the OP Stack chain. **This is incorrect.** OP Stack transactions are not reorganized in response to Fault Proof challenges. -The [Standard Bridge](/builders/app-developers/bridging/standard-bridge) is a bridge application that is included by default with any OP Stack chain and connects the chain to its "parent" blockchain (usually Ethereum). It offers a high level of security for ETH and ERC-20 tokens moved through the bridge. +The [Standard Bridge](/app-developers/bridging/standard-bridge) is a bridge application that is included by default with any OP Stack chain and connects the chain to its "parent" blockchain (usually Ethereum). It offers a high level of security for ETH and ERC-20 tokens moved through the bridge. When using the Standard Bridge, users who send ETH or ERC-20 tokens to Ethereum must first burn those tokens on the OP Stack chain and then create a **withdrawal claim** on Ethereum. diff --git a/pages/stack/transactions/withdrawal-flow.mdx b/pages/stack/transactions/withdrawal-flow.mdx index 14cac6fce..3cea1d847 100644 --- a/pages/stack/transactions/withdrawal-flow.mdx +++ b/pages/stack/transactions/withdrawal-flow.mdx @@ -17,7 +17,7 @@ Withdrawals require the user to submit three transactions: 3. **Withdrawal finalizing transaction**, which the user submits on L1 after the fault challenge period has passed, to actually run the transaction on L1. - You can see an example of how to do this [in the bridging tutorials](/builders/app-developers/tutorials/cross-dom-bridge-erc20). + You can see an example of how to do this [in the bridging tutorials](/app-developers/tutorials/cross-dom-bridge-erc20). ## Withdrawal initiating transaction diff --git a/pages/superchain/standard-configuration.mdx b/pages/superchain/standard-configuration.mdx index 7143976cd..5e9a4490f 100644 --- a/pages/superchain/standard-configuration.mdx +++ b/pages/superchain/standard-configuration.mdx @@ -11,7 +11,7 @@ import { Callout } from 'nextra/components' The standard configuration within the OP Stack ensures that chains deployed in the Superchain ecosystem adhere to a consistent set of technical and governance parameters. This standardization is critical for Superchain interoperability, network security, and ease of upgrading your chain. -This guide provides an in-depth explanation of what defines a standard configuration, how the [op-deployer](/builders/chain-operators/tools/op-deployer) aids standardization, and why adhering to these standards is essential. +This guide provides an in-depth explanation of what defines a standard configuration, how the [op-deployer](/operators/chain-operators/tools/op-deployer) aids standardization, and why adhering to these standards is essential. ## What is a Standard chain? @@ -33,7 +33,7 @@ Chains that deviate from these principles, such as introducing unsupported featu ## Role of op-deployer in standardization -The [op-deployer](/builders/chain-operators/tools/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. +The [op-deployer](/operators/chain-operators/tools/op-deployer) is a powerful tool designed to automate and streamline the deployment of standard configuration-compliant chains. Key features include: * **Default values:** diff --git a/pages/superchain/superchain-registry.mdx b/pages/superchain/superchain-registry.mdx index 28eb28f72..faa37dc11 100644 --- a/pages/superchain/superchain-registry.mdx +++ b/pages/superchain/superchain-registry.mdx @@ -23,7 +23,7 @@ This configuration targets the Optimism Collective's highest bar for security, u You can find more details in the [Standard Rollup Charter documentation](/superchain/blockspace-charter). - We **strongly** recommend using the [op-deployer](/builders/chain-operators/tools/op-deployer) to deploy L1 contracts and generate the L2 genesis file that meet the configuration requirements outlined in the [Standard Rollup Charter](/superchain/blockspace-charter). + We **strongly** recommend using the [op-deployer](/operators/chain-operators/tools/op-deployer) to deploy L1 contracts and generate the L2 genesis file that meet the configuration requirements outlined in the [Standard Rollup Charter](/superchain/blockspace-charter). ## Joining the Registry diff --git a/theme.config.tsx b/theme.config.tsx index 9aa67b05b..81898b3ac 100644 --- a/theme.config.tsx +++ b/theme.config.tsx @@ -31,7 +31,7 @@ const config: DocsThemeConfig = { banner: { key: 'viem/op-stack', text: ( - + 🎉 We are deprecating the Optimism SDK and migrating all tutorials to use viem/op-stack. Read more → ) From 7cdf99f741bc2121d3ce52977ac13e9998eff20f Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Tue, 28 Jan 2025 01:29:25 -0800 Subject: [PATCH 10/49] linter fix --- pages/connect/contribute/style-guide.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pages/connect/contribute/style-guide.mdx b/pages/connect/contribute/style-guide.mdx index ff400ebc8..eecbd1294 100644 --- a/pages/connect/contribute/style-guide.mdx +++ b/pages/connect/contribute/style-guide.mdx @@ -320,15 +320,15 @@ Developers trust that we will lead them to sites or pages related to their readi Content types help manage technical content by defining the purpose and common structure for each file type. All content types used in these technical docs have attributes or properties, as defined below. -| Document type | Purpose | Examples | -| ------------------ | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------- | -| Overviews | General introduction to a product or feature, provides a happy-path for readers | [Smart Contract Overview](/stack/smart-contracts) | +| Document type | Purpose | Examples | +| ------------------ | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ | +| Overviews | General introduction to a product or feature, provides a happy-path for readers | [Smart Contract Overview](/stack/smart-contracts) | | Guides | Explain what things are and how they work | [Standard Bridge Guide](/app-developers/bridging/standard-bridge) | | Quick Start Guides | Briefly explain how to "minimally" get started with a product, often in 30 minutes or less | [Superchain App Quick Start](/app-developers/quick-start) | | Tutorials | Provide task-oriented guidance with step-by-step "learn by doing" instructions | [Bridging ERC-20 tokens with viem](/app-developers/tutorials/cross-dom-bridge-erc20) | -| FAQs | Address frequently asked questions | [FAQ: OP Mainnet Security Model](/chain/security/faq) | -| Troubleshooting | List common troubleshooting scenarios and solutions | [Troubleshooting: Run a Node](/operators/node-operators/management/troubleshooting) | -| Reference | Provide deep, theoretical knowledge of the internal workings of a system, such as API endpoints and specifications | [Node and RPC Providers](/app-developers/tools/connect/rpc-providers) | +| FAQs | Address frequently asked questions | [FAQ: OP Mainnet Security Model](/chain/security/faq) | +| Troubleshooting | List common troubleshooting scenarios and solutions | [Troubleshooting: Run a Node](/operators/node-operators/management/troubleshooting) | +| Reference | Provide deep, theoretical knowledge of the internal workings of a system, such as API endpoints and specifications | [Node and RPC Providers](/app-developers/tools/connect/rpc-providers) | ### Overviews From 6235821070ee68e2c8cf8a5ec12094b567c6fc12 Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Tue, 28 Jan 2025 01:46:00 -0800 Subject: [PATCH 11/49] broken links --- pages/app-developers/tools/connect/networks.mdx | 2 +- public/_redirects | 11 +++++++++++ 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/pages/app-developers/tools/connect/networks.mdx b/pages/app-developers/tools/connect/networks.mdx index 7440c93ec..3b6b7a7f7 100644 --- a/pages/app-developers/tools/connect/networks.mdx +++ b/pages/app-developers/tools/connect/networks.mdx @@ -6,6 +6,6 @@ description: >- information and resources about networks. --- -import OPNetworks from '@/pages/chain/networks.mdx' +import OPNetworks from '@/pages/stack/chain/networks.mdx' diff --git a/public/_redirects b/public/_redirects index 7217f9a12..a232d0651 100644 --- a/public/_redirects +++ b/public/_redirects @@ -134,3 +134,14 @@ /builders/tools/fee-calculator /operators/chain-operators/tools/fee-calculator /builders/app-developers/tools/supersim /app-developers/tools/supersim /builders/app-developers/tools/ecosystem-overview /app-developers/tools/ecosystem-overview +/chain/getting-started /stack/chain/getting-started +/chain/networks /stack/chain/networks +/chain/addresses /stack/chain/addresses +/chain/tokenlist /stack/chain/tokenlist +/chain/testing /stack/chain/testing +/chain/testing/dev-node /stack/chain/testing/dev-node +/chain/testing/testing-apps /stack/chain/testing/testing-apps +/chain/security /stack/chain/security +/chain/security/faq /stack/chain/security/faq +/chain/security/privileged-roles /stack/chain/security/privileged-roles +/chain/security/security-policy /stack/chain/security/security-policy From 89e22ad55b5864b76435fe3496bf130331fe8bd7 Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Tue, 28 Jan 2025 01:50:34 -0800 Subject: [PATCH 12/49] lint fixes --- pages/app-developers/bridging/custom-bridge.mdx | 2 +- pages/app-developers/bridging/messaging.mdx | 2 +- pages/app-developers/bridging/standard-bridge.mdx | 4 ++-- pages/app-developers/overview.mdx | 2 +- pages/app-developers/tools/ecosystem-overview.mdx | 2 +- pages/app-developers/tools/overview.mdx | 2 +- pages/app-developers/tutorials/cross-dom-bridge-erc20.mdx | 2 +- pages/app-developers/tutorials/cross-dom-bridge-eth.mdx | 2 +- pages/app-developers/tutorials/cross-dom-solidity.mdx | 2 +- pages/app-developers/tutorials/sdk-estimate-costs.mdx | 2 +- pages/connect/contribute/docs-contribute.mdx | 2 +- pages/connect/contribute/stack-contribute.mdx | 2 +- pages/connect/contribute/style-guide.mdx | 2 +- pages/operators/chain-operators/management/key-management.mdx | 4 ++-- pages/operators/chain-operators/self-hosted.mdx | 2 +- pages/stack/chain/getting-started.mdx | 2 +- pages/stack/chain/security/faq.mdx | 4 ++-- pages/stack/security/faq.mdx | 2 +- pages/stack/smart-contracts.mdx | 2 +- 19 files changed, 22 insertions(+), 22 deletions(-) diff --git a/pages/app-developers/bridging/custom-bridge.mdx b/pages/app-developers/bridging/custom-bridge.mdx index ab5b02a0f..832cf8d49 100644 --- a/pages/app-developers/bridging/custom-bridge.mdx +++ b/pages/app-developers/bridging/custom-bridge.mdx @@ -31,7 +31,7 @@ You can read more about the design of the Standard Bridge in the guide on [Using ## The Superchain Token List -The [Superchain Token List](/chain/tokenlist) exists to help users and developers find the right bridged representations of tokens native to another blockchain. +The [Superchain Token List](/stack/chain/tokenlist) exists to help users and developers find the right bridged representations of tokens native to another blockchain. Once you've built and tested your custom bridge, make sure to register any tokens meant to flow through this bridge by [making a pull request against the Superchain Token List repository](https://github.com/ethereum-optimism/ethereum-optimism.github.io#adding-a-token-to-the-list). You **must** deploy your bridge to OP Sepolia before it can be added to the Superchain Token List. diff --git a/pages/app-developers/bridging/messaging.mdx b/pages/app-developers/bridging/messaging.mdx index 61213733f..a17f08dfd 100644 --- a/pages/app-developers/bridging/messaging.mdx +++ b/pages/app-developers/bridging/messaging.mdx @@ -118,7 +118,7 @@ contract MyContract { ``` - You can find the addresses of the `L1CrossDomainMessenger` and the `L2CrossDomainMessenger` contracts on OP Mainnet and OP Sepolia on the [Contract Addresses](/chain/addresses) page. + You can find the addresses of the `L1CrossDomainMessenger` and the `L2CrossDomainMessenger` contracts on OP Mainnet and OP Sepolia on the [Contract Addresses](/stack/chain/addresses) page. ## Communication speed diff --git a/pages/app-developers/bridging/standard-bridge.mdx b/pages/app-developers/bridging/standard-bridge.mdx index 6777721df..bc400e60d 100644 --- a/pages/app-developers/bridging/standard-bridge.mdx +++ b/pages/app-developers/bridging/standard-bridge.mdx @@ -194,7 +194,7 @@ Users simply need to trigger and send ETH to the [`bridgeETH`](https://github.co Users can also deposit ETH from Ethereum to OP Mainnet by sending a basic ETH transfer from an EOA to the `L1StandardBridgeProxy`. This works because the `L1StandardBridgeProxy` contains a [`receive`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L119-L121) function. - You can find the mainnet and testnet addresses on the [Contract Addresses](/chain/addresses) page. + You can find the mainnet and testnet addresses on the [Contract Addresses](/stack/chain/addresses) page. ## Tutorials @@ -206,7 +206,7 @@ Users simply need to trigger and send ETH to the [`bridgeETH`](https://github.co ## Superchain Token List -The [Superchain Token List](/chain/tokenlist) exists to help users discover the right bridged token addresses for any given native token. +The [Superchain Token List](/stack/chain/tokenlist) exists to help users discover the right bridged token addresses for any given native token. 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. diff --git a/pages/app-developers/overview.mdx b/pages/app-developers/overview.mdx index 60c59480d..57db6767c 100644 --- a/pages/app-developers/overview.mdx +++ b/pages/app-developers/overview.mdx @@ -18,7 +18,7 @@ It'll get you familiar with the basic steps required to get a contract deployed OP Mainnet is [EVM equivalent](https://web.archive.org/web/20231127160757/https://medium.com/ethereum-optimism/introducing-evm-equivalence-5c2021deb306) so you can feel confident that your existing Ethereum smart contract skills will carry over to OP Mainnet. Just make sure to be aware of the few small [differences between Ethereum and OP Mainnet](/stack/differences). -You might also want to check out the [testing on OP Networks guide](/chain/testing/testing-apps) and the tutorial on [running a local development environment](/stack/chain/testing/dev-node) to help you feel totally confident in your OP Mainnet deployment. +You might also want to check out the [testing on OP Networks guide](/stack/chain/testing/testing-apps) and the tutorial on [running a local development environment](/stack/chain/testing/dev-node) to help you feel totally confident in your OP Mainnet deployment. } /> diff --git a/pages/app-developers/tools/ecosystem-overview.mdx b/pages/app-developers/tools/ecosystem-overview.mdx index e6f08ef4c..f7c1c7200 100644 --- a/pages/app-developers/tools/ecosystem-overview.mdx +++ b/pages/app-developers/tools/ecosystem-overview.mdx @@ -13,7 +13,7 @@ The ecosystem repository was developed to help ease and expedite the development ## Getting started -Our initial launch includes an example [bridge application](https://github.com/ethereum-optimism/ecosystem/tree/main/apps/bridge-app) that demonstrates how to bridge ETH and any ERC20 tokens listed in the [Superchain Token List](/chain/tokenlist). +Our initial launch includes an example [bridge application](https://github.com/ethereum-optimism/ecosystem/tree/main/apps/bridge-app) that demonstrates how to bridge ETH and any ERC20 tokens listed in the [Superchain Token List](/stack/chain/tokenlist). This application serves as a reference for anyone looking to build their own bridge, offering a clearer understanding of how to interact with the protocol on both the L1 and L2 sides. Additionally, we provide a package containing common utilities essential for developers interacting with both L1 and L2. For instance, it includes features for tracking [network pairs](https://github.com/ethereum-optimism/ecosystem/blob/main/packages/op-app/src/configs/networkPairs.ts) and [deployment addresses](https://github.com/ethereum-optimism/ecosystem/blob/main/packages/op-app/src/configs/deploymentAddresses.ts) of smart contracts. diff --git a/pages/app-developers/tools/overview.mdx b/pages/app-developers/tools/overview.mdx index f7db715c2..1178d22cd 100644 --- a/pages/app-developers/tools/overview.mdx +++ b/pages/app-developers/tools/overview.mdx @@ -10,7 +10,7 @@ import { Cards, Card } from 'nextra/components' Welcome to the Optimism developer tools! -If you are already familiar with [building on OP Mainnet](/chain/getting-started) and just need the tools to get cracking, you are in the right place! +If you are already familiar with [building on OP Mainnet](/stack/chain/getting-started) and just need the tools to get cracking, you are in the right place! ## Connecting diff --git a/pages/app-developers/tutorials/cross-dom-bridge-erc20.mdx b/pages/app-developers/tutorials/cross-dom-bridge-erc20.mdx index f57f39877..7cd89e1e3 100644 --- a/pages/app-developers/tutorials/cross-dom-bridge-erc20.mdx +++ b/pages/app-developers/tutorials/cross-dom-bridge-erc20.mdx @@ -29,7 +29,7 @@ Make sure to check out the [Standard Bridge guide](/app-developers/bridging/stan ## Supported networks -The Optimism SDK supports any of the [Superchain networks](/chain/networks). +The Optimism SDK supports any of the [Superchain networks](/stack/chain/networks). [Some Superchain networks](https://sdk.optimism.io/enums/l2chainid) are already included in the SDK by default. If you want to use a network that isn't included by default, you can simply [instantiate the SDK with the appropriate contract addresses](/app-developers/overview). diff --git a/pages/app-developers/tutorials/cross-dom-bridge-eth.mdx b/pages/app-developers/tutorials/cross-dom-bridge-eth.mdx index 6acfefeeb..91b6abb9a 100644 --- a/pages/app-developers/tutorials/cross-dom-bridge-eth.mdx +++ b/pages/app-developers/tutorials/cross-dom-bridge-eth.mdx @@ -17,7 +17,7 @@ Make sure to check out the [Standard Bridge guide](/app-developers/bridging/stan ## Supported networks -Viem supports any of the [Superchain networks](/chain/networks). +Viem supports any of the [Superchain networks](/stack/chain/networks). The OP Stack networks are included in Viem by default. If you want to use a network that isn't included by default, you can add it to Viem's chain configurations. diff --git a/pages/app-developers/tutorials/cross-dom-solidity.mdx b/pages/app-developers/tutorials/cross-dom-solidity.mdx index feb22428b..96c36e865 100644 --- a/pages/app-developers/tutorials/cross-dom-solidity.mdx +++ b/pages/app-developers/tutorials/cross-dom-solidity.mdx @@ -257,7 +257,7 @@ Luckily, both `Greeter` contracts are exactly the same so it's easy to see how e ### The Messenger variable The `Greeter` contract has a `MESSENGER` variable that keeps track of the `CrossDomainMessenger` contract on the current chain. -Check out the [Contract Addresses page](/chain/addresses) to see the addresses of the `CrossDomainMessenger` contracts on whichever network you'll be using. +Check out the [Contract Addresses page](/stack/chain/addresses) to see the addresses of the `CrossDomainMessenger` contracts on whichever network you'll be using. ```solidity file=/public/tutorials/cross-dom-solidity.sol#L14 hash=ce8be857d4b4e1992cd3c16b8f2864b9 ``` diff --git a/pages/app-developers/tutorials/sdk-estimate-costs.mdx b/pages/app-developers/tutorials/sdk-estimate-costs.mdx index 6fce2ccdb..4a00715b9 100644 --- a/pages/app-developers/tutorials/sdk-estimate-costs.mdx +++ b/pages/app-developers/tutorials/sdk-estimate-costs.mdx @@ -18,7 +18,7 @@ You'll also learn how to estimate the total cost of the transaction all at once. ## Supported networks -Viem supports any of the [Superchain networks](/chain/networks). +Viem supports any of the [Superchain networks](/stack/chain/networks). The OP Stack networks are included in Viem by default. If you want to use a network that isn't included by default, you can add it to Viem's chain configurations. diff --git a/pages/connect/contribute/docs-contribute.mdx b/pages/connect/contribute/docs-contribute.mdx index d1472fcdd..694038d6d 100644 --- a/pages/connect/contribute/docs-contribute.mdx +++ b/pages/connect/contribute/docs-contribute.mdx @@ -38,7 +38,7 @@ Optimism Docs (docs.optimism.io) is an open-source project, and we welcome your * [Work on an open issue](https://github.com/ethereum-optimism/docs/issues): start with items we've already identified as needing attention, which range from general guides to tutorials and quickstarts. * [Create new content](https://github.com/ethereum-optimism/docs/issues/new): create new content to add to the technical docs. Review the [style guide](style-guide) and follow the PR process outlined in the [contributor guidelines](https://github.com/ethereum-optimism/docs/blob/main/CONTRIBUTING.md) to get started. -* [Submit a bug report](https://immunefi.com/bounty/optimism/): create a report to help us improve our products and developer tooling. For more information, please read our [Security Policy](/chain/security/security-policy). +* [Submit a bug report](https://immunefi.com/bounty/optimism/): create a report to help us improve our products and developer tooling. For more information, please read our [Security Policy](/stack/chain/security/security-policy). * [Contribute to the Optimism Collective](https://github.com/ethereum-optimism/ecosystem-contributions): select from several different categories where you can make an impact such as [foundation missions](https://github.com/ethereum-optimism/ecosystem-contributions/issues?q=is%3Aissue+is%3Aopen+label%3A%22Foundation+Mission+%28RFP%29%22) or general [contributor opportunities](https://github.com/ethereum-optimism/ecosystem-contributions/issues?q=is%3Aissue+is%3Aopen+label%3A%22Contribution+Opportunity%22). diff --git a/pages/connect/contribute/stack-contribute.mdx b/pages/connect/contribute/stack-contribute.mdx index a53ff01ca..42e981355 100644 --- a/pages/connect/contribute/stack-contribute.mdx +++ b/pages/connect/contribute/stack-contribute.mdx @@ -35,7 +35,7 @@ To make your first contribution to the codebase, check out the [open issues](htt ## Bounty hunting -The OP Stack needs YOU (yes you!) to help review the codebase for bugs and vulnerabilities. If you're interested in bounty hunting, check out our [Security Policy, Vulnerability Reporting, and Bug Bounties page](/chain/security/security-policy). +The OP Stack needs YOU (yes you!) to help review the codebase for bugs and vulnerabilities. If you're interested in bounty hunting, check out our [Security Policy, Vulnerability Reporting, and Bug Bounties page](/stack/chain/security/security-policy). ## Docs contributions diff --git a/pages/connect/contribute/style-guide.mdx b/pages/connect/contribute/style-guide.mdx index eecbd1294..b014cb0f0 100644 --- a/pages/connect/contribute/style-guide.mdx +++ b/pages/connect/contribute/style-guide.mdx @@ -326,7 +326,7 @@ Content types help manage technical content by defining the purpose and common s | Guides | Explain what things are and how they work | [Standard Bridge Guide](/app-developers/bridging/standard-bridge) | | Quick Start Guides | Briefly explain how to "minimally" get started with a product, often in 30 minutes or less | [Superchain App Quick Start](/app-developers/quick-start) | | Tutorials | Provide task-oriented guidance with step-by-step "learn by doing" instructions | [Bridging ERC-20 tokens with viem](/app-developers/tutorials/cross-dom-bridge-erc20) | -| FAQs | Address frequently asked questions | [FAQ: OP Mainnet Security Model](/chain/security/faq) | +| FAQs | Address frequently asked questions | [FAQ: OP Mainnet Security Model](/stack/chain/security/faq) | | Troubleshooting | List common troubleshooting scenarios and solutions | [Troubleshooting: Run a Node](/operators/node-operators/management/troubleshooting) | | Reference | Provide deep, theoretical knowledge of the internal workings of a system, such as API endpoints and specifications | [Node and RPC Providers](/app-developers/tools/connect/rpc-providers) | diff --git a/pages/operators/chain-operators/management/key-management.mdx b/pages/operators/chain-operators/management/key-management.mdx index 479b6ba0c..9256b77a2 100644 --- a/pages/operators/chain-operators/management/key-management.mdx +++ b/pages/operators/chain-operators/management/key-management.mdx @@ -9,7 +9,7 @@ import { Callout } from 'nextra/components' # Managing your keys This guide informs chain operators on important key management considerations. -There are certain [privileged roles](/chain/security/privileged-roles) that +There are certain [privileged roles](/stack/chain/security/privileged-roles) that need careful consideration. The privileged roles are categorized as hot wallets or cold wallets. @@ -39,6 +39,6 @@ of community members and avoid a single point of failure. The signers behind a multisig should probably also use a hardware wallet. - Refer to the [privileged roles](/chain/security/privileged-roles) documentation + Refer to the [privileged roles](/stack/chain/security/privileged-roles) documentation for more information about these different addresses and their security concerns. diff --git a/pages/operators/chain-operators/self-hosted.mdx b/pages/operators/chain-operators/self-hosted.mdx index 0edd8be4b..c46947d9c 100644 --- a/pages/operators/chain-operators/self-hosted.mdx +++ b/pages/operators/chain-operators/self-hosted.mdx @@ -46,7 +46,7 @@ OP Chains can be configured for throughput, cost, and other decentralization tra {

Setup Key Management and Privileged Roles

} * Configure hot wallets and cold wallets using the guide for [Managing Your Keys](/operators/chain-operators/management/key-management). - * Refer to the [Privileged Roles](/chain/security/privileged-roles) guide for detailed security information. + * Refer to the [Privileged Roles](/stack/chain/security/privileged-roles) guide for detailed security information. {

Make Standard Chain Configurations

} diff --git a/pages/stack/chain/getting-started.mdx b/pages/stack/chain/getting-started.mdx index 2011b9014..d4a95804d 100644 --- a/pages/stack/chain/getting-started.mdx +++ b/pages/stack/chain/getting-started.mdx @@ -51,7 +51,7 @@ Not only is it faster, but such EVMs often have extra features, such as the [abi ### Debug before deploying -After you are done with that development, debug your decentralized application using either a [development node](/chain/testing/dev-node) or the [Sepolia test network](/chain/networks). +After you are done with that development, debug your decentralized application using either a [development node](/stack/chain/testing/dev-node) or the [Sepolia test network](/stack/chain/networks). This lets you debug parts that are OP Mainnet specific such as calls to bridges to transfer ETH or tokens between layers. Only when you have a version that works well on a test network should you deploy to the production network, where every transaction has a cost. diff --git a/pages/stack/chain/security/faq.mdx b/pages/stack/chain/security/faq.mdx index 002244cc8..83bb44342 100644 --- a/pages/stack/chain/security/faq.mdx +++ b/pages/stack/chain/security/faq.mdx @@ -73,10 +73,10 @@ Check out Optimism's detailed [Pragmatic Path to Decentralization](https://web.a ### How can I help make OP Mainnet more secure? -[OP Mainnet has one of the biggest bug bounties (ever)](/chain/security/security-policy). +[OP Mainnet has one of the biggest bug bounties (ever)](/stack/chain/security/security-policy). You can earn up to $2,000,042 by finding critical bugs in the Optimism codebase. You can also run your own verifier node to detect network faults. ### Where do I report bugs? -For details about reporting vulnerabilities and available bug bounty programs, see the [Security Policy](/chain/security/security-policy). +For details about reporting vulnerabilities and available bug bounty programs, see the [Security Policy](/stack/chain/security/security-policy). diff --git a/pages/stack/security/faq.mdx b/pages/stack/security/faq.mdx index 2dd866b5a..1c7db438d 100644 --- a/pages/stack/security/faq.mdx +++ b/pages/stack/security/faq.mdx @@ -44,4 +44,4 @@ Don't forget that the OP Stack is a decentralized development stack. Anyone can ### Where do I report bugs? -For details about reporting vulnerabilities and available bug bounty programs, see the [Security Policy](/chain/security/security-policy). +For details about reporting vulnerabilities and available bug bounty programs, see the [Security Policy](/stack/chain/security/security-policy). diff --git a/pages/stack/smart-contracts.mdx b/pages/stack/smart-contracts.mdx index a5fde2e17..9b486de78 100644 --- a/pages/stack/smart-contracts.mdx +++ b/pages/stack/smart-contracts.mdx @@ -8,7 +8,7 @@ import { Callout } from 'nextra/components' # Smart Contract overview -This guide provides an overview of the functionality of the smart contract components. You can also find [contract addresses](/chain/addresses) on OP Mainnet. +This guide provides an overview of the functionality of the smart contract components. You can also find [contract addresses](/stack/chain/addresses) on OP Mainnet. ## Layer 1 contracts From aba31aee976edb933b93c2e3c2785f16afebd6a8 Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Tue, 28 Jan 2025 02:12:14 -0800 Subject: [PATCH 13/49] link updates --- pages/app-developers/bridging/standard-bridge.mdx | 2 +- pages/connect/contribute/docs-contribute.mdx | 2 +- pages/operators/chain-operators/deploy/genesis.mdx | 2 +- pages/operators/chain-operators/features/alt-da-mode.mdx | 2 +- pages/operators/chain-operators/tutorials.mdx | 2 +- pages/stack/chain/networks.mdx | 4 ++-- pages/stack/chain/security/faq.mdx | 2 +- pages/stack/chain/testing/testing-apps.mdx | 2 +- 8 files changed, 9 insertions(+), 9 deletions(-) diff --git a/pages/app-developers/bridging/standard-bridge.mdx b/pages/app-developers/bridging/standard-bridge.mdx index bc400e60d..54554aa93 100644 --- a/pages/app-developers/bridging/standard-bridge.mdx +++ b/pages/app-developers/bridging/standard-bridge.mdx @@ -217,7 +217,7 @@ Tokens on the Superchain Token List will automatically appear on certain tools l You should strongly consider using the Superchain Token List to verify that you're using the correct bridged representation of a token when bridging a native token. Doing so can help you avoid accidentally bridging to the wrong token and locking up your native token permanently. -You can easily find the bridged representation of a token for OP Mainnet on the [Bridged Token Addresses](/chain/tokenlist#op-mainnet) page. +You can easily find the bridged representation of a token for OP Mainnet on the [Bridged Token Addresses](/stack/chain/tokenlist#op-mainnet) page. If you want to find the bridged representation of a token for another chain, use the following steps. diff --git a/pages/connect/contribute/docs-contribute.mdx b/pages/connect/contribute/docs-contribute.mdx index 694038d6d..2b00e8962 100644 --- a/pages/connect/contribute/docs-contribute.mdx +++ b/pages/connect/contribute/docs-contribute.mdx @@ -20,7 +20,7 @@ Optimism Docs (docs.optimism.io) is an open-source project, and we welcome your * [Work on a good first issue](https://github.com/ethereum-optimism/docs/labels/good%20first%20issue): make the greatest and most immediate impact with a quick-start or tutorial. These special issues are clearly labeled for new contributors to Optimism. * [Edit existing content](#how-to-work-on-docsoptimismio): make tweaks to existing content using the ✏️ **Edit this page on GitHub** or ❤️ **Share general feedback** links on the right-side of any page. * [Add or update an FAQ item](https://github.com/ethereum-optimism/docs/issues/new?assignees=\&labels=documentation%2Cfaq%2Ccommunity-request\&projects=\&template=suggest_faq_item.yaml\&title=Suggest+an+FAQ+item): - add a new FAQ (question+answer set) to an [existing page](/chain/security/faq#security-model-faq), create a new FAQ page, or update an existing FAQ question/answer set. + add a new FAQ (question+answer set) to an [existing page](/stack/chain/security/faq#security-model-faq), create a new FAQ page, or update an existing FAQ question/answer set. * [Add or update a troubleshooting item](https://github.com/ethereum-optimism/docs/issues/new?assignees=\&labels=documentation%2Ctroubleshooting%2Ccommunity-request\&projects=\&template=suggest_troubleshooting_item.yaml\&title=Suggest+a+troubleshooting+item): add a new troubleshooting item (problem+solution set) to an [existing page](/operators/chain-operators/management/troubleshooting), create a new troubleshooting page, or update an existing troubleshooting problem/solution set. * [Add a glossary term](https://github.com/ethereum-optimism/docs/issues/new?assignees=\&labels=glossary%2Cdocumentation%2Ccommunity-request\&projects=\&template=suggest_glossary_term.yaml\&title=Suggest+a+glossary+term): diff --git a/pages/operators/chain-operators/deploy/genesis.mdx b/pages/operators/chain-operators/deploy/genesis.mdx index 57148fa33..acffb7dd0 100644 --- a/pages/operators/chain-operators/deploy/genesis.mdx +++ b/pages/operators/chain-operators/deploy/genesis.mdx @@ -91,5 +91,5 @@ go run cmd/main.go genesis l2 \ * Learn how to [initialize](/operators/node-operators/configuration/base-config#initialization-via-genesis-file) `op-geth` with your `genesis.json` file. -* Learn how to [initialize](https://docs.optimism.io/operators/node-operators/configuration/base-config#configuring-op-node) `op-node` with your `rollup.json` file. +* Learn how to [initialize](/operators/node-operators/configuration/base-config#configuring-op-node) `op-node` with your `rollup.json` file. * Learn more about the off chain [architecture](/operators/chain-operators/architecture). diff --git a/pages/operators/chain-operators/features/alt-da-mode.mdx b/pages/operators/chain-operators/features/alt-da-mode.mdx index e182f58cd..f72fa5fc6 100644 --- a/pages/operators/chain-operators/features/alt-da-mode.mdx +++ b/pages/operators/chain-operators/features/alt-da-mode.mdx @@ -92,7 +92,7 @@ You should use at least the following compatible op\* versions when running your * Chain operators are not posting everything to Ethereum, just commitments, so chain operators will need to determine fee scalars values to charge users. The fee scalar values are network throughput dependent, so values will need to be adjusted by chain operators as needed. * Cost structure for Alt-DA Mode: The transaction data is split up into 128kb chunks and then submitted to your DA Layer. Then, 32 byte commitments are submitted (goes to batch inbox address) to L1 for each 128kb chunk. Then, figure out how much that costs relative to the amount of transactions your chain is putting through. - * Set scalar values inside the deploy config. The example below shows some possible fee scalar values, calculated assuming negligible DA Layer costs, but will need to be adjusted up or down based on network throughput - as a reminder of how to set your scalar values, see [this section](https://docs.optimism.io/operators/chain-operators/management/blobs#update-your-scalar-values-for-blobs) of the docs. + * Set scalar values inside the deploy config. The example below shows some possible fee scalar values, calculated assuming negligible DA Layer costs, but will need to be adjusted up or down based on network throughput - as a reminder of how to set your scalar values, see [this section](/operators/chain-operators/management/blobs#update-your-scalar-values-for-blobs) of the docs. ``` // Set in Deploy Config diff --git a/pages/operators/chain-operators/tutorials.mdx b/pages/operators/chain-operators/tutorials.mdx index 7de592e70..199a2b939 100644 --- a/pages/operators/chain-operators/tutorials.mdx +++ b/pages/operators/chain-operators/tutorials.mdx @@ -23,5 +23,5 @@ This section provides information on adding attributes to the derivation functio - + diff --git a/pages/stack/chain/networks.mdx b/pages/stack/chain/networks.mdx index 8f52706a2..47d26aa76 100644 --- a/pages/stack/chain/networks.mdx +++ b/pages/stack/chain/networks.mdx @@ -25,7 +25,7 @@ This reference guide provides a listing of the different OP networks and public | Explorer | [https://optimistic.etherscan.io](https://optimistic.etherscan.io) | | Public RPC URL | [https://mainnet.optimism.io](https://mainnet.optimism.io) | | Sequencer URL2 | [https://mainnet-sequencer.optimism.io](https://mainnet-sequencer.optimism.io) | -| Contract Addresses | Refer to the [Contract Addresses page](/chain/addresses#mainnet) | +| Contract Addresses | Refer to the [Contract Addresses page](/stack/chain/addresses#mainnet) | | Connect Wallet | [Click here to connect your wallet to OP Mainnet](https://chainid.link?network=optimism) | 1. The "currency symbol" is required by some wallets like MetaMask. @@ -41,7 +41,7 @@ This reference guide provides a listing of the different OP networks and public | Explorer | [https://sepolia-optimistic.etherscan.io](https://sepolia-optimistic.etherscan.io) | | Public RPC URL | [https://sepolia.optimism.io](https://sepolia.optimism.io) | | Sequencer URL2 | [https://sepolia-sequencer.optimism.io](https://sepolia-sequencer.optimism.io) | -| Contract Addresses | Refer to the [Contract Addresses page](/chain/addresses#testnet-sepolia) | +| Contract Addresses | Refer to the [Contract Addresses page](/stack/chain/addresses#testnet-sepolia) | | Connect Wallet | [Click here to connect your wallet to OP Sepolia](https://chainid.link?network=op-sepolia) | 1. The "currency symbol" is required by some wallets like MetaMask. diff --git a/pages/stack/chain/security/faq.mdx b/pages/stack/chain/security/faq.mdx index 83bb44342..aa7f49030 100644 --- a/pages/stack/chain/security/faq.mdx +++ b/pages/stack/chain/security/faq.mdx @@ -40,7 +40,7 @@ Proposals can be submitted to the `DisputeGameFactory` contract by any user and 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/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. +Although the fault proof game is permissionless, the Optimism Security Council acting as the [Guardian](/stack/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. The Guardian can also choose to shift the system to use a `PermissionedDisputeGame` in which only specific `PROPOSER` and `CHALLENGER` roles can submit and challenge proposals. diff --git a/pages/stack/chain/testing/testing-apps.mdx b/pages/stack/chain/testing/testing-apps.mdx index bf337c5ca..510716d37 100644 --- a/pages/stack/chain/testing/testing-apps.mdx +++ b/pages/stack/chain/testing/testing-apps.mdx @@ -17,7 +17,7 @@ Most Ethereum development stacks include features that make testing easier, whic Therefore, it is a good idea to run the majority of tests, which do not rely on OP Mainnet-specific features, in the development stack. It is a lot faster. -It is a best practice to design and run thorough tests across an OP test network, either in your [local development environment](dev-node) or on [the test network](/chain/networks#op-sepolia), depending on your use case. +It is a best practice to design and run thorough tests across an OP test network, either in your [local development environment](dev-node) or on [the test network](/stack/chain/networks#op-sepolia), depending on your use case. Running proper testing is key to identifying fringe cases where the equivalence between OP Mainnet and Ethereum breaks down (or where Ethereum mainnet itself and the development stack may be non-equivalent in a production environment). ## Multilayer integration tests From e92a640da0771c4f938fbe917591d69a74bc94ac Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Tue, 28 Jan 2025 02:22:16 -0800 Subject: [PATCH 14/49] linter --- pages/stack/chain/networks.mdx | 4 ++-- pages/stack/chain/testing/testing-apps.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/stack/chain/networks.mdx b/pages/stack/chain/networks.mdx index 47d26aa76..580235c33 100644 --- a/pages/stack/chain/networks.mdx +++ b/pages/stack/chain/networks.mdx @@ -25,7 +25,7 @@ This reference guide provides a listing of the different OP networks and public | Explorer | [https://optimistic.etherscan.io](https://optimistic.etherscan.io) | | Public RPC URL | [https://mainnet.optimism.io](https://mainnet.optimism.io) | | Sequencer URL2 | [https://mainnet-sequencer.optimism.io](https://mainnet-sequencer.optimism.io) | -| Contract Addresses | Refer to the [Contract Addresses page](/stack/chain/addresses#mainnet) | +| Contract Addresses | Refer to the [Contract Addresses page](/stack/chain/addresses#mainnet) | | Connect Wallet | [Click here to connect your wallet to OP Mainnet](https://chainid.link?network=optimism) | 1. The "currency symbol" is required by some wallets like MetaMask. @@ -41,7 +41,7 @@ This reference guide provides a listing of the different OP networks and public | Explorer | [https://sepolia-optimistic.etherscan.io](https://sepolia-optimistic.etherscan.io) | | Public RPC URL | [https://sepolia.optimism.io](https://sepolia.optimism.io) | | Sequencer URL2 | [https://sepolia-sequencer.optimism.io](https://sepolia-sequencer.optimism.io) | -| Contract Addresses | Refer to the [Contract Addresses page](/stack/chain/addresses#testnet-sepolia) | +| Contract Addresses | Refer to the [Contract Addresses page](/stack/chain/addresses#testnet-sepolia) | | Connect Wallet | [Click here to connect your wallet to OP Sepolia](https://chainid.link?network=op-sepolia) | 1. The "currency symbol" is required by some wallets like MetaMask. diff --git a/pages/stack/chain/testing/testing-apps.mdx b/pages/stack/chain/testing/testing-apps.mdx index 510716d37..df82e37ba 100644 --- a/pages/stack/chain/testing/testing-apps.mdx +++ b/pages/stack/chain/testing/testing-apps.mdx @@ -32,4 +32,4 @@ For example, [Perpetual v. 2](https://docs.perp.com/docs/guides/integration-guid If that is the case you can use [mainnet forking](https://hardhat.org/hardhat-network/guides/mainnet-forking.html). It works with OP Mainnet. -Alternatively, you can connect to our [test network](/chain/networks#op-sepolia) if those contracts are also deployed there (in many cases they are). +Alternatively, you can connect to our [test network](/stack/chain/networks#op-sepolia) if those contracts are also deployed there (in many cases they are). From 53ea46f77896fbffc0a56ec75aca439566db1b98 Mon Sep 17 00:00:00 2001 From: cpengilly <29023967+cpengilly@users.noreply.github.com> Date: Tue, 4 Feb 2025 04:09:49 -0800 Subject: [PATCH 15/49] custom footer --- components/Footer.tsx | 94 ++++++++++++++++++++++++++++++ pages/_meta.json | 98 +++++++++++++++++--------------- pages/app-developers/_meta.json | 4 +- pages/connect/_meta.json | 7 +-- pages/get-started/_meta.json | 34 +++++++++++ pages/get-started/interop.mdx | 9 +++ pages/get-started/op-stack.mdx | 9 +++ pages/get-started/superchain.mdx | 9 +++ pages/operators/_meta.json | 8 +-- pages/stack/_meta.json | 12 ++-- pages/superchain/_meta.json | 4 +- styles/global.css | 52 ++++++++++++++++- theme.config.tsx | 9 ++- 13 files changed, 279 insertions(+), 70 deletions(-) create mode 100644 components/Footer.tsx create mode 100644 pages/get-started/_meta.json create mode 100644 pages/get-started/interop.mdx create mode 100644 pages/get-started/op-stack.mdx create mode 100644 pages/get-started/superchain.mdx diff --git a/components/Footer.tsx b/components/Footer.tsx new file mode 100644 index 000000000..7746dff86 --- /dev/null +++ b/components/Footer.tsx @@ -0,0 +1,94 @@ +import { Link } from 'nextra-theme-docs'; + +export function Footer() { + return ( +
+
+
+

Policies

+
    +
  • + + Community Agreement + +
    • +
  • + Terms of Service +
    • +
  • + + Privacy Policy + +
    • +
  • + Code of Conduct +
    • +
+
+
+

Tools

+
    +
  • + Superchain Faucet +
    • +
  • + Gas Tracker +
    • +
  • + + Service Status + +
    • +
  • + Changelog +
    • +
  • + Devnets +
    • +
+
+
+

Resources

+
    +
  • + Developer Support +
    • +
  • + Get Launch Support +
    • +
  • + Glossary +
    • +
  • + + Contribute to the OP Stack + +
    • +
  • + Protocol Specs +
    • +
+
+
+

Ecosystem

+
    +
  • + + GitHub ↗ + +
    • +
  • + Discord ↗ +
    • +
  • + Twitter ↗ +
    • +
+
+
+
+ © {new Date().getFullYear()} Optimism Foundation. All rights reserved. +
+
+ ); +} \ No newline at end of file diff --git a/pages/_meta.json b/pages/_meta.json index af0cf1fa8..81e46e2cc 100644 --- a/pages/_meta.json +++ b/pages/_meta.json @@ -1,44 +1,36 @@ { "index": { - "title": "Get started", + "title": "Home", "display": "hidden", "theme": { "breadcrumb": false, "footer": true, - "sidebar": true, + "sidebar": false, "toc": false, "pagination": false } }, - - "404": { - "title": "404", - "display": "hidden", - "theme": { - "layout": "full", - "breadcrumb": false, - "footer": true, - "sidebar": true, - "toc": false, - "pagination": false - } + "notices": { + "title": "Notices (README)" + }, + "+++ Notices": { + "title": "", + "type": "separator" }, - "500": { - "title": "500", - "display": "hidden", + "get-started": { + "title": "Get started", + "type":"page", "theme": { - "layout": "full", - "breadcrumb": false, - "footer": true, + "navbar": true, "sidebar": true, - "toc": false, - "pagination": false - } + "toc": true, + "pagination": true + }, + "display": "children" }, - "superchain": { - "title": "The Superchain", + "title": "Superchain", "type":"page", "theme": { "navbar": true, @@ -82,28 +74,42 @@ "display": "children" }, - "+++ NOTICES": { - "title": "", - "type": "separator" - }, - "--- NOTICES": { - "title": "NOTICES", - "type": "separator" - }, - "notices": { - "title": "Notices", - "display": "children" - }, - "+++ CONNECT": { - "title": "", - "type": "separator" - }, - "--- CONNECT": { - "title": "CONNECT", - "type": "separator" - }, "connect": { "title": "Connect", - "display": "children" + "type": "page", + "display": "hidden", + "theme": { + "breadcrumb": false, + "footer": true, + "sidebar": true, + "toc": false, + "pagination": false + } + }, + + "404": { + "title": "404", + "display": "hidden", + "theme": { + "layout": "full", + "breadcrumb": false, + "footer": true, + "sidebar": true, + "toc": false, + "pagination": false + } + }, + + "500": { + "title": "500", + "display": "hidden", + "theme": { + "layout": "full", + "breadcrumb": false, + "footer": true, + "sidebar": true, + "toc": false, + "pagination": false + } } } diff --git a/pages/app-developers/_meta.json b/pages/app-developers/_meta.json index f00e7d62b..d5afc0cfe 100644 --- a/pages/app-developers/_meta.json +++ b/pages/app-developers/_meta.json @@ -1,6 +1,6 @@ { - "--- APP DEVS": { - "title": "APP DEVELOPERS", + "--- App Devs": { + "title": "App Developers", "type": "separator" }, "overview": "Overview", diff --git a/pages/connect/_meta.json b/pages/connect/_meta.json index 3efad2c2d..4d04b9fe8 100644 --- a/pages/connect/_meta.json +++ b/pages/connect/_meta.json @@ -5,10 +5,5 @@ "title": "Get Launch Support", "href": "https://share.hsforms.com/1yENj8CV9TzGYBASD0JC8_gqoshb", "newWindow": true -}, - "governance": { - "title": "Optimism Governance", - "href": "https://community.optimism.io/docs/governance/", - "newWindow": true - } +} } diff --git a/pages/get-started/_meta.json b/pages/get-started/_meta.json new file mode 100644 index 000000000..448c98ad4 --- /dev/null +++ b/pages/get-started/_meta.json @@ -0,0 +1,34 @@ +{ + "--- GetStarted": { + "title": "Get Started", + "type": "separator" + }, + "superchain": "Superchain", + "op-stack": "OP Stack", + "interop": "Interoperability", + "governance": { + "title": "Optimism Governance", + "href": "https://community.optimism.io/docs/governance/", + "newWindow": true + }, + "+++ BuilderGuides": { + "title": "", + "type": "separator" + }, + "--- BuilderGuides": { + "title": "Builder Guides", + "type": "separator" + }, + "app-devs": { + "title": "App Developers", + "href": "/app-developers/overview" + }, + "chain-ops": { + "title": "Chain Operators", + "href": "/operators/chain-operators/architecture" + }, + "node-ops": { + "title": "Node Operators", + "href": "/operators/node-operators/architecture" + } +} \ No newline at end of file diff --git a/pages/get-started/interop.mdx b/pages/get-started/interop.mdx new file mode 100644 index 000000000..3a996050c --- /dev/null +++ b/pages/get-started/interop.mdx @@ -0,0 +1,9 @@ +--- +title: Getting started with the OP Stack +lang: en-US +description: Learn the basics of OP Stack development. +--- + +import InteropExplainer from '@/pages/stack/interop/explainer.mdx' + + diff --git a/pages/get-started/op-stack.mdx b/pages/get-started/op-stack.mdx new file mode 100644 index 000000000..d9bb4d003 --- /dev/null +++ b/pages/get-started/op-stack.mdx @@ -0,0 +1,9 @@ +--- +title: Getting started with the OP Stack +lang: en-US +description: Learn the basics of OP Stack development. +--- + +import StackExplainer from '@/pages/stack/getting-started.mdx' + + diff --git a/pages/get-started/superchain.mdx b/pages/get-started/superchain.mdx new file mode 100644 index 000000000..204ccb2a5 --- /dev/null +++ b/pages/get-started/superchain.mdx @@ -0,0 +1,9 @@ +--- +title: Superchain explainer +lang: en-US +description: Learn about Optimism Superchain components, features, and roadmap. +--- + +import SuperchainExplainer from '@/pages/superchain/superchain-explainer.mdx' + + diff --git a/pages/operators/_meta.json b/pages/operators/_meta.json index 113ad9d1c..73c5f101e 100644 --- a/pages/operators/_meta.json +++ b/pages/operators/_meta.json @@ -1,18 +1,18 @@ { - "--- CHAINS": { - "title": "CHAIN OPERATORS", + "--- Chains": { + "title": "Chain Operators", "type": "separator" }, "chain-operators": { "title": "Chains", "display": "children" }, - "+++ NODES": { + "+++ Nodes": { "title": "", "type": "separator" }, "--- NODES": { - "title": "NODE OPERATORS", + "title": "Node Operators", "type": "separator" }, "node-operators": { diff --git a/pages/stack/_meta.json b/pages/stack/_meta.json index 24d7967c8..be8940ea9 100644 --- a/pages/stack/_meta.json +++ b/pages/stack/_meta.json @@ -1,6 +1,6 @@ { - "--- OP STACK": { - "title": "OP STACK", + "--- OP Stack": { + "title": "OP Stack", "type": "separator" }, "getting-started": "Getting Started with OP Stack", @@ -19,8 +19,12 @@ "title": "OP Mainnet", "display": "hidden" }, - "--- EXPERIMENTAL": { - "title": "EXPERIMENTAL", + "+++ Experimental": { + "title": "", + "type": "separator" + }, + "--- Experimental": { + "title": "Experimental", "type": "separator" }, "opcm": "OP Contracts Manager", diff --git a/pages/superchain/_meta.json b/pages/superchain/_meta.json index ee551b1fe..87ebc747f 100644 --- a/pages/superchain/_meta.json +++ b/pages/superchain/_meta.json @@ -1,6 +1,6 @@ { - "--- SUPERCHAIN": { - "title": "THE SUPERCHAIN", + "--- Superchain": { + "title": "The Superchain", "type": "separator" }, "superchain-explainer": "The Superchain explainer", diff --git a/styles/global.css b/styles/global.css index 23c8cc467..ceeacd038 100644 --- a/styles/global.css +++ b/styles/global.css @@ -49,7 +49,7 @@ span.shasum code { border: none; background-color: transparent !important; } - +/* Custom WIP callout */ div.custom-callouts { position: -webkit-sticky; position: sticky; @@ -87,3 +87,53 @@ html.dark a.callout-link { color: red; font-size: 14px; } +/* Custom 4 column footer */ +div.footer-root { + flex: 1; + font-size: 0.875rem; + color: #666; + + :global(.dark) & { + color: #666; + } + + a.footer-root { + color: #666; + text-decoration: none; + + :global(.dark) & { + color: #666; + } + + &:hover { + color: rgb(17, 24, 39); + + :global(.dark) & { + color: rgb(249, 250, 251); + } + } + } +} + +div.footer-columns { + margin-bottom: 2rem; + display: grid; + gap: 32px; + grid-template-columns: repeat(auto-fit, minmax(140px, 1fr)); + +.footer-columns h3 { + margin-bottom: 20px; + color: rgb(17, 24, 39); + font-weight: 500; + line-height: 20px; + + :global(.dark) & { + color: rgb(243, 244, 246); + } + } + + li.footer-columns { + line-height: 21px; + margin-bottom: 12px; + } +} diff --git a/theme.config.tsx b/theme.config.tsx index 81898b3ac..79356fa13 100644 --- a/theme.config.tsx +++ b/theme.config.tsx @@ -5,6 +5,7 @@ import { useConfig } from "nextra-theme-docs"; import { FeelbackYesNo, PRESET_LIKE_DISLIKE } from "@feelback/react"; import "@feelback/react/styles/feelback.css"; import { Search } from "./components/Search"; +import { Footer } from "./components/Footer"; const config: DocsThemeConfig = { logo: ( @@ -39,12 +40,10 @@ const config: DocsThemeConfig = { search: { component: Search, }, - project: { - link: "https://github.com/ethereum-optimism/docs", - }, docsRepositoryBase: "https://github.com/ethereum-optimism/docs/blob/main/", footer: { - text: ( + text: