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

Decentralized Access Control

PreviousBalance AccountingNextPause/Unpause Access Control

Last updated 1 year ago

All access control logic for the decentralized contracts (KUMASwap, KIBToken, KBCToken, and MCAGRateFeed) is handled by the the KUMA protocol's contract. The following roles will be added to the KUMA protocol's access control to the following entities:

Entity
Mint KIBT
Burn KIBT
Pause KUMASwap
Un-Pause KUMASwap
Set KIBT Epoch
Manager
KUMASwap Claim
Set KBC URI

KIBTSwap

✅

✅

MCAG MultiSig

✅

KUMA DAO

✅

✅

✅

✅

✅

  • KIBT_MINT_ROLE - Mints KIBTokens

  • KIBT_BURN_ROLE - Burns KIBTokens

  • KUMA_SWAP_PAUSE_ROLE - Pauses KUMASwap, which prevents all transfers, minting, and burning of KUMA Bonds NFTs

  • KUMA_SWAP_UNPAUSE_ROLE - Unpauses KUMASwap, which re-enables transfers, minting, and burning of KUMA Bonds NFTs after a pause

  • KIBT_SWAP_CLAIM_ROLE - Claims the parent bonds of a clone bond in KIBTSwap

  • KIBT_SET_EPOCH_LENGTH_ROLE - Sets KIBToken epoch length

  • KUMA_MANAGER_ROLE - Sets configs of the protocol like sellBond fees, minGas in KIBTSwap , KUMAFeeCollector payees and shares, and contract addresses in the KUMAAddressProvider

  • KUMA_SET_URI_ROLE - Sets the URI for the Kuma Bond Clone Token contract

AccessController