Merge pull request #657 from OffchainLabs/add-missing-mentions-to-sep…

…olia

Add mentions to Sepolia on several places

arbitrum-docs/for-devs/concepts/public-chains.mdx

@@ -52,7 +52,7 @@ Finally, Arbitrum Sepolia is a testnet chain. It's designed for testing purposes
 
 ### Nitro
 
-Nitro is the technology that powers Arbitrum One, Arbitrum Nova (with Anytrust configuration) and Arbitrum Goerli. It's designed to offer high throughput and low cost, making it ideal for scaling Ethereum applications. Nitro is a major upgrade to the “Classic” stack, offering several improvements including advanced calldata compression, separate contexts for common execution and fault proving, Ethereum L1 gas compatibility, and more. You can find more information about Nitro in [Inside Arbitrum Nitro](/inside-arbitrum-nitro/inside-arbitrum-nitro.mdx).
+Nitro is the technology that powers Arbitrum One, Arbitrum Nova (with Anytrust configuration), Arbitrum Sepolia, and Arbitrum Goerli. It's designed to offer high throughput and low cost, making it ideal for scaling Ethereum applications. Nitro is a major upgrade to the “Classic” stack, offering several improvements including advanced calldata compression, separate contexts for common execution and fault proving, Ethereum L1 gas compatibility, and more. You can find more information about Nitro in [Inside Arbitrum Nitro](/inside-arbitrum-nitro/inside-arbitrum-nitro.mdx).
 
 ### AnyTrust (variant of Nitro)
 

arbitrum-docs/for-devs/dev-tools-and-resources/monitoring-tools-block-explorers.mdx

@@ -12,9 +12,10 @@ import KnowMoreToolsBox from '../partials/_know-more-tools-box-partial.md';
 
 Here, we offer a compilation of tools and blockchain explorers that enable you to examine and oversee transactions, smart contracts, and overall blockchain activity related to decentralized applications (dApps) on different Arbitrum chains.
 
-| Tool | Use-cases | Relevant links |
-| --------- | ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Arbiscan | Track/trace transactions and examine addresses on Arbitrum networks | <ul><li>Arbitrum One: [https://arbiscan.io/](https://arbiscan.io/)</li><li>Arbitrum Nova: [https://nova.arbiscan.io/](https://nova.arbiscan.io/)</li><li>Arbitrum Goerli: [https://goerli.arbiscan.io/](https://goerli.arbiscan.io/)</li></ul> |
-| DexGuru | Track/trace transactions and examine addresses on Arbitrum networks | <ul><li>Arbitrum One: [https://arbitrum.dex.guru/](https://arbitrum.dex.guru/)</li><li>Arbitrum Nova: [https://nova.dex.guru/](https://nova.dex.guru/)</li></ul> |
-| Dune | Visualize and analyze Arbitrum network data | <ul><li>[Dune](https://dune.com/)</li><li>[Arbitrum community-created Duune dashboard](https://dune.com/browse/dashboards?q=arbitrum)</li></ul> |
-| Chainbase | Index, transform, and use on-chain data at scale | [Chainbase](https://chainbase.com/) |
+| Tool | Use-cases | Relevant links |
+| ---------- | ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Arbiscan | Track/trace transactions and examine addresses on Arbitrum networks | <ul><li>Arbitrum One: [https://arbiscan.io/](https://arbiscan.io/)</li><li>Arbitrum Nova: [https://nova.arbiscan.io/](https://nova.arbiscan.io/)</li><li>Arbitrum Goerli: [https://goerli.arbiscan.io/](https://goerli.arbiscan.io/)</li></ul> |
+| DexGuru | Track/trace transactions and examine addresses on Arbitrum networks | <ul><li>Arbitrum One: [https://arbitrum.dex.guru/](https://arbitrum.dex.guru/)</li><li>Arbitrum Nova: [https://nova.dex.guru/](https://nova.dex.guru/)</li></ul> |
+| Blockscout | Track/trace transactions and examine addresses on Arbitrum networks | <ul><li>Arbitrum Sepolia: [https://sepolia-explorer.arbitrum.io/](https://sepolia-explorer.arbitrum.io/)</li></ul> |
+| Dune | Visualize and analyze Arbitrum network data | <ul><li>[Dune](https://dune.com/)</li><li>[Arbitrum community-created Duune dashboard](https://dune.com/browse/dashboards?q=arbitrum)</li></ul> |
+| Chainbase | Index, transform, and use on-chain data at scale | [Chainbase](https://chainbase.com/) |

arbitrum-docs/node-running/how-tos/running-a-classic-node.mdx

@@ -17,7 +17,7 @@ The following commands are supported when running an Arbitrum Classic archive no
 - `eth_getTransactionCount`
 - `eth_getStorageAt`
 
-🔉 Note that both Arbitrum Nova and Arbitrum Goerli started as a Nitro chain, so they don't have classic blocks.
+🔉 Note that Arbitrum Nova, Arbitrum Goerli and Arbitrum Sepolia started as a Nitro chain, so they don't have classic blocks.
 
 ### Required artifacts
 

arbitrum-docs/node-running/how-tos/running-a-full-node.mdx

@@ -41,7 +41,7 @@ The minimum storage requirements will change over time as the Nitro chain grows.
  - Note: this parameter was called --l1.url in versions prior to `v2.1.0`
 - L2 chain id or name
  - Use the parameter `--chain.id=<L2 chain ID>` to set the L2 chain from its chain id. See [RPC endpoints and providers](/node-running/node-providers.mdx#rpc-endpoints) for a list of Arbitrum chains and their respective L2 chain ids.
- - Alternatively, you can use the parameter `--chain.name=<L2 chain name>` to set the L2 chain from its name (options are: `arb1`, `nova` and `goerli-rollup`)
+ - Alternatively, you can use the parameter `--chain.name=<L2 chain name>` to set the L2 chain from its name (options are: `arb1`, `nova`, `goerli-rollup` and `sepolia-rollup`)
  - Note: this parameter was called --l2.chain-id and only accepted chain ids in versions prior to `v2.1.0`
 
 ### Important ports

arbitrum-docs/node-running/how-tos/running-an-archive-node.mdx

@@ -15,13 +15,13 @@ Before the Nitro upgrade happened, Arbitrum One was running on the Classic stack
 
 Running an Arbitrum One **full node** in **archive mode** lets you access both pre-Nitro and post-Nitro blocks, but it requires you to run **both Classic and Nitro nodes** together. You may not need to do this, depending on your use case:
 
-| Use case | Required node type(s) | Docs |
-| ------------------------------------------------------------------------------ | --------------------------------------------------------- | --------------------------------------------------------------------------- |
-| Access the **Arbitrum network** without running your own node | Fully managed by third-parties, exposed via RPC endpoints | [RPC endpoints and providers](/node-running/node-providers.mdx) |
-| Run an **archive node** for **Arbitrum Goerli (testnet)** or **Arbitrum Nova** | Full node (Nitro) | [How to run a full node (Nitro)](./running-a-full-node.mdx) |
-| Send **post-Nitro** archive requests | Full node (Nitro) | [How to run a full node (Nitro)](./running-a-full-node.mdx) |
-| Send **pre-Nitro** archive requests | Full node (Classic) | [How to run a full node (Classic, pre-Nitro)](./running-a-classic-node.mdx) |
-| Send **post-Nitro** _and_ **pre-Nitro** archive requests | Full node (Nitro) _and_ full node (Classic) | That's what this how-to is for; you're in the right place. |
+| Use case  | Required node type(s) | Docs |
+| -------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | --------------------------------------------------------------------------- |
+| Access the **Arbitrum network** without running your own node  | Fully managed by third-parties, exposed via RPC endpoints | [RPC endpoints and providers](/node-running/node-providers.mdx) |
+| Run an **archive node** for **Arbitrum Goerli (testnet)**, **Arbitrum Sepolia (testnet)** or **Arbitrum Nova** | Full node (Nitro) | [How to run a full node (Nitro)](./running-a-full-node.mdx) |
+| Send **post-Nitro** archive requests  | Full node (Nitro) | [How to run a full node (Nitro)](./running-a-full-node.mdx) |
+| Send **pre-Nitro** archive requests  | Full node (Classic) | [How to run a full node (Classic, pre-Nitro)](./running-a-classic-node.mdx) |
+| Send **post-Nitro** _and_ **pre-Nitro** archive requests  | Full node (Nitro) _and_ full node (Classic) | That's what this how-to is for; you're in the right place. |
 
 ### System requirements
 

arbitrum-docs/node-running/troubleshooting-running-nodes.md

@@ -67,6 +67,7 @@ If you're running into unexpected outputs or errors, the following checklist may
   { label: 'Arbitrum One (Classic)', value: 'arb-one-classic' },
   { label: 'Arbitrum Nova', value: 'arb-nova' },
   { label: 'Arbitrum Goerli', value: 'arb-goerli' },
+  { label: 'Arbitrum Sepolia', value: 'arb-sepolia' },
   { label: 'Localhost', value: 'localhost' },
   ]}
   >
@@ -106,6 +107,15 @@ If you're running into unexpected outputs or errors, the following checklist may
   may address your issue.
   </p>
   </TabItem>
+  <TabItem value="arb-sepolia">
+  <p>
+  The{' '}
+  <a href="/node-running/how-tos/running-a-full-node">
+  How to run a full node (Nitro)
+  </a>{' '}
+  may address your issue.
+  </p>
+  </TabItem>
   <TabItem value="localhost">
   <p>
   The <a href="/node-running/how-tos/local-dev-node">How to run a local dev node</a>{' '}

arbitrum-docs/partials/_multidimensional-content-controls-partial.md

@@ -28,6 +28,7 @@ import { MultiDimensionalContentWidget } from '@site/src/components/MultiDimensi
  { label: 'Arbitrum One (Classic)', value: 'arb-one-classic' },
  { label: 'Arbitrum Nova', value: 'arb-nova' },
  { label: 'Arbitrum Goerli', value: 'arb-goerli' },
+ { label: 'Arbitrum Sepolia', value: 'arb-sepolia' },
  { label: 'Localhost', value: 'localhost' },
  ]}
 >
@@ -36,6 +37,7 @@ import { MultiDimensionalContentWidget } from '@site/src/components/MultiDimensi
  <TabItem value="arb-one-classic"></TabItem>
  <TabItem value="arb-nova"></TabItem>
  <TabItem value="arb-goerli"></TabItem>
+ <TabItem value="arb-sepolia"></TabItem>
  <TabItem value="localhost"></TabItem>
 </Tabs>
 

arbitrum-docs/partials/_troubleshooting-building-partial.md

@@ -169,16 +169,16 @@ Once upon a time, Arbitrum developers were required to download supplemental pac
 ### What is a testnet or a devnet? {#what-is-a-testnet-or-a-devnet}
 <p>Testnets (or devnets) primarily serve developers who want to test out the applications they're building without having to use any real mainnet funds.</p>
 
-<p>Arbitrum Goerli testnet has the same full feature-set as the mainnet networks. It is also a "true" L2 that runs on top of the Goerli testnet (L1), using it for security and settlement.</p>
+<p>Arbitrum Goerli and Arbitrum Sepolia are both testnets that have the same full feature-set as the mainnet networks. They are also a "true" L2 that run on top of the Goerli testnet (L1) and the Sepolia testnet (L1) respectively, using them for security and settlement.</p>
 
-<p>Users can bridge any asset from the Goerli testnet (L1) into the Arbitrum Goerli testnet (and back!), using the official <a href="https://bridge.arbitrum.io/">bridge</a>.</p>
+<p>Users can bridge any asset from the Goerli testnet (L1) into the Arbitrum Goerli testnet, and from the Sepolia testnet (L1) into the Arbitrum Sepolia testnet (and back!), using the official <a href="https://bridge.arbitrum.io/">bridge</a>.</p>
 
 <p></p>
 
 
 
 ### Is there any testnet available on Arbitrum? {#is-there-any-testnet-available-on-arbitrum}
-<p>Yes, there's an Arbitrum Goerli testnet (421613) that uses the Nitro tech stack, running on top of Ethereum Goerli. You can find more information <a href="https://developer.arbitrum.io/public-chains">here</a>.</p>
+<p>Yes, there's an Arbitrum Goerli testnet (421613) that uses the Nitro tech stack, running on top of Ethereum Goerli, and an Arbitrum Sepolia testnet (421614) that also uses the Nitro tech stack and runs on top of Ethereum Sepolia. You can find more information <a href="https://developer.arbitrum.io/public-chains">here</a>.</p>
 
 <p></p>
 

arbitrum-docs/partials/_troubleshooting-nodes-partial.md

@@ -58,7 +58,7 @@
 ### **Is there any way to retrieve pre-Nitro archive data from a Nitro node?** {#is-there-any-way-to-retrieve-prenitro-archive-data-from-a-nitro-node}
 <p>The pre-nitro stack is also referred to as a "classic" stack. Full nitro nodes start with a database that contains the information from the "classic" era. However, it is not possible for a nitro node to query archive information contained in "classic" blocks right away. To do that, you need to also run a classic node (<a href="https://developer.arbitrum.io/node-running/how-tos/running-a-classic-node">instructions here</a>) and set the parameter <code>—node.rpc.classic-redirect=your-classic-node-RPC</code>.</p>
 
-<p>Keep in mind that this information only applies to Arbitrum One nodes. Arbitrum Nova and Arbitrum Goerli nodes started with a Nitro stack from the beginning, so they don't have "classic" data.</p>
+<p>Keep in mind that this information only applies to Arbitrum One nodes. Arbitrum Nova, Arbitrum Goerli and Arbitrum Sepolia nodes started with a Nitro stack from the beginning, so they don't have "classic" data.</p>
 
 <p></p>