Get desktop application:
View/edit binary Protocol Buffers messages
Block data sent in the response.
Used in:
Block header hash.
Block header if requested.
optional
Block body if requested.
optional
Block receipt if requested.
optional
Block message queue if requested.
optional
Justification if requested.
optional
True if justification should be treated as present but empty. This hack is unfortunately necessary because shortcomings in the protobuf format otherwise doesn't make in possible to differentiate between a lack of justification and an empty justification.
optional, false if absent
Justifications if requested. Unlike the field for a single justification, this field does not required an associated boolean to differentiate between the lack of justifications and empty justification(s). This is because empty justifications, like all justifications, are paired with a non-empty consensus engine ID.
optional
Indexed block body if requestd.
optional
Request block data from a peer.
Bits of block data to request.
Start from this block.
Start with given hash.
Start with given block number.
Sequence direction. If missing, should be interpreted as "Ascending".
Maximum number of blocks to return. An implementation defined maximum is used when unspecified.
optional
Indicate to the receiver that we support multiple justifications. If the responder also supports this it will populate the multiple justifications field in `BlockData` instead of the single justification field.
optional
Response to `BlockRequest`
Block data for the requested sequence.
Block enumeration direction.
Used in:
Enumerate in ascending order (from child to parent).
Enumerate in descending order (from parent to canonical child).
A key value state.
Used in:
Root of for this level, empty length bytes if top level.
A collection of keys-values.
Set to true when there are no more keys to return.
A key-value pair.
Used in:
Request storage data from a peer.
Block header hash.
Start from this key. Multiple keys used for nested state start.
optional
if 'true' indicates that response should contain raw key-values, rather than proof.
A collection of keys-values states. Only populated if `no_proof` is `true`
If `no_proof` is false in request, this contains proof nodes.