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
  • Responsibilities of a Performer Keeper:
  • Workflow of a Performer Keeper:
  • Example Scenario:
  1. Core Concepts
  2. Keepers

Keeper as Performer

A Performer Keeper is responsible for executing tasks on the blockchain when predefined conditions are met. These keepers actively listen for job triggers, fetch dynamic arguments if required, execute transactions, and submit the results.

Responsibilities of a Performer Keeper:

  • Task Monitoring: Continuously listens for new tasks.

  • Fetching Arguments: If the task requires dynamic arguments, the keeper retrieves real-time data from external APIs or smart contracts.

  • Transaction Execution: Calls the target smart contract function with the required parameters.

  • Gas Management: Ensures the transaction is executed with the optimal gas fee to avoid failures or excessive costs.

  • Result Submission: After executing the task, the keeper submits the execution proof to the Aggregator node.

Workflow of a Performer Keeper:

  1. Detects an available task from the TaskManager.

  2. Decodes the function call and fetches required parameters.

  3. If the task requires external data, it queries the API and processes the response.

  4. Executes the function call on-chain using the retrieved or static arguments.

  5. Submits proof of execution, including transaction details.

Example Scenario:

  • A DeFi protocol submits a job that requires swapping USDC to ETH when the price reaches a specific threshold.

  • The Performer Keeper monitors the USDC price, and once the condition is met, it executes the trade on a DEX.

  • The keeper then submits the transaction hash and execution details as proof.

PreviousKeepersNextKeeper as Attester

Last updated 1 month ago