Keeper as Performer

In the TriggerX ecosystem, Performer Keepers are the action-takers, the participants who actually execute tasks on-chain when a job is triggered. Think of them as the “workers” of the automation network: they listen, fetch, execute, and prove.

While Task Manager orchestrates jobs and Validators confirm correctness, the Performer Keeper is the one that actually makes things happen on the blockchain.

Responsibilities of a Performer Keeper

A Performer Keeper has five critical responsibilities:

1. Task Monitoring: Continuously listens to the Task Manager for new automation jobs.

2. Fetching Arguments: If a job requires dynamic inputs (e.g., a real-time price), the keeper fetches these arguments from on-chain contracts or off-chain APIs.

3. Transaction Execution: Once arguments are ready, the keeper calls the target smart contract function with the correct parameters.

4. Gas Management: Ensures the job is executed with an optimal gas strategy, balancing reliability and cost-efficiency.

5. Result Submission: After execution, the keeper submits a proof-of-execution (such as the transaction hash) to the Aggregator node, establishing a verifiable record of the completed task.

By fulfilling these roles, Performer Keepers deliver the execution power that makes decentralized, trustless automation possible.

Workflow of a Performer Keeper

Here’s a step-by-step look at the lifecycle of a job executed by a Performer Keeper:

1. Detects a Job: Listens for a valid, ready-to-execute task from the Task Manager.

2. Decodes the Function Call: Parses the job and identifies required smart contract interactions.

3. Fetches Parameters (if needed):

   • Static tasks → Parameters are predefined.

   • Dynamic tasks → Retrieves additional data (e.g., price feeds or oracle values) from APIs or contracts.

4. Executes Transaction: Calls the designated smart contract with the provided or fetched arguments.

5. Submits Proof: Provides the Aggregator with transaction details, including the hash, to confirm that the job was successfully executed.

Think of this as a closed feedback loop: listen → prepare → execute → prove.

Example Scenario

Let’s imagine a Performer Keeper in action:

• A DeFi protocol submits a job: “Swap USDC to ETH if ETH’s price falls below $1,500.”

• The Performer Keeper tracks the USDC-ETH pair price.

• Once the condition is satisfied, it automatically executes the swap on a decentralized exchange (DEX).

• After confirming the trade, it submits the transaction hash + execution proof to the TriggerX network for validation and transparency.

The result? A completely automated trading execution, no central servers, no manual interventions, just reliable decentralized actions.

Why Performer Keepers Matter

For developers building decentralized applications, Performer Keepers represent:

• Automation Without Trust: Jobs execute without relying on single points of failure or centralized cron-like services.

• Efficient On-Chain Operations: With automated monitoring and optimized gas strategies, dApps become faster and cheaper to operate.

• Transparency & Verifiability: Every execution is provable, logged, and verifiable by peers.

This forms the foundation for everything from DeFi liquidations to automated DAO proposals, NFT royalty payouts, and multi-chain workflows.

As the network evolves, Performer Keepers will not only execute isolated tasks but also participate in multi-step automation pipelines, cross-chain job execution, and AI-driven condition evaluation.

They’re not just executors, they’re pioneers helping build a decentralized future where applications don’t just run, they self-operate, in real time, with trustless precision.