Skip to content

Latest commit

 

History

History
71 lines (48 loc) · 2.54 KB

operator.md

File metadata and controls

71 lines (48 loc) · 2.54 KB
Raw

Run Operators

To run the AVS operator, there are 2 steps

  1. Register to become an EigenLayer operator by following EigenLayer Operator Guide
  2. Once become an operator, you can register for Ava Protocol AVS by following the below step

Run Ava Protocol AVS on Holesky testnet

Download the latest release from https://github.com/AvaProtocol/EigenLayer-AVS/releases for your platform. You can compile for yourself by simply running go build at the root level.

First, Generate Ava Protocol AVS config file. You can put it anywhere. Example config/operator.yaml with below content

# this sets the logger level (true = info, false = debug)
production: true

operator_address: <operator_address>

avs_registry_coordinator_address: 0x90c6d6f2A78d5Ce22AB8631Ddb142C03AC87De7a
operator_state_retriever_address: 0xb7bb920538e038DFFEfcB55caBf713652ED2031F

eth_rpc_url: https://holesky.drpc.org
eth_ws_url: wss://holesky.drpc.org/

ecdsa_private_key_store_path: <path_to_operator_ecdsa_key_json>
bls_private_key_store_path: <path_to_operator_bls_key_json>

aggregator_server_ip_port_address: "aggregator-holesky.avaprotocol.org:2206"

# avs node spec compliance https://eigen.nethermind.io/docs/spec/intro
eigen_metrics_ip_port_address: <operator_public_ip>:9090
enable_metrics: true
node_api_ip_port_address: <operator_public_ip>:9010
enable_node_api: true

Configure 2 env var for your ECDSA and BLS password. Recall that these are generated when you onboard your operator to EigenLayer. In case your password contains special characters to the command-line, here we export both variables by disabling history expansion temporarily.

set +H
export OPERATOR_BLS_KEY_PASSWORD="<operator_bls_password>"
export OPERATOR_ECDSA_KEY_PASSWORD="<operator_ecdsa_password>"
set -H

Now, we can start the registration process by running our ap-avs AVS release binary.

ap-avs register --config=./config/operator.yaml

At the end of process, you should see something like this:

successfully registered operator with AVS registry coordinator

Registered operator with avs registry coordinator

The status can also be checked with ap-avs status --config=./config/operator.yaml

At this point, you're ready to run our operator node by simply do

ap-avs operator --config=./config/operator.yaml

Running operator with docker compose

To help simplify the process and enable auto update you can use our official operator setup repository