zeekayandHanzo Dev 42ce072b1f zap: the state-sync surface has payload types
The six message numbers were reserved and nothing was ever built on them, so
neither end of the boundary could carry a state summary and the type assertion
that gates state sync failed on every chain in every release. The VM implements
sync; nothing could reach it.

Five of the calls are ordinary request/response. Accept is not: a summary is an
object with behaviour on the VM's side and only its identity can cross, so it
travels as an id and the server answers against the summary it produced under
that id. Rebuilding one from bytes the caller supplies would accept a summary
nobody ratified.

Absence has three answers rather than one zero: no summary is ErrorNotFound, a
VM that does not sync at all is ErrorStateSyncNotImplemented, and neither is
ErrorUnspecified, which means the fields can be trusted.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-16 08:17:26 -07:00
2026-01-16 11:52:14 -08:00
2026-01-16 11:52:14 -08:00
2026-02-14 05:26:18 -08:00
2026-07-26 10:01:48 -07:00
2026-01-16 11:52:14 -08:00
S
Description
No description provided
BSD-3-Clause
383 KiB
Languages
Go 79.5%
Cap'n Proto 12.8%
ZAP 7.7%