ReSource
  • Welcome
    • Introduction
    • Protocol Architecture
  • Stable Credit
    • Stable Credit Lifecycle
    • Credit Risk
      • Overview
      • Risk Prediction and Mitigation
      • Underwriting
      • Network Assurance
      • Network Debt Account
      • Default Management
        • Obligation enforcement
    • Soft Peg
    • Stable Credits <> Fiat Loans
      • The Credit Pool
      • The Launch Pool
    • Configurability
  • Inter-Network Trade
    • Inter-Network Trade
      • Inter-Network Clearing House
      • How inter-network trade is facilitated
      • Export Risk
      • Export Risk Mitigation
        • Import Fee Structure
        • Import Fee Proceeds
        • Import/Export Limits
      • Varying Reference Currencies
  • Contracts
    • StableCredit.sol
    • AccessManager.sol
    • FeeManager.sol
    • AssurancePool.sol
    • CreditIssuer.sol
Powered by GitBook
On this page
  1. Stable Credit
  2. Credit Risk

Risk Prediction and Mitigation

PreviousOverviewNextUnderwriting

Last updated 1 year ago

Network risk is mitigated by the constant adjustment of two network variables: The Reserve to Debt (RTD) Target and the Base Fee.

The RTD Target defines the desired ratio between reserved funds and the total outstanding debt of a given network. (read more under ).

The Base Fee is a reference from which individual member fees are deduced - comparable to the Prime Lending Rate used by commercial banks. While individual transaction fees levied on members are set by the network's CreditIssuer contract, the Base Fee serves as a starting point on top of which these individual fees are added.

In order to resolve these two variables, the Stable Credit protocol relies on an Assurance Oracle which perpetually collects network data, member data and external risk inputs. On the basis of these inputs the Assurance Oracle aims to predict the future default rate of a given network and the relative price of risk in the form of a reserves RTD target and a network's Base Fee rate.

Assurance