Skip to main content

Module render

Module render 

Source
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’s Display drops the 0x that its serde writes.
explorer_time πŸ”’
The same Rfc3339 format Timestamp’s own Serialize uses, so v1 and v2 agree on the string.
field_tb64 πŸ”’
The encoding jellyfish’s canonical serde helper gives every hash, index and element of a proof: ark-compressed bytes under the FIELD tag, whatever the underlying type is. block_state_path_mirrors_its_v1_rendering pins 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 in proto::HeaderResponse’s impl. A From<&Header> would let a 0.1 header reach them.
header_v5 πŸ”’
See header_v4 for why this is not a From impl.
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.