Hey Everyone,
We had a forkless upgrade issue which may require you to re-sync your testnet nodes. The team is working on a fix now that will result in a testnet reorganization, we will keep you posted.
On Fuel, sometimes we may have a block reordering, which can affect historical indexed data. I wanted to check how you guys see this and if you are ready to handle this situation.
- Reorgs have a limited window of 7 days
- We have a planned reorg to happen in the next few days, that is required, as we accidentally deployed a bad version of the Fuel transaction transition WASM.
When the reorg occurs, we might revert a limited set of transactions from block 7625610 to the reorganization block. Affected transactions would be ones that rely on a given block hash (since that will change in the re-org).
If your app is connected to the public Fuel RPC (https://testnet.fuel.network/v1/graphql) you should not be affected. If your infra is relying on a testnet node, you may be affected.
Please do the following if you’re impacted:
-
Upgrade immediately to the latest release (fuel-core
v0.32.1) to resume syncing -
Be ready for another upgrade in the next 7 days that will need to be applied as quickly as possible (chain sync will stop again until you upgrade once the release is ready). We’ll try to give 24 hours notice on the upgrade, and it’s possible testnet will be down for about an hour during the re-org.
Please let us know if you have any questions!