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. Algorithms

Payment

As mentioned earlier, the user who actually provides the data incurs a higher cost than a user who only endorses data. This is reflected in the payout system as a bonus for the user who brings the consensus data on chain for each dataset. All pay computations start with the PayRate as computed in the Cost Computation section above. The general idea is that the data provider gets a little extra and the endorsers get a little less. For example, say there is a dataset requested with a required lead of 6. This means there is one provider and five endorsers initially required. If the gas bonus percentage is 10%, then the provider receives

ProviderPayRate=PayRate+PayRate∗10%=PayRate+PayRate∗0.10=1.10∗PayRate=110%∗PayRateProviderPayRate = PayRate + PayRate * 10\%\\ \hspace{2.9cm}= PayRate + PayRate * 0.10\\ \hspace{1.06cm}= 1.10 * PayRate\\ \hspace{1.25cm}= 110\% * PayRateProviderPayRate=PayRate+PayRate∗10%=PayRate+PayRate∗0.10=1.10∗PayRate=110%∗PayRate

as compensation while the extra PayRate * 0.10 is “covered by the endorsers” (not really covered by them, but it’s a convenient way to think about it for computation). This means that the endorsers receive

EndorserPayRate=PayRate−PayRate∗10%5=PayRate−PayRate∗2%=PayRate−PayRate∗0.02=0.98∗PayRate=98%∗PayRateEndorserPayRate = PayRate - PayRate * \frac{10\%}{5}\\ \hspace{2.74cm}= PayRate - PayRate * 2\%\\ \hspace{2.88cm}= PayRate - PayRate * 0.02\\ \hspace{1.06cm}=0.98 * PayRate\\ \hspace{1.06cm}= 98\% * PayRate\\EndorserPayRate=PayRate−PayRate∗510%​=PayRate−PayRate∗2%=PayRate−PayRate∗0.02=0.98∗PayRate=98%∗PayRate

Since the effect is amortized across all of the endorsers the deviation from the base pay rate is much smaller for the endorsers and the increase in cost, difficulty, and pressure to get the data correct borne by the data provider is rewarded with a small bonus.

PreviousEndorsingNextSlashing

Last updated 1 year ago