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
  • Missed a Step?
  • triggerx-keeper Errors:
  • Health Service returned a non-OK status
  • triggerx-othentic Errors:
  • OperatorNotRegistered on chain 84532
  • Operator inactive, ignoring ...
  • Error while running attester: RangeError: cannot slice beyond data bounds
  • Grafana Errors:
  • Share Your Logs With Us
  • Change of Keeper (Operator Address)
  1. Appendices

FAQ and Troubleshooting

PreviousGlossaryNextChangelogs

Last updated 1 month ago

Missed a Step?

The ideal order for joining us as a Keeper would be:

  1. Fill the whitelist form,

  2. Register to EigenLayer, wait for the transaction to be mined,

  3. Deposit into strategy (get LST if not available for this step), wait for the transaction to be mined,

  4. Register to TriggerX, wait 10-15 mins for data to be updated on L2,

  5. Run your keeper after setting up the environment.

Missed any of these steps? Don't worry, and complete that step. No need to redo all the steps from the start again. Wait for some time, and restart the Keeper Docker.

Below are some common issues our Keepers run into, and steps to troubleshoot them.

triggerx-keeper Errors:

Health Service returned a non-OK status

  • You have neither filed the form nor registered to TriggerX using Othentic CLI. Hence, our health check-in service does not identify your Keeper.

  • Complete the previous steps to resolve this.

triggerx-othentic Errors:

OperatorNotRegistered on chain 84532

  • Either you have not registered on TriggerX AVS using Othentic CLI, or if done,

  • Your register operator action on Ethereum Holesky was done, however, data has not been updated on Base Sepolia. Please wait 15-30 minutes before restarting.

Operator inactive, ignoring ...

  • Your Voting Power is 0, you need to deposit some LSTs into our supported strategies and try restarting after some time.

Error while running attester: RangeError: cannot slice beyond data bounds

  • This is an RPC error. Please use Alchemy, Infura, or a node URL rather than public URLs. Public URLs fail often and are not capable of this task.

Grafana Errors:

  • To be listed soon ...

Share Your Logs With Us

In case our devs ask to share your logs, you can with these commands:

  • triggerx-keeper:

Adding soon ...

  • triggerx-othentic:

Adding soon ...

Change of Keeper (Operator Address)

Use this command to unregister your current keeper. Once you have done so, you can withdraw the LST tokens deposited in our strategies. The steps are . Start with step 1, using the new wallet address.

here