Skip to main content

Oracle Feeds

TODO: Complete On-Chain Oracle Documentation​

Consuming EigenWatch risk data from on-chain oracle contracts.

Required Sections​

  • Oracle Contract Details

    • Contract address (mainnet, testnet)
    • Contract ABI & interface
    • Deployed version & upgrade history

  • Oracle Feeds Available

    • Risk score oracle (which operators?)
    • Slashing event oracle
    • Reputation tier oracle
    • Historical data availability

  • Publishing Model

    • Update frequency (per-block? per-epoch?)
    • Update triggers (event-based? scheduled?)
    • Batch publishing strategy
    • Publisher identity & trust model

  • Oracle Consumers (Smart Contracts)

    • How to read risk score from contract
    • Data format on-chain (uint8, uint256?)
    • Staleness / recency checks
    • Fallback mechanisms

  • Gas Costs

    • Cost per query
    • Batch query costs
    • Update costs (publisher)
    • Optimization strategies

  • Data Format On-Chain

    • Risk score encoding (0-100 as uint8?)
    • Operator address format
    • Timestamp inclusion
    • Confidence / accuracy metrics

  • Example Integration

    // Pseudocode
    IRiskOracle oracle = IRiskOracle(0x...);
    uint8 riskScore = oracle.getRiskScore(operator);
    require(riskScore < 50, "Operator too risky");

  • Trust Model

    • Who publishes data?
    • Signature verification
    • Multi-signer requirements (if any)
    • Decentralization roadmap

  • Examples

    • LRT contract querying operator risk before minting
    • AVS contract checking operator health
    • Insurance contract pricing premiums by risk

Use Cases​

  • On-chain protocols making operator-aware decisions
  • Staking derivatives pricing risk
  • Insurance contracts automating premiums
  • DEX integrations for operator tokens

Status: NOT STARTED — Requires oracle contract design & deployment