Configuration Maintenance
Vote Result: YES
Rationale
Housekeeping exercises like this one are sensible and making it as clean as possible to update asset parameters is good hygiene. Therefore, we will vote YES in favour of this proposal.
Onboard eUSDe and eUSDe based PT Token to Aave V3 Core
Vote Result: YES
Rationale
Pendle PT tokens have a significant amount of demand and the remaining days of maturity, when compared to the amount of usage that could flow in for that period of time, make this onboarding profitable for Aave. The PT yield from Ethena’s points program is enough of a carrot to attract users. Therefore, we will vote YES in favour of this proposal.
stkAAVE Emissions
Vote Result: YES
Rationale
Ensuring stkAAVE emissions last until Umbrella launch is sensible; therefore, we will vote YES in favour of this proposal.
[ARFC] Aave Umbrella Activation
Vote Result: YES
Rationale
As we have voted for previously, we are completely in favour of Umbrella. Activating Umbrella in clear alignment with the service providers is a good move, as is starting Umbrella with some of the highest quality assets on Aave. Progressively deprecating the current Safety Module also makes sense. Therefore, we will vote YES in favour of this proposal.
[TEMP CHECK] Adopt The SEAL Safe Harbor Agreement
Vote Result: YES
Rationale
The SEAL Safe Harbor Agreement is a step up to protect Aave’s security infrastructure, especially in the absence of a pause function. Having a set of standardised rules of engagement for white hats to intervene during active exploits allows the protocol to be protected in difficult situations. The Safe Harbor Agreement has been vetted and is from a reputable team, with the provisions included being well thought out and applicable to Aave. Therefore, we will vote YES in favour of this proposal.
CAPO Adapter Maintenance Update
Vote Result: YES
Rationale
Updating the CAPO adapters to the latest version is logical and will enable stablecoins to work seamlessly across Aave v2 and v3. Therefore, we will vote YES in favour of this technical proposal from BGD Labs.
Onboarding wETH to Aave V3 Celo Instance
Vote Result: YES
Rationale
This is the onchain proposal for this Snapshot ARFC that we voted YES in favour of according to our rationale here. Therefore, we will vote YES in favour of this proposal as well.
Add FBTC to Aave v3 Main Market on Ethereum
Vote Result: YES
Rationale
This is the onchain proposal for this Snapshot TEMP CHECK that we voted YES in favour of according to our rationale here. Therefore, we will vote YES in favour of this proposal as well.
Aave V3.3 Soneium Activation
Vote Result: YES
Rationale
This is the onchain proposal for this Snapshot ARFC that we voted YES in favour of according to our rationale here. Therefore, we will vote YES in favour of this proposal as well.
Aave Umbrella Activation
Vote Result: YES
Rationale
We have voted in favour of activating Umbrella multiple times and will vote YES again here to finally activate the system.
May Funding Part B
Vote Result: YES
Rationale
This is an operational Aave Finance proposal that we will vote YES in favour of.
[ARFC] Aave Events & Sponsorship Budget 2025
Vote Result: YES
Rationale
Aave’s event strategy has been amongst the most successful in the space, with clear and distinctive events across the larger conferences, including rAAVE. The side events cover multiple conferences and seem reasonable. The 2024 events strategy was well-designed and operated - having $160k in unspent funds is a positive sign. One question would be whether the remainder of the 2024 funds will be spent on top of the requested $750k GHO, or whether they are part of the $750k GHO.
All in all, we will vote YES in favour of this proposal.
Asset Parameters Optimization
Vote Result: YES
Rationale
Adjusting the RFs and uOpt for these assets is necessary given their usage on the platform. Both risk providers are in support of this proposal as well.
We’re only wary about the impact on CRV; it would be best to ensure that capital does not migrate to other lending venues. rlUSD also has a significant market size and any changes made should be measured and take any large impact into account.
All in all, we will vote YES in favour of this proposal.
[ARFC] Onboard wrsETH to ZKsync V3 Instance
Vote Result: YES
Rationale
Both LlamaRisk and Chaos Labs are in favour of onboarding wrsETH. Moreover, wrsETH/wstETH is a popular eMode on Aave and its usage has grown over time. Therefore, we will vote YES in favour of this proposal.
[TEMP CHECK] Add XAUt to Aave V3 Core Instance
Vote Result: YES
Rationale
XAU₮ has no legal risk to being onboarded, and given that other lending platforms are onboarding the asset and that it is issued by Tether, which has significant reach in the space, it makes sense to move this proposal forward to the ARFC stage. As per our comment, we would like to see demand and revenue analysis for this asset. All in all, we will vote YES in favour of this proposal.
June Funding Update - Part I
Vote Result: YES
Rationale
This is an operational Aave Finance proposal that we will vote YES in favour of; the anticipated expenses are fair in terms of service provider renewals, AAVE buybacks according to the AAVEnomics proposal, and Merit and Ahab programs.
Chaos Labs x Aave DAO — Early Renewal Proposal
Vote Result: YES
Rationale
As per our comment, Chaos Labs has been a cornerstone of getting Aave to where it is right now in the market, and it is clear they have taken on more scope than outlined in their last renewal. The Edge system has been a huge value-add to the DAO in terms of automating risk management and taking off the burden from service providers. Therefore, we will vote YES in favour of this proposal.
[ARFC] Addition of USDe to Ethena Principal Token Stablecoin E-Modes
Vote Result: YES
Rationale
As per our comment, USDe has gained a lot of traction over the last few months and as such merits being included in the stablecoin e-mode for users to switch their debt between multiple stablecoins. Moreover, the proposal adds only minimal incremental risk and gives significant flexibility to users, while being approved of by the risk providers. Therefore, we will vote YES in favour of this proposal.