zeekayandHanzo Dev 40a666fb62 zap: message types for validator state (70-79) ...

Validator state is an interface over live node-owned state, so a plugin-hosted
VM cannot receive it by value and must ask across the boundary — the same reason
the atomic message types exist. M-Chain forms its threshold committee from these
answers.

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

2026-08-20 18:21:03 -07:00

..

atomic_test.go

zap: carry a validator-state server address to plugins

2026-08-20 18:18:31 -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: carry a validator-state server address to plugins

2026-08-20 18:18:31 -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: message types for validator state (70-79)

2026-08-20 18:21:03 -07:00