Kuma Protocol
WebsiteTwitterGovernance Forum
  • Introduction
  • KUMA Protocol
    • How does it work ?
    • Regulated NFTs
      • Real World Assets, onchain
      • Mimo Capital AG, a regulated entity
      • KUMA NFTs
    • Composable Interest-bearing tokens
      • KUMA Swap
        • User Scenario 1: Kuma Bond Token With Swap
      • KUMA Interest-bearing tokens
        • USK
        • FRK
        • EGK
      • Interest accrual
    • DeFi Integrations
      • DEXes Protocols
      • CDP Protocols
      • Lending Protocols
      • Yield Aggregators Protocols
      • Fixed Yield Protocols
      • Bridges
  • DAO & Governance
    • What is MIMO (Governance Token) ?
      • Where can i get MIMO ?
    • vMIMO and Voting Power
    • Governance process
      • Govern with MIMO tokens
    • Proposal Framework
      • KUMA Integration Request (KIR)
      • KUMA Governance Proposal (KGP)
      • KUMA Improvement Protocol (KIP)
    • Multisig
    • KUMA Emergency Guardians
  • developers
    • Developer Guide
    • Smart Contract Architecture
      • KUMA Interest Bearing Token (KIBT)
        • Interest Bearing Logic
        • ERC-20 Compliance and Updates
        • Balance Accounting
      • Decentralized Access Control
        • Pause/Unpause Access Control
      • KUMASwap
        • sellBond
        • buyBond
      • KUMA Bond Clone Tokens (KBCT)
      • Keepers
      • Deprecation Mode
      • Rate Feed
        • Central Bank Rate Validation
        • MCAGAggregator Volatility Check
    • Code Repositories
    • Contract Addresses
      • Ethereum
      • Polygon PoS
      • Linea
      • Mantle
      • Telos EVM
      • Neon EVM
  • Ressources
    • User Guides
      • Setting up
      • Managing transactions on EVM chains
      • Troubleshooting
      • Lock MIMO for vMIMO
    • Links
    • Security & Audits
    • Glossary
    • Press Kit
Powered by GitBook
On this page
  1. developers
  2. Smart Contract Architecture
  3. Rate Feed

Central Bank Rate Validation

Before returning data, the returned central bank data is validated with the following checks:

  • The RateFeed checks that the returned central bank rate is at most as old as the _stalenessThreshold. Note: Even though central bank rates seldom change (on the order of a few times a year at most), oracles are still expected to update the rate to be newer than the _stalenessThreshold, even if they are updating to the same rates as served in the previous round. This staleness threshold is set by the MCAG_MANAGER_ROLE.

  • Before data is accepted in a round, the MCAGAggregator checks that the rate feed's answer is less than a preconfigured maximum value, and that the newly transmitted rate has not changed too drastically from the previous rate. See the MCAGAggregator Volatility Check section for exact calculations on how this is done.

PreviousRate FeedNextMCAGAggregator Volatility Check

Last updated 2 years ago