Prerequisites
Operator on EigenLayer
First, an operator must be registered to the EigenLayer registry. To do so, one must follow the EigenLayer docs. The operator must have some stake delegated to it as well.
For testnet, one needs to get Holesky ETH via their faucet and manually stake on themselves. See their documentation for more information.
There is a main ecdsa key associated with that operator which we will call avs_key . Following the documentation of EigenLayer, the private key should be encrypted in keystore file.
Hardware
We recommend setting up the worker on a dedicated instance because of the ratio price / performance.
The baseline hardware is 8c / 16 threads with 40+GB RAM. We recommend setting these up for example:
Cloud based instances
We are also running different workers on the cloud. The following table represents the type of machine that we run on the three categories:
| Category | vCPU | RAM |
|---|---|---|
| small (sc) | 20 | 40 |
| medium (sp) | 40 | 80 |
| large | 90 | 180 |
Given the parallelism of the current proof system is not optimal yet (plonky2), it is possible to run 2 worker binaries in the same instance for the moment.
Installation
Prerequisites
For ease of use, the worker binary is delivered via Docker and we provide docker-compose scripts to automate some common operations.
-
Docker (installation link)
-
Docker-compose (installation link)
RPC Node endpoint
For the registration, the operator needs to access a working Eth JSON-RPC endpoints to submit his registration transaction.
-
For mainnet, this should point to an Eth mainnet node
-
For testnet, this should point to Holesky testnet node (testnet network ran by Eigen)
Worker Repository
Now you're ready to download the worker repository that contains predefined configuration files to run the worker:
git clone https://github.com/Lagrange-Labs/worker.git
cd worker