diff --git a/docs/fundamentals/configuration.md b/docs/fundamentals/configuration.md
index dfd39bd0e4..94414ae25a 100644
--- a/docs/fundamentals/configuration.md
+++ b/docs/fundamentals/configuration.md
@@ -258,6 +258,171 @@ The configuration options are case-sensitive and can be defined only once unless
The address of the transaction priority contract to use when selecting transactions from the transaction pool. Defaults to `null`.
+### Arbitrum
+
+- #### `Arbitrum.SafeBlockWaitForValidator` \{#arbitrum-safeblockwaitforvalidator\}
+
+
+
+ ```
+ --arbitrum-safeblockwaitforvalidator [true|false]
+ --Arbitrum.SafeBlockWaitForValidator [true|false]
+ ```
+
+
+ ```
+ NETHERMIND_ARBITRUMCONFIG_SAFEBLOCKWAITFORVALIDATOR=true|false
+ ```
+
+
+ ```json
+ {
+ "Arbitrum": {
+ "SafeBlockWaitForValidator": true|false
+ }
+ }
+ ```
+
+
+
+ Whether safe blocks should wait for validator. Defaults to `false`.
+
+- #### `Arbitrum.FinalizedBlockWaitForValidator` \{#arbitrum-finalizedblockwaitforvalidator\}
+
+
+
+ ```
+ --arbitrum-finalizedblockwaitforvalidator [true|false]
+ --Arbitrum.FinalizedBlockWaitForValidator [true|false]
+ ```
+
+
+ ```
+ NETHERMIND_ARBITRUMCONFIG_FINALIZEDBLOCKWAITFORVALIDATOR=true|false
+ ```
+
+
+ ```json
+ {
+ "Arbitrum": {
+ "FinalizedBlockWaitForValidator": true|false
+ }
+ }
+ ```
+
+
+
+ Whether finalized blocks should wait for validator. Defaults to `false`.
+
+- #### `Arbitrum.BlockProcessingTimeout` \{#arbitrum-blockprocessingtimeout\}
+
+
+
+ ```
+ --arbitrum-blockprocessingtimeout
+ --Arbitrum.BlockProcessingTimeout
+ ```
+
+
+ ```
+ NETHERMIND_ARBITRUMCONFIG_BLOCKPROCESSINGTIMEOUT=
+ ```
+
+
+ ```json
+ {
+ "Arbitrum": {
+ "BlockProcessingTimeout":
+ }
+ }
+ ```
+
+
+
+ Timeout in seconds for block processing operations. Defaults to `1`.
+
+- #### `Arbitrum.RebuildLocalWasm` \{#arbitrum-rebuildlocalwasm\}
+
+
+
+ ```
+ --arbitrum-rebuildlocalwasm
+ --Arbitrum.RebuildLocalWasm
+ ```
+
+
+ ```
+ NETHERMIND_ARBITRUMCONFIG_REBUILDLOCALWASM=
+ ```
+
+
+ ```json
+ {
+ "Arbitrum": {
+ "RebuildLocalWasm":
+ }
+ }
+ ```
+
+
+
+ Rebuild local WASM store mode: `false` to disable, `force` to force rebuild, or `auto` to continue from last position. Defaults to `auto`.
+
+- #### `Arbitrum.MessageLagMs` \{#arbitrum-messagelagms\}
+
+
+
+ ```
+ --arbitrum-messagelagms
+ --Arbitrum.MessageLagMs
+ ```
+
+
+ ```
+ NETHERMIND_ARBITRUMCONFIG_MESSAGELAGMS=
+ ```
+
+
+ ```json
+ {
+ "Arbitrum": {
+ "MessageLagMs":
+ }
+ }
+ ```
+
+
+
+ Allowed message lag in milliseconds while still considered in sync. Defaults to `1000`.
+
+- #### `Arbitrum.ExposeMultiGas` \{#arbitrum-exposemultigas\}
+
+
+
+ ```
+ --arbitrum-exposemultigas [true|false]
+ --Arbitrum.ExposeMultiGas [true|false]
+ ```
+
+
+ ```
+ NETHERMIND_ARBITRUMCONFIG_EXPOSEMULTIGAS=true|false
+ ```
+
+
+ ```json
+ {
+ "Arbitrum": {
+ "ExposeMultiGas": true|false
+ }
+ }
+ ```
+
+
+
+ Experimental: Expose multi-dimensional gas in transaction receipts. Defaults to `false`.
+
+
### Blocks
- #### `Blocks.BlockProductionBlobLimit` \{#blocks-blockproductionbloblimit\}
diff --git a/docs/get-started/running-node/l2-networks.md b/docs/get-started/running-node/l2-networks.md
index 9ae8b4aca8..007bdee33c 100644
--- a/docs/get-started/running-node/l2-networks.md
+++ b/docs/get-started/running-node/l2-networks.md
@@ -232,3 +232,75 @@ For more information, see [Run a node for Taiko Hoodi](https://docs.taiko.xyz/gu
**See also**
- [Enable a prover](https://docs.taiko.xyz/guides/node-operators/enable-a-prover/)
+
+## Arbitrum
+
+An [Arbitrum node](https://docs.arbitrum.io/run-arbitrum-node/overview) consists of two parts: [Nitro](https://github.com/OffchainLabs/nitro), the rollup node developed by Offchain Labs, paired with an L2 execution client.
+
+
+
+
+:::info Note
+For Arbitrum One, the L1 node must be running on Ethereum Mainnet.
+:::
+
+To run Nethermind on Arbitrum One, use the following command:
+
+```bash
+nethermind \
+ -c arbitrum-mainnet \
+ --data-dir path/to/data/dir
+```
+
+Below is a sample command to run Nitro paired with Nethermind, assuming they both are running on the same machine:
+
+```bash
+export L1_RPC_URL=... # The URL of the L1 node RPC interface
+export L1_BEACON_URL=... # The URL of the L1 node Beacon interface
+
+nitro \
+ --parent-chain.connection.url=$L1_RPC_URL \
+ --parent-chain.blob-client.beacon-url=$L1_BEACON_URL \
+ --chain.id=42161 \
+ --execution.forwarding-target="" \
+ --node.feed.input.url=wss://arb1.arbitrum.io/feed
+```
+
+
+
+
+:::info Note
+For Arbitrum Sepolia, the L1 node must be running on Sepolia.
+:::
+
+To run Nethermind on Arbitrum Sepolia, use the following command:
+
+```bash
+nethermind \
+ -c arbitrum-sepolia \
+ --data-dir path/to/data/dir
+```
+
+Below is a sample command to run Nitro paired with Nethermind, assuming they both are running on the same machine:
+
+```bash
+export L1_RPC_URL=... # The URL of the L1 Sepolia node RPC interface
+export L1_BEACON_URL=... # The URL of the L1 Sepolia node Beacon interface
+
+nitro \
+ --parent-chain.connection.url=$L1_RPC_URL \
+ --parent-chain.blob-client.beacon-url=$L1_BEACON_URL \
+ --chain.id=421614 \
+ --execution.forwarding-target="" \
+ --node.feed.input.url=wss://sepolia-rollup.arbitrum.io/feed
+```
+
+
+
+
+For available Nitro settings, see [Nitro configuration options](https://docs.arbitrum.io/run-arbitrum-node/nitro/reference/configuration).
+
+**See also**
+
+- [Arbitrum configuration](../../fundamentals/configuration.md#arbitrum)
+- [Run an Arbitrum node](https://docs.arbitrum.io/run-arbitrum-node/overview)