TriggerX Docs
  • Introduction
    • What is TriggerX?
    • Key Features
  • Core Concepts
    • Architecture
    • Triggers in TriggerX
      • Time-Based Trigger
      • Event-Based Trigger
      • Condition-Based Trigger
    • Task Manager
    • Keepers
      • Keeper as Performer
      • Keeper as Attester
    • Aggregator
    • Network Monitoring
    • Contracts
      • AVS Governance
      • Attestation Center
  • Getting Started as Keepers
  • Monitoring And Analytics
    • Monitor Your Keeper
    • Monitor Your Job
  • Rewards
    • Keeper Rewards
    • Developer Rewards
    • Contributor Rewards
  • Fee Calculation
  • Guide
    • Templates
    • Usecases
  • Security Model
  • Community and Support
  • Appendices
    • Glossary
    • FAQ and Troubleshooting
    • Changelogs
  • References
  • Create Your First Job
    • Create Your First Time Based Job
    • Create Your First Event Based Job
Powered by GitBook
On this page
  • 1. Internal Tasks Execution
  • 2. Performance Metrics
  • 3. Persistent Storage for Peer-to-Peer (P2P) Data
  • 4. Custom P2P Messaging
  • 5. Transaction Simulation
  • 6. Delayed Submission for More Attestations
  1. Core Concepts

Aggregator

The Aggregator node in the TriggerX network is a critical component responsible for collecting task execution proofs, ensuring consensus, and submitting finalized results on-chain. It provides various configuration options to enhance performance, persistence, and reliability. Below are the key features of the Aggregator node:

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
PreviousKeeper as AttesterNextNetwork Monitoring

Last updated 1 month ago