Do not use it in Production, testnet only.
Review the guide here: Operator Guide
cd contracts
cp sample.env .env
Edit the .env file with your variables
make build-contracts
make deploy-anzen-contracts-to-holesky-and-save-state
This will deploy the contracts to the holesky chain and save the state to contracts/script/output/17000/anzen_avs_deployment_output.json
Follow the Eigenlayer guide to create keys here, for holesky deployment it is okay to use the --insecure
flag in the key creation command. You will need both an edcsa
and bls
key.
You only need to set up the operator.yaml file for the operator. If you want to set up an aggregator you will need to set up the aggregator.yaml file as well, but this is not required to join the AVS.
cd config-files/holesky
cp sample.operator.yaml operator.yaml
Optional:
cp sample.aggregator.yaml aggregator.yaml
Edit the aggregator.yaml and operator.yaml files with your variables:
in a separate terminal
docker compose -f operator.docker-compose.yml up
Configure the aggregator environment variables with the aggregator private key
cp sample.aggregator.env .env
docker compose -f aggregator.docker-compose.yml up
make start-operator-holesky
Optional:
make start-aggregator-holesky
First, you should check for any updates to the operator image
docker pull ghcr.io/hydrogen-labs/anzen-avs/aggregator/cmd/main.go:latest
docker pull ghcr.io/hydrogen-labs/anzen-avs/operator/cmd/main.go:latest
Ensure that your RPC client let's you create websocket subscriptions. Recommended RPC providers are:
The free tier of Tenderly is sufficient for testing.
- Ensure that you have sufficient eth in your operator account to pay for gas costs.
- Ensure that you have wETH in your operator account to pay for joining the AVS (this is for the default strategy of the AVS)