# Please upgrade Flow Verification node to v0.33.20-patch.1

**URL:** <https://forum.flow.com/t/please-upgrade-flow-verification-node-to-v0-33-20-patch-1/6067>\
**Category:** Node Operations\
**Created:** [May 9, 2024, 4:58pm UTC](https://forum.flow.com/t/please-upgrade-flow-verification-node-to-v0-33-20-patch-1/6067 "2024-05-09T16:58:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vishal](https://avatars.discourse-cdn.com/v4/letter/v/49beb7/32.png) [@vishal](https://forum.flow.com/u/vishal)\
**Post date:** [May 9, 2024, 4:58pm UTC](https://forum.flow.com/t/please-upgrade-flow-verification-node-to-v0-33-20-patch-1/6067/1 "2024-05-09T16:58:48Z")

</div>

hello **Verification** @Node Operators -

The height coordinated upgrade is now complete.

If you are running a Flow **Verification** node, please upgrade your node to docker tag `v0.33.20-patch.1` or alternatively, `v0.33.20-patch.1-without-netgo-without-adx` or `v0.33.20-patch.1-without-adx` or `v0.33.20-patch.1-arm` as per your hardware.

* * *

**Optional Steps**

After the node restarts, if you observe that the disk usage on the node spikes unusually high, you can do the following to avoid running out of disk space:

1. Stop the node.

2. Move the data folder (`mv /var/flow/data /var/flow/old_data` - adjust the path to the data directory as per your setup)

3. If the file ` /var/flow/bootstrap/public-root-information/root-protocol-state-snapshot.json` exists, rename it to something else. (`mv /var/flow/bootstrap/public-root-information/root-protocol-state-snapshot.json /var/flow/bootstrap/public-root-information/root-protocol-state-snapshot.json_old`)

4. Add the following docker flags to allow the node to use dynamic bootstrapping to come up,

```auto
--dynamic-startup-access-address=secure.mainnet.nodes.onflow.org:9001 \
--dynamic-startup-access-publickey=28a0d9edd0de3f15866dfe4aea1560c4504fe313fc6ca3f63a63e4f98d0e295144692a58ebe7f7894349198613f65b2d960abf99ec2625e247b1c78ba5bf2eae \
--dynamic-startup-epoch-phase=EpochPhaseStaking

```

1. Update the docker tag to `v0.33.20-patch.1` or alternatively, `v0.33.20-patch.1-without-netgo-without-adx` or `v0.33.20-patch.1-without-adx or v0.33.20-patch.1-arm` as per your hardware (if not already done).

2. Start the node.

3. If the node running is OK at this point, delete the backup folder `rm -rf /var/flow/old_data` and the root snapshot file `rm -f /var/flow/bootstrap/public-root-information/root-protocol-state-snapshot.json_old`.

We observed that a verification node may experience a large spike in disk usage when coming up hence suggesting moving the data folder in step 2 and using [dynamic bootstrapping](https://developers.flow.com/networks/node-ops/node-operation/node-bootstrap#dynamic-startup) which lets the node start off the current block height.

* * *

_ **Please make this change in the next 24 hours.** _

_ **As per policy, rewards will be withheld if the node is not updated within 24 hours.** _

No action is needed from other node types.

Thank you,  
Flow Foundation