Arbitrum nodes: an overview
This document is currently in public preview and may change significantly as feedback is captured from readers like you. Click the Request an update button at the top of this document or join the Arbitrum Discord to share your feedback.
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 to get RPC access to fully-managed nodes hosted by a third party provider.
When exposing API endpoints to the Internet or any untrusted/hostile network, the following risks may arise:
- Increased risk of crashes due to OOM: Exposing endpoints raises the risk of Out-of-Memory (OOM) crashes.
- Increased risk of not keeping up with chain progression: Resource starvation (IO or CPU) may occur, leading to an inability to keep up with chain progression.
We strongly advise against exposing API endpoints publicly. Users considering such exposure should exercise caution and implement the right measures to enhance resilience.
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:
When it comes to 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 quickstart, 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 type of node, users can make an informed decision based on their specific requirements and objectives.
Considerations for running an Arbitrum full node
- 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 full confidence in the authenticity and integrity of the transactions they interact with.
- Reduced trust requirements: By running a full node, users can interact with the Arbitrum network without relying on third-party services or infrastructure. This reduces the need to trust external entities and mitigates the risk of potential centralized failures or vulnerabilities.
- Lower resource requirements: Compared to archive nodes, full nodes generally require fewer resources such as storage and computational power. This makes them more accessible to users with limited hardware capabilities or those operating on resource-constrained environments.
For detailed instructions on how to run an Arbitrum full node, see here.
Considerations for running an Arbitrum archive node
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 extensive historical data access or advanced analytical purposes. However, it's important to note that archive nodes are more resource-intensive, requiring significant storage capacity and computational power.
For detailed instructions on how to run an Arbitrum archive node, see here.
Considerations for running an Arbitrum classic node
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. More details can be found here.
For detailed instructions on how to run an Arbitrum classic node, see here.
Considerations for running a feed relay
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 datacenter. This setup offers several advantages such as reducing ingress fees and enhancing stability within the network.
In the near future, 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 will ensure that you have access to an uncompressed feed by default, maintaining optimal performance and compatibility.
For detailed instructions on how to run a feed relay, see here.