memoscan

0x9373…658a

All memos sent from and to 0x9373…658a.
0x93738d2a…658asent to0x683a4f99…6c02·#21,017,082·0x1683d6fb…c7e32c
addAsset((address,uint256,bool,address))removeAsset(address)setHooks(address)approve(address,uint256)_reduceReserves(uint256)approve(address,uint256)_reduceReserves(uint256)approve(address,uint256)deposit((address,uint256)[]) o# Aera <> Compound Extension ## Simple Summary For over a year, the Compound DAO has used Aera for treasury management. This proposal builds upon prior work to further operationalize the DAO's treasury. There is currently an excess of USDC and DAI reserves in Compound V2, which could be deployed in lending markets to generate yield for the treasury. Additionally, a portion of the ETH in the Compound Treasury can be utilized to generate yield. This continuation of the existing programs will enable the DAO to drive a new yield source. The expected impact of this proposal is $30M~ in additional Compound V3 TVL and $1M+ in additional treasury revenue via yield generation. Deployment details: * Compound Treasury (2,000 ETH) * Compound V2 Reserve Assets (15M DAI and 10M USDC) * The vault’s objective function will be updated from targeted volatility to yield generation. This ensures the stablecoin reserves do not get allocated to volatile assets. * The vault will continue to allocate into Compound V3 lending markets to generate yield on the underlying assets (this will be enabled in a subsequent proposal due to Compound's 10 action limit in governance proposals). For more details, please refer to the [Forum Post](https://www.comp.xyz/t/aera-for-compound-extension/5852). ## Specification This proposal is 1 of 2 proposals, the second of which will be put onchain after this one passes. The proposals are split up in order to operate within Compound's 10 action limit on proposals: 1. Add `DAI` as an asset to the vault 2. Accept ownership of a new hooks module at address `0x8A216F2C84a3fE5a51Bf57B685864A065D14C53a`. We need to deploy a new hooks module and have the Governor Bravo timelock accept ownership of it to work around a limitation in Governor Bravo that only 10 actions can be called in a single proposal. Without this workaround, adding the following function sighashes would put this proposal over that limit. This new hooks module already has all the existing hooks, plus the following new sighashes: cWETHv3 `supply` & `withdraw`, and DAI `approve` (needed to trade it for USDC) 3. Remove current cUSDCv3 C3PO from the asset registry. In a subsequent proposal we will be adding this back in. We are removing it due to a bug in solc and via-ir flag being able to verify the existing contract onchain (which has been successfully used for over 1 year, but cannot be verified on etherscan due to this bug). 4. Wrap a portion of the ETH currently in the timelock into WETH 5. _reduceReserves on both DAI and USDC V2 reserves 6. Approve WETH, DAI, and USDC to be deposited into the Aera vault 7. Deposit the assets into the Aera vault
0x93738d2a…658asent to0x683a4f99…6c02·#20,975,068·0x3cc9c370…c02400
addAsset((address,uint256,bool,address))addAsset((address,uint256,bool,address))setHooks(address)approve(address,uint256)_reduceReserves(uint256)approve(address,uint256)_reduceReserves(uint256)approve(address,uint256)deposit((address,uint256)[])# Aera <> Compound Extension ## Simple Summary For over a year, the Compound DAO has used Aera for treasury management. This proposal builds upon prior work to further operationalize the DAO's treasury. There is currently an excess of USDC and DAI reserves in Compound V2, which could be deployed in lending markets to generate yield for the treasury. Additionally, a portion of the ETH in the Compound Treasury can be utilized to generate yield. This continuation of the existing programs will enable the DAO to drive a new yield source. The expected impact of this proposal is $30M~ in additional Compound V3 TVL and $1M+ in additional treasury revenue via yield generation. Deployment details: * Compound Treasury (2,000 ETH) * Compound V2 Reserve Assets (15M DAI and 10M USDC) * The vault’s objective function will be updated from targeted volatility to yield generation. This ensures the stablecoin reserves do not get allocated to volatile assets. * The vault will continue to allocate into Compound V3 lending markets to generate yield on the underlying assets. For more details, please refer to the [Forum Post](https://www.comp.xyz/t/aera-for-compound-extension/5852). ## Specification This proposal will: 1. Add new assets to the vault: `DAI` and `cWETHv3` Pricer, which prices the vault's WETH lending position 2. Accept ownership of a new hooks module at address `0x8A216F2C84a3fE5a51Bf57B685864A065D14C53a`. We need to deploy a new hooks module and have the Governor Bravo timelock accept ownership of it to get around a limitation in Governor Bravo that only 10 actions can be called in a single proposal. Without this workaround, adding the following function sighashes would put this proposal over that limit. This new hooks module already has all the existing hooks, plus the following new sighashes: cWETHv3 `supply` & `withdraw`, and DAI `approve` (needed to trade it for USDC) 4. Wrap a portion of the ETH currently in the timelock into WETH 5. _reduceReserves on both DAI and USDC V2 reserves 6. Approve WETH, DAI, and USDC to be deposited into the Aera vault 7. Deposit the assets into the Aera vault
0x93738d2a…658asent to0x7b3c54e1…cc33·#20,214,270·0x486fa253…a9ee7d
createRetryableTicket(address,uint256,uint256,address,address,uint256,uint256,bytes)setBaseBorrowMin(address,uint104)setBaseMinForRewards(address,uint104)deployAndUpgradeTo(address,address)# [Gauntlet] - WETH Arbitrum v3 Global Param Updates ## Simple Summary Gauntlet recommends the following Comet parameter updates for the Arbitrum WETH comet: - Decrease Base Borrow Min from 0.1 WETH to 0.000001 WETH - Decrease Base Min for Rewards from 1000 WETH to 100 WETH ## Motivation Gauntlet recommends to adjust these params to match the setting on Base WETH Comet. The adjustment to lower BASE Borrow Min will allow users to borrow lower amounts of WETH and Base Min Rewards the adjustment will allow the incentives to kick off earlier within the market. [Full proposal and forum discussion](https://www.comp.xyz/t/add-eth-market-on-arbitrum/5252/11?u=gauntlet) ## Specification The proposal updates the setBaseBorrowMin and setBaseMinForRewards by using the respective methods on the Configurator. *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.*
0x93738d2a…658asent to0x683a4f99…6c02·#20,119,227·0x6917e652…e2915a
sendMessage(address,bytes,uint32)updateAssetSupplyCap(address,address,uint128)updateAssetLiquidationFactor(address,address,uint64)updateAssetSupplyCap(address,address,uint128)deployAndUpgradeTo(address,address)# [Gauntlet] Optimism USDC Risk Recommendations - 06-17-24 # Simple Summary Gauntlet recommends the following risk parameter updates for the **Optimism v3 USDC comet**: - Increase WBTC Liquidation Penalty from 5% to 10% - Increase WBTC Supply Cap from 60 to 120 - Increase OP Supply Cap from 700,000 to 1,400,000 ## Motivation Gauntlet recommends adjusting the risk parameters to increase capital efficiency within the Comet. [Full proposal and forum discussion](https://www.comp.xyz/t/gauntlet-optimism-usdc-risk-recommendations-05-20-2024/5263) ## Specification The proposal updates the Supply Cap and Liquidation Factor by using the respective methods on the Configurator. ***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.***
0x93738d2a…658asent to0x7b3c54e1…cc33·#19,962,220·0x8f346dbd…027b13
_grantComp(address,uint256)_grantComp(address,uint256)approve(address,uint256)depositERC20To(address,address,address,uint256,uint32,bytes)_grantComp(address,uint256)approve(address,uint256)outboundTransferCustomRefund(address,address,address,uint256,uint256,uint256,bytes)# [Gauntlet] Rewards Contract Top-Up for BASE, Ethereum, and Arbitrum (05/27/24) ## Simple Summary Gauntlet recommends adding COMP to the reward contracts of Base, Ethereum, and Arbitrum: | Chain | Reward Amount | | --- | --- | | Ethereum | 28,000 | | Base | 3,600 | | Arbitrum | 2,250 | For more details, see the full forum post [here](https://www.comp.xyz/t/gauntlet-rewards-contract-top-up-for-base-ethereum-and-arbitrum-05-24-24/5278). <sub> 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. </sub>
0x93738d2a…658asent to0x7b3c54e1…cc33·#19,415,574·0xd1d0b85e…54d6c0
setGuardianAndFeeRecipient(address,address)addAsset((address,uint256,bool,address))addAsset((address,uint256,bool,address))setHooks(address)# Aera Pilot Update **Simple summary** This proposal improves the execution and yield of the Compound Aera Vault pilot: 1. Allows the vault to use Milkman from CoWSwap when trading BAT. a. Liquidity conditions have severely deteriorated onchain for BAT since the initiation of this pilot, requiring additional exchange integration with Milkman in order to tap into offchain liquidity 2. Adds cUSDCv3 as an allowed asset in the asset registry, enabling the vault to earn yield and provide liquidity to Compound with its USDC 3. Changes the guardian address, a hygiene update for the Guardian as Gauntlet migrates some internal Guardian infrastructure This proposal does not change the goals of the Aera pilot (diversification out of BAT and ZRX, and managing the proceeds in a volatility-targeted vault), it is simply an update to the existing vault to better enable these goals. It similarly does not change any of the security properties of Aera, the vault is still non-custodial and only the Compound DAO can withdraw/pause the vault. **Motivation** *Milkman* After starting the pilot, BAT has been very difficult to sell on-chain. So far the vault has been able to sell roughly $55k of BAT and there is another $57k remaining in the vault. Since the pilot program began, we have added support in Aera for CoWSwap’s Milkman contract with the goal of increasing the available liquidity for BAT swaps. This integration allows us to dynamically adjust execution price as the market price changes and taps into a network of solvers that are able to fill these orders efficiently and competitively using offchain liquidity. We expect that this will enable the Aera Vault to swap 10x more BAT at same 100bps slippage bounds (increasing daily volume from $300-$800/day to $2k-$5k/day). Of course, this is just based on current liquidity conditions and existing solvers, and given that market liquidity is dynamic this could change. *cUSDCv3* We have also heard the community’s feedback on including cUSDCv3 as an asset in the vault and allocating the existing USDC in the vault into cUSDCv3. The benefits for the DAO would be as such: 1. Provide additional USDC liquidity to the Compound III ETH comet 2. Generate yield on an otherwise idle asset in the vault In the limited scope of the pilot, the actual need for this capital to cover insolvencies is dwarfed by the other reserves in the system (both V2 and V3 have over >$50M in reserves compared to the <$500k USDC in the pilot). [Full forum post](https://www.comp.xyz/t/proposal-aera-compound-pilot-operational-update/5003) ****************************Specification**************************** This proposal will: 1. Add new assets: 1. COMP, which we'll receive as rewards from lending USDC 2. cUSDCv3 Pricer, which prices the vault's lending position 2. Accept ownership of new hooks module at address 0x7A8E7F9490fb927d20835b97578E521c97720f64. We need to deploy a new hooks module and have the Governor Bravo timelock accept ownership of it to get around a limitation in Governor Bravo that only 10 actions can be called in a single proposal. Without this workaround, adding the following function sighashes would put this proposal over that limit. This new hooks module already has all the existing hooks, plus the following new sighashes: 1. Milkman Router: `requestSell`, `cancelSell`, `claim` 2. BAT: `transfer`, to move the token into the Milkman swap contract 3. ZRX: `transfer`, to move the token into the Milkman swap contract if needed in the future 4. cUSDCv3: `supply` & `withdraw` 5. Comet Rewards: `claim` 6. COMP: `approve` & `transfer`, to move the token into the Milkman swap contract if needed in the future 3. Change the guardian to our new guardian address: 0x7587D73Ec14157440c01485555F81F31cF6c549e. (The fee recipient will also change, but this is moot because fees are fixed at 0 for this pilot)
0x93738d2a…658asent to0x683a4f99…6c02·#19,314,633·0xe8bd0ca4…b7cb51
setTargetReserves(address,uint104)deployAndUpgradeTo(address,address)# [Gauntlet] 2023-02-26: Ethereum v3 USDC - targetReserves Recommendations ## Simple Summary Gauntlet recommends the following risk parameter updates for the Ethereum v3 USDC comet: - Increase TargetReserves from 5M to 20M. ## Motivation Gauntlet recommends increasing the targetReserves in Ethereum v3 USDC from 5M to 20M in order to allow the buyCollateral function to successfully be called in the future even when the comet’s USDC reserves exceed 5M. For more details, see the full forum post [here](https://www.comp.xyz/t/gauntlet-ethereum-v3-usdc-targetreserves-recommendations-02-21-2024/5002). ## Specification This proposal updates the targetReserves in Ethereum v3 USDC comet *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.*
0x93738d2a…658asent to0x683a4f99…6c02·#18,715,720·0x168fcde8…7325ad
_setCollateralFactor(address,uint256)_setCollateralFactor(address,uint256)_setCollateralFactor(address,uint256)_setCollateralFactor(address,uint256)_setCollateralFactor(address,uint256)_setCollateralFactor(address,uint256)_setCollateralFactor(address,uint256)_setMarketBorrowCaps(address[],uint256[])# [Gauntlet] 2023-12-04: Compound v2 Deprecation (Phase 5) ## Simple Summary A proposal from Gauntlet to adjust 8 Compound v2 risk parameters for Phase 4 of the Compound v2 Deprecation. Gauntlet recommends the following changes: * Decrease **cAAVE Collateral Factor** from 58% to **53%** * Decrease **cCOMP Collateral Factor** from 45% to **40%** * Decrease **cLINK Collateral Factor** from 64% to **59%** * Decrease **cMKR Collateral Factor** from 58% to **53%** * Decrease **cSUSHI Collateral Factor** from 52% to **47%** * Decrease **cYFI Collateral Factor** from 60% to **55%** * Decrease **cZRX Collateral Factor** from 50% to **45%** * Decrease **cWBTC2 Borrow Cap** to **250** For more details, see the full forum post [here]( https://www.comp.xyz/t/gauntlet-compound-v2-deprecation-phase-5-11-29-23/4857 ). ## Motivation In this [September 2022 snapshot vote](https://snapshot.org/#/comp-vote.eth/proposal/bafkreiar7qfbmmabclsogilncy542cyenehjulmdhhewuzojdooer4tnje), the community voted that each asset’s Collateral Factor may be reduced by an absolute percentage of up to 5%. After our analysis, Gauntlet recommends this max 5% decrease for each lowly supplied collateral asset in order to further deprecate the v2 market. Additionally, this proposal decreases the cWBTC2 Borrow Cap to 250. [Full proposal and forum discussion](https://www.comp.xyz/t/gauntlet-compound-v2-deprecation-phase-5-11-29-23/4857) ## Specification The proposal updates the parameters using the `_setCollateralFactor` methods of the relevant cToken contracts and the `_setMarketBorrowCaps` method of the Comptroller contract. *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.*
0x93738d2a…658asent to0x3630220f…6431·#18,463,134·0x1bd0a894…adc112
Hi, this is Matt from Gauntlet. We noticed you're delegating to our old Arbitrum address (0x683a4f9915d6216f73d6df50151725036bd26c02). Would you mind updating your delegation to our new address? It is 0x11cd09a0c5b1dc674615783b0772a9bfd53e3a8f. Feel free to message our official Twitter account (gauntlet_xyz) to verify this message. Thanks!
0x93738d2a…658asent to0x29222093…d43e·#18,463,126·0x6d2d9dc8…75fe4f
Hi, this is Matt from Gauntlet. We noticed you're delegating to our old Arbitrum address (0x683a4f9915d6216f73d6df50151725036bd26c02). Would you mind updating your delegation to our new address? It is 0x11cd09a0c5b1dc674615783b0772a9bfd53e3a8f. Feel free to message our official Twitter account (gauntlet_xyz) to verify this message. Thanks!
0x93738d2a…658asent to0xa6470f6f…6ea4·#18,463,121·0xc7f56020…824a87
Hi, this is Matt from Gauntlet. We noticed you're delegating to our old Arbitrum address (0x683a4f9915d6216f73d6df50151725036bd26c02). Would you mind updating your delegation to our new address? It is 0x11cd09a0c5b1dc674615783b0772a9bfd53e3a8f. Feel free to message our official Twitter account (gauntlet_xyz) to verify this message. Thanks!
0x93738d2a…658asent to0x683a4f99…6c02·#18,366,524·0xf2b85d52…d339bc
createRetryableTicket(address,uint256,uint256,address,address,uint256,uint256,bytes)updateAssetSupplyCap(address,address,uint128)deployAndUpgradeTo(address,address)# [Gauntlet] Arbitrum v3 USDC Native - Risk Recommendations (2023-10-16) ## Simple Summary A proposal from Gauntlet to adjust one risk parameter in the Arbitrum v3 USDC Native comet. Gauntlet recommends the following risk parameter change: * Increase WBTC supply cap from 300 tokens to 600 tokens For more details, see the full forum post [here]( https://www.comp.xyz/t/gauntlet-arbitrum-native-usdc-risk-recommendations-10-12-23/4721 ). ## Motivation Supply cap for WBTC has recently reached 100%. This change will decrease WBTC supply cap utilization from 100% to 50%, resulting in $8.02M additional WBTC able to be supplied, to allow further long-term protocol usage and growth. [Full proposal and forum discussion](https://www.comp.xyz/t/gauntlet-arbitrum-native-usdc-risk-recommendations-10-12-23/4721) ## Specification This proposal updates the supply cap in the Arbitrum v3 USDC Native comet through the `updateAssetSupplyCap` method in the Configurator contract. *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.*
0x93738d2a…658asent to0x7b3c54e1…cc33·#18,366,131·0xc1c1d2d5…c820f4
acceptOwnership()acceptOwnership()acceptOwnership()_reduceReserves(uint256)approve(address,uint256)_reduceReserves(uint256)approve(address,uint256)deposit((address,uint256)[])# Aera Pilot Proposal **Simple summary** A proposal from Aera to initiate a free $500k pilot to diversify out of ZRX and BAT reserves (from Compound V2 ETH) and then hold the proceeds in a Volatility targeted portfolio. The vault will do the following: - Sell out of ZRX and BAT over time using onchain execution venues which minimizes onchain slippage - The initial allocation will be 80% ZRX and 20% BAT, this allocation was chosen due to onchain liquidity conditions. - The proceeds of which will be then managed in a Volatility targeted vault consisting of wstETH and USDC. - The target will be 15% portfolio volatility of the wstETH and USDC holdings Key features - This is a non custodial vault, where the Compound Governor Bravo Timelock is the owner of the vault (and thus governance votes can initiate withdraw/deposit requests at any time) - Gauntlet will be the vault guardian for this vault For more details see the forum post [here](https://www.comp.xyz/t/aera-pilot-for-compound-v2-reserves/4655). **Motivation** The Compound v2 market on Ethereum has accumulated over $45m of reserves, including USD stablecoins, WBTC, ETH, BAT, and 0x, among others. These reserves are static and do not help the DAO future proof its reserve needs particularly because there is higher than necessary exposure to long tail assets such as BAT and 0x. With the launch of Aera, there is now a purpose-built solution that simplifies and automates much of this optimization. A few key benefits for Compound: - Aera helps to minimize bureaucracy. The DAO doesn’t need to plan strategies, but rather just pick assets. - The Aera protocol regularly rebalances Compound’s portfolio based on market conditions. - Aera is non-custodial - the DAO is in control of it’s assets. [Full proposal and forum discussion](https://www.comp.xyz/t/aera-pilot-for-compound-v2-reserves/4655) ****************************Specification**************************** This proposal will 1. acceptOwnership of the Aera vault, Hooks module, and Asset Registry 2. _reduceReserves on both ZRX and BAT V2 reserves 3. approve spending on these tokens to allow them to be deposited to the Aera vault 4. deposit into the Aera vault 5. resume the Aera vault, allowing the guardian to start rebalancing
0x93738d2a…658asent to0x683a4f99…6c02·#18,214,075·0xc809ebb1…e128bf
We echo Monet's thoughts, but beyond that, we haven't seen many (there are exceptions) competitive forks be successful either. Additionally, we think these types of initiatives are better directed towards more established, strategic parties.