From 9e6f7ccc08604560f6cb7a36bb089e7e0736b3ca Mon Sep 17 00:00:00 2001
From: vishal <1117327+vishalchangrani@users.noreply.github.com>
Date: Fri, 10 Oct 2025 22:44:28 -0700
Subject: [PATCH 01/11] hardware spec changes for the forte upgrade
---
.../node-operation/node-provisioning.md | 20 ++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/docs/protocol/node-ops/node-operation/node-provisioning.md b/docs/protocol/node-ops/node-operation/node-provisioning.md
index d7fc532575..c13768f614 100644
--- a/docs/protocol/node-ops/node-operation/node-provisioning.md
+++ b/docs/protocol/node-ops/node-operation/node-provisioning.md
@@ -9,18 +9,20 @@ sidebar_position: 10
The hardware your Node will need varies depending on the role your Node will play in the Flow network. For an overview of the differences see the [Node Roles Overview](./node-roles.md).
-| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
-|:----------------:| ---------:| ------:| ------:|:--------------:|:--------------:|
-| **Collection** | 4 cores | 32 GB | 200 GB | n2-highmem-4 | r6i.xlarge |
-| **Consensus** | 2 cores | 16 GB | 200 GB | n2-standard-4 | m6a.xlarge |
-| **Execution** | 128 cores | 864 GB | 9 TB (with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
-| **Verification** | 2 cores | 16 GB | 200 GB | n2-highmem-2 | r6a.large |
-| **Access** | 16 cores | 64 GB | 750 GB | n2-standard-16 | m6i.4xlarge |
-| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
-| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
+| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
+|:----------------:|-------------------------:|--------------------:|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
+| **Collection** | 2 cores 🆕 (was 4 cores) | 8 GB 🆕 (was 32 GB) | 200 GB | n2-highmem-4 | r6i.xlarge |
+| **Consensus** | 2 cores | 8 GB 🆕(was 16 GB) | 200 GB | n2-standard-4 | m6a.xlarge |
+| **Execution** | 128 cores | 864 GB | 9 TB (with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
+| **Verification** | 2 cores | 8 GB 🆕 (was 16 GB) | 200 GB | n2-highmem-2 | r6a.large |
+| **Access** | 16 cores | 64 GB | 750 GB | n2-standard-16 | m6i.4xlarge |
+| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
+| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
_Note: The above numbers represent our current best estimate for the state of the network. These will be actively updated as we continue benchmarking the network's performance._
+_Note: If you are running your node on bare metal, we recommend provisioning a machine with higher CPU and memory than the minimum requirements. Unlike cloud instances, bare metal servers cannot be easily scaled up, and over-provisioning upfront helps avoid the need for disruptive hardware upgrades later._
+
## Networking Requirements
Most of the load on your nodes will be messages sent back and forth between other nodes on the network. Make sure you have a sufficiently fast connection; we recommend at _least_ 1Gbps, and 5Gbps is better.
From b9970ce10983b409d31c5b76ecbc27b5cb044d28 Mon Sep 17 00:00:00 2001
From: vishal <1117327+vishalchangrani@users.noreply.github.com>
Date: Tue, 14 Oct 2025 14:56:54 -0700
Subject: [PATCH 02/11] revising AN hardware requirements for forte
---
.../node-operation/node-provisioning.md | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/protocol/node-ops/node-operation/node-provisioning.md b/docs/protocol/node-ops/node-operation/node-provisioning.md
index c13768f614..742e52c1df 100644
--- a/docs/protocol/node-ops/node-operation/node-provisioning.md
+++ b/docs/protocol/node-ops/node-operation/node-provisioning.md
@@ -9,15 +9,15 @@ sidebar_position: 10
The hardware your Node will need varies depending on the role your Node will play in the Flow network. For an overview of the differences see the [Node Roles Overview](./node-roles.md).
-| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
-|:----------------:|-------------------------:|--------------------:|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
-| **Collection** | 2 cores 🆕 (was 4 cores) | 8 GB 🆕 (was 32 GB) | 200 GB | n2-highmem-4 | r6i.xlarge |
-| **Consensus** | 2 cores | 8 GB 🆕(was 16 GB) | 200 GB | n2-standard-4 | m6a.xlarge |
-| **Execution** | 128 cores | 864 GB | 9 TB (with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
-| **Verification** | 2 cores | 8 GB 🆕 (was 16 GB) | 200 GB | n2-highmem-2 | r6a.large |
-| **Access** | 16 cores | 64 GB | 750 GB | n2-standard-16 | m6i.4xlarge |
-| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
-| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
+| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
+|:----------------:|--------------------------:|--------------------:|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
+| **Collection** | 2 cores 🆕 (was 4 cores) | 8 GB 🆕 (was 32 GB) | 200 GB | n2-highmem-4 | r6i.xlarge |
+| **Consensus** | 2 cores | 8 GB 🆕 (was 16 GB) | 200 GB | n2-standard-4 | m6a.xlarge |
+| **Execution** | 128 cores | 864 GB | 9 TB (with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
+| **Verification** | 2 cores | 8 GB 🆕 (was 16 GB) | 200 GB | n2-highmem-2 | r6a.large |
+| **Access** | 8 cores 🆕 (was 16 cores) | 64 GB | 750 GB | n2-standard-16 | m6i.4xlarge |
+| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
+| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
_Note: The above numbers represent our current best estimate for the state of the network. These will be actively updated as we continue benchmarking the network's performance._
From 529cd93a8c9ac495ebb586159429a0e1614fb177 Mon Sep 17 00:00:00 2001
From: vishal <1117327+vishalchangrani@users.noreply.github.com>
Date: Tue, 14 Oct 2025 15:21:00 -0700
Subject: [PATCH 03/11] updating examples of gcp instance type and aws instance
type
---
.../node-operation/node-provisioning.md | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/protocol/node-ops/node-operation/node-provisioning.md b/docs/protocol/node-ops/node-operation/node-provisioning.md
index 742e52c1df..f664ec605c 100644
--- a/docs/protocol/node-ops/node-operation/node-provisioning.md
+++ b/docs/protocol/node-ops/node-operation/node-provisioning.md
@@ -9,15 +9,15 @@ sidebar_position: 10
The hardware your Node will need varies depending on the role your Node will play in the Flow network. For an overview of the differences see the [Node Roles Overview](./node-roles.md).
-| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
-|:----------------:|--------------------------:|--------------------:|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
-| **Collection** | 2 cores 🆕 (was 4 cores) | 8 GB 🆕 (was 32 GB) | 200 GB | n2-highmem-4 | r6i.xlarge |
-| **Consensus** | 2 cores | 8 GB 🆕 (was 16 GB) | 200 GB | n2-standard-4 | m6a.xlarge |
-| **Execution** | 128 cores | 864 GB | 9 TB (with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
-| **Verification** | 2 cores | 8 GB 🆕 (was 16 GB) | 200 GB | n2-highmem-2 | r6a.large |
-| **Access** | 8 cores 🆕 (was 16 cores) | 64 GB | 750 GB | n2-standard-16 | m6i.4xlarge |
-| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
-| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
+| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
+|:----------------:|-----------------------------:|------------------------:|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
+| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Execution** | 128 cores | 864 GB | 9 TB (with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
+| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
+| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
+| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
_Note: The above numbers represent our current best estimate for the state of the network. These will be actively updated as we continue benchmarking the network's performance._
From 87c65e0610834555b89b85968e3dc1a692efd106 Mon Sep 17 00:00:00 2001
From: vishal <1117327+vishalchangrani@users.noreply.github.com>
Date: Tue, 14 Oct 2025 15:23:02 -0700
Subject: [PATCH 04/11] minor edit to the hw requirement table
---
.../node-operation/node-provisioning.md | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/protocol/node-ops/node-operation/node-provisioning.md b/docs/protocol/node-ops/node-operation/node-provisioning.md
index f664ec605c..8fc2c55dfe 100644
--- a/docs/protocol/node-ops/node-operation/node-provisioning.md
+++ b/docs/protocol/node-ops/node-operation/node-provisioning.md
@@ -9,15 +9,15 @@ sidebar_position: 10
The hardware your Node will need varies depending on the role your Node will play in the Flow network. For an overview of the differences see the [Node Roles Overview](./node-roles.md).
-| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
-|:----------------:|-----------------------------:|------------------------:|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
-| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Execution** | 128 cores | 864 GB | 9 TB (with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
-| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
-| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
-| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
+| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
+|:----------------:|-----------------------------:|------------------------:|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
+| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Execution** | 128 cores | 864 GB | 9 TB
(with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
+| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
+| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
+| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
_Note: The above numbers represent our current best estimate for the state of the network. These will be actively updated as we continue benchmarking the network's performance._
From 17f3cf746ffd975ccd2dc844fd809ee32fb9824d Mon Sep 17 00:00:00 2001
From: vishal <1117327+vishalchangrani@users.noreply.github.com>
Date: Tue, 14 Oct 2025 15:24:51 -0700
Subject: [PATCH 05/11] minor edit to the hw requirement table
---
.../node-operation/node-provisioning.md | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/protocol/node-ops/node-operation/node-provisioning.md b/docs/protocol/node-ops/node-operation/node-provisioning.md
index 8fc2c55dfe..af30f8c685 100644
--- a/docs/protocol/node-ops/node-operation/node-provisioning.md
+++ b/docs/protocol/node-ops/node-operation/node-provisioning.md
@@ -9,15 +9,15 @@ sidebar_position: 10
The hardware your Node will need varies depending on the role your Node will play in the Flow network. For an overview of the differences see the [Node Roles Overview](./node-roles.md).
-| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
-|:----------------:|-----------------------------:|------------------------:|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
-| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Execution** | 128 cores | 864 GB | 9 TB
(with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
-| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
-| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
-| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
+| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
+|:----------------:|:-----------------------------:|:------------------------:|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
+| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Execution** | 128 cores | 864 GB | 9 TB
(with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
+| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
+| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
+| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
_Note: The above numbers represent our current best estimate for the state of the network. These will be actively updated as we continue benchmarking the network's performance._
From cbe365a8a77af23683b45e23cdf244499c3447ea Mon Sep 17 00:00:00 2001
From: vishal <1117327+vishalchangrani@users.noreply.github.com>
Date: Tue, 14 Oct 2025 15:26:28 -0700
Subject: [PATCH 06/11] minor edit to the hw requirement table
---
.../node-operation/node-provisioning.md | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/protocol/node-ops/node-operation/node-provisioning.md b/docs/protocol/node-ops/node-operation/node-provisioning.md
index af30f8c685..9f2e2f3bc4 100644
--- a/docs/protocol/node-ops/node-operation/node-provisioning.md
+++ b/docs/protocol/node-ops/node-operation/node-provisioning.md
@@ -9,15 +9,15 @@ sidebar_position: 10
The hardware your Node will need varies depending on the role your Node will play in the Flow network. For an overview of the differences see the [Node Roles Overview](./node-roles.md).
-| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
-|:----------------:|:-----------------------------:|:------------------------:|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
-| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Execution** | 128 cores | 864 GB | 9 TB
(with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
-| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
-| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
-| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
+| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
+|:----------------:|:-----------------------------:|:------------------------:|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
+| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Execution** | 128 cores | 864 GB | 9 TB (with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
+| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
+| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
+| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
_Note: The above numbers represent our current best estimate for the state of the network. These will be actively updated as we continue benchmarking the network's performance._
From 4b89b8b8b4127d20f8a4392012ef1e77cf5c6617 Mon Sep 17 00:00:00 2001
From: vishal <1117327+vishalchangrani@users.noreply.github.com>
Date: Tue, 14 Oct 2025 15:32:15 -0700
Subject: [PATCH 07/11] minor edit to the hw requirement table
---
.../node-operation/node-provisioning.md | 20 ++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/docs/protocol/node-ops/node-operation/node-provisioning.md b/docs/protocol/node-ops/node-operation/node-provisioning.md
index 9f2e2f3bc4..639af14a1d 100644
--- a/docs/protocol/node-ops/node-operation/node-provisioning.md
+++ b/docs/protocol/node-ops/node-operation/node-provisioning.md
@@ -9,15 +9,17 @@ sidebar_position: 10
The hardware your Node will need varies depending on the role your Node will play in the Flow network. For an overview of the differences see the [Node Roles Overview](./node-roles.md).
-| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
-|:----------------:|:-----------------------------:|:------------------------:|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|:--------------------:|
-| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Execution** | 128 cores | 864 GB | 9 TB (with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167) or 30 TB without maintenance) | n2-highmem-128 | |
-| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
-| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
-| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
+| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
+|:----------------:|:----------------------------:|:-----------------------:|:--------:|:--------------------:|:--------------------:|
+| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Execution** | 128 cores | 864 GB | 9 TB[^1] | n2-highmem-128 | |
+| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
+| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
+| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
+
+ [^1]: Recommended with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167), 30 TB without maintenance.
_Note: The above numbers represent our current best estimate for the state of the network. These will be actively updated as we continue benchmarking the network's performance._
From 16dfea516ca4c7e01c0c2a7a7431009a9dffb7e0 Mon Sep 17 00:00:00 2001
From: vishal <1117327+vishalchangrani@users.noreply.github.com>
Date: Tue, 14 Oct 2025 15:35:51 -0700
Subject: [PATCH 08/11] minor edit to the hw requirement table
---
docs/protocol/node-ops/node-operation/node-provisioning.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/protocol/node-ops/node-operation/node-provisioning.md b/docs/protocol/node-ops/node-operation/node-provisioning.md
index 639af14a1d..0401270f2b 100644
--- a/docs/protocol/node-ops/node-operation/node-provisioning.md
+++ b/docs/protocol/node-ops/node-operation/node-provisioning.md
@@ -13,13 +13,13 @@ The hardware your Node will need varies depending on the role your Node will pla
|:----------------:|:----------------------------:|:-----------------------:|:--------:|:--------------------:|:--------------------:|
| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Execution** | 128 cores | 864 GB | 9 TB[^1] | n2-highmem-128 | |
+| **Execution** | 128 cores | 864 GB | 9 TB1 | n2-highmem-128 | |
| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
- [^1]: Recommended with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167), 30 TB without maintenance.
+1: Recommended with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167), 30 TB without maintenance.
_Note: The above numbers represent our current best estimate for the state of the network. These will be actively updated as we continue benchmarking the network's performance._
From 4c96faaec4c47376cdd8a68e6819d9d342d6891c Mon Sep 17 00:00:00 2001
From: vishal <1117327+vishalchangrani@users.noreply.github.com>
Date: Tue, 14 Oct 2025 15:40:27 -0700
Subject: [PATCH 09/11] changing
to
to fix vercel error
---
.../protocol/node-ops/node-operation/node-provisioning.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/protocol/node-ops/node-operation/node-provisioning.md b/docs/protocol/node-ops/node-operation/node-provisioning.md
index 0401270f2b..19710114a1 100644
--- a/docs/protocol/node-ops/node-operation/node-provisioning.md
+++ b/docs/protocol/node-ops/node-operation/node-provisioning.md
@@ -11,11 +11,11 @@ The hardware your Node will need varies depending on the role your Node will pla
| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
|:----------------:|:----------------------------:|:-----------------------:|:--------:|:--------------------:|:--------------------:|
-| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
| **Execution** | 128 cores | 864 GB | 9 TB1 | n2-highmem-128 | |
-| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
+| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
From a125caedc11dfb35ab46c2b534016c6a0752792a Mon Sep 17 00:00:00 2001
From: vishal <1117327+vishalchangrani@users.noreply.github.com>
Date: Tue, 14 Oct 2025 15:57:20 -0700
Subject: [PATCH 10/11] reformatted table
---
.../node-operation/node-provisioning.md | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/protocol/node-ops/node-operation/node-provisioning.md b/docs/protocol/node-ops/node-operation/node-provisioning.md
index 19710114a1..a6453893bf 100644
--- a/docs/protocol/node-ops/node-operation/node-provisioning.md
+++ b/docs/protocol/node-ops/node-operation/node-provisioning.md
@@ -9,15 +9,15 @@ sidebar_position: 10
The hardware your Node will need varies depending on the role your Node will play in the Flow network. For an overview of the differences see the [Node Roles Overview](./node-roles.md).
-| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
-|:----------------:|:----------------------------:|:-----------------------:|:--------:|:--------------------:|:--------------------:|
-| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Execution** | 128 cores | 864 GB | 9 TB1 | n2-highmem-128 | |
-| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
-| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
-| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
-| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
+| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
+|:----------------:|:------------------------------:|:-------------------------:|:----------------:|:--------------------:|:--------------------:|
+| **Collection** | 2 cores 🆕
(was 4 cores) | 8 GB 🆕
(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Consensus** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Execution** | 128 cores | 864 GB | 9 TB1 | n2-highmem-128 | |
+| **Verification** | 2 cores | 8 GB 🆕
(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
+| **Access** | 8 cores 🆕
(was 16 cores) | 32 GB 🆕
(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
+| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
+| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
1: Recommended with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167), 30 TB without maintenance.
From 4d0d0d251e6940f4470be5443d130ca21a148ecc Mon Sep 17 00:00:00 2001
From: vishal <1117327+vishalchangrani@users.noreply.github.com>
Date: Tue, 14 Oct 2025 16:03:10 -0700
Subject: [PATCH 11/11] minor edit to the hw requirement table
---
docs/protocol/node-ops/node-operation/node-provisioning.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/docs/protocol/node-ops/node-operation/node-provisioning.md b/docs/protocol/node-ops/node-operation/node-provisioning.md
index a6453893bf..2429a030fb 100644
--- a/docs/protocol/node-ops/node-operation/node-provisioning.md
+++ b/docs/protocol/node-ops/node-operation/node-provisioning.md
@@ -21,6 +21,7 @@ The hardware your Node will need varies depending on the role your Node will pla
1: Recommended with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167), 30 TB without maintenance.
+
_Note: The above numbers represent our current best estimate for the state of the network. These will be actively updated as we continue benchmarking the network's performance._
_Note: If you are running your node on bare metal, we recommend provisioning a machine with higher CPU and memory than the minimum requirements. Unlike cloud instances, bare metal servers cannot be easily scaled up, and over-provisioning upfront helps avoid the need for disruptive hardware upgrades later._