Hi, @Gauntlet Team,
Thanks for your detailed responses about parameter determination for Compound protocol markets and collateral. Your expertise is valuable for our Compound Sandbox project.
However, some aspects need clarification or further detail. We look forward to your responses to the additional questions below to better understand your methodologies.
To deliver a solid outcome, we’re also inviting https://www.chainrisk.xyz/ led by @Sudipan_Chainrisk to join us in refining calculations based on the material provided by Gauntlet above and the set of clarifying questions listed below. We appreciate your contribution.
Clarification list
Collateral Parameters:
- Could you provide detailed quantitative examples of how price impact thresholds influence BorrowCollateralFactor adjustments?
- How are historical liquidation premiums quantified for determining LiquidateCollateralFactor?
- Are there specific metrics or thresholds (e.g., slippage or deposit concentration) that guide SupplyCap limits?
- Have you ever had a situation where you increased the buffer between borrowCF and liquidateCF? Can you give an example?
- Does the buffer size depend on the frequency of price updates by Oracle?
- What limits do you know for volatile tokens in the current Compound V3? How volatile tokens can be used with each other. For the AERO market, the collateral factor for USDC is already 65%.
- How much does the frequency of updating oracles affect the risks? If somebody provides oracles with higher price update rates, is it possible to improve the use of collators?
Interest Rate Curve:
- How do kink adjustments differ across asset classes or market conditions?
- What stress-testing methodologies are used to validate slope adjustments?
Storefront Price Factor & Target Reserves:
- Could you share case studies or examples showing adjustments to the Storefront Price Factor?
- What is the exact framework for linking liquidation risks to reserve targets?
Your input on these areas would be immensely helpful in refining our design and ensuring robust implementation. Thank you again for your continued support and collaboration.