|
1 | 1 | --- |
2 | | -title: 'Arbitrum nodes overview' |
3 | | -description: "Arbitrum is a suite of Ethereum L2 scaling solutions supported by a decentralized network of nodes. This guide introduces you to Arbitrum's node types and how they work together to scale Ethereum." |
4 | | -author: mahsamoosavi |
| 2 | +title: 'Arbitrum nodes: an overview' |
| 3 | +description: Learn more about what type of ARb node one needs to run. |
| 4 | +author-objective: Build a quickstart that helps readers understand why they might want to run a specific type of an Arbitrum node. |
| 5 | +reader-audience: Moderately-technical readers who are familiar with command lines, but not Ethereum / Arbitrum infrastructure |
| 6 | +reader-task: Learn about the different types of Arbitrum nodes and understand the benefits and trade-offs of each type. |
| 7 | +content_type: overview |
5 | 8 | --- |
6 | 9 |
|
7 | | -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: |
| 10 | +import PublicPreviewBannerPartial from '../partials/_public-preview-banner-partial.mdx'; |
| 11 | +import { VanillaAdmonition } from '@site/src/components/VanillaAdmonition/'; |
8 | 12 |
|
9 | | -- 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 |
10 | | -- You can run your own Arbitrum node, especially if you want to always know the state of the Arbitrum chain |
| 13 | +<VanillaAdmonition type="note"> |
11 | 14 |
|
12 | | -Here, you can find resources that help you run different types of Arbitrum nodes: |
| 15 | +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 a node locally, 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. |
13 | 16 |
|
14 | | -- Step-by-step instructions for running different Arbitrum nodes, including [full Nitro node](/run-arbitrum-node/03-run-full-node.mdx), [full Classic node](/run-arbitrum-node/more-types/03-run-classic-node.mdx), [local full chain simulation](/run-arbitrum-node/04-run-local-full-chain-simulation.mdx), [Nitro dev node](/run-arbitrum-node/run-nitro-dev-node.mdx), [feed relay](/run-arbitrum-node/sequencer/01-run-feed-relay.mdx), and [validator](/run-arbitrum-node/more-types/02-run-validator-node.mdx) |
15 | | -- Step-by-step instructions for how to [read the sequencer feed](/run-arbitrum-node/sequencer/02-read-sequencer-feed.mdx), [build the Nitro locally](/run-arbitrum-node/nitro/01-build-nitro-locally.mdx) and [run the sequencer coordinator manager UI tool](/run-arbitrum-node/sequencer/03-run-sequencer-coordination-manager.mdx) |
16 | | -- Step-by-step instructions for [how to configure a Data Availability Committee](/run-arbitrum-node/data-availability-committees/01-get-started.mdx) |
17 | | -- [Troubleshooting page](/run-arbitrum-node/06-troubleshooting.mdx) |
18 | | -- [Frequently asked questions](/node-running/faq.mdx) |
| 17 | +</VanillaAdmonition> |
| 18 | + |
| 19 | +:::caution API security disclaimer |
| 20 | + |
| 21 | +When exposing API endpoints to the Internet or any untrusted/hostile network, the following risks may arise: |
| 22 | + |
| 23 | +- **Increased risk of crashes due to Out-of-Memory (OOM)**: |
| 24 | + Exposing endpoints increases the risk of OOM crashes. |
| 25 | +- **Increased risk of not keeping up with chain progression**: |
| 26 | + Resource starvation (IO or CPU) may occur, leading to an inability to keep up with chain progression. |
| 27 | + |
| 28 | +We strongly advise against exposing API endpoints publicly. Users considering such exposure should exercise caution and implement the right measures to enhance resilience. |
| 29 | + |
| 30 | +::: |
| 31 | + |
| 32 | +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: |
| 33 | + |
| 34 | +- You can use [ third party node providers ](/build-decentralized-apps/reference/01-node-providers.mdx) to get RPC access to fully-managed nodes |
| 35 | +- You can run your own Arbitrum node, especially if you want always to know the state of the Arbitrum chain |
| 36 | + |
| 37 | +The rest of this series focuses on the second approach: running your own Arbitrum node. |
| 38 | + |
| 39 | +::: |
| 40 | + |
| 41 | +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: |
| 42 | + |
| 43 | +When interacting with the Arbitrum network, users have the option to run either a full node or an archive node. There are distinct advantages to running an Arbitrum full node. In this quick start, we will explore the reasons why a user may prefer to run a full node instead of an archive node. By understanding the benefits and trade-offs of each node type, users can make an informed decision based on their specific requirements and objectives. |
| 44 | + |
| 45 | +### Considerations for running an Arbitrum full node |
| 46 | + |
| 47 | +- **Transaction validation and security**: Running a full node allows users to independently validate transactions and verify the state of the Arbitrum blockchain. Users can have complete confidence in the authenticity and integrity of the transactions they interact with. |
| 48 | +- **Reduced trust requirements**: By running a full node, users can interact with the Arbitrum network without relying on third-party services or infrastructure. This independence reduces the need to trust external entities and mitigates the risk of potential centralized failures or vulnerabilities. |
| 49 | +- **Lower resource requirements**: Compared to archive nodes, full nodes generally require fewer resources such as storage and computational power. These requirements make it more accessible to users with limited hardware capabilities or those operating in resource-constrained environments. |
| 50 | + |
| 51 | +For detailed instructions, read [how to run an Arbitrum full node](/run-arbitrum-node/02-run-full-node.mdx). |
| 52 | + |
| 53 | +### Considerations for running an Arbitrum archive node |
| 54 | + |
| 55 | +While full nodes offer numerous advantages, there are situations where running an archive node may be more appropriate. Archive nodes store the complete history of the Arbitrum network, making them suitable for users who require access to extensive historical data or advanced analytical purposes. However, it's important to note that archive nodes are more resource-intensive, requiring significant storage capacity and computational power. |
| 56 | + |
| 57 | +For detailed instructions, read [how to run an Arbitrum archive node](/run-arbitrum-node/more-types/01-run-archive-node.mdx). |
| 58 | + |
| 59 | +### Considerations for running an Arbitrum classic node |
| 60 | + |
| 61 | +The significance of running an Arbitrum classic node is mainly applicable to individuals with specific needs for an archive node and access to classic-related commands. |
| 62 | + |
| 63 | +For detailed instructions, read [how to run an Arbitrum classic node](/run-arbitrum-node/more-types/03-run-classic-node.mdx). |
| 64 | + |
| 65 | +### Considerations for running a feed relay |
| 66 | + |
| 67 | +If you are running a single node, there is no requirement to set up a feed relay. However, if you have multiple nodes, it is highly recommended to have a single feed relay per data center. This setup offers several advantages, including reducing ingress fees and enhancing network stability. |
| 68 | + |
| 69 | +Soon, feed endpoints will mandate compression using a custom dictionary. Therefore, if you plan to connect to a feed using anything other than a standard node, it is strongly advised to run a local feed relay. This local feed relay will ensure that you have access to an uncompressed feed by default, maintaining optimal performance and compatibility. |
| 70 | + |
| 71 | +For detailed instructions, read [how to run an Arbitrum feed relay](/run-arbitrum-node/sequencer/01-run-feed-relay.mdx). |
0 commit comments