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
{{ message }}
This repository was archived by the owner on Dec 22, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: src/getting-started/hw-requirements.md
+50-14Lines changed: 50 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,27 +8,63 @@ Additionally, SSDs may experience performance degradation when nearing full capa
8
8
9
9
See here how you can [optimize storage](/basic/optimizing-storage.md).
10
10
11
-
## RAID Configuration
12
11
13
-
When using multiple disks, consider implementing a **RAID 0** configuration to maximize performance and utilize space efficiently. RAID ZFS is not recommended.
12
+
Here is the outline of the hardware requirements for running Erigon on the following networks:
14
13
15
-
## Disk size
14
+
- Ethereum Mainnet
15
+
- Polygon (formerly Matic)
16
+
- Gnosis (formerly xDai)
16
17
17
-
Please refer to [disk space required](/basic/disk-space.md) for details. To ensure smooth operation, it is recommended to maintain at least 25% of free disk space. For more detailed guidance on optimizing storage, refer to disk space required.
18
+
Hardware requirements vary depending on whether you're running a Minimal, Full, or Archive node.
18
19
19
-
## CPU Requirements
20
+
General recommendations for all node types include:
20
21
21
-
***Architecture**: 64-bit architecture.
22
-
***Number of core and threads**: While a powerful CPU can be beneficial, it's not essential for running Erigon. A moderate number of cores and threads should be sufficient. However, we recommend at least 4 cores, or 8 cores for high performance.
22
+
-**Disk Type:** Use high-end NVMe SSDs. RAID or ZFS setups may improve performance for archive nodes.
23
+
-**RAM:** Adequate memory reduces bottlenecks during sync and improves performance under load.
24
+
-**CPU:** 4–8 cores recommended for Full nodes; 8–16 cores for Archive.
25
+
-**Linux**: kernel version > v4
26
+
- When using multiple disks, consider implementing a **RAID 0** configuration to maximize performance and utilize space efficiently. RAID ZFS is not recommended.
23
27
24
-
## RAM Requirements
25
-
26
-
***Minimum**: 64GB
27
28
28
-
## Kernel Requirements
29
+
## Minimal Node Requirements
29
30
30
-
***Linux**: kernel version > v4
31
+
Minimal nodes are suitable for light operation with pruned state and minimal historical data retention. (`--prune.mode=minimal`)
31
32
32
-
## Bandwith
33
+
| Network | Disk Size (Required) | Disk Size (Recommended) | RAM (Required) | RAM (Recommended) |
A stable and reliable internet connection is crucial for running a node, especially if you're running a validator node, as downtime can lead to missed rewards or penalties. We recommend a minimum inbound and outbound bandwidth of 20 Mbps, with a stable connection and low latency. For optimal performance, it's best to use an ISP with an uncapped data allowance.
39
+
40
+
## Full Node Requirements
41
+
42
+
Full nodes maintain full state with standard pruning and all recent data. (`--prune.mode=full`)
43
+
44
+
| Network | Disk Size (Required) | Disk Size (Recommended) | RAM (Required) | RAM (Recommended) |
Archive nodes retain **all** historical state and require significantly more disk space. These are typically used for block explorers or deep analytical queries. (`--prune.mode=archive`)
54
+
55
+
| Network | Disk Size (Required) | Disk Size (Recommended) | RAM (Required) | RAM (Recommended) |
*How to build Erigon in Linux and MacOS from source*
3
+
4
+
The basic Erigon configuration is suitable for most users just wanting to run a node. For building the latest stable release use the following command:
*How to install and run Erigon 3 on Linux or Mac OS*
3
3
4
-
The basic Erigon configuration is suitable for most users just wanting to run a node. For building the latest stable release use the following command:
4
+
There are 3 options for running Erigon 3, listed from easiest to most difficult installation:
-[Use pre-built binaries](/installation/prebuilt.md): Download and run the latest stable release of Erigon. This is the easiest option and requires no additional dependencies.
7
+
8
+
-[Use Docker](/installation/docker.md): Run Erigon in a Docker container for isolation from the host system. This avoids dependencies but requires installing Docker.
11
9
12
-
This should create the binary at `./build/bin/erigon`.
10
+
-[Build Erigon from source](/installation/build.md): Build the Erigon source code directly on your system. This is the most complex option and requires a working Go environment.
then download the appropriate binary for your system. as shown above.
13
+
- For **Linux**:
14
+
-`erigon_3.x.x_amd64.deb` for 64-bit Intel/AMD processors
15
+
-`erigon_3.x.x_arm64.deb` for 64-bit ARM processors
16
+
-`erigon_v3.x.x_linux_amd64.tar.gz` for 64-bit Intel/AMD processors
17
+
-`erigon_v3.x.x_linux_arm64.tar.gz` for 64-bit ARM processors
18
+
- For **MacOS**:
19
+
-`erigon_3.x.x_darwin_amd64.tar.gz` for 64-bit Intel/AMD processors
20
+
-`erigon_3.x.x_darwin_arm64.tar.gz` for 64-bit ARM processors
21
+
### Checksums
22
+
23
+
To verify the integrity of the downloaded file, you can use the checksums provided in the `erigon_v3.x.x_checksums.txt` file. This file contains SHA256 checksums for all Erigon binaries.
0 commit comments