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

Keeper as Attester

An Attester Keeper acts as a validator, ensuring that tasks are executed correctly by verifying the execution proofs submitted by Performers. Instead of performing transactions, attesters observe, verify, and sign execution proofs to confirm the legitimacy of an action.

Responsibilities of an Attester Keeper:

  • Observing Transactions: Listens to task execution events submitted by Performers.

  • Validation of Execution: Checks whether the submitted transaction was executed correctly and meets all required conditions.

  • Signature Generation: If valid, the keeper generates an attestation signature to confirm that the execution is legitimate.

  • Proof Submission: The signed attestation is sent to the Aggregator node for final verification and submission.

  • Fraud Detection: If a Performer submits incorrect or malicious execution data, Attesters can reject the attestation.

Workflow of an Attester Keeper:

  1. Monitors the blockchain for task execution submissions from Performers.

  2. Fetches the transaction data and validates it against the expected task details.

  3. If valid, generate a digital signature confirming the correctness of execution.

  4. Sends the signed attestation to the Aggregator for further processing.

Example Scenario:

  • A Performer executes a limit order for a user on a decentralized exchange.

  • The Attester Keeper checks whether the swap was performed at the correct price and in the right amount.

  • If the execution is valid, the attester signs the proof and submits it.

  • If invalid, the attester rejects the proof, ensuring that only correctly executed transactions are accepted.

PreviousKeeper as PerformerNextAggregator

Last updated 1 month ago