[ARFC] Optimize ETH-Correlated Asset Parameters
Vote Result: YES
Rationale
These changes would limit the negative yield experience for long-term Aave users and avoid the ETH utilisation being pushed above the kink. It is important to not penalise long-term Aave users and make these changes to accommodate their leveraged positions. Therefore, we will vote YES in favour of this proposal.
[TEMP CHECK] Onboard artMETIS to Aave V3 on Metis Market
Vote Result: YES
Rationale
Exploring the addition of artMETIS to the Metis market on Aave v3 is logical given that it is the largest LST protocol on the Metis network, and that listing it will lead to increased liquidity, market expansion, and user adoption, while enabling leveraged lending and benefiting from the incentives allocated by the Metis Foundation. These reasons make us believe that it is worth having Chaos Labs and LlamaRisk assess the merits of adding artMETIS onto the v3 Metis market. Therefore, we will vote YES in favour of this proposal.
[TEMP CHECK] AL Service Provider Proposal
Vote Result: YES
Rationale
Given our previous thoughts on v4, and the clear deliverables and timeframe outlined in this proposal, combined with the relatively reasonable cost of $12M GHO over 1 year to develop v4, approving this proposal is a no-brainer. From a cost-benefit perspective, this proposal seems entirely positive. Moreover, to alleviate any concerns about ‘other service providers being able to do this for a lower cost’, Aave Labs has institutional experience and history with Aave and is best placed to join the ranks as a service provider and develop v4 under the scope outlined. This proposal also addresses the feedback post v3’s development where there was a retroactive payment made - asking for the funds at the start is the best move to make and aligns Aave Labs with other Aave service provider models.
Therefore, we will vote YES in favour of this proposal.
[ARFC Addendum] Update Asset Onboarding Framework
Vote Result: YES
Rationale
Updating the Asset Onboarding Framework with this small addition will streamline the process for the DAO and make the market less vulnerable to market manipulation and issues. Therefore, we will vote YES in favour of this proposal.
[ARFC] Set ACI as Emission Manager for Liquidity Mining Programs
Vote Result: YES
Rationale
The ACI has already been doing this join and setting the ACI multisig as the emission manager will streamline the process for Aave. We would encourage the ACI to post regular updates about the incentives sent to and distributed from their multisig, and the success of these incentive programs, to enable greater transparency for the DAO. Therefore, we will vote YES in favour of this proposal.
Onboarding ETHx to Aave V3 Ethereum
Vote Result: YES
Rationale
BGD Labs, Chaos Labs, and LlamaRisk are all in favour of onboarding ETHx and providing diversity in terms of LSTs on Aave is beneficial for the protocol. ETHx has established itself in the market in the last few months and its yield and peg have remained stable, making the risk of listing it on Aave lower. A concern remains the lower liquidity of the asset and the influence of EigenLayer, and these must be kept in mind when determining the risk parameters for the asset. Therefore, we will vote YES in favour of this proposal.
[ARFC] Deployment of Aave on zkSync
Vote Result: YES
Rationale
Deploying Aave on zkSync as one of the more innovative ZK rollups makes sense. Chaos Labs and LlamaRisk are in favour of the deployment and agree on the proposed parameters. It is to be expected that liquidity conditions are low, and slippage is high, as the zkSync dApp and DeFi ecosystem is not yet developed enough. Therefore, we would prefer more conservative parameters set, and the assets that are proposed to be listed (USDC, USDT, wETH, wstETH) are assets with higher liquidity and usage across DeFi. Adding other assets once liquidity increases is logical and Aave having a presence on zkSync and helping the network scale its DeFi ecosystem is beneficial for both zkSync and Aave.
Therefore, we will vote YES in favour of this proposal.
[TEMP CHECK] Deploy Whitelabel Aave V3 Market - Reental
Vote Result: YES
Rationale
Given that Aave v3 is built on an open codebase and forking it does not require permission to be taken from the Aave DAO, we have no issue with Reental deploying a whitelabel version of Aave v3 on Polygon if there are no costs for the Aave DAO. Offering 20% of the fees generated to the DAO is generous in our opinion and we are generally in favour of RWAs. Therefore, we will vote YES in favour of this proposal.
[ARFC] Onboard USDC.e to Aave V3 Gnosis Chain
Vote Result: YES
Rationale
Onboarding USDC.e on v3 Gnosis is beneficial for users since it creates a better cross-chain experience, interoperability with Circle products, and standardises transfers. Moreover, there is no migration required by holders and applications, addresses, and balances are maintained. Using the Bridged USDC Standard is a logical step and will make it easier for Circle to deploy native USDC on Gnosis. Both risk providers are also in favour of this proposal. Therefore, we will vote YES in favour of this proposal.
[TEMP CHECK] Deploy a Lido Aave v3 Instance
Vote Result: YES
Rationale
Exploring a Lido-specific Aave v3 instance makes sense if all the revenue generated by this instance is transmitted back to the Aave DAO. Enabling leveraged looping through this instance and making it as profitable and efficient as possible for users while isolating risk is an interesting proposition and one we’d like to explore further in the ARFC stage. However, our vote at this point does not indicate full support at the ARFC stage given that we’d like @EzR3aL and @WintermuteGovernance’s queries answered and more clarity to be provided on the nature of this deployment.
Therefore, we will vote YES in favour of this proposal.
GHO Cross-Chain - Part 1
Vote Result: YES
Rationale
This is the on-chain vote for this Snapshot ARFC that we voted in favour of according to our rationale here. Therefore, we will vote YES in favour of this proposal as well.
Optimize ETH-Correlated Asset Parameters
Vote Result: YES
Rationale
This is the on-chain vote for this Snapshot ARFC that we voted in favour of according to our rationale here. Therefore, we will vote YES in favour of this proposal as well.
[ARFC] Aave Liquidity Committee Funding Phase III
Vote Result: YES
Rationale
The ALC has done a great job over the first two phases to get GHO on track and on peg, and increase liquidity for GHO while encouraging integrations and use cases across DeFi. The achievements made by the ALC speak for themselves and funding the ALC further to bolster GHO, which is one of Aave’s key revenue drivers now and in the future, is important. We think a budget of 600k GHO for Ethereum and 375k for Arbitrum is more than fair enough and would have even funded a larger amount given the criticality of GHO for Aave. The aims for Phase III are outlined well and make sense - reduced volatility and deeper liquidity for GHO are worthy goals and will consolidate its stability. We think the utility of GHO can be even more enhanced by incentivising further integrations across DeFi through grants.
All in all, we will vote YES in favour of this proposal.
[ARFC] AL Service Provider Proposal
Vote Result: YES
Rationale
This is the Snapshot ARFC for this TEMP CHECK that we voted in favour of according to our rationale here. Therefore, we will vote YES in favour of this proposal as well.
Set ACI as Emission Manager for Aave Liquidity Mining Program
Vote Result: YES
Rationale
This is the on-chain vote for this Snapshot ARFC that we voted in favour of according to our rationale here. Therefore, we will vote YES in favour of this proposal as well.
Set ACI as Emission Manager on the Avalanche Network
Vote Result: YES
Rationale
This is the on-chain vote for this Snapshot ARFC that we voted in favour of according to our rationale here. Therefore, we will vote YES in favour of this proposal as well.
Onboard sUSDe to Aave V3 on Ethereum
Vote Result: YES
Rationale
This is the on-chain vote for this Snapshot ARFC that we voted in favour of according to our rationale here. Therefore, we will vote YES in favour of this proposal as well.
GHO Cross-Chain - Part 2
Vote Result: YES
Rationale
This is the on-chain vote for this Snapshot ARFC that we voted in favour of according to our rationale here. Therefore, we will vote YES in favour of this proposal as well.
AL Service Provider Proposal
Vote Result: YES
Rationale
This is the on-chain vote for this Snapshot ARFC that we voted in favour of according to our rationale here. Therefore, we will vote YES in favour of this proposal as well.
[ARFC] Reduce Reserve Factor on wstETH
Vote Result: YES
Rationale
This is part of the Lido Alliance proposal passing and will make the wstETH/wETH recursive loop more economical and attractive. Therefore, we will vote YES in favour of this proposal.