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

MCAGAggregator Volatility Check

Before an MCAGAggregator contract accepts a newly transmitted rate in a new round, it checks that the new rate has not changed too drastically from the previous round. This is done by comparing the absolute differences between the new and previous rate are less than the _volatilityThreshold, given in a per-second cumulative rate.

For example, if the previous rate transmitted by the aggregator corresponds to a yearly coupon of 5% (or an on-chain per-second cumulative rate of 1000000001547125957863212449), and the _volatilityThreshold is set to 315522921573372069, or a yearly coupon of 1%, the next rate must be:

  • greater than a minimum rate of the current rate + the _volatilityThreshold, or 1000000001547125957863212449 + 315522921573372069 = 1000000001862648879436584518, corresponding to a yearly coupon of 4%

  • less than a maximum rate of the current rate + the _volatilityThreshold, or 1000000001547125957863212449 - 315522921573372069 = 1000000001231603036289840380, corresponding to a yearly coupon of 6%

PreviousCentral Bank Rate ValidationNextCode Repositories

Last updated 2 years ago