docs: build-dapps-reference-md-to-mdx

.gitignore

@@ -1,3 +1,4 @@
 .vscode
 arbitrum-docs/sdk
 arbitrum-docs/stylus-by-example
+.vercel

arbitrum-docs/arbitrum-bridge/01-quickstart.mdx

@@ -30,7 +30,7 @@ You'll also need to add the desired chain's RPC endpoint to your wallet. Here we
 
 ![Add the desired destination network to your MetaMask wallet](images/getting_started_users_1.png)
 
-Here we display the information of the most common Arbitrum chains, but you can find a more exhaustive list in our [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.md) page.
+Here we display the information of the most common Arbitrum chains, but you can find a more exhaustive list in our [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.mdx) page.
 
 | Parameter          | Arbitrum One                 | Arbitrum Nova                | Arbitrum Sepolia (testnet)             |
 | ------------------ | ---------------------------- | ---------------------------- | -------------------------------------- |

arbitrum-docs/build-decentralized-apps/01-quickstart-solidity-hardhat.mdx

@@ -513,7 +513,7 @@ If you have any questions or feedback, reach out to us on [Discord](https://disc
 <!--todo: figure out what next steps they're actually looking for by performing content tests -->
 
 - Visit [How to estimate gas](/build-decentralized-apps/02-how-to-estimate-gas.mdx) to learn how to estimate the gas cost of your smart contract transactions.
-- Visit [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.md#rpc-endpoints) for a list of public chains that you can deploy your smart contracts to.
+- Visit [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.mdx#rpc-endpoints) for a list of public chains that you can deploy your smart contracts to.
 
 [^1]: The vending machine example was inspired by [Ethereum.org's "Introduction to Smart Contracts"](https://ethereum.org/en/developers/docs/smart-contracts/), which was inspired by [Nick Szabo's "From vending machines to smart contracts"](http://unenumerated.blogspot.com/2006/12/from-vending-machines-to-smart.html).
 [^2]: Although application front-ends are usually hosted by centralized services, smart contracts allow the underlying logic and data to be partially or fully decentralized. These smart contracts are hosted and executed by Ethereum's public, decentralized network of nodes. Arbitrum has its own network of nodes that use advanced cryptography techniques to "batch process" Ethereum transactions and then submit them to Ethereum L1, which significantly reduces the cost of using Ethereum. All without requiring developers to compromise on security or decentralization.

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

@@ -30,7 +30,7 @@ The `parent-chain` argument needs to provide a standard RPC endpoint for an EVM
 
 :::note
 
-[Public Arbitrum RPC endpoints](/build-decentralized-apps/reference/01-node-providers.md#arbitrum-public-rpc-endpoints) rate-limit connections. To avoid hitting a bottleneck, you can run a local node for the parent chain or rely on third-party RPC providers.
+[Public Arbitrum RPC endpoints](/build-decentralized-apps/reference/01-node-providers.mdx#arbitrum-public-rpc-endpoints) rate-limit connections. To avoid hitting a bottleneck, you can run a local node for the parent chain or rely on third-party RPC providers.
 
 :::
 

arbitrum-docs/partials/_contribute-docs-partial.mdx

@@ -114,7 +114,7 @@ Every document should be a specific _type_ of document. Each type of document ha
 | Concept             | Explain what things are and how they work                                          | [Token bridging](/build-decentralized-apps/token-bridging/03-token-bridge-erc20.md) <br/>[Nodes and networks](https://docs.prylabs.network/docs/concepts/nodes-networks) |
 | FAQ                 | Address frequently asked questions                                                 | [FAQ: Run a node](../node-running/faq.md)                                                                                                                                |
 | Troubleshooting     | List common troubleshooting scenarios and solutions                                | [Troubleshooting: Run a node](/run-arbitrum-node/06-troubleshooting.md)                                                                                                  |
-| Reference           | Lists and tables of things, such as API endpoints and developer resources          | [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.md)                                                                                  |
+| Reference           | Lists and tables of things, such as API endpoints and developer resources          | [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.mdx)                                                                                 |
 
 This isn't an exhaustive list, but it includes most of the document types that we use.
 
@@ -205,7 +205,7 @@ The following document was contributed by @todo-twitter-handle. Give them a shou
 
 ### Frequently asked questions
 
-#### Can I point to my product from core docs? For example - if my product hosts a public RPC endpoint, can I add it to your [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.md) page?
+#### Can I point to my product from core docs? For example - if my product hosts a public RPC endpoint, can I add it to your [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.mdx) page?
 
 These types of contributions are generally **not merged** unless they're submitted by employees of Offchain Labs.
 

arbitrum-docs/run-arbitrum-node/01-overview.md

@@ -6,7 +6,7 @@ author: mahsamoosavi
 
 In order to be able to _interact with_ or _build applications on_ any of the Arbitrum chains, you need access to the corresponding Arbitrum node. Options are:
 
-- You can use third party node providers (see the list [here](/build-decentralized-apps/reference/01-node-providers.md)) to get RPC access to fully-managed nodes
+- You can use third party node providers (see the list [here](/build-decentralized-apps/reference/01-node-providers.mdx)) to get RPC access to fully-managed nodes
 - You can run your own Arbitrum node, especially if you want to always know the state of the Arbitrum chain
 
 Here, you can find resources that help you run different types of Arbitrum nodes:

arbitrum-docs/run-arbitrum-node/02-quickstart.md

@@ -9,7 +9,7 @@ content_type: quickstart
 
 :::info
 
-There is no protocol level incentive to run an Arbitum full node. If you’re interested in accessing an Arbitrum chain, but you don’t want to set up your own node, see our [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.md) to get RPC access to fully-managed nodes hosted by a third party provider.
+There is no protocol level incentive to run an Arbitum full node. If you’re interested in accessing an Arbitrum chain, but you don’t want to set up your own node, see our [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.mdx) to get RPC access to fully-managed nodes hosted by a third party provider.
 
 :::
 

arbitrum-docs/run-arbitrum-node/03-run-full-node.md

@@ -7,7 +7,7 @@ content_type: how-to
 
 :::info
 
-There is no protocol-level incentive to run an Arbitum full node. If you’re interested in accessing an Arbitrum chain but don’t want to set up your own node, see our [Node Providers](/build-decentralized-apps/reference/01-node-providers.md) to get RPC access to fully managed nodes hosted by a third-party provider.
+There is no protocol-level incentive to run an Arbitum full node. If you’re interested in accessing an Arbitrum chain but don’t want to set up your own node, see our [Node Providers](/build-decentralized-apps/reference/01-node-providers.mdx) to get RPC access to fully managed nodes hosted by a third-party provider.
 
 :::
 
@@ -61,7 +61,7 @@ Even though there are alpha and beta versions of the <a data-quicklook-from='arb
   - Note: this parameter was called `--l1.url` in versions prior to `v2.1.0`
   - Note: 8545 is usually the default port for the execution layer. For the Beacon endpoint port, you should connect to the correct port set on your parent chain's consensus client.
 - 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](/build-decentralized-apps/reference/01-node-providers.md#rpc-endpoints) for a list of Arbitrum chains and their respective L2 chain IDs.
+  - Use the parameter `--chain.id=<L2 chain ID>` to set the L2 chain from its chain id. See [RPC endpoints and providers](/build-decentralized-apps/reference/01-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 `sepolia-rollup`)
   - Note: this parameter was called --l2.chain-id and only accepted chain IDs in versions before `v2.1.0`
 

arbitrum-docs/run-arbitrum-node/data-availability-committees/02-deploy-das.md

@@ -81,7 +81,7 @@ DA servers also have an optional REST aggregator which, when a data batch is not
 Gather the following information:
 
 - The latest Nitro docker image: `@latestNitroNodeImage@`
-- An RPC endpoint for the <a data-quicklook-from="parent-chain">parent chain</a>. It is recommended to use a [third-party provider RPC](/build-decentralized-apps/reference/01-node-providers.md#third-party-rpc-providers) or [run your own node](/node-running/how-tos/running-an-orbit-node.mdx) to prevent being rate limited.
+- An RPC endpoint for the <a data-quicklook-from="parent-chain">parent chain</a>. It is recommended to use a [third-party provider RPC](/build-decentralized-apps/reference/01-node-providers.mdx#third-party-rpc-providers) or [run your own node](/node-running/how-tos/running-an-orbit-node.mdx) to prevent being rate limited.
 - The SequencerInbox contract address in the parent chain.
 - If you wish to configure a [REST aggregator for your DAS](#state-synchronization), you'll need the URL where the list of REST endpoints is kept.
 

arbitrum-docs/run-arbitrum-node/data-availability-committees/03-deploy-mirror-das.md

@@ -46,7 +46,7 @@ A mirror DAS will use the same tool and, thus, the same configuration options as
 Gather the following information:
 
 - The latest Nitro docker image: `@latestNitroNodeImage@`
-- An RPC endpoint for the <a data-quicklook-from="parent-chain">parent chain</a>. It is recommended to use a [third-party provider RPC](/build-decentralized-apps/reference/01-node-providers.md#third-party-rpc-providers) or [run your own node](/node-running/how-tos/running-an-orbit-node.mdx) to prevent being rate limited.
+- An RPC endpoint for the <a data-quicklook-from="parent-chain">parent chain</a>. It is recommended to use a [third-party provider RPC](/build-decentralized-apps/reference/01-node-providers.mdx#third-party-rpc-providers) or [run your own node](/node-running/how-tos/running-an-orbit-node.mdx) to prevent being rate limited.
 - The SequencerInbox contract address in the parent chain.
 - URL of the list of REST endpoints of other DA servers to configure the REST aggregator.
 

arbitrum-docs/run-arbitrum-node/more-types/01-run-archive-node.md

@@ -22,7 +22,7 @@ Running an Arbitrum One **full node** in **archive mode** lets you access both p
 
 | 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](/build-decentralized-apps/reference/01-node-providers.md)             |
+| Access the **Arbitrum network** without running your own node                   | Fully managed by third-parties, exposed via RPC endpoints | [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.mdx)            |
 | Run an **archive node** for **Arbitrum Sepolia (testnet)** or **Arbitrum Nova** | Full node (Nitro)                                         | [How to run a full node (Nitro)](/run-arbitrum-node/03-run-full-node.md)                            |
 | Send **post-Nitro** archive requests                                            | Full node (Nitro)                                         | [How to run a full node (Nitro)](/run-arbitrum-node/03-run-full-node.md)                            |
 | Send **pre-Nitro** archive requests                                             | Full node (Classic)                                       | [How to run a full node (Classic, pre-Nitro)](/run-arbitrum-node/more-types/03-run-classic-node.md) |
@@ -70,13 +70,13 @@ The minimum storage requirements will change as the Nitro chains grow (growing r
 
 ### Review and configure parameters
 
-| Arbitrum Nitro                                             | Arbitrum Classic                            | Description                                                                                                                                                                                      |
-| ---------------------------------------------------------- | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `--parent-chain.connection.url=<Layer 1 Ethereum RPC URL>` | `--l1.url=<Layer 1 Ethereum RPC URL>`       | Provide an standard L1 node RPC endpoint that you run yourself or from a third-party node provider (see [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.md)) |
-| `--chain.id=<L2 chain ID>`                                 | `--l2.chain-id=<L2 Chain ID>`               | See [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.md) for a list of Arbitrum chains and the respective L2 chain IDs                                        |
-| `--execution.caching.archive`                              | `--node.caching.archive`                    | Required for running an **Arbitrum One Nitro** archival node and retains past block state                                                                                                        |
-| -                                                          | `--node.cache.allow-slow-lookup`            | Required for running an **Arbitrum One Classic** archival node. When this option is present, it will load old blocks from disk if not in memory cache.                                           |
-| -                                                          | `--core.checkpoint-gas-frequency=156250000` | Required for running an **Arbitrum One Classic** archival node.                                                                                                                                  |
+| Arbitrum Nitro                                             | Arbitrum Classic                            | Description                                                                                                                                                                                       |
+| ---------------------------------------------------------- | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--parent-chain.connection.url=<Layer 1 Ethereum RPC URL>` | `--l1.url=<Layer 1 Ethereum RPC URL>`       | Provide an standard L1 node RPC endpoint that you run yourself or from a third-party node provider (see [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.mdx)) |
+| `--chain.id=<L2 chain ID>`                                 | `--l2.chain-id=<L2 Chain ID>`               | See [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.mdx) for a list of Arbitrum chains and the respective L2 chain IDs                                        |
+| `--execution.caching.archive`                              | `--node.caching.archive`                    | Required for running an **Arbitrum One Nitro** archival node and retains past block state                                                                                                         |
+| -                                                          | `--node.cache.allow-slow-lookup`            | Required for running an **Arbitrum One Classic** archival node. When this option is present, it will load old blocks from disk if not in memory cache.                                            |
+| -                                                          | `--core.checkpoint-gas-frequency=156250000` | Required for running an **Arbitrum One Classic** archival node.                                                                                                                                   |
 
 ### Run the Docker image(s)