Decentralized Oracle Aggregation Trigger

WHAT IT DOES

The Decentralized Oracle Aggregation Trigger enables users to trigger the aggregation of reports from multiple oracle nodes into a single consolidated value. It reads oracle aggregation contract state, user address, wallet balance, and oracle node states including registered nodes, stakes, and latest reports. The tool processes aggregation parameters such as threshold and deviation, report data including price, timestamp, and source, and aggregation status. It supports triggerAggregation for standard triggers, batchTriggerAggregation for multiple aggregations in one transaction, and triggerWithProof for proof-attached triggers. The tool reads gas price, base fee, block timestamp, chain ID, transaction nonce, approval state, and contract owner state before execution.

HOW TO USE

Connect your wallet and select the target network. Enter the oracle aggregation contract address and the aggregation ID or round number. Set the threshold (number of reports required for aggregation) and deviation tolerance in basis points. Optionally provide proof data for triggerWithProof. Choose the execution method (triggerAggregation, batchTriggerAggregation, or triggerWithProof). The tool will fetch the aggregation state, display the current report count, aggregation status, and latest aggregated price. Once confirmed, it submits the trigger transaction. The tool validates the threshold and deviation before signing.

TECHNICAL MECHANISM

Unlike generic trigger tools, this executor is purpose-built for decentralized oracle aggregation workflows. It first reads the aggregation contract's isActive() to ensure the contract is operational. The tool fetches the aggregation status via getAggregationStatus() to check if the aggregation has already been triggered or finalized. It reads the report count via getReportCount() to show how many reports have been submitted. It retrieves the latest price via getLatestPrice() to display the current aggregated value. The tool selects the optimal method: triggerAggregation for standard triggers, batchTriggerAggregation for multiple aggregations in one transaction, or triggerWithProof for triggers with proof data. The threshold determines how many reports are needed before aggregation can proceed, while deviation controls the maximum allowed variance. Gas costs are calculated using receipt.effectiveGasPrice for accurate post-EIP-1559 fee accounting.

WHAT IT CANNOT SEE

This tool cannot verify that the aggregation result is correct or that the oracle nodes have reported honestly. It cannot detect if the aggregation has already been triggered or if the threshold has been met. It also cannot guarantee that the aggregation will complete successfully or that the result will be accepted. The tool cannot verify the authenticity of the proof data or detect if the aggregation has been manipulated. It also cannot detect if the contract has been paused or upgraded.

PLEASE NOTE

This tool supports EVM-compatible chains. Triggering aggregation is a critical operation—verify the threshold and deviation before signing. The aggregation contract must implement the trigger functions expected by this tool. The threshold must be less than or equal to the number of registered oracle nodes. Batch triggering requires arrays of aggregation IDs, thresholds, and deviations. This tool does not submit oracle reports—for that, use the Oracle Report Submission Tool.