SHAKOTN
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Gauntlet Liquity report findings ref: https://liquity-report.gauntlet.network/ ## TL;DR and key points - **Stability pool needs another form of incentives(such as LQTY tokens), otherwise there will not be enough liquidity to protect from insolvent state.** - **It is beneficial to have CCR higher in relation to MCR. This will result in less time spent in insolvent mode for the price of being in recovery mode** - **The gas compensation for Liquidators appears to be sufficient for preserving the functionality of the protocol** - **Borrowers should be incentivized as much as possible to maintain their ICR more frequently. This improves protocol health and decreases time spent in recovery mode** - **Collateral price volatility has almost no effect on amount of redemptions** - **Borrowed asset price volatility has significant effect on amount of redemptions(arb opportunities)** --- ## Overview about simulation ### What type of modelling is it? Gauntlet uses Agent-Based Simulations. Agent-based models are a kind of microscale model that simulate the simultaneous operations and interactions of multiple agents in an attempt to re-create and predict the behaviour of a complex system(protocol), such as Liquity. Each Agent represents a micro part of the system. Agents can be: borrowers, eth volatility, gas prices, redemptions, network congestion, etc; each playing it's role in protocol behaviour. NOTE: Gauntlet used data for loan openings from Maker CDP NOTE2: Simulation assumes some parameters of the system to be perfect. For instance: when redemption happens, system expect borrowers redeem LUSD for ETH and immediately sell ETH for USD to lock in profits. This might not be the case in real world scenario NOTE3: Simulation doesn't take into account LQTY rewards for Stability pool at all ## Effects of ETH volatility on system insolvency Simulation ran for 3 scenarios: 1. low: ETH vol=41% annualized 2. normal: ETH vol=97% annualized 3. high: ETH vol=173% annualized Input parameters: - 14 days time window - 365gWei gas price(why tho?) All heatmaps have: - X-axis as MCR(Minimum Collateral Ratio) - Y-axis as CCR(Critical Collateral Ratio) - MCR - Z-axis as % of time spent in specific state against total time(14 days) ### System insolvency sims against ETH volatility #### Insolvent state This simulation shows that there is minimal risk for the protocol when ETH volatility being "low" or "normal". However, when ETH volatility is "high", protocol can spend up to 3.5% of time in insolvent state. ![](https://i.imgur.com/LgTjw93.png) #### Recovery state Heatmap below demonstrates(in relation to the chart above), that the bigger CCR-MCR value is, the more protocol might spend in recovery mode. However, this can significantly decrease time spend in insolvent mode ![](https://i.imgur.com/zLUIqID.png) #### Stability pool returns One more interesting sim for Stability pool returns. It seems that pool returns are low under "low" and "normal" scenarios and only rise when ETH volatility is very high. ![](https://i.imgur.com/fMYhhNv.png) ### Conclusions: - **Stability pool needs another form of incentives(such as LQTY tokens), otherwise there will not be enough liquidity to protect from insolvent state.** - **It is beneficial to have CCR higher in relation to MCR. This will result in less time spent in insolvent mode for the price of being in recovery** --- ## Effects of dynamic borrower behaviour on protocol As in previous sim, this simulation runs against 3 different scenarios: 1. No dynamic behavior: Borrowers never top up or withdraw collateral 2. 2-week mean: Borrowers check their troves every two weeks on average 3. 3-day mean: Borrowers check their troves every three days on average Obviously, the percentage of time the protocol is insolvent significantly decreases as borrowers maintain the CR of their troves on a more regular cadence ![](https://i.imgur.com/Tg7brzh.png) Also, time spent in recovery mode decreases significantly if borrowers check their troves more frequently ![](https://i.imgur.com/pQEGQ4L.png) ### Conclusions: - **Borrowers should be incentivized as much as possible to maintain their ICR more frequently. This improves protocol health and decreases time spent in recovery mode** --- ## Effect of gas prices on protocol For this sumulation, again, there are 3 different scenarios: 1. 15 GWei 2. 80 Gwei 3. 315 Gwei ETH Volatility is set to high number of 173% annualized We can observe, that protocol has some insolvent time over 14 days, ![](https://i.imgur.com/H9ADEQG.png) but the time spent in recovery mode is relatively unchanged ![](https://i.imgur.com/fFSjocy.png) ### Conclusions: **The gas compensation for Liquidators appears to be sufficient for preserving the functionality of the protocol** --- ## Analyzing effect of Redemptions on protocol The effect of LUSD and ETH volatility on redemptions. Very high gas price is used (315 GWei) with mean_borrower_reaction_time of 14 days for these sims. **NOTE**: Higher base rate indicates increasing number of redemptions at a given time On the heatmap below you can see that num of redemptions, redemptions volume and base rate are dependant only on LUSD volatility on the market. Obviously, unpegging LUSD creates arb opportunities. ![](https://i.imgur.com/1ZvXHKU.png) Interesting, that ETH volatility has almost no effect on num of redemptions ### Conclusions - **Collateral price volatility has almost no effect on amount of redemptions** - **Borrowed asset price volatility has significant effect on amount of redemptions(arb opportunities)** --- ## Outcome: Recommended Parameters | Parameter | Current | Conservative | Aggresive | | -------- | -------- | -------- | -------- | | Minimum Collateralization Ratio (MCR)| 110% | 130% | 120% | | Critical Collateralization Ratio (CCR) | 150% | 140% | 130% |

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully