Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

• Auto
• Light
• Dark

Algorand Specifications

Each transaction is associated with some information about how it is applied to the Account State. This information is called ApplyDataApplyData, and contains the fields based on the transaction type (type).

• The closing amount, ClosingAmountClosingAmount, encoded as msgpack field ca, specifies how many μALGO were transferred to the close-to address (close).

• The asset closing amount AssetClosingAmountAssetClosingAmount, encoded as msgpack field aca, specifies how many of the asset units were transferred to the asset close-to address (aclose).

• The eval delta, encoded as msgpack field dt, is associated with the successful execution of the corresponding application’s Approval Program or Clear State Program. It contains the following fields:

  • A global delta, encoded as msgpack field gd, encoding the changes to the global state of the called application. This field is a State Delta;

• Zero or more local deltas, encoded as msgpack field ld, encoding changes to some local states associated with the called application. The local delta ld maps an “account offset” to a State Delta. Account offset 00 is the transaction’s sender. Account offsets 11 and greater refer to the account specified at that offset minus one in the transaction’s foreign accounts (apat). An account would have a ld entry as long as there is at least a single change in that set.

• Zero or more logs, encoded as msgpack array lg, recording the arguments to each call of the log opcode in the called application. The order of the entries follows the execution order of the log opcode invocations. The total number of log calls MUST NOT exceed 3232, and the total size of all logged bytes is MUST NOT exceed 10241024. No logs are included if a Clear State Program fails.

• Zero or more inner transactions, encoded as msgpack array itx. Each element of itx records a successful inner transaction. Each element will contain the transaction fields, encoded under the msgpack field txn, in the same way that the regular (top-level) transaction is encoded, recursively, including ApplyDataApplyData that applies to the inner transaction.

  • The recursive depth of inner transactions is MUST NOT exceed 88;
  • In Program Version 5, the inner transactions MUST NOT exceed 1616. From Program Version 6, the count of all inner transactions across the transaction group MUST NOT exceed 256256.
  • Before Program Version 6, the inner transaction types (type) are limited to pay, axfer, acfg, and afrz. From Program Version 6, keyreg and appl are allowed.
  • A Clear State Program execution MUST NOT have any inner transaction.

The following ApplyDataApplyData item refers to the legacy Distribution Reward system.

• The amount of rewards distributed to each of the accounts touched by this transaction, encoded as three msgpack fields rs, rr, and rc, representing amount of reward distributed respectively to:
  • The sender address,
  • The receiver address,
  • The cose-to addresses.

The fields have integer values representing μALGO.

If any of the addresses are the same (e.g., the sender and receiver are the same), then that account received the sum of the respective reward distributions (i.e., rs plus rr).

Important

IMPLEMENTATION:

In the reference implementation, one of these two fields will be zero in that case.

TODO (Similarities and differences with respect to regular transactions)

A state delta represents an update to a Key/Value Store (KV). It is constructed as an associative array mapping a byte-array key to a single value delta. It represents a series of actions that, when applied to the previous state of the Key/Value store, will yield the new state. These state deltas are included in the Application Call ApplyDataApplyData structure under the field eval delta (dt).

A value delta is composed of three fields:

• An action, encoded as msgpack field at, which specifies how the value for this key has changed. It has three possible values:

  • SetUintAction (value = 1), indicating that the value for this key should be set to the value delta’s Uint field.
  • SetBytesAction (value = 2), indicating that the value for this key should be set to the value delta’s Bytes field.
  • DeleteAction (value = 3), indicating that the value for this key should be deleted.

• Bytes, encoded as msgpack field bs, which specifies a byte slice value to set.

• Uint, encoded as msgpack field ui, which specifies a 64-bit unsigned integer value to set.