Getting Started as Keepers
At the heart of TriggerX lies its Keeper Network, a decentralized layer of operators that enables automated jobs. Keepers are the guardians of automation, responsible for executing, validating, and securing tasks within the TriggerX ecosystem.
Becoming a Keeper means contributing to the trustless infrastructure that ensures smart contracts run reliably and securely across multiple chains. You’re not just running code, you’re powering the decentralized backbone of Web3 automation.
Universal Keeper Responsibilities
All Keepers (whether Performer or Attester) take part in the job lifecycle:
Listen: Monitor for new jobs from the Task Manager.
Perform: Execute transactions or validate those executed by peers.
Prove: Submit execution results or attestations back to the network.
Secure: Ensure correctness, detect fraud, and maintain reliability for the wider ecosystem.
Prerequisites (Common Across EigenLayer & Imua)
Before diving into a specific setup, all Keepers should ensure:
Technical Environment:
Linux server (Ubuntu, Amazon Linux, etc.)
Docker + Docker Compose installed
Node.js (v22.6.0 for Othentic CLI)
Hardware Requirements:
1 vCPU
1 GB RAM
10 GB storage minimum
Network Config:
Public IPv4 address available
Relevant ports open for P2P, RPC, and metrics
Wallet Keys:
Operator key pair (safe storage required)
RPC Access:
Reliable Ethereum (Holesky, Sepolia, or Imua Testnet) RPC endpoints — Infura or Alchemy recommended
Once you’re ready, the next step is registering as a Keeper through either:
EigenLayer — leveraging Eigen’s restaking AVS model.
ImuaChain — leveraging Imua’s Cosmos/Ethereum hybrid re/staking model.
Where to Start?
If you are running within the EigenLayer ecosystem, go to: ➡ Getting Started as Keeper on EigenLayer
If you are preparing to validate through the ImuaChain ecosystem, go to: ➡ Getting Started as Keeper on ImuaChain
Each flow has its own registration process, tooling, and staking model.
Last updated