From 68abc8c761d44406db98d13cce863b0a9e936701 Mon Sep 17 00:00:00 2001 From: vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Tue, 14 Oct 2025 16:22:40 -0700 Subject: [PATCH 1/5] updating the the steps for network upgrade for forte --- .../node-operation/network-upgrade.md | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/docs/protocol/node-ops/node-operation/network-upgrade.md b/docs/protocol/node-ops/node-operation/network-upgrade.md index 79d06e3002..ea79be6160 100644 --- a/docs/protocol/node-ops/node-operation/network-upgrade.md +++ b/docs/protocol/node-ops/node-operation/network-upgrade.md @@ -16,12 +16,14 @@ Network Upgrades are approximately once every year. Upcoming network upgrades are announced in advance on the `#flow-validators-announcements` [Discord channel](https://discord.gg/flow) and on the [status](https://status.flow.com/) page. The `#flow-validators-announcements` channel is also used to coordinate during the upgrade process with all the node operators. +> 📢 [Forte Upgrade](https://status.flow.com/incidents/x91d6t1x1qh4) on Wednesday, Oct 22nd, 2025 at 15:00 UTC + This guide is for existing operators participating in a network upgrade. See [Node Bootstrap](./node-bootstrap.md) for a guide to joining the network for the first time. ## Step 1 - Cleaning Up Previous Spork State -Once the spork start has been announced on, stop your node and clear your database. The node should stay stopped for the duration of the spork. +Once the spork start has been announced on Discord, stop your node and clear your database. The node should stay stopped for the duration of the spork. You can skip this step if it is your first time running a node on Flow. @@ -54,7 +56,8 @@ If you had set the [dynamic bootstrap arguments](https://developers.flow.com/pro - It will generally be `testnet-x` or `mainnet-x` if execution data indexing is not enabled. - It will generally be `testnet-x-execution` or `mainnet-x-execution` if execution data indexing is enabled. See [here](../access-nodes/access-node-configuration-options.md) to enable execution date indexing. -- `YOUR_NODE_TYPE` should be one of `collection`, `consensus`, `execution`, `verification`, `access` based on the node(s) that you are running. +- `YOUR_NODE_TYPE` should be one of `collection`, `consensus`, `execution`, `verification` based on the node(s) that you are running. + - For access nodes however, if you have execution data index enabled use the role `execution` otherwise use `access`. ```shell Example $ ./boot-tools/transit pull -b ./bootstrap -t mainnet-16 -r consensus @@ -78,7 +81,17 @@ $ tree ./bootstrap/ └── random-beacon.priv.json.39fa54984b8eaa463e129919464f61c8cec3a4389478df79c44eb9bfbf30799a ``` -2. Start your Flow node via `docker` or `systemd` +2. Adjust command line arguments + +For the Forte upgrade, for all node type: Remove the `pebble-dir` argument as it has been deprecated. +The node will continue to use the `datadir` argument which points to the location of the node database. + + +3. Start your Flow node via `docker` or `systemd` + +The FlowFoundation team will share the new docker tag at the completion of the upgrade. Please use that docket tag to bring up the node. + +You can also compile and run the node software from [source](https://github.com/onflow/flow-go). The release tag will also be shared at the completion of the upgrade. See [Node Bootstrap](./node-bootstrap.md) for detailed information on Docker/Systemd configuration. From 68baa5329a27f8e3f7bfc6860e0b8d312ccd9dc3 Mon Sep 17 00:00:00 2001 From: vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Tue, 14 Oct 2025 16:24:13 -0700 Subject: [PATCH 2/5] updating the the steps for network upgrade for forte --- docs/protocol/node-ops/node-operation/network-upgrade.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/protocol/node-ops/node-operation/network-upgrade.md b/docs/protocol/node-ops/node-operation/network-upgrade.md index ea79be6160..4e27b5e8ad 100644 --- a/docs/protocol/node-ops/node-operation/network-upgrade.md +++ b/docs/protocol/node-ops/node-operation/network-upgrade.md @@ -81,9 +81,9 @@ $ tree ./bootstrap/ └── random-beacon.priv.json.39fa54984b8eaa463e129919464f61c8cec3a4389478df79c44eb9bfbf30799a ``` -2. Adjust command line arguments +2. Update command line arguments -For the Forte upgrade, for all node type: Remove the `pebble-dir` argument as it has been deprecated. +For the Forte upgrade, remove the `pebble-dir` argument as it has been deprecated. This applies to all node types. The node will continue to use the `datadir` argument which points to the location of the node database. From b2fcc2048753f9232e2211d6fab06102d450adf7 Mon Sep 17 00:00:00 2001 From: Vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Thu, 16 Oct 2025 13:42:39 -0700 Subject: [PATCH 3/5] Apply suggestion from @peterargue Co-authored-by: Peter Argue <89119817+peterargue@users.noreply.github.com> --- docs/protocol/node-ops/node-operation/network-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/protocol/node-ops/node-operation/network-upgrade.md b/docs/protocol/node-ops/node-operation/network-upgrade.md index 4e27b5e8ad..8ec161f7cd 100644 --- a/docs/protocol/node-ops/node-operation/network-upgrade.md +++ b/docs/protocol/node-ops/node-operation/network-upgrade.md @@ -89,7 +89,7 @@ The node will continue to use the `datadir` argument which points to the locatio 3. Start your Flow node via `docker` or `systemd` -The FlowFoundation team will share the new docker tag at the completion of the upgrade. Please use that docket tag to bring up the node. +The FlowFoundation team will share the new docker tag at the completion of the upgrade. Please use that docker tag to bring up the node. You can also compile and run the node software from [source](https://github.com/onflow/flow-go). The release tag will also be shared at the completion of the upgrade. From 6d8bb0342f27d24f4926fbc174fb301f6f772e0d Mon Sep 17 00:00:00 2001 From: vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Thu, 16 Oct 2025 13:48:12 -0700 Subject: [PATCH 4/5] updating based on review comment --- docs/protocol/node-ops/node-operation/network-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/protocol/node-ops/node-operation/network-upgrade.md b/docs/protocol/node-ops/node-operation/network-upgrade.md index 8ec161f7cd..d333300b3a 100644 --- a/docs/protocol/node-ops/node-operation/network-upgrade.md +++ b/docs/protocol/node-ops/node-operation/network-upgrade.md @@ -57,7 +57,7 @@ If you had set the [dynamic bootstrap arguments](https://developers.flow.com/pro - It will generally be `testnet-x-execution` or `mainnet-x-execution` if execution data indexing is enabled. See [here](../access-nodes/access-node-configuration-options.md) to enable execution date indexing. - `YOUR_NODE_TYPE` should be one of `collection`, `consensus`, `execution`, `verification` based on the node(s) that you are running. - - For access nodes however, if you have execution data index enabled use the role `execution` otherwise use `access`. + - For access nodes however, if you have execution data index enabled use the role `execution` to ensure the execution state files (`root.checkpoint*`) are also downloaded. If you do not have execution data indexing enabled, specify the role as `access`. ```shell Example $ ./boot-tools/transit pull -b ./bootstrap -t mainnet-16 -r consensus From bd39eaaba502f8308e72f7fa159a86ab0631800a Mon Sep 17 00:00:00 2001 From: vishal <1117327+vishalchangrani@users.noreply.github.com> Date: Thu, 16 Oct 2025 13:56:14 -0700 Subject: [PATCH 5/5] removing the line about build from source --- docs/protocol/node-ops/node-operation/network-upgrade.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/protocol/node-ops/node-operation/network-upgrade.md b/docs/protocol/node-ops/node-operation/network-upgrade.md index d333300b3a..01c4af2008 100644 --- a/docs/protocol/node-ops/node-operation/network-upgrade.md +++ b/docs/protocol/node-ops/node-operation/network-upgrade.md @@ -91,8 +91,6 @@ The node will continue to use the `datadir` argument which points to the locatio The FlowFoundation team will share the new docker tag at the completion of the upgrade. Please use that docker tag to bring up the node. -You can also compile and run the node software from [source](https://github.com/onflow/flow-go). The release tag will also be shared at the completion of the upgrade. - See [Node Bootstrap](./node-bootstrap.md) for detailed information on Docker/Systemd configuration. ## Common Issues