On main branch.
Affected "Sync-from-scratch" test runs (10 of May):
Relevant logs from mainnet:
[INFO] [05-10|06:40:10.896] [4/6 Execution] DONE in=1m25.793297586s block=25021261
--> [2026-05-10 06:40:22] [INFO] SyncSentinel: node syncing, currentBlock=25019999, highestBlock=25019999
[INFO] [05-10|06:40:27.576] [4/6 Execution] serial starting from=25021261 to=25024999 initialTxNum=3496484374 initialBlockTxOffset=266 lastFrozenStep=8948 initialCycle=true isForkValidation=false
[WARN] [05-10|06:40:27.578] [4/6 Execution] Execution failed block=25021261 txNum=3496484375 header-hash=0x63b68d3af2ad04a2ce6467b0fffcdf4a742ae298349aafd15ca49b931388269e err="invalid block, txnIdx=266, nonce too low: address 0x3C329F13286B1F2C940113e84dEe097dbd7C35e9, tx: 24 state: 25" isForkValidation=false
[WARN] [05-10|06:40:27.578] no unwindable block found from changesets, falling back to latest with commitment block=25021261 err=nil
[INFO] [05-10|06:40:27.578] [4/6 Execution] serial done in=1.921074ms buf=0B/512.0MB blk=25021261 blks=1 blk/s=520 txs=0 tx/s=0 gas/s=0 stepsInDB=2.00 step=8951.0 alloc=20.2GB sys=25.6GB isForkValidation=false isApplyingBlocks=true
[WARN] [05-10|06:40:27.578] Cannot update chain head hash=0x29e78002a4472522d6ee20c26e82d2a4d8029ef0874be5dc1088d0ff3c94de1e err="updateForkChoice: [4/6 Execution] too far unwind. requested=25021260, minAllowed=25021261"
Affected "Sync-from-scratch (minimal node)" test run: :
The regression seems to have appeared between 5 and 6 May.
On main branch.
Affected "Sync-from-scratch" test runs (10 of May):
Relevant logs from mainnet:
Affected "Sync-from-scratch (minimal node)" test run: :
The regression seems to have appeared between 5 and 6 May.