Holesky Setup
Watchtower Client Setup for an EigenLayer node operator
Last updated
Watchtower Client Setup for an EigenLayer node operator
Last updated
We have our pre-built binaries in form of container images hosted on docker hub. The following is a quick start guide on running the same for a node operator who is interested to setup a diligence watchtower on the Holesky chain
Read the Node Requirements, if you haven't
Access
Watchtower Node Operator should be a registered EigenLayer Node Operator.
Registered EL Operator needs to be whitelisted on Witness Chain Network. Whitelisting will be done with the help of the Witness Chain team through a whitelisting process. If you are not sure how, Steps for setup will guide you through it.
Software
Docker client, engine and container runtime installed (version 23.0.0 or above, refer: https://docs.docker.com/desktop/install/linux-install/)
Hardware
Hardware requirements for the watchtower node can accessed here
One of the node configurations as described in the Node Types section below. Don't worry about how to configure right now ! As long as you have access to one of the configurations, we are good. We have you covered in the Steps for setup section !
The node operator is expected to deploy the watchtower container alongside both L1 and L2 Archived nodes in the ideal scenario. But, we offer a few more configurations if you would like to re-use some of your existing infrastructure or setup. The configuration parameters for the L1 and L2 Archived nodes may belong to one of the following distinct categories.
Use a Hosted L1 Node RPC Provider
Use Witness Chain provided L2 Node snapshot to bootstrap the node
Medium
Use a Hosted L1 Node RPC Provider
Run an L2 Archive Node synced from a public checkpoint
Full
Run an L1 Full Node
Run an L2 Archive Node synced from a public checkpoint
Note: Make sure there aren't any older version of watchtower images or containers. Use the below command to remove older/stale images
docker rm <stale_container_id>
docker rmi -f <stale_image_name>
The Witness Chain watchtower network is a permissioned network currently. Please connect with us on our Discord, if you want to become a watchtower operator
Before you start any activity on this network, ensure your operator and watchtower addresses are sufficiently funded to cover the gas costs. Use the faucet to fund it.
Register your EL operator address on the WitnessChain OperatorRegistry contract. You can do so with the help of our CLI utility.
The CLI tool expects Ubuntu 22.04 (if you are running on linux) or if you are running on Ubuntu 20.04, ensure the glibc version is 2.34+
# Run ldd --version to get the GLIBC version
ldd --versionInstallation:
curl -sSfL https://witnesschain-com.github.io/install-operator-cli-testnet | bashRunning:
export PATH="$PATH:~/.witnesschain/cli/"
watchtower-operator --version
Expected VERSION:
v0.3.0If you are facing the following error, please upgrade to Ubuntu 22.04
$ watchtower-operator --version
watchtower-operator: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by watchtower-operator)
watchtower-operator: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by watchtower-operator)
Once you've ensured the tool is installed correctly, run the below commands to register the operator with our AVS and associate the watchtowers to the operator.
Setup the configuration files for the OPERATOR CLI
# Set of watchtower private keys that will sign the Diligence Proofs.
# This is used for registration purposes
# Registration will happen both on L1 and L2 simultaneously{
"watchtower_private_keys": [
"<raw-watchtower-private-key e.g. 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef>"
],
"operator_private_key": "<raw-watchtower-private-key e.g. 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef>",
"eth_rpc_url": "https://ethereum-holesky-rpc.publicnode.com",
"proof_submission_rpc_url": "https://blue-orangutan-rpc.eu-north-2.gateway.fm/"
}If you are operating a Smart Contract Wallet as the operator address
then
set
"eth_rpc_url": ""
This will register the Operator EoA only on L2.
# Registers the Operator to WitnessHub AVS on EigenLayer
# This is required for the Operator to be listed on EigenLayer's
# AVS-Operator Page (https://holesky.eigenlayer.xyz/avs/0xa987ec494b13b21a8a124f8ac03c9f530648c87d)
# Witnesschain Txns can be monitored via Blockscout at
# https://witnesschain-testnet-blockscout.eu-north-2.gateway.fm
$ watchtower-operator registerOperatorToAVS --config-file <path to operator-config.json file># Registers the Operator's watchtower to WitnessHub AVS on Layer 1
# and Witness Chain's L2 CDK Chain
# This registration is required for operators to be associated with the
# points awarded as a result of diligently watching the chains.
# To understand what are watchtowers, please read the FAQs
$ watchtower-operator registerWatchtower --config-file <path to operator-config.json file>Mask the operator private-keys or remove it from the config files once the registration process is complete. We don't require it for submitting the bounties in this file
Post the registrations are complete, install the watchtower client, by running the following command.
Note: Make sure there aren't any older version of watchtower images or containers. Use the below command to remove older/stale images
docker rm <stale_container_id>
docker rmi -f <stale_image_name>
curl https://witnesschain-com.github.io/install-watchtower-testnet | shThe above command will guide you through the rest of installation process.