Module transaction_meta

Transaction Meta contains data that follows a transaction through the execution pipeline in runtime. Examples of metadata could be limits specified by compute-budget instructions, simple-vote flag, transaction costs, durable nonce account etc;

The premise is if anything qualifies as metadata, then it must be valid and available as long as the transaction itself is valid and available. Hence they are not Option type. Their visibility at different states are defined in traits.

The StaticMeta and DynamicMeta traits are accessor traits on the RuntimeTransaction types, not the TransactionMeta itself.

Structs

• TransactionMeta

Traits

• DynamicMeta
  Statically loaded meta is a supertrait of Dynamically loaded meta, when transaction transited successfully into dynamically loaded, it should have both meta data populated and available. Dynamic metadata available after accounts addresses are loaded from on-chain ALT, examples are: transaction usage costs, nonce account.
• StaticMeta
  metadata can be extracted statically from sanitized transaction, for example: message hash, simple-vote-tx flag, limits set by instructions