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

..

service.go

api: initial v1.0.0

2026-01-16 11:52:14 -08:00

types.go

chore: sync dependencies and format code

2026-02-04 15:46:05 -08:00

zap_gen.go

The shapes every chain answers in state their own ZAP wire

2026-08-29 18:58:36 -07:00