You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: arbitrum-docs/run-arbitrum-node/01-overview.mdx
+15-22Lines changed: 15 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,54 +12,47 @@ import { VanillaAdmonition } from '@site/src/components/VanillaAdmonition/';
12
12
13
13
<VanillaAdmonitiontype="note">
14
14
15
-
There is no protocollevel 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 thirdparty provider.
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 fullymanaged nodes hosted by a third-party provider.
16
16
17
17
</VanillaAdmonition>
18
18
19
19
:::caution API security disclaimer
20
20
21
21
When exposing API endpoints to the Internet or any untrusted/hostile network, the following risks may arise:
22
22
23
-
- Increased risk of crashes due to OOM:
24
-
Exposing endpoints raises the risk of Out-of-Memory (OOM) crashes.
25
-
- Increased risk of not keeping up with chain progression:
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
26
Resource starvation (IO or CPU) may occur, leading to an inability to keep up with chain progression.
27
27
28
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
+
29
30
:::
30
31
31
-
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:
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:
32
33
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
34
-
- You can run your own Arbitrum node, especially if you want to always know the state of the Arbitrum chain
35
+
- You can run your own Arbitrum node, especially if you want always to know the state of the Arbitrum chain
35
36
36
37
The rest of this series focuses on the second approach: running your own Arbitrum node.
37
38
38
-
When exposing API endpoints to the Internet or any untrusted/hostile network, the following risks may arise:
39
-
40
-
- Increased risk of crashes due to OOM:
41
-
Exposing endpoints raises the risk of Out-of-Memory (OOM) crashes.
42
-
- Increased risk of not keeping up with chain progression:
43
-
Resource starvation (IO or CPU) may occur, leading to an inability to keep up with chain progression.
44
-
45
-
We strongly advise against exposing API endpoints publicly. Users considering such exposure should exercise caution and implement the right measures to enhance resilience.
46
39
:::
47
40
48
-
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:
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:
49
42
50
-
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.
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.
51
44
52
45
### Considerations for running an Arbitrum full node
53
46
54
-
- 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.
55
-
- 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.
56
-
- 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.
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.
57
50
58
51
For detailed instructions, read [how to run an Arbitrum full node](/run-arbitrum-node/02-run-full-node.mdx).
59
52
60
53
### Considerations for running an Arbitrum archive node
61
54
62
-
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.
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.
63
56
64
57
For detailed instructions, read [how to run an Arbitrum archive node](/run-arbitrum-node/more-types/01-run-archive-node.mdx).
65
58
@@ -71,8 +64,8 @@ For detailed instructions, read [how to run an Arbitrum classic node](/run-arbit
71
64
72
65
### Considerations for running a feed relay
73
66
74
-
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.
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.
75
68
76
-
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.
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.
77
70
78
71
For detailed instructions, read [how to run an Arbitrum feed relay](/run-arbitrum-node/sequencer/01-run-feed-relay.mdx).
|[Arbitrum Rollup](/how-arbitrum-works/05-validation-and-proving/02-rollup-protocol.mdx)| A **protocol** for scaling Ethereum smart contracts. |
20
-
|[Arbitrum AnyTrust](/how-arbitrum-works/08-anytrust-protocol.mdx)| A **protocol** for scaling Ethereum smart contracts even further, with a mild trust assumption. |
21
-
|[Arbitrum Nitro](/how-arbitrum-works/01-a-gentle-introduction.mdx)| The node **software** that codifies the Rollup and AnyTrust protocols. |
22
-
|[Arbitrum nodes](/run-arbitrum-node/02-run-full-node.mdx)|**Machines** that run Nitro in order to service and/or interact with an Arbitrum chain. |
23
-
|[Arbitrum One](https://portal.arbitrum.io/?chains=arbitrum-one)| A public Rollup **chain**. |
24
-
|[Arbitrum Nova](https://portal.arbitrum.io/?chains=arbitrum-nova)| A public AnyTrust **chain**. |
25
-
|[Arbitrum bridge](https://bridge.arbitrum.io/)| Lets you move ETH and ERC-20 tokens between Ethereum, Arbitrum, and select Arbitrum (Orbit) chains. |
26
-
|[Arbitrum (Orbit) chains](https://orbit.arbitrum.io/)| Lets you run your own Rollup and AnyTrust chains. |
27
-
|[Arbitrum Stylus](/stylus/gentle-introduction.mdx)| Lets you write EVM-compatible smart contracts in Rust and any other language that compiles to Wasm. |
|[Arbitrum Rollup](/how-arbitrum-works/05-validation-and-proving/02-rollup-protocol.mdx)| A **protocol** for scaling Ethereum smart contracts. |
20
+
|[Arbitrum AnyTrust](/how-arbitrum-works/08-anytrust-protocol.mdx)| A **protocol** for scaling Ethereum smart contracts even further, with a mild trust assumption. |
21
+
|[Arbitrum Nitro](/how-arbitrum-works/01-a-gentle-introduction.mdx)| The node **software** that codifies the Rollup and AnyTrust protocols. |
22
+
|[Arbitrum nodes](/run-arbitrum-node/02-run-full-node.mdx)|**Machines** that run Nitro in order to service and/or interact with an Arbitrum chain. |
23
+
|[Arbitrum One](https://portal.arbitrum.io/?chains=arbitrum-one)| A public Rollup **chain**. |
24
+
|[Arbitrum Nova](https://portal.arbitrum.io/?chains=arbitrum-nova)| A public AnyTrust **chain**. |
25
+
|[Arbitrum bridge](https://bridge.arbitrum.io/)| Lets you move `ETH` and `ERC-20` tokens between Ethereum, Arbitrum, and select Arbitrum (Orbit) chains. |
26
+
|[Arbitrum (Orbit) chains](https://orbit.arbitrum.io/)| Lets you run your own Rollup and AnyTrust chains. |
27
+
|[Arbitrum Stylus](/stylus/gentle-introduction.mdx)| Lets you write EVM-compatible smart contracts in Rust and any other language that compiles to Wasm. |
0 commit comments