Nicholas Del Zingaro
    • 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
    # MIP 30 Artemis Risk Parameter Recs (2023-02-21) parameters: { "mUSDC.wh": { // previous value: 40 collateralFactorPercentage: 50, // previous value: 516000 borrowCapInWholeTokens: 1000000 }, "mETH.wh": { // previous value: 35 collateralFactorPercentage: 45, // previous value: 400 borrowCapInWholeTokens: 800 }, "mWBTC.wh": { // previous value: 25 collateralFactorPercentage: 30, // previous value: 30 borrowCapInWholeTokens: 60 }, mDOT: { // previous value: 62 reserveFactorPercentage: 64 }, "mBUSD.wh": { // previous value: 20 collateralFactorPercentage: 15, // previous value: 15 reserveFactorPercentage: 99, // previous value: 20 collateralFactorPercentage: 15, MintPaused, BorrowPaused } } ## Artemis Summary We recommend the following parameter changes: - **Increase USDC.wh collateral factor from 40.0% to 50.0%.** - **Increase WBTC.wh collateral factor from 25.0% to 30.0%.** - **Increase WETH.wh collateral factor from 35.0% to 45.0%.** - **Increase xcDOT collateral factor from 62.0% to 64.0%.** - **Increase WETH.wh borrow cap from 400 to 800** - **Increase WBTC.wh borrow cap from 30 to 60** - **Increase USDC.wh borrow cap from 516,000 to 1,000,000** Rationale: The VaR is $358k and our recommendations will increase it by $2k to $360k. The LaR is $58k and our recommendations will increase it by $3k to $61k. FRAX has a VaR of $360k and a LaR of $47k. USDC.wh has a VaR of $169 and a LaR of $11.9k. WETH.wh has a VaR of $326 and a LaR of $0. xcDOT has a VaR of $3.76k and a LaR of $46k. USDC.wh, WBTC.wh, WETH.wh, and xcDOT are relatively safe from a market risk perspective, so can have their collateral factors gradually increased to improve capital efficiency. BUSD.wh, FRAX, and WGLMR's collateral factors are effectively balancing risk and capital efficiency. Borrow Amounts for USDC.wh, WETH.wh, and WBTC.wh have approached near full utilization of ther respective borrow caps. Gauntlet analyzed the assets' liquidity on-chain and potential risk of short market manipulation attack to assess the risk of increasing borrow caps on the protocol. Gauntlet recommends increasing the borrow cap for these assets in order to optimize user experience and growth while mitigating tail risks to the protocol. ## BUSD Increased Risk Gauntlet is reaching out to the Artemis community to address the recent news related to the regulatory actions against BUSD and Paxos. As of recent news reports, Paxos plans to [sunset](https://paxos.com/2023/02/13/paxos-will-halt-minting-new-busd-tokens/) BUSD but they plan to maintain it fully backed and redeemable until February 2024. Binance plans to support BUSD until they are able to find an [alternative](https://forkast.news/headlines/binance-ceo-non-usd-stablecoins-emerge/) stablecoin. However, Paxos has announced that they will cease minting the token as of February 21, 2023, which will lead to a decline in the circulating token supply of BUSD over time. Here are some of the following risk concerns we have for Artemis: - The liquidity of BUSD in Moonbeam has been gradually declining. On Stellaswap, the BUSD market's liquidity has decreased by 30% from $1.2M to $827k since the regulatory announcement against BUSD. Despite this, there is still a sufficient amount of liquidity in StellaSwap to support Artemis positions that are utilizing $158k BUSD as collateral and $276k BUSD in outstanding borrows. However, if the decline in BUSD liquidity on Stellaswap continues, it could result in higher slippage and increase the likelihood of insolvencies. ![](https://i.imgur.com/irAzZGI.png) - As it currently stands, 99.73% of the BUSD on Moonbeam is concentrated between StellaSwap and Artemis. However, if the liquidity of BUSD on StellaSwap continues to decrease, Artemis will surpass StellaSwap as the largest holder of BUSD on the network in relation to the circulating supply and could potentially lead to overweight exposure to the asset. ![](https://i.imgur.com/u4nAVpK.png) - Furthermore, there have been multiple [publications](https://www.coindesk.com/policy/2023/02/13/circle-sounded-alarm-on-paxos-told-nydfs-binances-stablecoin-wasnt-fully-backed-bloomberg/) questioning whether there are sufficient reserves to support BUSD, this could potentially lead to market uncertainty about BUSD’s reserves and cause the asset to depeg from the US dollar across all markets. ### BUSD Potential Next Steps Given the increased risk, Gauntlet is recommending a deprecation plan should the communituy decide to deprecate the Artemis BUSD market. This plan entails reducing exposure to BUSD by using the listed risk parameters. - Freeze the BUSD market. Pause both borrow and supply. - This will prevent users from opening any further positions in the liquidity pool. - Adjust the IR curves to disincentivize further supply and borrow of BUSD - Increase reserve factor to 99% for BUSD (suppliers will stop receiving interest) - This will increase BUSD reserves from $6 to ~$37 per day and incentivize suppliers to remove their BUSD positions since they are not receiving any further Supply APY. - Incrementally reduce collateral factors every 2 weeks, shown in the following table: | Rec Cadence | Initial | 2 weeks | 4 weeks | 6 weeks | | --- | --- | --- | --- | --- | | CF Reduction | .2 → .15 | .15→.1 | .1→.05 | .05→0 | | Liquidation ($) Impact | 0 | 0 | 1 | 4 | | Liquidation Accounts Total Supply Impact | 0 | 0 | $37,630.95 | $467,561.28 | | Estimated Active Collateral Usage ($) | $118.5k | $78.6k | $39k | $0k | | Estimated Loss Annualized Reserve Impact | -$612.64 | -$618.84 | -$614.19 | -$605 | Gauntlet will continue to monitor BUSD news and liquidity positions to ensure an efficient deprecation. As BUSD CF is reduced, we will update our deprecation plan as needed. Depending on developing BUSD market behavior and regulatory risk, certain adjustments may need to be expedited. ## Methodology This set of parameter updates seeks to maintain the overall risk tolerance of the protocol while making risk trade-offs between specific assets. Gauntlet’s parameter recommendations are driven by an optimization function that balances 3 core metrics: insolvencies, liquidations, and borrow usage. Parameter recommendations seek to optimize for this objective function. Our agent-based simulations use a wide array of varied input data that changes on a daily basis (including but not limited to asset volatility, asset correlation, asset collateral usage, DEX / CEX liquidity, trading volume, expected market impact of trades, and liquidator behavior). Gauntlet’s simulations tease out complex relationships between these inputs that cannot be simply expressed as heuristics. As such, the input metrics we show below can help understand why some of the param recs have been made but should not be taken as the only reason for recommendation. To learn more about our methodologies, please see the Helpful Links section at the bottom. ## Supporting Data The below figures show trends on key market statistics regarding borrows and utilization that we will continue to monitor: ### Top 10 Borrowers’ Aggregate Positions & Borrow Usages ![](https://i.imgur.com/Io3Dmh9.png) This large BTC whale account 0xb4B7c91a46C7d4BFFe99D2ce4b056a5B280ed8e3 opened a borrowable position Feb 15th. ### Top 10 Borrowers’ Entire Supply ![](https://i.imgur.com/d0NIxHS.png) ### Top 10 Borrowers’ Entire Borrows ![](https://i.imgur.com/bgTG9ce.png) ### Utilization Rate Over Time ![](https://i.imgur.com/b8RKrR0.png) ### Borrow Cap Utilization ![](https://i.imgur.com/NKzyhH8.png) ### Individual Account Analysis Gauntlet wants to notify the community about account 0xb4B7c91a46C7d4BFFe99D2ce4b056a5B280ed8e3 opening an borrow position on Moonwell. This account has a large position representing 99% of WBTC.wh supply on Artemis. The supply balance for this account represents 92% of the circulating supply of WBTC.wh. ## Position on Artemis ![](https://i.imgur.com/ONgaEFQ.png) ## Borrow Usage ![](https://i.imgur.com/ZDWUvqp.png) The position is taking a small recursive position in Artemis. Our models and date do not estimate any impactful risk of insolvency. ## Risk Dashboard The community should use Gauntlet’s [Gauntlet’s Artemis Risk Dashboard](https://gov.gauntlet.network/artemis) to better understand the updated parameter suggestions and general market risk in Artemis. Value at Risk represents the 95th percentile **insolvency value** that occurs from simulations we run over a range of volatilities to approximate a tail event. Liquidations at Risk represents the 95th percentile **liquidation volume** that occurs from simulations we run over a range of volatilities to approximate a tail event. ![](https://i.imgur.com/qfCZAy7.png) ## Quick Links *Please click below to learn about our methodologies:* [Gauntlet Parameter Recommendation Methodology](https://medium.com/gauntlet-networks/gauntlets-parameter-recommendation-methodology-8591478a0c1c) [Gauntlet Model Methodology](https://medium.com/gauntlet-networks/gauntlets-model-methodology-ea150ff0bafd) *By approving this proposal, you agree that any services provided by Gauntlet shall be governed by the terms of service available at gauntlet.network/tos.*

    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