An important update on the chain configuration

We completed Reorg successfully, and the network is now operational as expected. However, following today’s network upgrade, those who are running the node and want to connect to the network should download and use the new genesis chain configuration chain-configuration/ignition/chain_config.json at 3167a19d2ddc6808a9446ed244846d238cbc41e8 · FuelLabs/chain-configuration · GitHub and use the fuel-core v0.33.0

3 Likes

I am running node already in a vps, how can I change the config and update it? Any help?

Should I have to follow this guide again? Running a Testnet Node | Fuel Docs

How can I run upgrade the prev node or make it sync with this new upgrade?

Yes, you should follow the guide with the above chain config

then my prev node running history will be removed right If I do from start?

If you restart your node with the updated configuration and use the --db-type in-memory option, your previous node running history will be removed because the blockchain state is only stored in memory and not persisted. However, if you use the --db-path option to specify a persistent storage path, your node’s history will be preserved.

Thank you for the input but can you please write the commands I can use in terminal to fetch the updated config file and my prev node can sync automatically?

your node wont sync automatically, you will have to stop and restart after fetching the updated chain config.
you can do git pull followed by git fetch in your current locally cloned chain config directory