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. Core Concepts

Keepers

In the TriggerX architecture, keepers play a crucial role as performers and attesters, responsible for executing and validating automation tasks in a decentralized manner. These keepers ensure that smart contract functions are triggered based on predefined conditions, such as time-based, event-based, or condition-based automation.

Role of Keepers in TriggerX

Keepers function as both performers and attesters in the network. Their primary responsibilities include:

1. Task Execution (Performer Role)

  • When a task is assigned to a keeper, it executes the smart contract function as specified in the job definition.

  • The task execution may require fetching real-time data from on-chain or off-chain sources (e.g., price feeds from an API or data from IPFS).

  • Once the execution is completed, the keeper generates a Proof of Task (PoT), a cryptographic proof confirming the successful execution of the assigned job.

2. Attestation (Attester Role)

  • Since TriggerX operates as an AVS (Actively Validated Service), all participating keepers act as attesters.

  • Multiple keepers validate the correctness of executed tasks by checking the Proof of Task (PoT) submitted by other keepers.

  • The attestation process involves a quorum-based approach where a threshold number of attestations is required before finalizing the execution result.

PreviousTask ManagerNextKeeper as Performer

Last updated 1 month ago