A message that doesn't have any deploys, targets one block (no secondary parents), and cannot be used as a parent (is a leaf in the DAG).

Regular block (with deploys, multiple parents etc).

Message in response to leader messages, with no other justification except the validator's own last message; a.k.a.

Message from the round leader; a.k.a.

Message created during the round to form summits, a.k.a.

A signature together with the corresponding public key that can be used to validate it for situations where the key is not part of the data being signed, which is usually the case where multiple signatures are required.

Full block information.

Limited block information for gossiping.

A smart contract invocation, singed by the account that sent it.

Code (either session or payment) to be deployed to the platform.

Old definition of Arg, still kept around to support old JSON format.

Limited deploy information for gossiping.

To allow nodes in the beginning to verify that they are joining the right network, while there is no DAG to look at, they disseminate approvals for the Genesis candidate until it gathers enough support for individual nodes to pass their thresholds and transition to processing blocks and deploys.

Signature over for example a deploy or a block.

Highway specific role of a message.