EigenLayer Operators Guide
Last updated
Last updated
This guide explains how operators can integrate with Byzantine's EigenLayer vaults. Operators are entities running infrastructure for decentralized networks within the EigenLayer ecosystem.
Operator Sets: Operator Sets are groups of operators responsible for securing an AVS (Autonomous Verifiable Service) and earning rewards. Each AVS defines one or more Operator Sets that operators can choose to join. By joining an Operator Set, operators take on the responsibility of securing the system and gain access to its rewards, as well as the risk of slashing penalties. (cf. code)
Allocation Delay: Number of blocks required for an Operator's allocation to become active in an Operator Set for a specific Strategy.
Deallocation Delay: Number of blocks between an operator's request to deallocate stake from an Operator Set for a strategy and the deallocation becoming effective.
Magnitudes: Magnitude tracks Operator's allocations within Operator Sets. It represents proportions of an Operatorβs stake delegations for a particular Strategy. The initial value of the total magnitude is 1x1018.
An Ethereum account (EOA) or smart contract (e.g multisig) that will act as the operator. If you don't have operator account yet, it will be possible to create the operator's keys on the step Create operator's keys
Understanding of the following EigenLayer contracts:
Find the complete guide here: https://docs.eigenlayer.xyz/operators/howto/operator-installation
Docker
Docker Compose
Linux Environment
Go β₯ 1.21 (if you choose to install eigenlayer-cli using the Go programming language)
To check if Docker is installed, run:
docker --version
To install a binary inside the ~/bin
directory for latest release, run:
curl -sSfL https://raw.githubusercontent.com/layr-labs/eigenlayer-cli/master/scripts/install.sh | sh -s
The binary will be installed inside the ~/bin
directory. To add the binary to your path, run:
export PATH=$PATH:~/bin
To install the eigenlayer-CLI using Go, run:
go install github.com/Layr-Labs/eigenlayer-cli/cmd/eigenlayer@latest
To check if the GOBIN is not in your PATH, you can execute echo $GOBIN
from the Terminal. If it doesn't print anything, then it is not in your PATH. To add GOBIN to your PATH, add the following lines to your $HOME/.profile
:
export GOBIN=$GOPATH/bin
export PATH=$GOBIN:$PATH
To generate the binary manually, download and compile the source code, run:
git clone https://github.com/Layr-Labs/eigenlayer-cli.git
cd eigenlayer-cli
mkdir -p build
go build -o build/eigenlayer cmd/eigenlayer/main.go
or if you have make installed, run:
git clone https://github.com/Layr-Labs/eigenlayer-cli.git
cd eigenlayer-cli
make build
The executable will be in the build
folder.
In case you want the binary in your PATH (or if you used the Go method and you don't have $GOBIN in your PATH), please copy the binary to /usr/local/bin
:
In this section, you will register your operator Ethereum address as an Eigen Layer operator. You will have to prepare beforehand some data tied to your operator:
a Delegation Approver: an address who approves new delegations from Stakers to this Operator. If this address is left as the zero (0x000...) then all new delegations to this operator will be automatically approved without the need for any signature. This parameter allows operators to have permissioned and approved delegations. Learn how to approve stakers' delegation
an Allocation Delay: The number of blocks required for an Operator's allocation to become active in an Operator Set.
a metadata URI: a URI for the operator's metadata, i.e. a link providing more details on the operator (name, website, logo, twitter, ...)
Find the complete guide here: https://docs.eigenlayer.xyz/operators/howto/operator-installation#operator-configuration-and-registration
eigenlayer operator config create
The command will create two files:
operator.yaml
metadata.json
metadata.json
Upload the logo of the operator (only .png
file within 1MB in size) to a publicly accessible location and set the url in your metadata.json
file.
The name
and description
should comply with the regex mention here. You can use services like https://regex101.com/ to validate your fields.
The metadata.json
must be less than 4KB in size. Upload the file to a publicly accessible location and set that url in operator.yaml
.
For Mainnet Operators - the metadata.json
and operator logo.png
files MUST be hosted via github.com repositories specifically. Caveat: gist.github.com hosted files are not permitted. These requirements do not apply to Testnet Operators.
An example operator.yaml file is provided for your reference here: operator.yaml.
When using Github for hosting please ensure you link to the raw file (example), rather than the github repo URL (example).
The EigenLayer CLI requires access to an Ethereum RPC node in order to post registration.
Please find example lists of RPC node providers here:
Ensure that your Operator server can reach your RPC provider at this point. You may run the following command from your Operator server: curl -I [your_server_url]
DelegationManager
Contract AddressYou must configure the correct DelegationManager
contract address for your environment.
Navigate to EigenLayer Contracts: Deployments and locate the Proxy address for DelegationManager
for your environment (Mainnet, Testnet).
Set the value for el_delegation_manager_address
in your operator.yaml
config file to the address for your environment.
Operators have the option to set delegationApprover when they register. If the delegationApprover
is set to a nonzero value, then the delegationApprover
address will be required sign its approval of new delegations from Stakers to this Operator. If the default value is left as the zero address (0x000...) then all new delegations will be automatically approved without the need for any signature. Please see delegationApprover Design Patterns for more detail.
To register your operator, run:
eigenlayer operator register operator.yaml
Find the complete guide here: https://docs.eigenlayer.xyz/operators/howto/operator-sets
If you are using the eigenlayer-cli you must check that the --caller-address
has been imported or created on the cli environment
If not already done, set the Allocation Delay by running:
eigenlayer operator allocations set-delay <flags> <allocation-delay>
To register to Operator Set, run:
eigenlayer operator register-operator-sets
--operator-address <operator-address>
--avs-address <avs-service-manager-address>
--operator-set-ids <comma-separated-list-of-operator-set-ids>
--caller-address <address-of-caller>
To Set Allocations per Operator Set and Strategy, run:
eigenlayer operator allocations update
--network sepolia
--operator-address <operator-address>
--csv-file updates.csv
--caller-address <address-of-caller>
Use the csv in the below format to set multiple allocations in one transaction, where update.csv
will look like:
avs_address,operator_set_id,strategy_address,bips
0x2222AAC0C980Cc029624b7ff55B88Bc6F63C538f,2,0x4936BA8f0a04CcC2e49b8C9E42448c5cD04bF3f5,1200
0x2222AAC0C980Cc029624b7ff55B88Bc6F63C538f,1,0x4936BA8f0a04CcC2e49b8C9E42448c5cD04bF3f5,165
To view all your allocations, run:
eigenlayer operator allocations show
--network sepolia
--operator-address <operator-address>
--strategy-addresses <comma-separated-strategy-addresses>
To de-register from Operator Sets, run:
eigenlayer operator deregister-operator-sets
--operator-address <operator-address>
--avs-address <avs-address>
--operator-set-ids <comma-separated-list-of-operator-set-ids>
--caller-address <address-of-caller>
Now that you've opted in to EigenLayer and received delegation to one or more AVSs, you're ready to actually run the infrastructure that powers these services, and start earning rewards.
Each AVS in the EigenLayer ecosystem has its own setup process and technical requirements.
To help you get started, we've put together a table listing supported AVSs along with direct links to their operator documentation.
π Click here to access the full list of AVS node setup guides
Registered operators can update their metadata (if they change their restaking strategy or update their website)
This is the command you can use to make changes or updates to the metadata of your operator.
eigenlayer operator update-metadata-uri operator.yaml