Rivalz Network
  • Introducing Rivalz
  • ROME - Swarm Protocol
    • rAgent Creation
    • What is a PAG?
    • ROME Rewards
      • ROME Season 1 - 25,000,000 $RIZ in rewards
    • Swarms and Swarm Staking
    • Lending Market
    • User Guide - ROME Dashboard
      • PAG
      • Reputation & Rewards
      • Swarm Project Creation
      • Swarm Staking
      • Borrow Market
      • Lending Guide
  • rClients (ROME 🏛️)
    • rClient CLI Guide
  • OCY - DATA
  • ADCS - CONNECTIVITY
    • Overview
    • Core components
    • Create an Adapter
    • Create your consumer smart contract
    • How to automate your contract execution with Gelato
    • How to Become a Provider
    • Developer
  • NOSTRINGS - IDENTITY
  • VORD - APPLICATION
    • VORD
    • Sidelined
    • AI-Powered Telegram Bots (Coming Soon)
  • Rivalz Alliance & Ecosystem
  • Intel Incentivized Testnet
  • zNode (Validators)
    • zNode Utility
    • Running a zNode
    • Delegating a zNode
      • Rivalz zNode - NodeOps Delegation
    • zNode Burn Event (Ended)
  • RIZ Token
    • RIZ Overview & Contracts
    • Airdrop and Eligibility Requirements
      • Airdrop User Guide
      • Claim Page Guide
    • zNode RIZ Drop
    • $RIZ Tokenomics
    • $RIZ Staking User Guide
    • $wRIZ Staking User Guide
    • Stake to Aerodrome Liquidity Pool
    • Wrapping and Unwrapping $wRIZ User Guide
  • Roadmap
  • Official Links
Powered by GitBook
On this page
  1. ADCS - CONNECTIVITY
  2. Design Components
  3. On-chain Components

Oracle Router

The Oracle Router is a critical component within the Agentic Data Coordination Service (ADCS), responsible for directing data requests to the appropriate oracles based on user specifications and data requirements. It plays a pivotal role in ensuring that data retrieval is efficient, accurate, and aligned with the needs of the application.

Functionality

When the Coordinator Contract receives a request from a Consumer Contract, it performs a detailed analysis of the request. This includes understanding the type of data required and evaluating specific parameters or filters defined by the user, such as data source preferences, required data freshness, or acceptable latency.

Based on this analysis, the Coordinator routes the request to the Oracle Router, which dynamically selects the most suitable oracles for fulfilling the request. Selection criteria may include:

  • Data Specialization: Oracles that specialize in the specific type of data needed.

  • Performance Metrics: Oracles with proven reliability, low latency, and high accuracy.

  • Cost Efficiency: Oracles that offer competitive pricing for their services.

  • Reputation Scores: Oracles with high trust and reputation within the ADCS network.

By intelligently directing requests, the Oracle Router enhances scalability and reliability. It distributes requests among multiple oracles, preventing overloading any single oracle and optimizing resource utilization within the network. This approach also improves response times by leveraging the fastest available oracles and mitigates the impact of potential oracle failures or slowdowns.

Last updated 6 months ago