zeekay 8005e1a29a The byte a warp reader dispatches on is a shape of its own ...

Both warp tables open with a kind byte and share nothing else, so reading it
meant wrapping the buffer as whichever answer the file listed first and asking
that one for its Kind. It gives the right byte and reads like a mistake — a
Conversion view over a message that is a Register.

`struct Tag` is that byte and nothing else: the question a reader asks before
it knows which answer it holds. Each arm then builds its own view over the
same object.

Where a shared PREFIX really does exist the code says so instead: every block
kind opens with the four fields a decided block is, and a proposal block's
transaction list sits at a standard block's offsets.

2026-09-06 13:24:17 -07:00

..

genesis.zap

The P-chain reads and writes its wire out of a schema

2026-09-06 13:20:10 -07:00

warp.zap

The P-chain reads and writes its wire out of a schema

2026-09-06 13:20:10 -07:00

warpmsg.zap

The byte a warp reader dispatches on is a shape of its own

2026-09-06 13:24:17 -07:00

wire.zap

The P-chain reads and writes its wire out of a schema

2026-09-06 13:20:10 -07:00