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

Bumping

If a user tries to stake and there are no spots remaining, then the contract will check for a user who is late. If there is a late user occupying a slot that the staking user would be eligible to take were it open, then the late user will lose their slot and the user trying to stake will take it. Tiers are searched from the highest tier to the lowest tier the staking user is eligible to fill.

The search order stated above applies to any time a user is staking, not just bumping another user. The reason the available slots are searched from highest to lowest is to optimize for speed. For example, if there is only a MiddleTier slot and a LowerTier slot available and there is a MiddleTier user and a LowerTier user, then if the MiddleTier user takes the LowerTier slot, the LowerTier user cannot participate and we have to wait for another user to come along. It is better to give the MiddleTier slot to the MiddleTier user and the LowerTier slot to the LowerTier user, regardless of the order they stake. Searching from highest to lowest achieves this goal.

PreviousTiming/LatenessNextWithdrawing

Last updated 1 year ago