mirror of
https://github.com/luxfi/api.git
synced 2026-09-24 00:24:53 +00:00
zeekayandHanzo Dev
324f613c3d
The six state-sync messages were reserved with payloads defined and no capability bit, so a node could only learn whether a VM syncs by asking and reading the reply. That conflates two different answers: a VM with no state-sync surface cannot respond at all, and a VM that has one may still choose to replay. A node repairing a damaged chain has to tell those apart — the first means look elsewhere, the second means this VM decided. CapStateSync is set at the handshake, where every other optional surface is already discovered, so the distinction costs no round trip. Co-authored-by: Hanzo Dev <[email protected]>