Overview
This guide will walk you through the process of setting up and running a Chainbase AVS (Actively Validated Service) operator node.Requirements
Recommended Hardware SpecificationsClass | 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 |
Installation Process
Migration From Previous Version
If you’ve previously run a Chainbase AVS operator node:- You can delete old version
chainbase-avs-setup
directory on your server, but need to back up your encrypted ECDSA and BLS keys. - Skip the EigenLayer Registration step and only start from Chainbase AVS Setup step.
EigenLayer Registration
Ensure you’ve registered with EigenLayer before proceeding. For guidance, refer to the EigenLayer Operator Installation Guide.Chainbase AVS Setup
- Clone the Chainbase AVS setup repository:
- Set up the environment file:
.env
file with your specific information:
eigenlayer operator keys list
to retrieve information about your ECDSA and BLS key paths and operator address.
- OPERATOR_ADDRESS: Set to your operator address (must match your ECDSA key address).
- NODE_SOCKET: Set to your server’s public IP address (format:
<your_server_public_ip>:8011
).
- Ensure your server’s public IP is internet-accessible.
- Verify that port 8011 is open and properly configured in your firewall settings.
- Set execution permissions for the script:
Operating the Chainbase AVS
Register as an Operator
Run the following command to register as an operator:Run Node
Run the following command to startup node:Test Node
Run the following command to test node:All systems are working for your manuscript node
in the command line output, it indicates that your node is running correctly.
Update Node socket
If your server’s public IP address is changed after you register as an operator, you need to update the node socket. ConfigureNODE_SOCKET
in .env
file, then run the following command:
Update Node version
Run the following command to update node version:Monitor Logs
View container logs using any of these commands:Dashboard
You can visit<your_server_public_ip>:3010
on browser to view the dashboard to confirm the status of your node.If you are unable to access the page in your browser, please verify that port 3010 on your server is open and properly configured in firewall settings.