Operator Guide
Last updated
Last updated
This guide contains the steps needed to set up and register your node for DODOchain MACH AVS.
4 CPU
16GB Memory
50GB SSD
Ubuntu 24.04 LTS
v24 and above
EigenLayer CLI
💡 For smooth onboarding of operators, we will set the initial stake requirement to be 0.
Beacon Chain Ether and all LSTs supported by EigenLayer are supported by our AVS.
Generate ECDSA and BLS keypair using the following command
💡 Please ensure you backup your private keys to a safe location. By default, the encrypted keys will be stored in ~/.eigenlayer/operator_keys/
Fund at least 0.3 ETH to the ECDSA address generated. It will be required for node registration in the later steps.
💡 You may skip the following steps if you are already a registered operator on the EigenLayer testnet and mainnet.
You will need to do it once for testnet and once for mainnet.
Create the configuration files needed for operator registration using the following commands. Follow the step-by-step prompt. Once completed, operator.yaml
and metadata.json
will be created.
Edit metadata.json
and fill in your operator's details.
If this is your first time registering this operator, run the following command to register and update your operator
Upon successful registration, you should see ✅ Operator is registered successfully to EigenLayer
If you need to edit the metadata in the future, simply update metadata.json
and run the following command
You can also check the operator registration status using the following command.
For opt-in and out, copy the following env
Update the TODO
sections in the .env.opt
To opt-in
💡 Before you opt-in to MACH AVS, please ensure that
You have the right infrastructure (e.g., cloud hosting) to keep the operator up and running. Non-performing AVS operators may be subjected to ejection out of MACH AVS.
You have already been whitelisted as an operator for MACH AVS.
If you no longer want to run the AVS, you can opt out by running
💡 It may take a few minutes for EigenLayer AVS and operator page to be updated This is an automatic process.
Update the TODO
sections in the .env
💡 The default path where your generated keys are stored in ~/.eigenlayer/operator_keys/
We have pre-configured mach-config.toml
with RPC hosted by AltLayer. Alternatively, you can reach out to the AltLayer team members on the Slack working group for instructions on how to host your own RPC node.
If you wish to update L1 or Rollup RPC,
Navigate to /chain-config/mach-config.toml
Locate the fetcher
and l1-fetcher.
Look for the variable url
and l1_url
. Replace the value with your endpoint.
To run MACH AVS, you may launch it using docker compose.
To tear down the container
If you want to enable monitoring, run the following
If you want to stop the monitoring:
When using the monitoring
profile, you may wish to add grafana
to monitor the service, the default port is 1300
can access via localhost:13000
.
Please feel free to reach out to us via the Slack working group.
How do I know whether my operator is running?
First, check whether your operator docker container is running, by running docker compose ps
.
Next, you can check the logs to see whether the services has been started or not
Who is running the aggregator and doing BLS signature aggregator?
AltLayer will provide an aggregator to which your MACH AVS can connect and submit the signatures for aggregation. The aggregator endpoint has been pre-configured in the configuration file.
How do I know when I do not meet sufficient minimal stake requirements during registration? You will encounter execution reverted: StakeRegistry.registerOperator: Operator does not meet minimum stake
Will there be token rewards?
There will be rewards for mainnet MACH AVS in the future. More details will be announced in the future.
I am unable to opt in and encounter Unable to register operator with avs registry coordinator
Please check that your ECDSA address is sufficiently funded. We recommend maintaining at least 0.3 ETH to ensure you have sufficient gas tokens for AVS registering, opt-in and de-registering operations.
Follow and Install EigenLayer CLI
Please submit the ECDSA address via MACH AVS interest form .
Upload metadata.json
to a public URL. Then update the operator.yaml
file with the url (metadata_url
). If you need hosting service to host the metadata, you can consider uploading the metadata and get the raw
url.
After your operator has been registered, it will be reflected on the .
Testnet:
Maiinnet:
💡 Training wheels AltLayer Mach AVS will initially launch in operator allowlist mode. Interested operators can register their interest with us using this form:
Run the following command to clone the and change directory to DODOchain MACH AVS mainnet config.
If you encounter rate limits on public endpoints, we recommend that you use managed RPC services such as , , or
To run MACH AVS within your Kubernetes cluster, you can use the reference Helm chart available in the MACH AVS Operator Setup repository. You can find the Helm chart at the following link: .