Modefi
  • Introduction
  • Oracle Solutions Suite
    • Decentralized Aggregated Oracle
    • On-Demand Oracle
      • On-Demand Oracle - Technical Manual v0.1
        • The On-Demand Oracle System
        • Types of Users
          • Data Request Creators
            • Requesting Data
            • Setting Times
            • Cancelling Data Requests
            • Disputing Results
          • Validators
            • Account Management
            • Staking (and Unstaking)
            • Providing/Endorsing Data
            • Disputing Results
            • Receiving Payment
          • ODO Custodian
        • Algorithms
          • Computing Request Costs
          • Depositing and Withdrawing Coins
          • Staking to Endorse Data
          • User and Staking Slot Tiers
          • Timing/Lateness
          • Bumping
          • Withdrawing
          • Endorsing
          • Payment
          • Slashing
          • Reputation
          • Staking Bonuses
          • Disputes and Resolutions
          • Coin Credits
          • Account Transfer
      • On-Demand Oracle - High-Level Overview
    • Oracle Marketplace
  • Defi Dashboard
    • What is the Modefi DeFi Dashboard?
  • Token
    • Tokenomics
      • Token Distribution
      • Token Stats
      • Token Emission Schedule
    • Token Sale
    • Token Utility
  • General Information
    • History of Oracle Based Hacks / Exploits
      • Synthetix $1 Billion Exploit
      • Trader Exploits bZx Oracle for $330,000 Profit
      • $100 M Liquidated on Compound Following Oracle Exploit
  • Blockchain Basics
    • What is a Smart Contract?
    • What is an Oracle?
  • FAQ
    • Staking on Fantom
    • Staking on Binance Smart Chain
  • How-to's
  • Smart Contract Addresses
  • Links and Socials
  • Media Kit
  • Disclaimer
  • Terms and Conditions
  • Privacy Policy
Powered by GitBook
On this page
  1. Oracle Solutions Suite
  2. On-Demand Oracle
  3. On-Demand Oracle - Technical Manual v0.1

The On-Demand Oracle System

PreviousOn-Demand Oracle - Technical Manual v0.1NextTypes of Users

Last updated 1 year ago

Broadly speaking, the contracts can be categorized in five ways. On the far left of the diagram are the contracts that hold permanent user data that is independent of any data request. The contracts in the bottom half of the middle handle deployment of the on-demand contracts that handle each request. The right side of the diagram contains the contracts that work together to handle all of the data that is sent in. These contracts also play a big role in consensus. The contracts towards the top of the diagram are the contracts that handle dataset configuration, staking, and disputes. The contracts with a name that looks like OD* are deployed when a new request batch is registered. The last category of contracts help connect and control the other contracts by acting as data stores (e.g., RequestDetails) or, in the case of the OnDemandMain, coordinate interactions across branches of the system.

In the first section of the manual, we'll cover all the ways in which the ODO can be interacted with. We'll cover the roles that system users can fill, the tasks they can perform, and how they can perform them.

In the second part of the manual, we'll go into great detail, covering how the ODO handles various occurrences and why it behaves the way it does.

Data Requestor
Data Endorser
ODO Custodian
Algorithms
Cost Computation
Depositing and Withdrawing Coins
Staking to Endorse Data
User and Staking Slot Tiers
Timing/Lateness
Bumping
Withdraws
Endorsing
Payment
Slashing
Reputation
Staking Bonuses
Disputes and Resolutions
Coin Credits
Account Transfer
Types of Users