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
  4. Types of Users

Validators

PreviousDisputing ResultsNextAccount Management

Last updated 1 year ago

Once a dataset is open and ready for data any user who is staked for the dataset may send in what they believe to be the data. Once data has been sent in for a dataset, any other user who is staked may either send in an endorsement of the data that was already sent in, or they may send in their own data if they believe the existing data is incorrect. Any data that is sent in can even be endorsed if a dispute occurs, to prevent the data from having to be ever sent in twice. The Algorithms section will cover providing, endorsing, and consensus in detail. This section provides an overview of the ‘what’, whereas the Algorithms section will go deeper into the ‘why’.

We’ll start off with what users can do with their accounts, then discuss staking and the options that are available for when things go wrong, next we’ll discuss providing and endorsing data, and, finally, we’ll end with post-validation actions.

Account Management
Staking (and Unstaking)
Data Endorsement
Disputes
Payment