daeilcha
    • 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
    # [ARC] Gauntlet Borrow / Supply Cap Updates for Aave V3 AVAX and Aave V3 OP (2023-02-24) TLDR: Please see our Specification Summary below for a synopsis of recommended changes. # Motivation Following the [Snapshot vote](https://snapshot.org/#/aave.eth/proposal/0xb4c756ac701b5cbc0ec2d832652e4f1c820aa40f7d9be18eb81f87080a52c5f1), we are updating and providing more clarity on Gauntlet's borrow and supply cap recommendations for Aave V3 markets on Avalanche and Optimism chains. Our initial recommendation for the same markets can be found [here](https://governance.aave.com/t/arc-gauntlet-borrow-supply-cap-updates-for-aave-v3-op-and-aave-v3-avax-2023-01-27/11488) and a brief description of the methodology used can be found [here](https://governance.aave.com/t/gauntlet-methodologies-borrow-and-supply-cap/11487). The above methodology has been fine-tuned based on the feedback we received from the community in our previous post. More specifically: - **For small or “non-strategic” assets**, we set `conservative` borrow and supply caps. - **For large or “strategic” assets**, we set `aggressive` borrow and supply caps. - **For assets listed on V2 Avalanche**, we aim to accomodate the migration from V2 to V3. Generally, we considered it safer for the protocol to deviate from our initial recommendations to allow migration to V3 to continue rather than leave assets on Aave V2. - For liquid staked tokens (LSTs) that are easily redeemable (i.e., sAVAX), we readjusted borrow and supply caps upwards by considering liquidity of the underlying token. - For very aggressive supply cap increases for assets that were near the supply cap, we limit the change to 150% of increase relative to current supply cap. We may follow up with additional recommendations for further supply increases in the future. - For supply cap decreases where the recommended values are below current supply, we limit the change to a 75% decrease relative to current supply. We may follow up with additional recommendations for further supply cap decreases in the future. - Our approach is to update borrow cap and supply cap recommendations once borrows or supplies reach 75% of their respective caps or liquidity conditions change for each respective token. - Further, we provide bridge information for assets on V3 Avalanche and V3 Optimism. We hope this information around bridges provides greater transparency to the community for their decision-making. ## Updated Parameter Recommendations ![](https://i.imgur.com/gtmFz0K.png) ## Bridged and liquid staking tokens The majority of bridged tokens on the Avalanche chain used on Aave V3 (WETH.e, AAVE.e, LINK.e, WBTC.e, DAI.e, BTC.b) are issued by [the Avalanche bridge](https://core.app/) and proof of reserves are provided on their website. FRAX is issued by [frax.finance](https://frax.finance/), MAI is issued by [mai.finance](https://www.mai.finance/), USDT is issued by [Tether](https://tether.to/en/), and USDC is issued by [Circle](https://www.circle.com/en/). sAVAX is the only liquid staking token provided by Aave V3 on Avalanche, and the staking services are provided by [BENQi](https://staking.benqi.fi/stake). For Optimism, bridging from Ethereum happens through the [official bridge](https://app.optimism.io/bridge/deposit) for all Aave V3 assets except for sUSD where [the Synthetix bridge](https://staking.synthetix.io/bridge) can be used. Bridging back to Ethereum through the native bridge introduces a 7-day delay, which can force users to use 3rd party bridges. | Chain | Asset | Issuing Entity | Official Issuance/Bridging | Estimated Days to Bridge in | Estimated Days to Bridge out | | --- | --- | --- | --- | --- | --- | | Avalanche | DAI.e | Avalanche | https://core.app/bridge/ | <1 | <1 | | Avalanche | FRAX | Frax Finance | https://app.frax.finance | <1 | <1 | | Avalanche | MAI | MAI Finance | https://www.mai.finance/ | <1 | <1 | | Avalanche | USDC | Circle | https://www.circle.com/en/ | KYC restrictions/TradFi Speeds | <1 | | Avalanche | USDt | Tether | https://tether.to/en/ | KYC restrictions/TradFi Speeds | <1 | | Avalanche | Aave.e | Avalanche | https://core.app/bridge/ | <1 | <1 | | Avalanche | BTC.b | Avalanche | https://core.app/bridge/ | <1 | <1 | | Avalanche | LINK.e | Avalanche | https://core.app/bridge/ | <1 | <1 | | Avalanche | sAVAX | Avalanche | https://core.app/bridge/ | <1 | <1 | | Avalanche | WBTC.e | Avalanche | https://core.app/bridge/ | <1 | <1 | | Avalanche | WETH.e | Avalanche | https://core.app/bridge/ | <1 | <1 | | | | | | | | Optimism | DAI | Optimism | https://app.optimism.io/bridge/ | <1 | 7 | | Optimism | sUSD | Synthetix.io | https://staking.synthetix.eth.limo/bridge | <1 | <1 | | Optimism | USDC | Optimism | https://app.optimism.io/bridge/ | <1 | 7 | | Optimism | USDT | Optimism | https://app.optimism.io/bridge/ | <1 | 7 | | Optimism | AAVE | Optimism | https://app.optimism.io/bridge/ | <1 | 7 | | Optimism | LINK | Optimism | https://app.optimism.io/bridge/ | <1 | 7 | | Optimism | WBTC | Optimism | https://app.optimism.io/bridge/ | <1 | 7 | | Optimism | ETH | Optimism | https://app.optimism.io/bridge/ | <1 | 7 | | Optimism | WSTETH | Optimism | https://app.optimism.io/bridge/ | <1 | 7 | ## Specification We provide a tailored set of recommendations below, aiming to account for the community's strategic preferences while limiting governance fatigue resulting from other ongoing parameter proposals. We hope that the below provides transparency into the risk analysis rationale. **As a result of our asset-by-asset analysis, we recommend proactively freezing new supply for several assets to mitigate outsized tail risk.** #### V3 AVAX: * Stablecoins: the majority of Gauntlet's recommendations are more aggressive than [other recommendations](https://governance.aave.com/t/arc-chaos-labs-supply-and-borrow-cap-updates-aave-v3-2023-02-24/12048?u=pauljlei). As such, we will not move forward with our stablecoin recommendations. * AAVE.e: our analysis recommends an increase in the supply cap to allow for migration, but we will not move forward with this recommendation because there is an existing proposal to increase it (that is more conservative than our recommendation). * BTC.b: we recommend decreasing the cap to below the current supply, which would effectively **freeze new supply of BTC.b**. We also recommend lowering the borrow cap. BTC.b is an asset that can pose potential risk given the size of the Aave market relative to circulating supply (over 50%). * LINK: our analysis shows that the supply cap can be higher, but we will not move forward with this recommendation because ongoing proposals are increasing it. For the borrow cap - our analysis shows that the borrow cap can be higher, but because there is still room for borrow growth under the current cap, we will not move forward with this parameter change. * sAVAX: our conservative figure is lower than other ongoing recommendations. However, if the community has an Aggressive risk preference, the ongoing recommendations may be preferred. Thus, we will not move forward with our recommendation. * AVAX: we recommend decreasing the supply cap and implementing a borrow cap. * WBTC.e: we recommend decreasing the supply cap and implementing a borrow cap. * WETH.e: we recommend decreasing the supply cap and decreasing the borrow cap. #### V3 Optimism * Stablecoins: the majority of Gauntlet's recommendations are more aggressive than ongoing recommendations. As such, we will not move forward with our stablecoin recommendations. * AAVE: we recommend decreasing the cap to below the current supply, which would effectively **freeze new supply of AAVE**. AAVE is an asset that can pose potential risk given the size of the market relative to the circulating supply. * LINK: we recommend lowering the supply and borrow caps. * WBTC: current supply is greater than even our Aggressive recommendation (624). As such, we recommend lowering the supply cap, which would effectively freeze new supply of WBTC and also lower the borrow cap. * ETH: our recommendations are more aggressive than the current caps. Because the current caps still allow room for growth, we will not move forward with these recommendations. ### Specification Summary For better user experience, we round the recommendations to an easily interpretable number. #### Asset parameter current parameter recommended parameter notes ### V3 AVAX | Asset | Parameter | Current Parameter | Recommended Parameter | Notes | | --- | --- | --- | --- | --- | | BTC.b | Supply Cap | 5,800 | 3,000 | Effectively freeze supply | | BTC.b | Borrow Cap | 3,190 | 900 | --- | | AVAX | Supply Cap | 13,100,000 | 3,800,000 | --- | | AVAX | Borrow Cap | NA | 1,200,000 | At this cap, utilization would be 80% | | WBTC.e | Supply Cap | 5,233 | 2,000 | --- | | WBTC.e | Borrow Cap | NA | 1,100 | --- | | WETH.e | Supply Cap | 113,000 | 38,000 | --- | | WETH.e | Borrow Cap | 62,150 | 33,000 | --- | ### V3 OP | Asset | Parameter | Current Parameter | Recommended Parameter | Notes | | --- | --- | --- | --- | --- | | AAVE | Supply Cap | 100,000 | 45,000 | Effectively freeze supply | | LINK | Supply Cap | 258,000 | 160,000 | --- | | LINK | Borrow Cap | 141,900 | 84,000 | --- | | WBTC | Supply Cap | 1,100 | 620 | Effectively freeze supply | | WBTC | Borrow Cap | 605 | 250 | --- | *<sup>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.<sup>*

    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