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
  • Why did my operator fail to opt-in the Multi-Prover AVS?
  • I encountered a insufficient stake error when opting in. What should I do?
  • How to solve the unknown shorthand flag: d in -d error?
  • Why do I receive errors when running the docker compose xxx commands?
  • There are some weird docker permission errors such as docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock
  • I have other questions.

Was this helpful?

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

FAQ

PreviousOpt in to run AVSNextTEE Compile

Last updated 12 months ago

Was this helpful?

Why did my operator fail to opt-in the Multi-Prover AVS?

Confirm that your operator’s ECDSA key is added to the whitelist. Also, make sure that you have staked at least 32 ETH or LST.

I encountered a insufficient stake error when opting in. What should I do?

You may receive execution reverted: StakeRegistry.registerOperator: Operator does not meet minimum stake error when running the ./run.sh opt-in even if you have staked 32 ETH or LST. In that case, just stake more ETH and opt-in again.

The Multi-Prover AVS requires operators to own at least 32 weighted shares in proportion to the overall staking asset. This error occurs when the amount of ETH staked is not 1:1 to the share staked.

How to solve the unknown shorthand flag: d in -d error?

Please make sure that the docker-compose is installed in a way.

Why do I receive errors when running the docker compose xxx commands?

Run . ./docker-compose-env.sh under the multiprover-avs-operator-setup folder. This will update the ENV variables according to the latest config/operator.json file.

There are some weird docker permission errors such as docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock

Make sure that the user you are running the command with have the appropriate permissions, such as being in the docker group.

I have other questions.

Drop us a message .

plugin
here