zeekayandHanzo Dev 8308671775 config: state sync is on ...

It was the zero value, so a chain got it only by carrying a per-chain config
file that said so — and most deployments have no chain-config path at all, which
made the one mechanism for rejoining after a deep gap unreachable on whole
fleets. There is no posture where refusing it and re-executing instead is the
right answer, so it is not a decision to hand an operator. The bound is
StateSyncMinBlocks, which lives inside the mechanism: a smaller gap replays and
never reaches this path.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-16 00:23:16 -07:00

..

evm

config: state sync is on

2026-08-16 00:23:16 -07:00

runner

plugin: refresh vm + main + runner

2026-05-20 16:24:51 -07:00

main.go

plugin: refresh vm + main + runner

2026-05-20 16:24:51 -07:00