zeekayandHanzo Dev 324f613c3d zap: a VM that cannot answer is not a VM that said no ...

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]>

2026-08-16 08:19:06 -07:00

..

atomic_test.go

zap: carry the cross-chain atomic seam across the plugin boundary

2026-08-06 14:08:52 -07:00

atomic.go

zap: add Indexed to the atomic surface, and stop Serve panicking after Close

2026-08-06 14:21:00 -07:00

doc.go

Add ZAP wire protocol transport for VM communication

2026-01-24 11:39:40 -08:00

LLM.md

docs(zap): canonical TCP port 9999 documented

2026-05-06 10:37:28 -07:00

sender.go

fix(zap): bound element counts before make() to stop unbounded-alloc DoS

2026-06-06 20:46:47 -07:00

transport_test.go

zap: add Indexed to the atomic surface, and stop Serve panicking after Close

2026-08-06 14:21:00 -07:00

transport.go

zap: add Indexed to the atomic surface, and stop Serve panicking after Close

2026-08-06 14:21:00 -07:00

vm_test.go

fix(zap): length-tolerant InitializeResponse decode (evolvable VM wire)

2026-07-16 12:31:15 -07:00

vm.go

zap: a VM that cannot answer is not a VM that said no

2026-08-16 08:19:06 -07:00

warp.go

fix(zap): bound element counts before make() to stop unbounded-alloc DoS

2026-06-06 20:46:47 -07:00

wire_test.go

Add ZAP wire protocol transport for VM communication

2026-01-24 11:39:40 -08:00

wire.go

zap: add Indexed to the atomic surface, and stop Serve panicking after Close

2026-08-06 14:21:00 -07:00