Aggregator

In the TriggerX network, the Aggregator node (powered by the Othentic Stack) acts as the final checkpoint of trust. While Performers execute jobs and Attesters verify proofs, the Aggregator coordinates consensus across the Keeper network and submits the finalized result on-chain.

Think of it as the gateway between decentralized off-chain automation and immutable on-chain finality. Without it, automation would lack trust and traceability.

Core Responsibilities

The Aggregator node is designed to:

• Collect Execution Proofs → Gather proofs from Performers and Attesters.

• Ensure Consensus → Verify quorum and aggregate signatures before finalizing.

• Submit Transactions On-Chain → Record outcomes immutably and reliably.

• Optimize Performance → Provide configuration options for speed, persistence, and reliability.

It’s not just about validating, it’s about anchoring automation to the blockchain with confidence.

1. Internal Tasks Execution

• By enabling the --internal-tasks flag, the Aggregator node can execute internal tasks locally, reducing dependency on external keepers.

• This feature is useful for operations that do not require external validation, ensuring faster execution of internal automation tasks.

othentic-cli node aggregator --internal-tasks true

2. Performance Metrics

• The --metrics flag allows users to enable real-time performance monitoring of the Aggregator node.

• Metrics track various parameters such as task execution time, quorum formation success rate, and network latency to provide insights into system efficiency.

othentic-cli node aggregator --metrics true

3. Persistent Storage for Peer-to-Peer (P2P) Data

• The --p2p.datadir flag ensures that peerStore data is saved persistently to maintain peer connections across node restarts.

• This prevents loss of peer information and enhances network stability.

othentic-cli node aggregator --p2p.datadir ./data/peers

4. Custom P2P Messaging

• Allows users to customize peer-to-peer messaging behavior through various configuration options.

• It supports custom message topics, such as othentic.p2p.custom_messagedefining specialized P2P interactions.

• The sendCustomMessage RPC method enables direct messaging between peers.

othentic-cli node aggregator --p2p.custom_message "task_update"

5. Transaction Simulation

• The --aggregator.simulate-transactions flag simulates transactions before submission, helping prevent failed transactions due to gas estimation issues or incorrect execution logic.

• This ensures that only valid and successful transactions are submitted on-chain.

othentic-cli node aggregator --aggregator.simulate-transactions true

6. Delayed Submission for More Attestations

• The --delay <time> flag allows the Aggregator to wait for additional attestations before submitting an on-chain transaction.

• This helps achieve higher consensus accuracy by collecting more votes from keepers.

• Delay time is specified in milliseconds.

othentic-cli node aggregator --delay 5000  # Waits 5 seconds before submitting