How to Setup an AVS Operator
The setup for AVS Operators has been updated since the release of this article. For the most up to date information please use the Chainbase operator docs as an authoritative source! https://docs.chainbase.com/node/operator
AVS Registry Contract: 0x5e78eff26480a75e06ccdabe88eb522d4d8e1c9d
🚀Introduction
Not another AVS! But, yes, indeed there will be another - because Chainbase will be using Eigenlayer for its execution layer. AVS Operators play a crucial role in Chainbase’s 4-Layer, Dual-Staking, Dual-Chain, data network. Operators process data and receive rewards, directly incentivized by network tokenomics.
The purpose of this guide is to assist a would-be Operator understand and execute the requirements to provide computational resources for the execution layer of Chainbase. Being an operator for Chainbase is a unique and honorable activity - as you’ll be actively contributing to the infrastructure of the network.
The great news is that becoming an Operator is a standardized, universal and simple process. Per Eigenlayer documentation, “Any Ethereum address can serve as an Operator […] An Operator can participate in the EigenLayer network without having any restaked tokens.” Moreover, an Operator can choose can interact with multiple AVSs using the same base setup, so there is minimal opportunity cost to setting one up for Chainbase.
Journey along and see the fastest way to do so!
❓Requirements
Before dedicating your valuable resources, take some time to ensure you have the following requirements met.
Hardware
Class | vCPUs (10th gen+) | Memory | Networking Capacity |
|---|---|---|---|
General Purpose - large | 2 | 8 GB | 5 Mbps |
General Purpose - xl | 4 | 16 GB | 25 Mbps |
General Purpose - 4xl | 16 | 64 GB | 5 Gbps |
Software
Docker: Docker is a requirement for AVS operators.
Docker Compose: Docker Compose is used alongside Docker for executing Operator software.
Linux Environment: Eigenlayer’s CLI only runs in a Linux environment.
Go: Two out of three installation routes require the use of Go. It’s safer to go with Go than go without. 😉
🛠Set Up
1. Install your Operator 📥
The installation of an AVS operator requires several steps, as is covered in depth in EIgenlayer’s comprehensive docs. There are three routes outlined for installation:
2. Create or Import your Keys 🔑
As stated, a working address is required. Once you have the CLI installed, you can import existing ECDSA or BLS keys using the eigenlayer operator keys import command. Otherwise, you will need to create a new key using the eigenlayer operator keys create command.
3. Fund your wallet 👜
Best practice suggests that you’ll need at least 1 ETH to cover the gas cost of the operator registration. Make sure to send at least 1 ETH to your operator’s address. Unsure of the address? You can check the operator.yaml .
4. Configure your Operator 🔧
A funded operator still needs to be configured! Use eigenlayer operator config create . There are several steps here and we recommend that you follow Eigenlayer’s official docs on how to do so.
For a full wrap-around experience, we also recommend you use Chainbase’s RPC for any RPC configuration necessary :)
5. Check that your Operator is Functional 🔍
Once you have installed eigenlayer, run the following to verify that your operator is correctly operating and correctly registered with Eigenlayer:
eigenlayer operator status operator.yaml
6. Install Chainbase-AVS-CLI ⛓
After that, download the latest chainbase-avs-cli release from here and install it on your local machine.
7. Register your operator ↗️
git clone <https://github.com/chainbase-labs/chainbase-avs-contracts.git>rename
avs.toml.exampletoavs.tomland replace filed:operator_config_path,keystore_pwd
chainbase-avs-contracts/avs.toml.example at main · chainbase-labs/chainbase-avs-contracts
Contribute to chainbase-labs/chainbase-avs-contracts development by creating an account on GitHub.
Run the following command to register as a Chainbase operator:
chainbase-avs-cli register --config ~/path/to/avs.toml
8. Run your AVS ↗️
Edit operator.yaml’s private_key_store_path point to /opt/operator.yaml.
Run the following command
export OPERATOR_CONFIG_PATH=/path/to/operator.yaml EIGEN_KEY_PATH=/path/to/ecdsa.key.json docker-compose up -d
That’s it ! Your operator should be fully functional 🚀🚀🚀
🤝🏿Get Involved
Chainbase is building a burgeoning community of developers and crypto enthusiasts passionate about AI and data access. Besides becoming an Operator, there are many opportunities for interested technologists to get involved. Come check out our Discord and get to know more of our team and community. We’d love to see where you fit!
