Getting Started as Keeper on ImuaChain

ImuaChain is a purpose-built Layer 1 protocol for shared security. Unlike EigenLayer’s Ethereum-native model, Imua aggregates security from multiple ecosystems via re/staking, anchors value with a USD-pegged oracle, and extends this pooled security to services like TriggerX AVS.

By joining as a Keeper in the Imua environment, you leverage Cosmos-based validator mechanics plus Ethereum compatibility, allowing you to participate in TriggerX validation through Imua’s universal security protocol.

Prerequisites

Before you begin, ensure the following are in place:

• Follow the Imua Node Setup Prerequisites

• Complete Node Install

• Install imuad

• Install TriggerX CLI (provided binary or built from source)

Step 1: Configure Environment

Create a .env file in the root of your project directory:

# Ethereum RPC Configuration
ETH_HTTP_RPC_URL=https://public-imua-testnet-rpc.fastnode.io
ETH_WS_RPC_URL=wss://api-eth-wss.exocore-restaking.com
ETHEREUM_RPC_URL=https://eth-sepolia.g.alchemy.com/v2/<YOUR_ALCHEMY_KEY>

# Contract Addresses
AVS_ADDRESS=0x72A5016ECb9EB01d7d54ae48bFFB62CA0B8e57a5
OPERATOR_ADDRESS=
AVS_OWNER_ADDRESS=

# Private Keys
OPERATOR_PRIVATE_KEY=
IMUA_PRIVATE_KEY=

# API Configuration
NODE_API_IP_PORT_ADDRESS=localhost:8080
ENABLE_NODE_API=false
PRODUCTION=false

# Imuachain Configuration
OPERATOR_NAME=<your-operator-name>
IMUA_HOME_DIR=path/to/your/.imuad
IMUA_ACCOUNT_KEY_NAME=<your-key-name>
IMUA_CHAIN_ID=imuachaintestnet_233-9
IMUA_COS_GRPC_URL=https://api-cosmos-grpc.exocore-restaking.com:443

# Optional
DEPOSIT_AMOUNT=25
TOKEN_ADDRESS=0xF79F563571f7D8122611D0219A0d5449B5304F79
IMUA_ETH_RPC_URL=https://api-eth.exocore-restaking.com

KEYRING_PASSWORD=
KEYRING_BACKEND=file

Step 2: Generate Keys

./triggerx generate-keys

• Generates ECDSA & BLS keys

• Stores them in keys/

• Updates .env with key paths

Step 3: Set up Imua Keys

./triggerx setup-imua-keys

This will:

• Ensure imuad is installed and accessible

• Initialize $IMUA_HOME_DIR if needed

• Create the key $IMUA_ACCOUNT_KEY_NAME if not already present

Step 4: Fund Imua Account

./triggerx fund-imua-account

• Automatically funds your Imua validator account with IMUA testnet tokens using the faucet

Step 5: Register Operator on Imua Chain

./triggerx register-imua-operator

This command:

• Loads values from .env

• Verifies validator key and balance

• Registers your operator on-chain

• Outputs the success confirmation

Step 6: Get Testnet imETH Tokens

./triggerx get-imeth-tokens

• Request free imETH test tokens for staking and testing

Step 7: Deposit Tokens to Gateway

./triggerx deposit-tokens

• Approves vault to spend your tokens

• Sends a deposit transaction to the Imua Gateway Contract

Step 8: Delegate Tokens to Your Operator

./triggerx delegate-tokens

• Find your Imua validator address using imuad

• Sends a delegation transaction to the gateway contract

Step 9: Export Imua Private Key (Optional)

To store the Imua validator’s private key in .env:

imuad --home $IMUA_HOME_DIR keys unsafe-export-eth-key $IMUA_ACCOUNT_KEY_NAME

Copy the output to your .env:

IMUA_PRIVATE_KEY=<exported-private-key>

Step 10: Associate Operator

./triggerx associate-operator

• Checks if your Ethereum address is linked to your Imua operator

• Creates the association if it doesn’t exist

Step 11: Opt-in to TriggerX AVS on Imua

./triggerx opt-in-to-avs

• Once you've registered your operator, deposited and delegated tokens, and associated your Ethereum address with your Imua validator, you must opt in to the AVS to officially become a validator for the TriggerX Actively Validated Service.

🧩 Useful Commands

Task	Command
Generate Keys	./triggerx generate-keys
Setup Imua Keys	./triggerx setup-imua-keys
Fund Imua Account	./triggerx fund-imua-account
Register Operator	./triggerx register-imua-operator
Get imETH	./triggerx get-imeth-tokens
Deposit Tokens	./triggerx deposit-tokens
Delegate Tokens	./triggerx delegate-tokens
Associate Operator	./triggerx associate-operator
Opt into AVS	./triggerx opt-in-to-avs