Running an operator

CURRENT VERSION: Aligned Operator v0.11.2

IMPORTANT: You must be whitelisted to become an Aligned operator.

Requirements

This guide assumes you are already registered as an operator with EigenLayer.

Hardware Requirements

Minimum hardware requirements:

Component	Specification
CPU	16 cores
Memory	32 GB RAM
Bandwidth	1 Gbps
Storage	256 GB disk space

Step 1 - Clone the repo

To start with, clone the Aligned repository and move inside it

git clone https://github.com/yetanotherco/aligned_layer.git --branch v0.11.2
cd aligned_layer

Step 2 - Building the Operator

Ensure you have the following installed:

• Go

• Rust

• Foundry

Also, you have to install the following dependencies for Linux:

• pkg-config

• libssl-dev

To install foundry, run:

make install_foundry
foundryup

To build the operator binary, run:

make build_operator

Upgrading the Operator

If you want to upgrade the operator, run:

make update_operator

This will recreate the binaries. You can then proceed to restart the operator.

You can find the latest version of the operator here.

Checking the Operator Version

To see the operator version, run:

./operator/build/aligned-operator --version

This will display the current version of the operator binary.

Step 3 - Update the configuration for your specific Operator

Update the following placeholders in ./config-files/config-operator.yaml:

• "<operator_address>"

• "<earnings_receiver_address>"

• "<ecdsa_key_store_location_path>"

• "<ecdsa_key_store_password>"

• "<bls_key_store_location_path>"

• "<bls_key_store_password>"

"<ecdsa_key_store_location_path>" and "<bls_key_store_location_path>" are the paths to your keys generated with the EigenLayer CLI, "<operator_address>" and "<earnings_receiver_address>" can be found in the operator.yaml file created in the EigenLayer registration process. The keys are stored by default in the ~/.eigenlayer/operator_keys/ directory, so for example <ecdsa_key_store_location_path> could be /path/to/home/.eigenlayer/operator_keys/some_key.ecdsa.key.json and for <bls_key_store_location_path> it could be /path/to/home/.eigenlayer/operator_keys/some_key.bls.key.json.

Two RPCs are used, one as the main one, and the other one as a fallback in case one node is working unreliably.

Default configurations is set up to use the same public node in both scenarios.

PUBLIC NODES SHOULDN'T BE USED AS THE MAIN RPC. We recommend not using public nodes at all.

FALLBACK AND MAIN RPCs SHOULD BE DIFFERENT.

Most of the actions will pass through the main RPC unless there is a problem with it. Events are fetched from both nodes.

eth_rpc_url: "https://<RPC_1>" 
eth_rpc_url_fallback: "https://<RPC_2>"
eth_ws_url: "wss://<RPC_1>"
eth_ws_url_fallback: "wss://<RPC_2>"

Step 4 - Deposit Strategy Tokens

We are using WETH as the strategy token.

To do so, there are two options, either doing it through EigenLayer's website, and following their guide, or running the commands specified by us below.

You will need to stake a minimum of 1000 WEI in WETH. We recommend to stake a maximum amount of 10 WETH. If you are staking more than 10 WETH please unstake any surplus over 10.

Option 1

EigenLayer's guide can be found here.

Option 2

If you have ETH and need to convert it to WETH you can use the following command, that will convert 1 ETH to WETH. Make sure to have foundry already installed. Change the parameter in ---value if you want to wrap a different amount:

cast send 0x94373a4919B3240D86eA41593D5eBa789FEF3848 --rpc-url https://ethereum-holesky-rpc.publicnode.com --private-key <private_key> --value 1ether

Here <private_key> is the placeholder for the ECDSA key specified in the output when generating your keys with the EigenLayer CLI.

Finally, to end the staking process, you need to deposit into the WETH strategy, as shown in the EigenLayer guide.

An alternative using the CLI

Run the following command to deposit one WETH

./operator/build/aligned-operator deposit-into-strategy --config ./config-files/config-operator.yaml --strategy-address 0x80528D6e9A2BAbFc766965E0E26d5aB08D9CFaF9 --amount 1000000000000000000

If you don't have Holesky ETH, these are some useful faucets:

• Google Cloud for Web3 Holesky Faucet

• Holesky PoW Faucet

Step 5 - Start the operator

./operator/build/aligned-operator start --config ./config-files/config-operator.yaml

Run Operator using Systemd

To manage the Operator process on Linux systems, we recommend use systemd with the following configuration:

You should create a user and a group in order to run the Operator and set the service unit to use that. In the provided service unit, we assume you have already created a user called aligned

# aligned-operator.service

[Unit]
Description=Aligned Operator
After=network.target

[Service]
Type=simple
User=aligned
ExecStart=<path_to_aligned_layer_repository>/operator/build/aligned-operator start --config <path_to_operator_config>
Restart=always
RestartSec=1
StartLimitBurst=100

[Install]
WantedBy=multi-user.target

aligned-operator.service is just an arbitrary name. You can name your service as you wish, following the format <service-name>.service.

Once you have configured the aligned-operator.service file, you need to run the following commands:

sudo cp aligned-operator.service /etc/systemd/system/aligned-operator.service
sudo systemctl enable --now aligned-operator.service

All paths must be absolute.

Those commands will link the service to systemd directory and then, will start the Operator service.

Also, if the server running the operator goes down, systemd will start automatically the Operator on server startup.

Restart operator

If you want to restart the operator, you can use the following command:

sudo systemctl restart aligned-operator.service

Get Operators logs

Once you are running your operator using systemd, you can get its logs using journalctl as follows:

journalctl -xfeu aligned-operator.service

Unregistering the operator

To unregister the Aligned operator, run:

cast send --rpc-url https://ethereum-holesky-rpc.publicnode.com --private-key <private_key> 0x3aD77134c986193c9ef98e55e800B71e72835b62 'deregisterOperator(bytes)' 0x00

<private_key> is the one specified in the output when generating your keys with the EigenLayer CLI.