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
    • 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
      • 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
    • 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
Export as PDF
  1. Build on EO
  2. Builders Workflow

Off-chain Computation

The first step in the data processing flow is defining what off-chain data the blockchain oracle service needs to submit on-chain and implementing the appropriate operator code.

  1. Define and implement data validators execution logic - Writing DV code to retrieve the required data. Data here refers broadly to any output from computations, including fetching information from APIs, querying databases (blockchains included), and calculating statistics on account balances.

  2. Transaction format - Data validators must pack their computation results into a transaction structure before sending them to EO chain. Data reports may include additional data such as timestamps, proof of computation etc. Transaction are signed using either BLS or ECDSA.

  3. Sending transaction to EO chain - The EO chain is EVM-compatible, supporting the standard transaction formats used by common libraries like ethers.js and web3.js.

After the data validator code is established, The EO Wrapper facilitates interaction with the EO chain:

  • Retrieving OVS configuration, including update notifications

  • Sending reports to the EO chain with minimal latency

  • Publishing Prometheus metrics to monitor the off-chain component's health

Key considerations

  • Data validators typically run identical logic. This redundancy achieves decentralization and ensures that malicious behaviors can be easily validated on-chain. However, this replication creates coordination challenges. Data validator task should be easily scaled to run among all OVS operators.

  • In certain scenarios, computation integrity evidence can be recorded on-chain to verify the actions of data validators. This process helps in validating data accuracy and quality.

PreviousSet-upNextOn-chain Components

Last updated 2 days ago