Glossary

TERM	DEFINITION
Automation Task	A transaction registered by a user to be executed automatically when specific conditions are met.
Automation Registry	The on-chain storage module that tracks all registered tasks, their metadata, and current state.
Cycle	A fixed period used for automation bookkeeping. At each cycle boundary the registry activates pending tasks, removes expired and cancelled tasks, and charges the automation fee. Governance sets the cycle duration; `get_cycle_info` returns the current one.
Automated Execution	The process by which validators determine whether and when an automation task should trigger execution based on predefined conditions or scheduled criteria. This occurs at the end of each block.
Gas Price Cap	The highest unit gas price a user is willing to pay for each execution of the automation task.
Task Max Gas	The maximum amount of gas that can be consumed by the task during execution. If this limit is exceeded, the transaction fails with execution failure.
Automation Fee Cap	The maximum automation fee a user is willing to pay per cycle, in quants. The same amount is locked as a deposit at registration. If the fee for a cycle exceeds it, the task is removed.
Pending Task	A task that is registered but not yet active. Tasks are pending until the next cycle begins.
Active Task	A task that is currently eligible for evaluation and execution in each block.
Task ID	A unique identifier assigned to every automation task upon registration. It is used to track, manage, and reference tasks across the registry, API calls, and validator execution.
Cancelled Task	A task that has been cancelled manually by the user or removed automatically due to fee or balance constraints. A manually cancelled active task stays in the registry until the current cycle ends and is removed at the next cycle boundary. Fee and balance-based removals happen at the cycle boundary when the fee for the new cycle is charged.
Zero-Block Delay	Execution model in which a task is evaluated and executed within the same block when its condition becomes true.
Congestion Fee	An additional fee applied when the gas committed by registered tasks exceeds the congestion threshold of the registry. It grows with the congestion exponent set by governance.
Automated Transaction Payload	The encoded data submitted via Supra CLI, REST, or SDK during task registration. It contains the target function call and the call’s arguments. The logic for execution, such as conditional checks is defined inside the target function itself, rather than as a separate component.
Payload Transaction	The packaged Move function call that runs when an automated task is triggered. It includes the function identifier and arguments submitted during task registration, and is executed by the validator if the task conditions are met.
Quant	The smallest unit of SUPRA. 1 SUPRA = 100,000,000 quants. Automation fees and caps are in quants.
Deposit	An amount equal to the automation fee cap, locked when a task is registered. It is refunded in full when an active task expires, is cancelled or stopped, or is removed because its fee for a cycle exceeds the fee cap, and for every task when governance suspends automation. Half of it is refunded when a pending task is cancelled or stopped. It is not refunded when the task is removed for an insufficient balance.