LogoLogo
GitHub
  • Quickstart
    • What is eOracle?
    • eOracle Vision
    • Use eOracle
  • Build on eOracle
    • Introduction to eOracle Stack
    • What is an OVS
    • eOracle Features
    • eOracle Data Processing Flow
    • Builders Workflow
      • Set-up
      • Off-chain Computation
      • On-chain Components
      • Target Chains Publishing
    • Smart Contracts Overview
      • eOracle Chain contracts
      • Target Contracts
    • Aggregation Library
      • Median
      • Clustering
      • TWAP
      • Robust Aggregation 101
    • eOracle Cryptographic Broadcaster
    • Incentives Management
      • 🥢On-chain-Subjective Slashing Framework
    • Active Specialized Blockchain Oracles
      • EtherOracle - Peg Securing Oracle by Etherfi
      • Pulse - Risk Oracle By Bitpulse
      • ECHO - Social Media 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 eOracle 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 Oracle Design
  • Understand eOracle
    • eOracle 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
    • eOracle Chain
Powered by GitBook
On this page
Export as PDF
  1. Build on eOracle

eOracle Cryptographic Broadcaster

eOracle cryptographic Broadcaster responsible for data publishing to target chains.

Overview

The eOracle Broadcaster is a distributed system designed to bridge data feeds from the eOracle Chain to various target chains with high reliability, low latency, and cryptographic security.

The broadcaster's multilayer architecture enables flexibility and dynamism in handling data report formats, verification schemes, and update triggering logic.

System Architecture

The system consists of four main components that work together through message queues and a shared state database:

  • Witnesses

  • Aggregators

  • Processors

  • Publishers

Witnesses

Witnesses monitor the eOracle Chain for specific events and cryptographically attest to their validity.

Key responsibilities:

  • Monitor eOracle Chain events in real-time

  • Validate feed data against predefined criteria

  • Generate Merkle trees for efficient data verification

  • Sign data using both BLS and ECDSA signatures

  • Submit signed attestations to the aggregators

The witness component ensures that each feed update is independently verified and signed by multiple parties.

Aggregators

Aggregators process witness signatures and combine them when sufficient voting power is achieved. They implement a stake-weighted consensus mechanism based on witness voting power.

Key responsibilities:

  • Threshold-based sealing

  • BLS and ECDSA signature aggregation

  • Distributed coordination

aggregators achieve distributed coordination through the state database and capable for horizontal scaling.

Processors

Processors handle sealed aggregations and prepare them for target chain distribution. They maintain the latest state of feeds and generate proofs for target chain verification.

Key responsibilities:

  • Verify aggregated signatures

  • Maintain latest feed values in the state database

  • Generate and store Merkle proofs

  • Route updates to appropriate target chains and schedules.

  • Implement feed routing logic based on target chain configurations

Publishers

Publishers handle the final submission of verified feed updates to target chains, implementing chain-specific optimizations and transaction management to ensure proper delivery, the one and only task of the publisher is to get the package delivered, no altering, or other logic and without opening the package.

Key features:

  • Dynamic gas price optimization

  • Transaction retry logic

  • Chain-specific batching strategies

PreviousRobust Aggregation 101NextIncentives Management

Last updated 4 months ago

Page cover image