Merge branch 'master' into update-dac-documentation

0xflair · Jan 19, 2024 · 16df3f0 · 16df3f0
2 parents 363beca + 64b868f
commit 16df3f0
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 0 deletions.
diff --git a/arbitrum-docs/node-running/node-providers.mdx b/arbitrum-docs/node-running/node-providers.mdx
@@ -62,6 +62,7 @@ Alternatively, to interact with public Arbitrum chains, you can rely on many of
 | [Infura](https://docs.infura.io/infura/networks/arbitrum)                            | ✅       |           | ✅           |            |
 | [Lava](https://docs.lavanet.xyz/gateway-access)                                      | ✅       | ✅        |              |            |
 | [Moralis](https://docs.moralis.io/reference/introduction)                            | ✅       |           |              |            |
+| [Nirvana Labs](https://nirvanalabs.io)                                               | ✅       |           |              | ✅         |
 | [NodeReal](https://nodereal.io/meganode/api-marketplace/arbitrum-nitro-rpc)          | ✅       | ✅        |              |            |
 | [NOWNodes](https://nownodes.io/nodes/arbitrum-arb)                                   | ✅       |           |              |            |
 | [Pocket Network](https://docs.pokt.network/welcome-to-pokt-network/supported-chains) | ✅       |           |              |            |

diff --git a/arbitrum-docs/node-running/quickstart-running-a-node.md b/arbitrum-docs/node-running/quickstart-running-a-node.md
@@ -17,6 +17,18 @@ There is no protocol level incentive to run an Arbitum full node. If you’re in
 
 :::
 
+:::caution API security disclaimer
+
+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.
+:::
+
 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