diff --git a/docs/run-arbitrum-node/sequencer/04-run-sequencer-node.mdx b/docs/run-arbitrum-node/sequencer/04-run-sequencer-node.mdx
index 500811f52c..56d3a91d2e 100644
--- a/docs/run-arbitrum-node/sequencer/04-run-sequencer-node.mdx
+++ b/docs/run-arbitrum-node/sequencer/04-run-sequencer-node.mdx
@@ -1,6 +1,6 @@
---
-title: 'How to run a normal sequencer node for an Orbit chain'
-description: Learn how to run an normal Arbitrum orbit sequencer node on your local machine
+title: 'How to run a normal sequencer node for an Arbitrum chain'
+description: Learn how to run an normal Arbitrum chain sequencer node on your local machine
author: Jason Wan
sme: Jason Wan
content_type: how-to
@@ -8,9 +8,9 @@ content_type: how-to
:::caution
-The following instructions are meant for Arbitrum Orbit chains only. This article only applies to test environments. If you need support spinning up a production Orbit chain, we recommend contacting a [provider](/launch-arbitrum-chain/06-third-party-integrations/02-third-party-providers.md#rollup-as-a-service-raas-providers).
+The following instructions are meant for Arbitrum chains only. This article only applies to test environments. If you need support spinning up a production Arbitrum chain, we recommend contacting a [provider](/launch-arbitrum-chain/06-third-party-integrations/02-third-party-providers.md#rollup-as-a-service-raas-providers).
-We also provide a guide for running a high-availability sequencer node for an Orbit chain. You can find it [here](./05-high-availability-sequencer-docs.mdx).
+We also provide a [guide for running a high-availability sequencer node for an Arbitrum chain](./05-high-availability-sequencer-docs.mdx).
:::
This how-to provides step-by-step instructions for running a sequencer node on your local machine.
@@ -196,7 +196,7 @@ chmod -fR 777 /data/arbitrum
## Optional parameters
-Here's a list of the parameters that are most commonly used when running your Orbit sequencer node. You can also use the flag `--help` for a comprehensive list of available parameters.
+Here's a list of the parameters that are most commonly used when running your Arbitrum chain sequencer node. You can also use the flag `--help` for a comprehensive list of available parameters.
import OptionalOrbitSequencerCompatibleCLIFlagsPartial from '../partials/run-full-node/_optional-orbit-sequencer-compatible-cli-partial.mdx';
diff --git a/sidebars.js b/sidebars.js
index 2fdcd5db43..2e08799bac 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -56,7 +56,7 @@ const sidebars = {
},
{
type: 'link',
- label: 'Run an Arbitrum (Orbit) chain',
+ label: 'Run an Arbitrum chain',
href: '/launch-arbitrum-chain/a-gentle-introduction',
},
{
@@ -164,7 +164,7 @@ const sidebars = {
runArbitrumChainSidebar: [
{
type: 'category',
- label: 'Run an Arbitrum (Orbit) chain',
+ label: 'Run an Arbitrum chain',
collapsed: false,
items: [
{
diff --git a/static/building-faqs.json b/static/building-faqs.json
index 9c38dd6373..ceef1f7ac5 100644
--- a/static/building-faqs.json
+++ b/static/building-faqs.json
@@ -26,7 +26,7 @@
},
{
"question": "Why do I get \"custom tx type\" errors when I use hardhat?",
- "answer": "In Arbitrum, we use a number of non-standard [EIP-2718](https://eips.ethereum.org/EIPS/eip-2718) typed transactions. See [here](https://developer.arbitrum.io/arbos/geth#transaction-types) for the full list and the rationale.\n\nNote that if you're using Hardhat, [v2.12.2](https://github.com/NomicFoundation/hardhat/releases/tag/hardhat%402.12.2) added support for forking networks like Arbitrum with custom transaction types (find more information [here](https://github.com/NomicFoundation/hardhat/issues/2995)).\n\n\n\n",
+ "answer": "In Arbitrum, we use a number of non-standard [EIP-2718](https://eips.ethereum.org/EIPS/eip-2718) typed transactions. Feel free to consult the [full list of transaction types](https://developer.arbitrum.io/arbos/geth#transaction-types) and the rationale.\n\nNote that if you're using Hardhat, [v2.12.2](https://github.com/NomicFoundation/hardhat/releases/tag/hardhat%402.12.2) added support for forking networks like Arbitrum with custom transaction types (find more information [in this HardHat GitHub issue](https://github.com/NomicFoundation/hardhat/issues/2995)).\n\n\n\n",
"key": "why-do-i-get-custom-tx-type-errors-when-i-use-hardhat"
},
{
@@ -96,7 +96,7 @@
},
{
"question": "What is the WASM module root?",
- "answer": "The WASM module root is a 32-byte hash, which is a Merkelization of the Go replay binary and its dependencies.\n\nThe replay binary is much too large to post on-chain, so this hash is set in the L1 rollup contract to determine the correct replay binary during fraud proofs.\n\nYou can find more information in [How to Customize your Orbit chain's behavior](https://docs.arbitrum.io/launch-orbit-chain/how-tos/customize-stf#step-4-enable-fraud-proofs).\n\n\n\n",
+ "answer": "The WASM module root is a 32-byte hash, which is a Merkelization of the Go replay binary and its dependencies.\n\nThe replay binary is much too large to post on-chain, so this hash is set in the L1 rollup contract to determine the correct replay binary during fraud proofs.\n\nYou can find more information in [How to Customize your Arbitrum chain's behavior](https://docs.arbitrum.io/launch-orbit-chain/how-tos/customize-stf#step-4-enable-fraud-proofs).\n\n\n\n",
"key": "what-is-the-wasm-module-root"
},
{
diff --git a/static/building-orbit-faqs.json b/static/building-orbit-faqs.json
index e096404e32..2aa9374480 100644
--- a/static/building-orbit-faqs.json
+++ b/static/building-orbit-faqs.json
@@ -1,63 +1,63 @@
[
{
- "question": "Can I use Orbit to deploy a mainnet chain?",
- "answer": "Yes! Arbitrum Orbit's core technology has undergone a comprehensive audit and is now capable of supporting deployments to mainnet. You can read more about it [here](https://docs.arbitrum.io/launch-orbit-chain/concepts/public-preview-expectations#arbitrum-orbit-is-mainnet-ready-but-deploy-to-testnet-first).\n\n\n\n",
- "key": "can-i-use-orbit-to-deploy-a-mainnet-chain"
+ "question": "Can I use the Chain SDK to deploy a mainnet chain?",
+ "answer": "Yes! The Arbitrum Chain SDK's core technology has undergone a comprehensive audit and is now capable of supporting deployments to mainnet. You can read more about it in our [preview expectations notice](https://docs.arbitrum.io/launch-orbit-chain/concepts/public-preview-expectations#arbitrum-orbit-is-mainnet-ready-but-deploy-to-testnet-first).\n\n\n\n",
+ "key": "can-i-use-the-chain-sdk-to-deploy-a-mainnet-chain"
},
{
- "question": "Do I need permission/license to launch an Orbit chain?",
- "answer": "You can launch any Arbitrum Orbit chain permissionlessly.\n\nNitro's license is under a [Business Source license](https://github.com/OffchainLabs/nitro?tab=License-1-ov-file), similar to DeFi protocols like Uniswap and Aave, among others. This license contains an Additional Use Grant that permits the permissionless deployment of Nitro software on blockchains that settle to Arbitrum One or Nova.\n\nHowever, Arbitrum Orbit chains that settle to a parent chain other than Arbitrum One or Nova are subject to additional licensing guidelines under the [AEP](https://docs.arbitrum.foundation/aep/ArbitrumExpansionProgramTerms.pdf).\n\n",
- "key": "do-i-need-permissionlicense-to-launch-an-orbit-chain"
+ "question": "Do I need permission/license to launch an Arbitrum chain?",
+ "answer": "You can launch any Arbitrum chain permissionlessly.\n\nNitro's license is under a [Business Source license](https://github.com/OffchainLabs/nitro?tab=License-1-ov-file), similar to DeFi protocols like Uniswap and Aave, among others. This license contains an Additional Use Grant that permits the permissionless deployment of Nitro software on blockchains that settle to Arbitrum One or Nova.\n\nHowever, Arbitrum chains that settle to a parent chain other than Arbitrum One or Nova are subject to additional licensing guidelines under the [AEP](https://docs.arbitrum.foundation/aep/ArbitrumExpansionProgramTerms.pdf).\n\n",
+ "key": "do-i-need-permissionlicense-to-launch-an-arbitrum-chain"
},
{
"question": "Does Arbitrum officially deploy and/or maintain L3s for external teams?",
- "answer": "No. Teams are required to deploy and maintain their Arbitrum Orbit chains. There are, however, several RaaS (Rollup as a Service) providers that can deploy and maintain your Arbitrum Orbit chain on your behalf.\n\n\n\n",
+ "answer": "No. Teams are required to deploy and maintain their Arbitrum chains. There are, however, several RaaS (Rollup as a Service) providers that can deploy and maintain your Arbitrum chain on your behalf.\n\n\n\n",
"key": "does-arbitrum-officially-deploy-andor-maintain-l3s-for-external-teams"
},
{
- "question": "Can I modify Orbit's underlying technology to customize my chain?",
+ "question": "Can I modify the underlying technology to customize my Arbitrum chain?",
"answer": "Yes, you can make any changes you require to the underlying Nitro code base.\n\n\n\n",
- "key": "can-i-modify-orbits-underlying-technology-to-customize-my-chain"
+ "key": "can-i-modify-the-underlying-technology-to-customize-my-arbitrum-chain"
},
{
- "question": "What Data Availability (DA) solutions are currently available for Orbit chains?",
- "answer": "Arbitrum Orbit currently supports three different DA solutions:\n\n- Rollup, posting data to the parent chain, which ultimately posts the data to Ethereum.\n- AnyTrust, posting data to a Data Availability Committee, selected by the chain owner.\n- Celestia, posting data to the [Celestia network](https://blog.celestia.org/celestia-is-first-modular-data-availability-network-to-integrate-with-arbitrum-orbit/).\nNote that using AnyTrust provides the chain owner with the most flexibility and the most cost-effective fees.\n\n",
- "key": "what-data-availability-da-solutions-are-currently-available-for-orbit-chains"
+ "question": "What Data Availability (DA) solutions are currently available for Arbitrum chains?",
+ "answer": "Arbitrum chains currently support three different DA solutions:\n\n- Rollup, posting data to the parent chain, which ultimately posts the data to Ethereum.\n- AnyTrust, posting data to a Data Availability Committee, selected by the chain owner.\n- Celestia, posting data to the [Celestia network](https://blog.celestia.org/celestia-is-first-modular-data-availability-network-to-integrate-with-arbitrum-orbit/).\nNote that using AnyTrust provides the chain owner with the most flexibility and the most cost-effective fees.\n\n",
+ "key": "what-data-availability-da-solutions-are-currently-available-for-arbitrum-chains"
},
{
- "question": "What token is used to pay gas fees on Orbit chains?",
- "answer": "By default, Arbitrum Orbit chains pay gas in `ETH`. However, Arbitrum Orbit chains that use AnyTrust are configurable to use any `ERC-20` token for the gas fee token of the chain.\n\n\n\n",
- "key": "what-token-is-used-to-pay-gas-fees-on-orbit-chains"
+ "question": "What token is used to pay gas fees on Arbitrum chains?",
+ "answer": "By default, Arbitrum chains pay gas in `ETH`. However, Arbitrum chains that use AnyTrust are configurable to use any `ERC-20` token for the gas fee token of the chain.\n\n\n\n",
+ "key": "what-token-is-used-to-pay-gas-fees-on-arbitrum-chains"
},
{
- "question": "Can I use Ethereum toolkits to develop on my Orbit chain?",
- "answer": "Arbitrum Orbit chains are fully EVM-compatible. Most tools that support Ethereum should be able to support an Arbitrum Orbit chain. There are, however, specific differences that developers need to consider when building on an Orbit chain. You can find them [here](https://docs.arbitrum.io/for-devs/concepts/differences-between-arbitrum-ethereum/overview).\n\n\n\n",
- "key": "can-i-use-ethereum-toolkits-to-develop-on-my-orbit-chain"
+ "question": "Can I use Ethereum toolkits to develop on my Arbitrum chain?",
+ "answer": "Arbitrum chains are fully EVM-compatible. Most tools that support Ethereum should be able to support an Arbitrum chain. There are, however, specific differences that developers need to consider when building on an Arbitrum chain. You can find them in our [overview of the differences between Arbitrum and Ethereum](https://docs.arbitrum.io/for-devs/concepts/differences-between-arbitrum-ethereum/overview).\n\n\n\n",
+ "key": "can-i-use-ethereum-toolkits-to-develop-on-my-arbitrum-chain"
},
{
- "question": "Do Orbit chains have any built-in AA solution?",
+ "question": "Do Arbitrum chains have any built-in AA solution?",
"answer": "Not by default, but they can be customized to have native AA.\n\n",
- "key": "do-orbit-chains-have-any-builtin-aa-solution"
+ "key": "do-arbitrum-chains-have-any-builtin-aa-solution"
},
{
- "question": "Is there any cross-chain bridging solution between two Orbit chains?",
- "answer": "There is currently no native Orbit-to-Orbit chain bridging solution, except for going through the parent chain (even if they share the same parent chain). However, many third-party bridges have expressed interest in supporting Arbitrum Orbit chains.\n\n\n\n",
- "key": "is-there-any-crosschain-bridging-solution-between-two-orbit-chains"
+ "question": "Is there any cross-chain bridging solution between two Arbitrum chains?",
+ "answer": "There is currently no native Arbitrum-to-Arbitrum chain bridging solution, except for going through the parent chain (even if they share the same parent chain). However, many third-party bridges have expressed interest in supporting Arbitrum chains.\n\n\n\n",
+ "key": "is-there-any-crosschain-bridging-solution-between-two-arbitrum-chains"
},
{
- "question": "Is there an official block explorer for Orbit chains?",
- "answer": "Arbitrum Orbit chains deployments usually come with an open-source Blockscout explorer by default, but there are many third-party solutions that have expressed interest in supporting Arbitrum Orbit chains.\n\n\n\n",
- "key": "is-there-an-official-block-explorer-for-orbit-chains"
+ "question": "Is there an official block explorer for Arbitrum chains?",
+ "answer": "Arbitrum chains deployments usually come with an open-source Blockscout explorer by default, but there are many third-party solutions that have expressed interest in supporting Arbitrum chains.\n\n\n\n",
+ "key": "is-there-an-official-block-explorer-for-arbitrum-chains"
},
{
- "question": "Is there any indexing solution that supports Orbit chains?",
- "answer": "Similar to bridges and block explorers, there are many third-party indexing solutions that have expressed interest in supporting Arbitrum Orbit chains.\n\n\n\n",
- "key": "is-there-any-indexing-solution-that-supports-orbit-chains"
+ "question": "Is there any indexing solution that supports Arbitrum chains?",
+ "answer": "Similar to bridges and block explorers, there are many third-party indexing solutions that have expressed interest in supporting Arbitrum chains.\n\n\n\n",
+ "key": "is-there-any-indexing-solution-that-supports-arbitrum-chains"
},
{
- "question": "Can I increase the maximum contract size for my Orbit chain?",
- "answer": "Yes, Arbitrum Orbit chains support an increased smart contract size limit of up to 96kB. You can use our [Orbit SDK](https://github.com/OffchainLabs/arbitrum-orbit-sdk) and configure the parameters `[MaxCodeSize](https://github.com/OffchainLabs/arbitrum-orbit-sdk/blob/main/src/prepareChainConfig.ts#L29)`[ and ](https://github.com/OffchainLabs/arbitrum-orbit-sdk/blob/main/src/prepareChainConfig.ts#L29)`[MaxInitCodeSize](https://github.com/OffchainLabs/arbitrum-orbit-sdk/blob/main/src/prepareChainConfig.ts#L29)` when calling `[prepareNodeConfig](https://github.com/OffchainLabs/arbitrum-orbit-sdk/blob/main/examples/prepare-node-config/index.ts#L43)`. Once deployed, you cannot change the parameters for the smart contract size limit through an upgrade.\n\n\n\n",
- "key": "can-i-increase-the-maximum-contract-size-for-my-orbit-chain"
+ "question": "Can I increase the maximum contract size for my Arbitrum chain?",
+ "answer": "Yes, Arbitrum chains support an increased smart contract size limit of up to 96kB. You can use our [Chain SDK](https://github.com/OffchainLabs/arbitrum-orbit-sdk) and configure the parameters `[MaxCodeSize](https://github.com/OffchainLabs/arbitrum-orbit-sdk/blob/main/src/prepareChainConfig.ts#L29)`[ and ](https://github.com/OffchainLabs/arbitrum-orbit-sdk/blob/main/src/prepareChainConfig.ts#L29)`[MaxInitCodeSize](https://github.com/OffchainLabs/arbitrum-orbit-sdk/blob/main/src/prepareChainConfig.ts#L29)` when calling `[prepareNodeConfig](https://github.com/OffchainLabs/arbitrum-orbit-sdk/blob/main/examples/prepare-node-config/index.ts#L43)`. Once deployed, you cannot change the parameters for the smart contract size limit through an upgrade.\n\n\n\n",
+ "key": "can-i-increase-the-maximum-contract-size-for-my-arbitrum-chain"
},
{
"question": "How can I modify Nitro to force posting an invalid assertion and test the fraud proof mechanism?",
@@ -66,12 +66,12 @@
},
{
"question": "What fee collectors can be configured on my chain?",
- "answer": "Four fee types are configurable on an Orbit chain:\n\n- **L2 base fee**: L2 execution fees corresponding to the minimum base price of the chain. This fee is deposited into the infraFeeAccount, which can be set by calling `ArbOwner.setInfraFeeAccount().`\n- **L2 surplus fee**: L2 execution fees above the minimum base price (in the case of congestion). This fee goes to the `networkFeeAccount`, which can be set by calling `ArbOwner.setNetworkFeeAccount().`\n- **L1 base fee**: Relative fees for posting a transaction on the parent chain. This fee is paid ultimately to the fee collector of the active batch poster. A call to `SequencerInbox.setIsBatchPoster()` on the parent chain will set the batch poster. Delegating a different fee collector for that batch poster can be specified by calling `ArbAggregator.setFeeCollector()`.\n- **L1 surplus fee**: Any extra fees rewarded to the batch poster. This is paid to a specific `L1RewardRecipient`, which can be set by calling `ArbOwner.setL1PricingRewardRecipient()`.\nFor more detailed information about fees, please refer to the [L1 Fees](https://docs.arbitrum.io/arbos/l1-pricing) and [L2 Fees](https://docs.arbitrum.io/arbos/gas) pages.\n\nTo learn more about precompiles, refer to the [Precompiles reference page](https://docs.arbitrum.io/build-decentralized-apps/precompiles/reference).\n\n",
+ "answer": "Four fee types are configurable on an Arbitrum chain:\n\n- **L2 base fee**: L2 execution fees corresponding to the minimum base price of the chain. This fee is deposited into the `infraFeeAccount`, which can be set by calling `ArbOwner.setInfraFeeAccount().`\n- **L2 surplus fee**: L2 execution fees above the minimum base price (in the case of congestion). This fee goes to the `networkFeeAccount`, which can be set by calling `ArbOwner.setNetworkFeeAccount().`\n- **L1 base fee**: Relative fees for posting a transaction on the parent chain. This fee is paid ultimately to the fee collector of the active batch poster. A call to `SequencerInbox.setIsBatchPoster()` on the parent chain will set the batch poster. Delegating a different fee collector for that batch poster can be specified by calling `ArbAggregator.setFeeCollector()`.\n- **L1 surplus fee**: Any extra fees rewarded to the batch poster. This is paid to a specific `L1RewardRecipient`, which can be set by calling `ArbOwner.setL1PricingRewardRecipient()`.\nFor more detailed information about fees, please refer to the [L1 Fees](https://docs.arbitrum.io/arbos/l1-pricing) and [L2 Fees](https://docs.arbitrum.io/arbos/gas) pages.\n\nTo learn more about precompiles, refer to the [Precompiles reference page](https://docs.arbitrum.io/build-decentralized-apps/precompiles/reference).\n\n",
"key": "what-fee-collectors-can-be-configured-on-my-chain"
},
{
"question": "What is the lowest you can set the base fee to?",
- "answer": "You can set the base fee to any amount to charge users less. You can even set it to `0` (however, this would open the chain to DOS attacks). If the Orbit base fee is `0`, users are then only paying for the cost of DA.\n\n",
+ "answer": "You can set the base fee to any amount to charge users less. You can even set it to `0` (however, this would open the chain to DOS attacks). If the Arbitrum chain base fee is `0`, users are then only paying for the cost of DA.\n\n",
"key": "what-is-the-lowest-you-can-set-the-base-fee-to"
},
{
@@ -101,12 +101,12 @@
},
{
"question": "What is the max theoretical TPS for an Arbitrum Chain?",
- "answer": "Max TPS is a challenging metric to measure, as it relies on network activity and the type of submitted transactions. We can, however, calculate the max throughput using default orbit chain parameters.\n\nThe actual maximum throughput depends on the configurable execution parameters:\n\n**Using standard Arbitrum chain defaults**\n\n- Block time: 250ms\n- Block gas limit: 32M L2 gas\n- Max L2 gas per second: 128M gas/sec\n- These parameters are entirely configurable, for example, by dropping the block time to 100ms or by increasing the block gas limit (which comes at the cost of faster state bloat).\n- Dropping to 100ms and doubling the block gas limit to 64m L2 gas would achieve 640m L2 gas per second.\n**The actual TPS varies depending on the gas cost per transaction:**\n\n- A simple transfer (~21,000 gas) could approximately achieve around 6,000 TPS.\n- A more complex transaction (~200,000 gas) would enable approximately 640 TPS.\n",
+ "answer": "Max TPS is a challenging metric to measure, as it relies on network activity and the type of submitted transactions. We can, however, calculate the max throughput using default Arbitrum chain parameters.\n\nThe actual maximum throughput depends on the configurable execution parameters:\n\n**Using standard Arbitrum chain defaults**\n\n- Block time: 250ms\n- Block gas limit: 32M L2 gas\n- Max L2 gas per second: 128M gas/sec\n- These parameters are entirely configurable, for example, by dropping the block time to 100ms or by increasing the block gas limit (which comes at the cost of faster state bloat).\n- Dropping to 100ms and doubling the block gas limit to 64m L2 gas would achieve 640m L2 gas per second.\n**The actual TPS varies depending on the gas cost per transaction:**\n\n- A simple transfer (~21,000 gas) could approximately achieve around 6,000 TPS.\n- A more complex transaction (~200,000 gas) would enable approximately 640 TPS.\n",
"key": "what-is-the-max-theoretical-tps-for-an-arbitrum-chain"
},
{
"question": "Why is the WETH Gateway not necessary for custom gas token chains?",
- "answer": "The `WETH` gateway used in the token bridge is a special, custom gateway that unwraps the `WETH` deposits and sends them to the Arbitrum chain, then wraps them again on the Arbitrum chain. Since `ETH` is the gas token in the Arbitrum (Orbit) chain, there's no need to perform this operation, so you can use a standard `ERC-20` for `WETH` (this is the default case of the token bridge so that you wouldn't need a special `WETH` gateway).\n\nIf you want to enable extra custom operations with `WETH`, you can create a custom token and a custom gateway to handle this case.\n\n",
+ "answer": "The `WETH` gateway used in the token bridge is a special, custom gateway that unwraps the `WETH` deposits and sends them to the Arbitrum chain, then wraps them again on the Arbitrum chain. Since `ETH` is the gas token in the Arbitrum chain, there's no need to perform this operation, so you can use a standard `ERC-20` for `WETH` (this is the default case of the token bridge so that you wouldn't need a special `WETH` gateway).\n\nIf you want to enable extra custom operations with `WETH`, you can create a custom token and a custom gateway to handle this case.\n\n",
"key": "why-is-the-weth-gateway-not-necessary-for-custom-gas-token-chains"
},
{
diff --git a/static/get-started-faqs.json b/static/get-started-faqs.json
index b3229e30ec..4f095c33dd 100644
--- a/static/get-started-faqs.json
+++ b/static/get-started-faqs.json
@@ -79,14 +79,9 @@
"answer": "There is no notion of a mempool on Arbitrum; transactions are processed on a first-come, first-served basis by the Sequencer. Thus, the gas price bid parameter does not affect the order in which transactions get processed.\n\n\n\n",
"key": "will-transactions-with-a-higher-gas-price-bid-be-confirmed-first"
},
- {
- "question": "Where can I find a list of the current validators of the Arbitrum chains?",
- "answer": "Validation on both Arbitrum One and Arbitrum Nova is currently allow-listed to a committee of public entities. You can see the list of validators **[here](https://docs.arbitrum.foundation/state-of-progressive-decentralization#allowlisted-validators)**. Governance currently has the power to change this status.\n\n\n\n",
- "key": "where-can-i-find-a-list-of-the-current-validators-of-the-arbitrum-chains"
- },
{
"question": "Where can I find the current Data Availability Committee members?",
- "answer": "The Arbitrum Nova chain has a 7-party DAC, whose members can be seen **[here](https://docs.arbitrum.foundation/state-of-progressive-decentralization#data-availability-committee-members)**. Governance has the ability to remove or add members to the committee.\n\n\n\n",
+ "answer": "The Arbitrum Nova chain has a 7-party DAC, whose members can be seen in the [Arbitrum Foundation's state of progressive decentralization status document](https://docs.arbitrum.foundation/state-of-progressive-decentralization#data-availability-committee-members). Governance has the ability to remove or add members to the committee.\n\n\n\n",
"key": "where-can-i-find-the-current-data-availability-committee-members"
},
{
diff --git a/static/glossary.json b/static/glossary.json
index 62b58092cd..53d3193b97 100644
--- a/static/glossary.json
+++ b/static/glossary.json
@@ -41,7 +41,7 @@
},
"arbitrum-chains": {
"title": "Arbitrum Chains",
- "text": "Arbitrum chains (Orbit) refers to the ability for anyone to permissionlessly deploy Layer 3 (L3) chains on top of Arbitrum Layer 2 (L2) chains.
\n"
+ "text": "Arbitrum chains refers to the ability for anyone to permissionlessly deploy Layer 3 (L3) chains on top of Arbitrum Layer 2 (L2) chains.
\n"
},
"arbitrum-classic": {
"title": "Arbitrum Classic",
diff --git a/static/node-running-faqs.json b/static/node-running-faqs.json
index 2daefd9a41..c1a01fa3f9 100644
--- a/static/node-running-faqs.json
+++ b/static/node-running-faqs.json
@@ -1,7 +1,7 @@
[
{
"question": "How do I run a node?",
- "answer": "See instructions [here](https://developer.arbitrum.io/node-running/how-tos/running-a-full-node)! \n\n\n\n",
+ "answer": "See instructions [in our guide about running a full node](https://developer.arbitrum.io/node-running/how-tos/running-a-full-node)!\n\n\n\n",
"key": "how-do-i-run-a-node"
},
{
@@ -36,7 +36,7 @@
},
{
"question": "Is there any way to retrieve pre-Nitro archive data from a Nitro node?",
- "answer": "The pre-Nitro stack is also called the \"classic\" stack. Full Nitro nodes start with a database that contains the information from the \"classic\" era.\n\nHowever, a Nitro node can't query archive information contained in \"classic\" blocks right away. To do that, you also need to run a classic node ([instructions here](https://developer.arbitrum.io/node-running/how-tos/running-a-classic-node)) and set the parameter `—node.rpc.classic-redirect=your-classic-node-RPC`.\n\nPlease note that this information only applies to Arbitrum One nodes. Arbitrum Nova and Sepolia nodes started with a Nitro stack, so they don't have \"classic\" data.\n\n",
+ "answer": "The pre-Nitro stack is also called the \"classic\" stack. Full Nitro nodes start with a database that contains the information from the \"classic\" era.\n\nHowever, a Nitro node can't query archive information contained in \"classic\" blocks right away. To do that, you also need to run a classic node ([instructions in our guide about running a classic node](https://developer.arbitrum.io/node-running/how-tos/running-a-classic-node)) and set the parameter `—node.rpc.classic-redirect=your-classic-node-RPC`.\n\nPlease note that this information only applies to Arbitrum One nodes. Arbitrum Nova and Sepolia nodes started with a Nitro stack, so they don't have \"classic\" data.\n\n\n\n",
"key": "is-there-any-way-to-retrieve-prenitro-archive-data-from-a-nitro-node"
},
{
diff --git a/vercel.json b/vercel.json
index ad693a20fc..16d55b69eb 100644
--- a/vercel.json
+++ b/vercel.json
@@ -75,6 +75,11 @@
"destination": "/(docs/get-started/overview/?)",
"permanent": true
},
+ {
+ "source": "/(/node-running/how-tos/running-an-orbit-node/?)",
+ "destination": "launch-arbitrum-chain/a-gentle-introduction",
+ "permanent": false
+ },
{
"source": "/(anytrust/inside-anytrust/?)",
"destination": "/how-arbitrum-works/deep-dives/anytrust-protocol",
@@ -1433,7 +1438,7 @@
},
{
"source": "/(launch-orbit-chain/reference/command-line-options/?)",
- "destination": "/node-running/how-tos/running-an-orbit-node",
+ "destination": "/launch-arbitrum-chain/a-gentle-introduction",
"permanent": false
},
{