Skip to main content

Deploy Attestation Node

Once an operator has successfully registered to Lagrange State Committees AVS and subscribed to rollup chain/s, they can proceed to deploy attestation node/s.

Deploy using CLI​

In the latest version of the CLI (v1.1.x), we have introduced the feature of remote Signer for secured key management of the attestation nodes. This is an optional feature so if the operator doesn't want to configure this feature, please use the CLI version v1.0.x and directly deploy the attestation node.

Signer​

The remote signer enhances security and flexibility within the State Committee network as this allows the operators to manage private keys more securely and efficiently, especially when operating multiple attestation nodes across different chains.

For secure communication between the signer server and attestation nodes, TLS encryption has been added. This step is optional and can be omitted if you are operating within a private or secured network environment. The operators can configure TLS by generating the required certificates and keys.

Generate Certificates and Keys​

  • Use the script available in lsc-node repository (here) to generate necessary certificates.
  • Before running the script, specify the signer server’s IP or DNS in this file.

Setting up Remote Signer​

  • Configure the config_signer.toml file
  • Add the following keys to your config_signer.toml file:
    • EigenLayer operator's ECDSA key
    • BLS (BN254) key
    • Lagrange's ECDSA key
  • Run deploy-signer command to generate a config and deploy a docker container for the signer server.
info

The operators should be able to add all the private keys to the signer by modifying this config_signer.toml file.

Attestation Node​

  • Run generate-config command to generate a config specific to the chain and network for which you want to run an attestation node. Then run deploy command to deploy the docker container of your attestation node. Alternately, run generate-config-deploy which combines the generate-config and deploy commands.

If you choose to run multiple attestation nodes on the same machine for the same or different chains, then the deployment can be simplified using the bulk-generate-config-deploy command.

info

The information about the State Committee CLI commands can be found on the Commands page.

After deploying an attestation node docker container, it is imperative for an operator to monitor its status to check if it is running and attesting successfully.

Deploy using template​

The templates for attestation node's config file and the docker-compose can be found in the CLI repository.

info

Please review the configuration description.

  1. Replace {{.xxx}} in the template files with appropriate values.
  2. Run the following command to deploy the docker container for attestation node:
docker compose up -f <docker_compose_file_name> -d