Automata Docs
  • Understanding Automata
    • What is Automata?
      • TEE Coprocessor
      • Proof of Machinehood
        • Optimistic Attestation
        • Zero Knowledge Proof
        • Modular Trust
    • Key terms
  • TEE Overview
    • TEE Prover
    • Multi-Prover AVS (EigenLayer)
      • Operator guide
        • Installation
        • Deposit strategies
        • Opt in to run AVS
        • FAQ
    • TEE Compile
      • Getting Started
      • Vendorizing
      • Attestation Report
    • TEE Builder
      • Block Builder Architecture
      • Stateless Executor
    • Verifiable Random Function
      • Why Automata VRF
      • How does Automata VRF work
      • Attestation
  • Build with PoM
    • Introduction
      • Smart contract libraries
      • Attestations on Verax
      • Frequently asked questions
    • Attestation module
      • Machine Attestation
        • Intel SGX
        • AWS Nitro Enclaves
        • Miscellaneous
      • Device Attestation
        • Yubikey
        • Andriod
        • Apple
        • Windows
        • FIDO U2F Authenticator
      • WebAuthn Attestation
        • WebAuthn Attestation Types
        • Attestation Statements & Privacy Impacts
  • Backed by PoM
    • 1RPC
    • L2Faucet
      • Frequently asked questions
  • Protocol
    • App-Specific Rollup
    • Mainnet
    • Testnet
    • Bridge
      • Bridging Native Tokens from L1 to L2
      • Bridging Native Tokens from L2 to L1
    • Explorer
    • Specification
      • Attestation
      • Attestor
      • Smart Contract
  • Research
    • Account Abstraction
    • Decentralized Randomness
    • Maximal Extractable Value
    • Reproducible Build
    • Lightpaper
Powered by GitBook
On this page
  • Requirements
  • Operator setup
  • Install EigenLayer CLI and register as operator
  • Running Multi-Prover AVS
  • Clone the setup repository
  • Update the configuration

Was this helpful?

  1. TEE Overview
  2. Multi-Prover AVS (EigenLayer)
  3. Operator guide

Installation

PreviousOperator guideNextDeposit strategies

Last updated 10 months ago

Was this helpful?

This guide lays out the requirements and steps to register an operator with EigenLayer and opt-in to running the Multi-Prover AVS on Holesky testnet. Responsibilities of the operator will include sampling and proving batched transactions submitted by Scroll to the base layer.

Requirements

  • 4 CPU

  • 8GB Memory

  • 100GB SSD

  • and

  • Ubuntu 20.04 LTS

  • 32 ETH or LST on Holesky testnet

Operator setup

Skip this section if you have already as a node operator on EigenLayer

Install EigenLayer CLI and register as operator

Follow to install the EigenLayer CLI and register as an operator.

Running Multi-Prover AVS

Clone the setup repository

git clone <https://github.com/automata-network/multiprover-avs-operator-setup.git>

Update the configuration

cd multiprover-avs-operator-setup/holesky
cp config/operator.json.example config/operator.json
vim config/operator.json

Below are the configs you need to provide:

  • BlsKeyFile: BLS key generated using EigenLayer CLI, the default path is ~/.eigenlayer/operator_keys/xxx.bls.key.json , please use absolute path for this configuration.

  • EcdsaKeyFile: ECDSA key generated using EigenLayer CLI, the default path is ~/.eigenlayer/operator_keys/xxx.bls.key.json , please use absolute path for this configuration.

  • BlsKeyPassword: Password of the BLS key.

  • EcdsaKeyPassword: Password of the ECDSA key.

  • TaskFetcher.Endpoint: RPC endpoint of the Ethereum mainnet, replace the https://1rpc.io/eth with the endpoint you get from RPC service provider.

Below are the configs that you can use the default value:

  • ProverURL: RPC endpoint of the TEE Prover, the default value is https://avs-prover-staging.ata.network , which is a TEE prover run by Automata Network.

  • Simulation: The default value is false . In the simulation mode, the operator will not actually process the task.

  • ETHRpcURL: Holesky RPC url used to interact with Ethereum Holesky testnet.

  • ETHWsURL: Holesky WS url used to interact with Ethereum Holesky testnet.

  • AggregatorURL: URL of aggregator hosted by Automata team. Aggregator will check validity of TEE prover, aggregator the BLS signature and submit the task to AVS service manager.

  • EigenMetricsIpPortAddress: The ip + port used to fetch metrics.

  • TaskFetcher: Define the tasks of this operator. On Holesky testnet, the task is to sample and prove the batch submitted by scroll to L1.

  • RegistryCoordinatorAddress: Registry coordinator contracts address of Multi-Prover AVS on Holesky testnet.

  • TEELivenessVerifierAddress: TEE liveness verifier contracts address on Holesky testnet, which verify the attestation provided by the TEE prover and manage its lifecycle.

EigenLayer CLI
Docker
docker-compose plugin
registered
EigenLayer’s guide