Sina M e444823394 core: fix sync reset in pruned nodes (#31638) ... This is an attempt at fixing #31601. I think what happens is the startup logic will try to get the full block body (it's `bc.loadLastState`) and fail because genesis block has been pruned from the freezer. This will cause it to keep repeating the reset logic, causing a deadlock. This can happen when due to an unsuccessful sync we don't have the state for the head (or any other state) fully, and try to redo the snap sync. --------- Co-authored-by: Gary Rong <garyrong0905@gmail.com>		2025-04-17 16:32:40 +08:00
..
blobpool	core/txpool: allow tx and authority regardless of admission order (#31373)	2025-04-09 19:11:24 -06:00
legacypool	core/txpool/legacypool: fix data race of txlookup access (#31641)	2025-04-17 10:36:53 +08:00
locals	core/txpool: fix nonce assignment in local tracker (#31496)	2025-03-28 12:32:24 +01:00
errors.go	core/txpool: add 7702 protection to blobpool (#31526)	2025-04-08 07:46:27 -06:00
reserver.go	core/txpool: allow tx and authority regardless of admission order (#31373)	2025-04-09 19:11:24 -06:00
subpool.go	core/txpool: allow tx and authority regardless of admission order (#31373)	2025-04-09 19:11:24 -06:00
txpool.go	core: fix sync reset in pruned nodes (#31638)	2025-04-17 16:32:40 +08:00
validation.go	eth: check blob transaction validity on the peer goroutine when received (#31219)	2025-03-01 14:10:38 +01:00