rjl493456442 1be5da2330 eth/protocols/snap: redo the snap sync if the bal is unavailable (#35181) ... This PR introduces a new condition that if the local node falls behind too much and the required BAL for catching up is very likely to be unavailable, the entire snap sync will be restarting from scratch. As the defined BAL retention window is weak-subjective-period which is calculated dynamically. A more conservative threshold is used (90K blocks) for robustness. Apart from that, the BAL catchup will be divided into several spans and apply one by one. It's essential to prevent the potential out-of-memory panic of placing the entire BAL set in memory.		2026-06-17 09:57:08 +08:00
..
eth	eth/protocols/eth: track announced tx hashes only after send (#35122)	2026-06-08 16:02:20 -04:00
snap	eth/protocols/snap: redo the snap sync if the bal is unavailable (#35181)	2026-06-17 09:57:08 +08:00