Node syncing issues since 0.43.2

General
1

I tried to resync my mainnet node, which got stuck at block 424886, so I created a whole new server and tried to download and sync everything from scratch but it gets stuck at the exact same block.
I’ve been constantly battling issues since 0.43.2 and I have no clue how to solve them. I have tried running with systemd, setting open files limits, with fuelup, building from source, with forc node ignition. They all result in the following error. When I sync from scratch they get stuck at the exact same block with this error:

2025-05-20T13:09:05.905937Z  INFO new{name=fuel-mainnet-node}:initialize_loop{service="SyncTask"}:sync:observe{self=State { status: Committed(424886) } height=22560336}: fuel_core_sync::state: 204: Status change from: Committed(424886), to: Processing(424887..=22560336)
2025-05-20T13:09:06.039969Z  INFO new{name=fuel-mainnet-node}:initialize_loop{service="SyncTask"}:sync:observe{self=State { status: Processing(424887..=22560336) } height=22560337}: fuel_core_sync::state: 204: Status change from: Processing(424887..=22560336), to: Processing(424887..=22560337)
2025-05-20T13:09:06.283787Z ERROR fuel_core_services: 71: Failed to wait for DA layer to sync Relayer is too far out of sync
2025-05-20T13:09:06.528498Z  WARN fuel_core_upgradable_executor::executor: 782: The block version(10) is different from the native executor version(28). The WASM executor will be used.
2025-05-20T13:09:06.529519Z ERROR new{name=fuel-mainnet-node}:initialize_loop{service="ImportTask"}:import:launch_stream{range=424887..=22560336}:execute_and_commit{height=424887 id=b34d8efd08446e0e7c2175315a22c754f7c256a4e45a36946899d37587b8b93f}: fuel_core_sync::import: 735: Execution of height 424887 failed: The execution of the block failed: Block generated during validation does not match the provided block.
2025-05-20T13:09:06.529758Z ERROR new{name=fuel-mainnet-node}:initialize_loop{service="ImportTask"}:import:launch_stream{range=424887..=22560336}:execute_and_commit{height=424887 id=b34d8efd08446e0e7c2175315a22c754f7c256a4e45a36946899d37587b8b93f}: fuel_core_sync::import: 713: error=The execution of the block failed: Block generated during validation does not match the provided block.
2025-05-20T13:09:06.529887Z ERROR new{name=fuel-mainnet-node}:initialize_loop{service="ImportTask"}:import:launch_stream{range=424887..=22560336}: fuel_core_sync::import: 357: Failed to execute and commit block from peer Some(PeerId([0, 37, 8, 2, 18, 33, 2, 4, 68, 234, 22, 49, 108, 59, 173, 128, 212, 95, 65, 135, 116, 168, 99, 158, 52, 61, 161, 220, 138, 133, 225, 78, 85, 129, 37, 133, 101, 238, 81])): The execution of the block failed: Block generated during validation does not match the provided block.

Environment

fuel-core : 0.43.2
x86_64-unknown-linux-gnu (ubuntu)

3 Likes
2

Hey @soltheon, we are looking into it. we will get back to you soon

1 Like
3

this should be fixed with Release v0.68.6 · FuelLabs/sway · GitHub

4

This was a problem with sway?

6

@naz3eh can you explain how this has anything to do with sway?

1 Like
7

Hey @soltheon, sorry for the late reply. this was not the bug with Sway but with the tooling team. That was dependent on the newer version of forc.

I hope your issue is fixed.

Also, do checkout our latest fuel-core v0.45.1 upgrade Fuel Core 0.45.1 Upgrade Notice (Recommended Upgrade)

8

I had this same issue, upgrading to 0.45.1 didn’t helpI also tried syncing with 0.35.0, which has the native executor for state transition 10, to no avail

Sep 17 09:30:05 vmi2499923 fuel-core[547930]: 2025-09-17T07:30:05.471995Z ERROR new{name=fuel-mainnet-node}:initialize_loop{service=“ImportTask”}:import:launch_stream{range=424887..=32898963}:execute_and_commit{height=424887 id=b34d8efd08446e0e7c2175315a22c754f7c256a4e45a36946899d37587b8b93f}: fuel_core_sync::import: 663: Execution of height 424887 failed: The execution of the block failed: Block generated during validation does not match the provided block.
Sep 17 09:30:05 vmi2499923 fuel-core[547930]: 2025-09-17T07:30:05.472024Z ERROR new{name=fuel-mainnet-node}:initialize_loop{service=“ImportTask”}:import:launch_stream{range=424887..=32898963}:execute_and_commit{height=424887 id=b34d8efd08446e0e7c2175315a22c754f7c256a4e45a36946899d37587b8b93f}: fuel_core_sync::import: 641: error=The execution of the block failed: Block generated during validation does not match the provided block.
Sep 17 09:30:05 vmi2499923 fuel-core[547930]: 2025-09-17T07:30:05.472033Z ERROR new{name=fuel-mainnet-node}:initialize_loop{service=“ImportTask”}:import:launch_stream{range=424887..=32898963}: fuel_core_sync::import: 324: Failed to execute and commit block from peer Some(PeerId([0, 37, 8, 2, 18, 33, 3, 108, 44, 192, 254, 141, 208, 181, 30, 191, 240, 2, 187, 236, 235, 88, 78, 44, 93, 200, 64, 46, 0, 54, 223, 89, 238, 65, 242, 126, 74, 207, 77])): The execution of the block failed: Block generated during validation does not match the provided block.

I think most people syncing from zero will hit this

9

i also see that the block id on @soltheon logs and mine for 424887 is b34d8efd0… but the fuel explorer says is 2757ADD5F9…

and the peer we got the block from is the same, could it be that the peer is relaying a bad block?

EDIT: the peer is not the same… only the peer id is similar