5 Commits
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 a47abce458 WIP: session checkpoint 2026-06-05 (codec rip in flight) 2026-06-05 15:33:51 -07:00
zeekay 06b7887c87 feat: GetNodeVersionReply.Consensus + ConsensusInfo (info api); drop dead agentic_network.go
agentic_capnp sub-package was never generated; build-tag dead code referencing it
broke 'go mod tidy' (could not resolve unused phantom import). No-fake policy.

deps: tls v1.0.3 (hkdf.New); go mod tidy
2026-05-05 16:57:04 -07:00
zeekay 57d45de11a chore: sync dependencies and format code 2026-02-04 15:46:05 -08:00
zeekay b1db41a415 api: initial v1.0.0 2026-01-16 11:52:14 -08:00