Expand description
Consensus and query service types rendered as v2 proto messages.
FunctionsΒ§
- advz_
merkle_ πnode - builder_
commitment π - Empty from 0.7, when the header stopped carrying a builder commitment but kept the 0.5 shape.
- explorer_
accounts π FeeAccountβsDisplaydrops the0xthat its serde writes.- explorer_
time π - The same
Rfc3339formatTimestampβs ownSerializeuses, so v1 and v2 agree on the string. - field_
tb64 π - The encoding jellyfishβs
canonicalserde helper gives every hash, index and element of a proof: ark-compressed bytes under theFIELDtag, whatever the underlying type is.block_state_path_mirrors_its_v1_renderingpins the two to the same bytes. - header_
v4 π - Private, unlike the 0.1 and 0.3 shapes above, because the two
expects are sound only under the variant match inproto::HeaderResponseβs impl. AFrom<&Header>would let a 0.1 header reach them. - header_
v5 π - See
header_v4for why this is not aFromimpl. - json_
array π - json_
entry π - json_
field π - A missing or mistyped field means the upstream type changed, which is a 500 rather than an
empty value. v1 writes byte fields as integer arrays, which read back as
Vec<u8>. - qc_
signatures π - An aggregate signature and who signed it.
- quorum_
signatures π - reward_
merkle_ πtree_ root - 0.3 uses the first reward tree (Left), later versions the second (Right). 0.1 and 0.2 have none, and the accessor would fabricate an empty treeβs commitment for them.
- to_json π
- jellyfish keeps the fields of the VID shares and common, the range proofs and the bad-encoding proof private, so v1βs serde encoding is their one public view.