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

Coin Credits

The coin credits that are received after cheating or some similar data-invalidating event has occurred can be used as collateral when staking for another dataset. Coin credits are automatically applied when staking for a dataset if there are any in the user’s account, and the credits will be used up at the end of the dataset for which they are used. The coin credits can only cover up to 50% of the stake required for a dataset, so there will always be some real collateral that a user has at stake in a dataset.

The idea behind the coin credits is to offset an opportunity cost that manifests and is borne by being unlucky enough to be in an event with such an outcome. The credits give a way to essentially “catch back up”.

For example, consider a user with 100 FTM who plans to stake for two datasets, one after the other, and suppose there are three datasets each paying out at 2%. Normally, the user would stake their 100 FTM and receive 2FTM as payment, and afterwards, they can take their 102 FTM, stake 100 FTM, and end up with 104 FTM by the end.

Instead, if after the first dataset the user ended up getting 0 FTM and 100 coin credits, then they can stake in the two remaining datasets simultaneously (provided their level is high enough) by staking 50 FTM and 50 credits in each of the two remaining datasets. At the end of the two datasets, the user would receive 2 FTM from each for a total of 104 FTM, which is the same as the normal case without the credits above. It’s not perfect, but it comes quite close.

PreviousDisputes and ResolutionsNextAccount Transfer

Last updated 1 year ago