The Task is executed off-chain, with the result of the computation being attested by multiple operators' signatures. These signatures are subsequently aggregated before the final validation and on-chain value writing occurs.
Imua-AVS-Task Lifecycle (Flow)
Each task request follows a specific process. To illustrate this, let's examine the example of summing two numbers.
The Task Generator entity transmits the two numbers to be summed to the AVS contract.
The AVS contract emits a NewTaskCreated event, representing the two numbers to be summed.
Operators listen to the AVS contract for this event, perform the summation, sign the result using a , and transmit their signature to the Aggregator entity.
The Aggregator consolidates these signatures into a single aggregated signature using . Once the required threshold is met, the Aggregator submits the aggregated signature back to the AVS contract.
The AVS contract verifies that the thresholds have been met and that the aggregated signature is valid. Upon successful verification, the execution result is accepted.
Task Creation
The following parameters are utilized to create tasks and can use them to register essential information on Imuachain:
/// @dev CreateTask , avs owner create a new task
/// @param sender The external address for calling this method.
/// @param name The name of the task.
/// @param hash The data supplied by the contract, usually ABI-encoded.
/// @param taskResponsePeriod The deadline for task response.
/// @param taskChallengePeriod The challenge period for the task.
/// @param thresholdPercentage The signature threshold percentage.
/// @param taskStatisticalPeriod The statistical period for the task.
function createTask(
address sender,
string memory name,
bytes calldata hash,
uint64 taskResponsePeriod,
uint64 taskChallengePeriod,
uint64 thresholdPercentage,
uint64 taskStatisticalPeriod
) external returns (bool success);
An illustrative example demonstrating task submission utilizing the aforementioned parameters is as follows:
