LogoLogo
GitHub
  • Quickstart
    • What is EO?
    • EO Vision
    • Use EO
  • Build on EO
    • Introduction to EO Stack
    • What is an OVS
    • EO Features
    • EO Data Processing Flow
    • Builders Workflow
      • Set-up
      • Off-chain Computation
      • On-chain Components
      • Target Chains Publishing
    • Smart Contracts Overview
      • EO Chain contracts
      • Target Contracts
    • Aggregation Library
      • Median
      • Clustering
      • TWAP
      • Robust Aggregation 101
    • EO Cryptographic Broadcaster
    • Incentives Management
      • 🥢On-chain-Subjective Slashing Framework
    • Active Specialized Blockchain Oracles
      • EtherOracle - Peg Securing Blockchain Oracle by Etherfi
      • Pulse - Risk Blockchain Oracle By Bitpulse
      • ECHO - Social Media Blockchain Oracle
      • Borsa - Intent Optimisation
  • ePRICE
    • Introduction to ePRICE
    • Integration Guide
    • Risk Management and Market Integrity
    • Feeds Addresses
      • Price Feed Addresses
        • Arbitrum
        • Arbitrum Sepolia
        • Base
        • Base Sepolia Testnet
        • Berachain
        • Blast
        • BNB Smart Chain
        • BOB
        • B Squared
        • B Squared Testnet
        • Hemi
        • Ink Sepolia
        • Ink Mainnet
        • Linea
        • Linea Sepolia
        • Ethereum
        • Manta
        • Manta Sepolia Tesnet
        • Mode
        • Mode Testnet
        • Monad Testnet
        • Morph
        • Morph Holesky
        • Polygon zkEVM
        • Polygon zkEVM Cardona Testnet
        • Plume
        • Plume Testnet
        • Scroll
        • Soneium
        • Sonic
        • Soneium Testnet
        • TAC Turin Testnet
        • Taiko Mainnet
        • Unichain
        • Unichain Sepolia
        • Zircuit
        • Zircuit Testnet
        • zkLink Nova Mainnet
      • PT Feeds Addresses
        • Pendle
          • Ethereum
          • Sonic
      • Custom Asset Feeds
    • API Reference
      • 🧩Examples
      • 🧩Off-chain Examples
    • Advanced
      • 🤖Automating EO consumption
      • 💱Getting a different currency pair
  • EO Token
    • The EO Token
    • Ecosystem Participants
    • EO Token Utility
    • EO Token Flywheel
    • Security and Enforcement
    • A New Chapter in Blockchain Oracle Design
  • Understand EO
    • EO Trust Model
    • Architecture Overview
    • Data Processing
    • Security
      • Cryptoeconomic Security
      • Aegis - Validator Set Configuration
  • Operators
    • Installation
    • Registration
    • Running the Client
    • Monitoring
  • 🔍Concepts
    • EigenLayer
    • Data Validators
    • Chain Validators
    • eBFT
    • OVS
    • EO Chain
Powered by GitBook
On this page
  • Prerequisites
  • Operator System Requirements
  • ​Prepare Local EO data validator
  • Clone repo
  • Navigate to correct folder
  • Setup .env file for EO Mainnet
  • Setup .env file EO testnet
  • Edit .env file with your specific details
Export as PDF
  1. Operators

Installation

Prepare your system to run the EO operator.

PreviousAegis - Validator Set ConfigurationNextRegistration

Last updated 21 days ago

Prerequisites

  1. Registered EigenLayer Operator Account: Ensure you have a fully registered EigenLayer operator account. If you don't have one, follow the steps in the to create and fund your account.

Operator System Requirements

  • Operating System: Linux AMD x64

  • vCPUs: 2

  • Memory: 4 GiB

  • Storage: 100 GB

  • EC2 Equivalent: m5.large

  • Expected Network Utilization:

    • Total download bandwidth usage: 1 Mbps

    • Upload bandwidth usage: 1 Mbps

  • Open Ports:

    • 3000 Grafana dashboards

    • 9090 Prometheus

​Prepare Local EO data validator

1

Clone repo

git clone https://github.com/eodata/operator-setup.git
2

Navigate to correct folder

cd operator-setup
3

Setup .env file for EO Mainnet

Copy operator-setup/data-validator/.example_env into operator-setup/data-validator/.env.

cp data-validator/.example_env data-validator/.env
4

Setup .env file EO testnet

Copy operator-setup/data-validator/.example_env_holesky into operator-setup/data-validator/.env.

cp data-validator/.example_env_holeksy data-validator/.env
5

Edit .env file with your specific details

Edit the operator-setup/data-validator/.env and update the values for your setup

EigenLayer Operator Guide