4 Commits

Include renames

Author	SHA1	Message	Date
zeekay	1de772ad2d	The shapes every chain answers in state their own ZAP wire ... A JSONTxID, a GetTxArgs, a GetBlockArgs and the ids inside them are what P and X reply with, and each holds an ids.ID — [32]byte, bytes_fixed[32] on the wire, which the derived codec refuses to carry. So none of those calls could cross the op-call plane. zap_gen.go is generated by zip.Codecs from the same layout the plane encodes against, and the JSON edge does not move: encoding/json reads the tags and knows nothing about a ZAP codec.	2026-08-29 18:58:36 -07:00
zeekay	57d45de11a	chore: sync dependencies and format code	2026-02-04 15:46:05 -08:00
zeekay	dd2f2c716e	Add ZAP wire protocol transport for VM communication ... - Add zap/ package with zero-copy binary wire protocol - Support for VM client/server communication over ZAP - Wire format: [4-byte length][1-byte message type][payload] - Includes sender, transport, and VM implementations	2026-01-24 11:39:40 -08:00
zeekay	b1db41a415	api: initial v1.0.0	2026-01-16 11:52:14 -08:00