Witness Chain
  • Introduction to Witness Chain
  • Infinity Watch
    • Proof of Location (Mainnet)
      • Introduction
      • Process flow
      • Architecture
      • Run a watchtower!
        • For Partner node runners
          • Running on Akash Cloud
          • Running on SuperNoderz
        • EigenLayer operators
          • Running a PoL Watchtower
          • Witness Chain AVS opt-in guide
        • At-home watchtowers
        • For DePIN/Validator Node provider
      • Demos
      • PoL Research
    • APIs
      • Campaign APIs
        • Key Terminologies
        • Authentication
        • Create Campaign
        • Edit campaign
        • Get Photo feed from campaign
        • Get Campaigns
      • Challenge APIs
        • Overview
        • Getting Started
  • Resources
    • Blogs
      • How Proof of Location Works
      • Redefining Geolocation Compliance: Witness Chain & Predicate
    • 🗞️Research
    • 🎙️Talks and Podcasts
    • 🤝Community
    • ⚖️Smart Contracts
    • File a bug
  • Archive
    • Introduction
    • Proof of Diligence Watchtower Protocol
      • How it works
      • Diligence Watchtower Roadmap
      • Watchtower Architecture
      • Chains watched
      • Smart Contracts
      • Quick Links
      • FAQs
    • For the node operators
      • Node requirements
      • Watchtower setup
        • [ARCHIVE] Mainnet Setup
          • L2 Archive Node Setup guide
        • Holesky Setup
          • L2 Archive Node Setup guide
        • Migration from archive to full node
      • Monitoring
    • Research
    • Keys Management
    • Proof of Bandwidth
      • Introduction
      • Architecture
      • For the node operators
        • Running a PoB Challenger Client
        • Running a PoB Prover Client
      • Demos
      • Research
    • 🤝Watchtower Protocol (Architecture v1)
      • 🗼How it works
      • 📅Watchtower Roadmap
      • 🏦Watchtower Architecture
      • 🔗Chains supported
Powered by GitBook
On this page
  • Prerequisites
  • Node Types
  • Steps for setup
  • Step 1: Register with EigenLayer as an Operator
  • Step 2: Get whitelisted on the Watchtower Network.
  • Step 3: Register the operator on the Witness Chain Watchtower Network
  • Step 4: Submitting the bounties
  1. Archive
  2. For the node operators
  3. Watchtower setup

Holesky Setup

Watchtower Client Setup for an EigenLayer node operator

PreviousL2 Archive Node Setup guideNextL2 Archive Node Setup guide

Last updated 9 months ago

Testnet is available on Holesky

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

Prerequisites

  • Read the , if you haven't

  • Access

    • Watchtower Node Operator should be a registered EigenLayer Node Operator.

    • Registered 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, will guide you through it.

  • Software

    • Docker client, engine and container runtime installed (version 23.0.0 or above, refer: )

  • Hardware

    • Hardware requirements for the watchtower node can accessed

    • One of the node configurations as described in the 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 section !

Node Types

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.

Configuration Type
L1 Node
L2 Node

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

Steps for setup

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>

Step 1: Register with EigenLayer as an Operator

Step 2: Get whitelisted on the Watchtower Network.

Step 3: Register the operator on the Witness Chain Watchtower Network

Register your EL operator address on the WitnessChain OperatorRegistry contract. You can do so with the help of our CLI utility.

Prerequisites

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 --version

Step 3.1 : Installation and Running the CLI

  1. Installation:

    curl -sSfL https://witnesschain-com.github.io/install-operator-cli-testnet | bash
  2. Running:

    export PATH="$PATH:~/.witnesschain/cli/"
    watchtower-operator --version
    
    Expected VERSION:
       v0.3.0

If 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)

Step 3.2 : Registering the operator and the watchtowers

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

operator-config.json

# 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

Step 4: Submitting the bounties

  1. 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 | sh

The above command will guide you through the rest of installation process.

ONLY If you aren't yet an EigenLayer Operator yet, HOW TO can be found

The Witness Chain watchtower network is a permissioned network currently. Please connect with us on our , 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 to fund it.

Note: Refer to our to understand the difference between watchtower addresses and operator addresses

here
Discord
faucet
Node Requirements
Formal guide to register
EL Operator
https://docs.docker.com/desktop/install/linux-install/
here
Steps for setup
Node Types
Steps for setup
Light
FAQs