Constants
Constants can be pushed onto the Stack in two different ways:
-
Constants can be pushed directly with
pushintorpushbytesopcodes. This method is more efficient for constants that are only used once. -
Constants can be loaded into storage separate from the Stack and Scratch Space, with
intcblockorbytecblockopcodes. Then, constants from this storage can be pushed onto the Stack by referring to the type and index usingintc,intc_[0123],bytec, andbytec_[0123]. This method is more efficient for constants that are used multiple times.
The opcodes intcblock and bytecblock use proto-buf style variable length unsigned int,
reproduced in the varuint section.
The intcblock opcode is followed by a varuint specifying the number of integer
constants, and then that number of varuint.
The bytecblock opcode is followed by a varuint specifying the number of byte
constants, and then that number of pairs of (varuint, bytes) length prefixed byte
strings.
Assembly
The Assembler will hide most of this, for example, allowing
simple use of int 1234 and byte 0xcafed00d. Constants introduced via int and
byte will be assembled into appropriate uses of pushint|pushbytes and {int|byte}c, {int|byte}c_[0123] to minimize program bytecode size.
Named Integer Constants
On Complete Action Enum Constants
An application call transaction MUST indicate the action to be taken following the execution of its Approval Program or Clear State Program.
The constants below describe the available actions.
| ACTION | VALUE | DESCRIPTION |
|---|---|---|
NoOpOC | 0 | Only execute the Approval Program associated with the application ID, with no additional effects. |
OptInOC | 1 | Before executing the Approval Program, allocate local state for the application ID into the sender’s account data. |
CloseOutOC | 2 | After executing the Approval Program, clear any local state for the application ID out of the sender’s account data. |
ClearStateOC | 3 | Do not execute the Approval Program, and instead execute the Clear State Program (which may not reject this transaction). Additionally, clear any local state for the application ID out of the sender’s account data (as in CloseOutOC). |
UpdateApplicationOC | 4 | After executing the Approval Program, replace the Approval Program and Clear State Program associated with the application ID with the programs specified in this transaction. |
DeleteApplicationOC | 5 | After executing the Approval Program, delete the parameters of with the application ID from the account data of the application’s creator. |
Transaction Type Enum Constants
| TYPE | VALUE | DESCRIPTION |
|---|---|---|
unknown | 0 | Unknown type, invalid transaction |
pay | 1 | ALGO transfers (payment) |
keyreg | 2 | Consensus keys registration |
acfg | 3 | Asset creation and configuration |
axfer | 4 | Asset transfer |
afrz | 5 | Asset freeze and unfreeze |
appl | 6 | Application calls |
stpf | 7 | State Proof |
hb | 8 | Consensus heartbeat |