StableLab Delegate Platform

Kene_StableLab · October 21, 2024, 11:44am

[TEMP CHECK] Onboard EIGEN to Aave V3 Ethereum

Vote: Yes

Rationale: In our opinion with the current demand for EIGEN, we believe that the token is still too early to onboard to the Aave Protocol, we would gladly revisit this later when there is better demand.

[ARFC] Renew LlamaRisk as Risk Service Provider

Vote: Yes

Rationale: We are in support of this proposal to renew LlamaRisk’s engagement due to its scope, budget and the wealth of experience that the LlamaRisk team brings to Aave Governance.

Increase cbBTC Supply Caps

Vote: Yes

Rationale: Due to the demand for cbBTC we are in support of safely the supply caps for the asset to meet the user demand while creating value for the protocol.

[ARFC] Continuous Security Proposal Aave <> Certora

Vote: Yes

Rationale: Certora is an essential service provider for the Aave DAO, therefore we are glad to support the renewal of Certora’s engagement with the Aave DAO.

3.2 patch for legacy periphery

Vote: Yes

Rationale: We are in support of this proposal which upgrades the pool contracts to add a n extra fallback mechanism, we appreciate the design thinking that goes into Aave’s infrastructure.

[ARFC] Chaos Labs <> Aave Risk Management Service Renewal

Vote: Yes

Rationale: Risk Management is an essential aspect of the Aave Protocol, through the past contributions of Chaos Labs, we are confident that the Aave DAO will continue to benefit from Chaos Lab’s contributions.

[ARFC] Launch GHO on Base & set ACI as Emissions Manager for rewards

Vote: Yes

Rationale: We are in support of launching GHO across multiple networks which have demand for the Stablecoin, therefore we are glad to support launching GHO on Base.

[ARFC] Launch GHO on Avalanche & set ACI as Emissions Manager for rewards

Vote: Yes

Rationale: We are in support of launching GHO across multiple networks which have demand for the Stablecoin, therefore we are glad to support launching GHO on Avalanche.

[TEMP CHECK] Add rlUSD to Aave v3 Main Market on Ethereum

Vote: Yes

Rationale: We support adding rlUSD to Aave in order to give rlUSD users an opportunity to leverage this stablecoin to generate yield on Aave. Aave can boast of its safely curated variety of stablecoins which enables diverse users across the ecosystem to use Aave.

[ARFC] Remove Frax from Isolation Mode on Aave v3 Mainnet

Vote: Yes

Rationale: Due to the the synergies between the Aave and Frax ecosystem, we are in support of removing from isolation mode and onboarding sFRAX with the input of the Aave DAOs service providers.

Increase USDS Borrow Rate to Match Sky Savings Rate

Vote: Yes

Rationale: We support increasing the USDS borrow rate to Match the Sky Savings Rate, by matching these rates we ensure that the true depositors are rewarded instead of users who use looping strategies.

[TEMP CHECK] World Liberty Financial Aave v3 Instance on Ethereum Mainnet Proposal

Vote: Yes

Rationale: With 20% of the revenue from the instance going to the Aave DAO, and the strong adoption of Aave’s Tech Stack, we are in support of this Instance with WLF. We look forward to more instances with valuable protocols looking to deploy Aave Instances.

Update legacy guardian

Vote: Yes

Rationale: We support updating the permissions for the Emergency Guardians to ensure that they are well equipped to enact changes on behalf of the DAO.

Renew LlamaRisk as Risk Service Provider

Vote: Yes

Rationale: We are in support of this proposal to renew LlamaRisk’s engagement due to its scope, budget and the wealth of experience that the LlamaRisk team brings to Aave Governance.

Chaos Labs <> Aave Risk Management Service Renewal

Vote: Yes

Rationale: Risk Management is an essential aspect of the Aave Protocol, through the past contributions of Chaos Labs, we are confident that the Aave DAO will continue to benefit from Chaos Lab’s contributions.

Reserve Factor Updates Mid October

Vote: Yes

Rationale: We are in support of adjusting the Reserve Factor for Ethereum and Avalanche to encourage users to port their positions from Aave V2 to Aave V3. It is important to ensure that users port their positions to Aave V3 to enjoy more features, while the Aave protocol can increasingly protect itself from its exposure to Aave V2.

wstETH Slope1 & Uoptimal Update

Vote: Yes

Rationale: We are in support of adjusting the risk parameters for the Lido instance in order to ensure that it functions optimally and creates value for all users and the core protocol.

Kene_StableLab · October 30, 2024, 9:31am

Aave <> Certora Continuous Security Services

Vote: Yes

Rationale: Certora is an essential service provider for the Aave DAO, therefore we are glad to support the renewal of Certora’s engagement with the Aave DAO.

Onboard ezETH to Lido instance

Vote: Yes

Rationale: We support this proposal to onboard ezETH into the Aave V3 Lido instance, Aave’s commitment to LST diversity is a key feature that actively contributes to the success of the protocol.

[ARFC] Aave <> BGD Labs. Phase 4

Vote: Yes

Rationale: BGD Labs has been a valuable service provider to the Aave Protocol, therefore we are in support of continuing BGD Labs’ engagement with Aave.

[ARFC] Dolce Vita Extension

Vote: Yes

Rationale: The ACI has been doing an excellent job of coordinating the Aave DAOs operations on the Governance side, we are in support of formalising the ACI’s responsibilities in this regard.

[ARFC] Launch aUSDC GSM on Ethereum

Vote: Yes

Rationale: In order to ensure that the GSM is able to function optimally we are in support of deploying aUSDC as a more efficient approach to improving the GSM resilience.

Fix USDS Borrow Rate to Match Sky Savings Rate

Vote: Yes

Rationale: We support increasing the USDS borrow rate to Match the Sky Savings Rate, by matching these rates we ensure that the true depositors are rewarded instead of users who use looping strategies.

Aave BGD Phase 4

Vote: Yes

Rationale: BGD Labs has been a valuable service provider to the Aave Protocol, therefore we are in support of continuing BGD Labs’ engagement with Aave.

[TEMP CHECK] Onboard SCR to Aave V3 Scroll Instance

Vote: Abstain

Rationale: It is still too early to onboard SCR to the Aave V3 Scroll Instance, we would propose waiting for the token to generate significant traction before onboarding the token.

[TEMP CHECK] Onboard AUSD to Aave V3

Vote: Yes

Rationale: One of Aave’s key features is its diversity of Stablecoins, therefore we gladly support onboarding AUSD to Aave V3 Avalanche.

[ARFC]. Aave Generalized Risk Stewards (AGRS) activation

Vote: Yes

Rationale: We support empowering the Risk Stewards with the permission that they need to do their work effectively, as the service providers with the highest context it is important that decisions which relate to risk parameters are entrusted to these service providers to ensure that the protocol is safely managed in a timely manner.

Kene_StableLab · November 11, 2024, 1:11pm

[ARFC] PYUSD Reserve Configuration Update & Incentive Campaign

Vote: Yes

Rationale: We are in support of the reserve configuration and the incentive program, PYUSD has generated significant traction and this incentive program will help bolster more activity.

stkGHO Incentives

Vote: Yes

Rationale: We are in support of renewing Aave’s GHO incentives. In order to ensure that GHO reaches full adoption, it essential for Aave to continue investing in incentivising users to use GHO as a store of value.

Onboard wstETH to Aave V3 on BNB Chain

Vote: Yes

Rationale: We support adding wstETH to the Aave BNB Pool. Having multiple Liquid Staking Derivates is an important aspect of onboarding users unto Aave V3.

GHO Steward v2 Upgrade

Vote: Yes

Rationale: By activating the GHO Stewards Permission, we empower risk service providers with the permissions they need to effect necessary changes.

[TEMP CHECK] Deploy GHO Facilitator

Vote: Yes

Rationale: This proposal is a great next step towards ensuring that the demand for GHO is met across multiple chains, we support this cautious approach to meeting GHO demand.

[ARFC] Framework for Instances and Friendly Forks

Vote: Yes

Rationale: Aave’s technology has proven to be battle tested and safely innovative, with other protocols looking to leverage the Aave Codebase, it is important for Aave to have a framework to manage these partnerships with teams looking to use Aave’s tech stack.

[TEMP CHECK] Add FBTC to Aave v3 Main Instance on Ethereum

Vote: Yes

Rationale: We support onboarding FBTC to the Aave V3 Ethereum. There are clear opportunities for synergy for FBTC holders looking to participate in the broader DeFi ecosystem.

Aave Generalized Risk Stewards (AGRS) activation

Vote: Yes

Rationale: We supporting empowering the Risk Stewards with the permission that they need to do their work effectively, as the service providers with the highest context it is important that decisions which relate to risk parameters are entrusted to these service providers to ensure that the protocol is safely managed in a timely manner.

GHO CCIP Integration Maintenance (CCIP v1.5 upgrade)

Vote: Yes

Rationale: In order to ensure that the GHO CCIP functions optimally, we are in support of upgrading this component.

[TEMP CHECK] Aave Instances Strategy Shift

Vote: Yes

Rationale: We are in support of this strategic shift which proposes merging the Etherfi add Lido instances. Merging the Etherfi and Lido instances into a new “Prime” instance will consolidate liquidity around blue-chip collaterals and high-leverage correlated assets. This will create a deeper pool of liquidity for these popular assets, improving efficiency and potentially reducing borrowing costs.

Kene_StableLab · November 25, 2024, 10:02am

[TEMP CHECK] Aave Instances Strategy Shift

Vote: Yes

Rationale: We are in support of this strategic shift which proposes merging the Etherfi and Lido instances. Merging the Etherfi and Lido instances into a new “Prime” instance will consolidate liquidity around blue-chip collaterals and high-leverage correlated assets. This will create a deeper pool of liquidity for these popular assets, improving efficiency and potentially reducing borrowing costs.

[TEMP CHECK] Add PAXG to Aave v3 Main Instance on Ethereum

Vote: Yes

Rationale: With the traction gathered by the PAXG Stablecoin and the incentives allocated for this asset onboarding, we are glad to support the addition of this asset to Aave.

Safety Module stkAAVE - Re-enable Rewards

Vote: Yes

Rationale: We support renewing the Aave DAOs Safety Module rewards for another 180 days in order to ensure that the Aave DAO is capitalised in the event of a shortfall event.

Automated (Edge) AGRS Activation

Vote: Yes

Rationale: We supporting empowering the Risk Stewards with the permission that they need to do their work effectively, as the service providers with the highest context it is important that decisions which relate to risk parameters are entrusted to these service providers to ensure that the protocol is safely managed in a timely manner.

PYUSD Reserve Configuration Update & Incentive Campaign

Vote: Yes

Rationale: We are in support of the reserve configuration and the incentive program, PYUSD has generated significant traction and this incentive program will help bolster more activity.

wstETH Reserve Borrow Rate Update - Main Instance

Vote: Yes

Rationale: We are in support of lowering the borrowing rate for wstETH in order to improve utilisation from users, it is important for Aave to incentivise safe borrowing through validated parameter changes.

Onboard and Enable sUSDe liquid E-Mode on Aave v3 Mainnet and Lido Instances

Vote: Yes

Rationale: Due to the trend of sUSDe being used as collateral we are in support of enabling liquid E-Mode on Aave V3 Ethereum and Lido Instances. By allowing users borrow more against their collateral, utilisation will increase and ultimately result in more revenue for Aave.

Onboard rsETH to Aave V3 Ethereum

Vote: Yes

Rationale: From our perspective rsETH would be a valuable addition to Aave V3 Ethereum, it is important for Aave to continue to uphold LST diversity as it continues to expand.

[ARFC] [ARFC] Onboard AUSD to Aave V3 on Avalanche

Vote: Yes

Rationale: One of Aave’s key features is its diversity of Stablecoins, therefore we gladly support onboarding AUSD to Aave V3 Avalanche.

[ARFC] Onboard GHO and Migrate Streams to Lido Instance

Vote: Yes

Rationale: From our perspective onboarding GHO to the Aave V3 Lido Instance is a great step towards advancing GHO, as well as migrating service provider streams to the Aave V3 Lido Instance.

[TEMP CHECK] Aave V3 Deployment on the Spiderchain (Botanix Labs)

Vote: Yes

Rationale: In order to capture the marketshare in the Bitcoin Ecosystem, we are in support of deploying Aave V3 on the Spiderchain, Aave’s existence in diverse ecosystem’s is one of its key features that sets it apart.

[ARFC] Enable cbBTC/WBTC liquid E-Mode on Aave v3 Mainnet

Vote: Yes

Rationale: Enabling liquid E-Mode for cbBTC/WBTC will allow borrowers to improve their capital efficiency when using this asset as collateral. Additionally, this will give users the ability to borrow larger amounts of stablecoins against their cbBTC/WBTC collateral, which could increase platform utilization and revenue.

[ARFC] Enable tBTC/WBTC liquid E-Mode on Aave v3 Mainnet

Vote: Yes

Rationale: Enabling liquid E-Mode for tBTC/WBTC will allow borrowers to improve their capital efficiency when using this asset as collateral. Additionally, this will give users the ability to borrow larger amounts of stablecoins against their tBTC/WBTC collateral, which could increase platform utilization and revenue.

Kene_StableLab · December 2, 2024, 10:02am

[TEMP CHECK] Aave x Metis: Strategic Alignment Initiative

Vote: Yes

Rationale: After clarification from the Metis Team, we are in support of having a strategic alignment with Metis. The terms of this proposal seem beneficial for the Aave DAO.

[ARFC] Onboard SCR to Aave V3 Scroll Instance

Vote: Yes

Rationale: It is still too early to onboard SCR to the Aave V3 Scroll Instance, we would propose waiting for the token to generate significant traction before onboarding the token.

Enable sUSDe/USDT Liquid E-Mode on Core Instance

Vote: Yes

Rationale: Due to the trend of sUSDe being used as collateral we are in support of enabling liquid E-Mode on Aave V3 Ethereum and Lido Instances. By allowing users borrow more against their collateral, utilisation will increase and ultimately result in more revenue for Aave.

WBTC Reserve Factor and UOptimal Increase

Vote: Yes

Rationale: With demand for WBTC poised to increase with the introduction of Aave v3.2 Liquid E-Modes, we are in support of adjusting the UOptimal and Reserve Factor to boost DAO revenue without affecting demand.

[ARFC] Aave Instances Strategy Shift

Vote: Yes

Rationale: We are in support of this strategic shift which proposes merging the Etherfi amd Lido instances. Merging the Etherfi and Lido instances into a new “Prime” instance will consolidate liquidity around blue-chip collaterals and high-leverage correlated assets. This will create a deeper pool of liquidity for these popular assets, improving efficiency and potentially reducing borrowing costs.

Add dHEDGE Protocol to flashBorrowers

Vote: Yes

Rationale: Whitelisting dHEDGE Protocol as a flashborrower on Aave V3 across multiple networks would benefit both DAOs. Many of their vaults already utilize Aave V3, demonstrating their reliance on the Aave. Waiving flashloan fees for dHEDGE would make their strategies more efficient and cost-effective. This would, in turn, attract more users to both dHEDGE and Aave V3, increasing liquidity and trading volume on both protocols.

USDS borrow rate update on Core and Prime Instances

Vote: Yes

Rationale: We are in support of increasing the USDS borrow rate to stay competitive and avoid excessive borrowing.

September Funding Update - Part A

Vote: Yes

Rationale: We support the migration of funds from Aave V2 to Aave V3 Instances in order to meet our financial obligations as a DAO.

Kene_StableLab · December 10, 2024, 12:19pm

Fluid Alignment

Vote: Yes

Rationale: Due to the potential for the success of the InstaDapp Protocol and the synergy between Aave and InstaDapp, we support buying 1% of the INST circulating supply.

[ARFC] Onboard ezETH to Arbitrum and Base Instances

Vote: Yes

Rationale: We support this proposal to onboard ezETH into the Aave V3 Arbitrum and Base instance, Aave’s commitment to LST diversity is a key feature that actively contributes to the success of the protocol.

[ARFC] Add FBTC to Aave v3 Main Market on Ethereum

Vote: Yes

Rationale: We support onboarding FBTC to the Aave V3 Ethereum. There are clear opportunities for synergy for FBTC holders looking to participate in the broader DeFi ecosystem.

wstETH Reserve Update

Vote: Yes

Rationale: We are in support adjusting the UOptimal to make a greater portion of liquidity available as demand continues to grow, it is important to ensure that there is liquidity to meet the demand.

Remove Frax from Isolation Mode on Aave v3 Mainnet

Vote: Yes

Rationale: Due to the the synergies between the Aave and Frax ecosystem, we are in support of removing from isolation mode and onboarding sFRAX with the input of the Aave DAOs service providers.

[TEMP CHECK] Onboard & Enable LBTC/WBTC liquid E-Mode on Aave v3 Core Instance

Vote: Yes

Rationale: Due to the high utilisation of LBTC/WBTC as collateral for borrowing stablecoins, we are in support of enabling liquid e-mode to enable capital efficiency for borrowers.

[TEMP CHECK] Onboard & Enable eBTC/WBTC liquid E-Mode on Aave v3 Core Instance

Vote: Yes

Rationale: Due to the high utilisation of LBTC/WBTC as collateral for borrowing stablecoins, we are in support of enabling liquid e-mode to enable capital efficiency for borrowers.

[ARFC] Aave Liquidity Committee Funding Phase V

Vote: Yes

Rationale: We are in support of funding the Aave Liquidity Committee Program to continue the work required to deepen liquidity for GHO.

Kene_StableLab · December 30, 2024, 7:58am

[ARFC] Deployment of Aave on Linea

Vote: Yes

Rationale: In line with Aave’s multi-chain future, we support deploying Aave on Linea, with Linea being a zkEVM with a robust distribution network, we believe that Aave would benefit from being deployed on this zkEVM.

[ARFC] Orbit Program Renewal - Q4 2024

Vote: Yes

Rationale: The Aave delegate program has been a valuable part of Aave Governance. By incentivising delegates to participate, Aave has created an accountability layer that ensures that proposals are a minimum standard before passing through the governance process.

Onboard GHO and Migrate Streams to Prime Instance

Vote: Yes

Rationale: From our perspective onboarding GHO to the Aave V3 Prime Instance is a great step towards advancing GHO, as well as migrating service provider streams to the Aave V3 Prime Instance.

Onboard rsETH to Lido Instance

Vote: Yes

Rationale: From our perspective rsETH would be a valuable addition to Aave V3 Lido, it is important for Aave to continue to uphold LST diversity as it continues to expand.

Increase Borrow Slope1 to all Stablecoins across all Aave Instances

Vote: Yes

Rationale: We support increasing the borrow slope because it creates an opportunity for the DAO to increase revenue for the Aave DAO while maintaining competitive lending rates.

Onboard SCR to Aave V3 Scroll

Vote: Yes

Rationale: It is still too early to onboard SCR to the Aave V3 Scroll Instance, we would propose waiting for the token to generate significant traction before onboarding the token.

[TEMP CHECK] Onboard Pendle PT tokens to Aave V3 Core Instance

Vote: Yes

Rationale: At the TEMP-CHECK stage this proposal is generally a step in the right direction, however at the ARFC stage, the risk parameters must work to limit Aave’s exposure considering the possible risks for the DAO.

[ARFC] World Liberty Financial Aave v3 Instance on Ethereum Mainnet Proposal

Vote: Yes

Rationale: With 20% of the revenue from the instance going to the Aave DAO, and the strong adoption of Aave’s Tech Stack, we are in support of this Instance with WLF. We look forward to more instances with valuable protocols looking to deploy Aave Instances.

a.DI Linea path activation

Vote: Yes

Rationale: In order to ensure that Aave functions optimally on Linea, we are in support of activating the adapters necessary for the operation of Aave V3 Linea.

Aave Liquidity Committee Funding Phase V

Vote: Yes

Rationale: We are in support of funding the Aave Liquidity Committee Program to continue the work required to deepen liquidity for GHO.

Orbit Program Renewal - Q4 2024

Vote: Yes

Rationale: The Aave delegate program has been a valuable part of Aave Governance. By incentivising delegates to participate, Aave has created an accountability layer that ensures that proposals are a minimum standard before passing through the governance process.

[ARFC] TokenLogic Financial Services Provider

Vote: Yes

Rationale: TokenLogic has been a valuable service provider to the Aave DAO and we are in favour of extending this engagement.

[ARFC] Enable LBTC/WBTC liquid E-Mode on Aave v3 Core Instance

Vote: Yes

Rationale: Due to the high utilisation of LBTC/WBTC as collateral for borrowing stablecoins, we are in support of enabling liquid e-mode to enable capital efficiency for borrowers.

[ARFC] Enable eBTC/WBTC liquid E-Mode on Aave v3 Core Instance

Vote: Yes

Rationale: Due to the high utilisation of eBTC/WBTC as collateral for borrowing stablecoins, we are in support of enabling liquid e-mode to enable capital efficiency for borrowers.

[ARFC] karpatkey GHO Growth Service Provider

Vote: Yes

Rationale: karpartkey has been a valuable service provider to the Aave DAO and we are in favour of extending this engagement.

Onboard AUSD

Vote: Yes

Rationale: One of Aave’s key features is its diversity of Stablecoins, therefore we gladly support onboarding AUSD to Aave V3 Avalanche.

[TEMP CHECK] Deploy Aave v3 on BOB

Vote: Yes

Rationale: In order to gain further exposure to the Bitcoin ecosystem, we are in support of deploying Aave V3 on BOB, Aave’s multichain ambitions have been part of its biggest appeal.

[TEMP CHECK] Deploy Aave v3 on Sonic

Vote: Yes

Rationale: We are in support of deploying Aave on the Sonic network, Aave being available across most ecosystems continues to grow its diverse deposit and borrower base, which is beneficial for Aave.

[TEMP CHECK] Onboard rstETH to Aave V3 Prime Instance

Vote: Yes

Rationale: From our perspective rsETH would be a valuable addition to Aave V3 Prime Instance, it is important for Aave to continue to uphold LST diversity as it continues to expand.

[ARFC] Proposal to Remove USDS from sUSDe Liquid E-Mode in Aave Prime Instance

Vote: Yes

Rationale: In order to mitigate risk for the Aave DAO, we are in support of removing USDS and sUSDe from e-mode, it is important not to sacrifice safety for user capital efficiency, therefore we are glad to support this proposal.

[ARFC] Aave v3 Gnosis Instance Updates

Vote: Yes

Rationale: Due to the stability of GNO and numerous other assets in the Gnosis Ecosystem, we are in support of the proposed changes to the Aave V3 Gnosis Instance.

[TEMP CHECK] Deploy Aave v3 on Mantle

Vote: Yes

Rationale: In line with Aave’s multi-chain future, we support deploying Aave on Mantle, with Mantle having a robust distribution network, we believe that Aave would benefit from being deployed on this Mantle.

Funding Proposal: TokenLogic Financial Service Provider

Vote: Yes

Rationale: TokenLogic has been a valuable service provider to the Aave DAO and we are in favour of extending this engagement.

USDS Interest Rate Curve Update

Vote: Yes

Rationale: We are in support of changing the interest rate in order to regulate the USDS asset on the Ethereum and Prime Instance in view of recent market events.

weETH Risk Parameter Adjustment

Vote: Yes

Rationale: This parameter proposal will ensure that the Aave V3 WETH pool remains profitable for Aave users, this will in turn attract more deposits to the benefit of the Aave DAO.

Kene_StableLab · January 20, 2025, 10:47am

[ARFC] Add rlUSD to Core Instance

Vote: Yes

Rationale: One of Aave’s key features is its diversity of Stablecoins, therefore we gladly support onboarding rlUSD to Aave V3.

Proposal to Remove USDS from sUSDe Liquid E-Mode in Aave Prime Instance

Vote: Yes

Rationale: In order to mitigate risk for the Aave DAO, we are in support of removing USDS and sUSDe from e-mode, it is important not to sacrifice safety for user capital efficiency, therefore we are glad to support this proposal.

[ARFC]. BGD. Aave v3.3 Sherlock contest

Vote: Yes

Rationale: Aave’s continued investment into its culture of security ensures that Aave continues to operate without incident, therefore we support this proposal.

Aave v3 Gnosis Instance Updates Part 1

Vote: Yes

Rationale: Due to the stability of GNO and numerous other assets in the Gnosis Ecosystem, we are in support of the proposed changes to the Aave V3 Gnosis Instance.

Deploy 10M GHO into Aave v3 Lido Instance

Vote: Yes

Rationale: We are in support of bootstrapping initial liquidity for the Aave V3 Lido Instance by deploying 10M into the instance.

Aave v3.3 Sherlock contest funding

Vote: Yes

Rationale: Aave’s continued investment into its culture of security ensures that Aave continues to operate without incident, therefore we support this proposal and fund the contest.

Funding Proposal: karpatkey as GHO Growth Service Provider

Vote: Yes

Rationale: karpartkey has been a valuable service provider to the Aave DAO and we are in favour of extending this engagement.

Onboard ezETH to Arbitrum and Base Instances

Vote: Yes

Rationale: We support this proposal to onboard ezETH into the Aave V3 Arbitrum and Base instance, Aave’s commitment to LST diversity is a key feature that actively contributes to the success of the protocol.

[TEMP CHECK] Deploy Aave on Rootstock Network

Vote: Yes

Rationale: We are in support of deploying Aave on the Rootstock network, Aave being available across most ecosystems continues to grow its diverse deposit and borrower base, which is beneficial for Aave.

[TEMP CHECK] Add EURC to BASE Aave V3 Instance

Vote: Yes

Rationale: We are in support of onboarding EURC to the Aave V3 Base Market, with the present parameters of this proposal, we believe this asset will be a valuable addition to the Aave V3 Base market.

Onboard sUSDe and weETH to Aave v3 on zk

Vote: Yes

Rationale: We are in support of onboarding the rebranded versions of sDAI and weETH into Aave V3 zkSync. These assets have played a key role in the ecosystem therefore this an essential onboarding for zkSync.

a.DI Celo path activation

Vote: Yes

Rationale: In order to ensure that Aave functions optimally on Celo, we are in support of activating the adapters necessary for the operation of Aave V3 Celo.

[ARFC] Extend GHO Steward on Aave Prime Instance

Vote: Yes

Rationale: In order to facilitate the efficient management of GHO, we are in support of extending the GHO Steward to the Aave Prime Instance, this is especially important considering the expansion GHO ecosystem.

Kene_StableLab · January 27, 2025, 1:45pm

[ARFC] Extend GHO Steward on Aave Prime Instance

Vote: Yes

Rationale: In order to facilitate the efficient management of GHO, we are in support of extending the GHO Steward to the Aave Prime Instance, this is especially important considering the expansion GHO ecosystem.

[ARFC] Prime Instance - wstETH Borrow Rate + rsETH Supply Cap Update

Vote: Yes

Rationale: We are in support of adjusting the borrowing rate for wstETH in order to improve utilisation from users, it is important for Aave to incentivise safe borrowing through validated parameter changes. We also support the supply cap changes for rsETH.

Onboard LBTC & Enable LBTC/WBTC liquid E-Mode on Aave v3 Core Instance

Vote: Yes

Rationale: Due to the high utilisation of LBTC/WBTC as collateral for borrowing stablecoins, we are in support of enabling liquid e-mode to enable capital efficiency for borrowers.

[ARFC] Whitelist Balancer DAO to Claim Liquidity Mining Rewards

Vote: Yes

Rationale: We are in support of whitelisting Balancer DAO to claim liquidity mining rewards and distribute these rewards accordingly.

Update Lido GHO base borrow rate

Vote: Yes

Rationale: In order to incentivise users to borrow GHO on the Lido Instance we are in support of reducing the GHO borrow rate on the Prime Instance.

Set REZ, KERNEL and rsETH Emission Admin to ACI

Vote: Yes

Rationale: The ACI is a valuable and trusted member of Aave Governance, therefore we are glad to support this proposal which appoints them as an Emission Manager for REZ, KERNEL and rsETH on Aave V3.

[TEMP CHECK] Aave <> Chainlink SVR v1 integration

Vote: Yes

Rationale: We are in support of this safe approach to MEV extraction, through this proposal Aave can safely capture a significant amount of that is not currently being captured.

GHO Risk Stewards Update and GHO CCIP Integration Upgrade

Vote: Yes

Rationale: We supporting updating the Risk Stewards permissions in order to empower them to do their work effectively, as the service providers with the highest context it is important that decisions which relate to risk parameters are entrusted to these service providers to ensure that the protocol is safely managed in a timely manner.

[TEMP CHECK] Joint Incentive Program With Polygon

Vote: Yes

Rationale: While specific terms of this proposal may not be the best, we support the sentiment of Polygon launching an incentive program, we would like to see the Polygon team come back with a proposal where Polygon solely funds this incentive program.

[ARFC] Sunset stMATIC on Polygon instance

Vote: Yes

Rationale: We are in support of sunsetting stMATIC following its deprecation by Lido Governance.

[ARFC] Add EURC to BASE Aave V3

Vote: Yes

Rationale: We are in support of onboarding EURC to the Aave V3 Base Market, with the present parameters of this proposal, we believe this asset will be a valuable addition to the Aave V3 Base market.

[ARFC] Deploy stataUSDC and stataUSDT GSMs on Ethereum

Vote: Yes

Rationale: We are in support of deploying the DAOs USDC and USDT holdings into the stataUSDC and statUSDT GSMs to generate revenue passively, estimated $593.8k USD in annual revenue would be a beneficial addition to the DAOs balance sheet.

Kene_StableLab · February 22, 2025, 11:10pm

Due to the Gnosis Safe Downtime, StableLab cannot vote until Safe restores its functionalities.

We apologize for any inconvenience that this may cause.

Kene_StableLab · February 24, 2025, 9:19am

[ARFC] wstETH Borrow Rate Update

Vote: Yes

Rationale: We support adjusting the borrowing rate for wstETH to improve user usage. Aave needs to incentivize safe borrowing through validated parameter changes.

Collector upgrade

Vote: Yes

Rationale: We support upgrading the Collector Contract to allow for multiple admins, which would facilitate the efficient management of the funds collected by this smart contract.

Prime Instance - wstETH Borrow Rate + rsETH Supply Cap Update

Vote: Yes

Rationale: We support using the borrowing rate for waste to improve user utilization. Aave should incentivize safe borrowing through validated parameter changes.

[TEMP CHECK] Onboard pufETH to Aave V3 Core Instance

Vote: Yes

Rationale: We support this proposal to onboard pufETH into the Aave V3 Core Instance; Aave’s commitment to LST diversity is a key feature that actively contributes to the protocol’s success.

[ARFC] sUSD Risk Parameter Adjustment

Vote: Yes

Rationale: This parameter proposal will ensure that the Aave V3 sUSD pool remains profitable for Aave users, attracting more deposits to benefit the Aave DAO.

[ARFC] Deploy Aave v3 on Sonic

Vote: Yes

Rationale: We support deploying Aave on the Sonic network. Aave’s availability across most ecosystems continues to grow its diverse deposit and borrower base, which benefits Aave.

sUSDe and USDe Price Feed Update

Vote: Yes

Rationale: This proposal must ensure that the price feeds for sUSD and USDe stay consistent and do not cause artificial volatility for the insets.

[ARFC] Supply and Borrow Cap Risk Oracle Activation

Vote: Yes

Rationale: We support activating the Supply and Borrow Cap RIsk Oracle. It is essential to empower risk service providers to manage supply and borrow caps actively.

[ARFC] Adjust Risk Parameters for Aave V2 and V3 on Polygon

Vote: Yes

Rationale: Polygon Governance is considering a proposal to change the risk profile of these risk assets. We support these risk parameter changes to Aave V2 and V3 Polygon.

Collector upgrade

Vote: Yes

Rationale: We support upgrading the Collector Contract to allow for multiple admins to facilitate efficient management of the funds collected by this smart contract.

GHO Base Launch

Vote: Yes

Rationale: We are in support of launching GHO across multiple networks which have demand for the Stablecoin, therefore we are glad to support launching GHO on Base.

Sunset stMATIC on Polygon instance

Vote: Yes

Rationale: We support sunsetting stMATIC following its deprecation by Lido Governance.

Update USDS & GHO Borrow Rate

Vote: Yes

Rationale: We support reducing the USDS borrowing rate to match the Sky Savings Rate and the GHO borrowing rate. Lowering the borrowing rate can encourage more users to borrow these assets and promote their use.

Allow Balancer To Claim Mining Rewards

Vote: Yes

Rationale: We support the whitelisting of Balancer DAO to claim liquidity mining rewards and distribute these rewards accordingly.

wstETH Borrow Rate Update

Vote: Yes

Rationale: We support adjusting the borrowing rate for wstETH to improve user usage. Aave needs to incentivize safe borrowing through validated parameter changes.

Aave v3 Linea Activation

Vote: Yes

Rationale: To ensure that Aave functions optimally on Linea, we support activating the adapters necessary to operate Aave V3 Linea.

February Funding Update (Part 1)

Vote: Yes

Rationale: This proposal will ensure that the Aave DAO is adequately capitalised to meet all of its obligations as they become due, therefore, we are glad to support it.

Decrease Slope1 Parameter for Stablecoins on Aave V3

Vote: Yes

Rationale: We support decreasing the slope1 parameter because it allows the DAO to increase revenue for the Aave DAO while maintaining competitive lending rates by setting the target borrow rate for all stablecoins to 9.50%.

[ARFC] Deploy stataUSDC GSM on Base

Vote: Yes

Rationale: We support deploying the DAO’s USDC holdings into the stataUSDC GSM to generate passive revenue. The additional revenue would benefit the DAO’s balance sheet.

[ARFC] Prime Instance - Restore ETH LTV

Vote: Yes

Rationale: To avoid farming rewards, we support restoring the ETH LTV to 82% and changing the approach to distributing incentives to ensure that rewards deliver the most impact.

[ARFC] Proposal to Allocate AGD treasury to Aave DAO

Vote: Yes

Rationale: We support the discontinuation of the Aave Gants DAO, the AGD has been a valuable actor in growing the Aave Community and its broader ecosystem through events and builder grants, however at this time it makes sense to slow down and reassess how Aave should approach Grants.

[TEMP CHECK] Add bCSPX to Aave V3 Gnosis Instance

Vote: Yes

Rationale: We support this proposal. In our opinion, the Aave DAO’s integration of RWA Assets is a massive step in the right direction. With the possibility of integrating Pendle Tokens, Aave is already deliberating on the infrastructure needed to handle RWA assets shortly.

Request for Bounty Payout - Feb 2025

Vote: Yes

Rationale: We are supporting bug bounty contributors for February. By compensating security contributors, the Aave DAO continues to signal that future vulnerabilities disclosed through the proper channels will be adequately rewarded.

a.DI Sonic path activation

Vote: Yes

Rationale: To ensure that Aave functions optimally on Sonic, we support activating the adapters necessary to operate Aave V3 Sonic.

stkBPT Incentives

Vote: Yes

Rationale: We support the new Aave stkBPT incentives. To ensure adoption, it is essential that Aaventinue invest in incentivizing users to use stkBPT as a valuable tool.

[ARFC] Aave V2 Deprecation Update - Disable New Borrows, IR Curve, and Reserve Factor Adjustments

Vote: Yes

Rationale: We support using the Reserve Factor to encourage users to port their positions from Aave V2 to Aave V3. It is essential to ensure that users port their positions to Aave V3 to enjoy more features, while the Aave protocol can increasingly protect itself from being insecure to Aave V2.

[TEMP CHECK] Deploy Aave v3 on Ink

Vote: Yes

Rationale: In line with Aave’s multi-chain future, we support deploying Aave on Ink. Ink is an L2 with a robust distribution network, and we believe that Aave would benefit from being deployed on this L2.

[TEMP CHECK] Recognize HyperLend as a Friendly Fork

Vote: Yes

Rationale: We support this friendly fork. Acknowledges Aave’s Intellectual Property and pays homage through this profit-sharing mechanism.

[ARFC] Core & Base - BTC Correlated Asset Update

Vote: Yes

Rationale: Due to the high use of LBTC across other networks as collateral for borrowing stablecoins, we support onboarding LBTC on Base and enabling liquid e-mode to improve capital efficiency for borrowers on the Core and Base Instances.

[ARFC] Update AAVE LTV and Liquidation Threshold Percentages

Vote: Yes

Rationale: We support increasing the LTV for the AAVE Token response to its current price action. This would give AAVE holders more utility for lending against AAVE Tokens.

Prime Instance - Restore ETH LTV

Vote: Yes

Rationale: To avoid farming rewards, we support restoring the ETH LTV to 82% and changing the approach to distributing incentives to ensure that rewards deliver the most impact.

[ARFC] Add sUSDE to Aave V3 Base Instance

Vote: Yes

Rationale: We support onboarding the rebranded versions of sDAI into the Aave V3 Base Instance. sUSDE has played a key role in the ecosystem, so this is an essential onboarding for Base.

[TEMP CHECK]: Add support for Wrapped Origin Sonic (wOS) to Aave v3

Vote: Yes

Rationale: Following the deployment of Aave on Sonic, we support onboarding Wrapped Origin Sonic to Aave V3. There are clear synergies between the wOS and Aave V3 Sonic.

Upgrade Aave instances to v3.3

Vote: Yes

Rationale: We support this proposal, which empowers Aave to track bad debt and support Umbrella. We support this proposal, which upgrades all Aave instances to this effect.

Caps Risk Oracle Activation on Arbitrum

Vote: Yes

Rationale: We support activating the proposal, which activates the correlated-assets price oracle (CAPO) for assets on Aave V3 Arbitrum.

Adjust Risk Parameters for Aave V2 and V3 on Polygon

Vote: Yes

Rationale: Polygon Governance is considering a proposal to change the risk profile of these risk assets. We support these risk parameter changes to Aave V2 and V3 Polygon.

[ARFC] Onboard rsETH to Arbitrum and Base V3 Instances

Vote: Yes

Rationale: From our perspective, rsETH would be a valuable addition to Aave V3 Arbitrum and Base Instances. As Aave expands, it must continue to uphold LST diversity.

[TEMP CHECK] Deploy Aave on Soneium

Vote: Yes

Rationale: We support deploying Aave on the Soneium network. Because it is available across most ecosystems, Aave continues to grow its diverse deposit and borrower base, which benefits it.

Kene_StableLab · March 14, 2025, 2:06pm

Update AAVE Token LTV/Liquidation Percentages

Vote: Yes

Rationale: We support increasing the LTV for the AAVE Token in order to the current price action of the AAVE Token. This gives AAVE holders more utility for lending against AAVE Tokens.

sUSD Risk Parameter Adjustment

Vote: Yes

Rationale: This parameter proposal will ensure that the Aave V3 sUSD pool remains profitable for Aave users, this will in turn attract more deposits to the benefit of the Aave DAO.

Aave V3.3 Sonic Activation

Vote: Yes

Rationale: In order to ensure that Aave functions optimally on Sonic, we are in support of activating the adapters necessary for the operation of Aave V3 Sonic.

Extend GHO Steward on Aave Prime Instance

Vote: Yes

Rationale: In order to facilitate the efficient management of GHO, we are in support of extending the GHO Steward to the Aave Prime Instance, this is especially important considering the expansion GHO ecosystem.

[TEMP CHECK] Deploy Aave v3 on megaETH

Vote: Yes

Rationale: We are in support of deploying Aave on the megaETH network, Aave being available across most ecosystems continues to grow its diverse deposit and borrower base, which is beneficial for Aave.

[TEMP CHECK] GHO Gas Token Framework

Vote: Yes

Rationale: We are in support of enabling GHO to be used as a Gas Token across multiple networks, from our perspective this creates utility for GHO.

February Funding Update - Part B

Vote: Yes

Rationale: This proposal will ensure that the Aave DAO is adequately capitalised to meet all of its obligations as they become due, therefore, we are glad to support it.

[ARFC] Onboard tBTC to Aave v3 on Arbitrum

Vote: Yes

Rationale: We support onboarding tBTC to the Aave V3 Arbitrum. There are clear opportunities for synergy for tBTC holders looking to participate in the broader DeFi ecosystem.

[ARFC] Onboard rstETH to Aave V3 Prime Instance

Vote: Yes

Rationale: From our perspective rsETH would be a valuable addition to Aave V3 Prime Instance, it is important for Aave to continue to uphold LST diversity as it continues to expand.

[ARFC] BGD.Aave ClinicSteward

Vote: Yes

Rationale: We are in support of using this automated approach to cleaning up the bad debt on Aave V3 ahead of the launch of Umbrella.

Adjust Aave Polygon V3 Risk Parameters

Vote: Yes

Rationale: Due to the proposal being considered by Polygon Governance which changes the risk profile of these assets, we are in support of these risk parameter changes to Aave V2 and V3 Polygon.

Aave V2 Deprecation Update

Vote: Yes

Rationale: We are in support of adjusting the Reserve Factor to encourage users to port their positions from Aave V2 to Aave V3. It is important to ensure that users port their positions to Aave V3 to enjoy more features, while the Aave protocol can increasingly protect itself from its exposure to Aave V2.

sUSDe and USDe Price Feed Update

Vote: Yes

Rationale: This proposal is a necessary change to ensure that price feeds for sUSD and USDe stay consistent and do not cause artificial volatility for the assets.

wrsETH Base Onboarding

Vote: Yes

Rationale: From our perspective wrsETH would be a valuable addition to Aave V3 Base Instance, it is important for Aave to continue to uphold LST diversity as it continues to expand.

[ARFC] Orbit Program Renewal - Q1 2025

Vote: Yes

Rationale: The Aave delegate program has been a valuable part of Aave Governance. By incentivizing delegates to participate, Aave has created an accountability layer that ensures that proposals are a minimum standard before passing through the governance process.

Core & Base - BTC Correlated Asset Update

Vote: Yes

Rationale: Due to the high utilisation of LBTC across other networks as collateral for borrowing stablecoins, we are in support of onboarding LBTC on Base and enabling liquid e-mode to enable capital efficiency for borrowers on the Core and Base Instances.

Add EURC to BASE Aave V3

Vote: Yes

Rationale: One of Aave’s key features is its diversity of Stablecoins, therefore we gladly support onboarding EURC to Aave V3.

AUSD on V3 Avalanche

Vote: Yes

Rationale: One of Aave’s key features is its diversity of Stablecoins. Therefore, we gladly support onboarding AUSD to Aave V3.

[ARFC] Recognize HyperLend as a Friendly Fork

Vote: Yes

Rationale: We support this friendly fork which. acknowledges Aave’s Intellectual Property and pays homage through this profit sharing mechanism.

[ARFC]. Aave <> Chainlink SVR v1. Phase 1 activation

Vote: Yes

Rationale: We are in support of this safe approach to MEV extraction, through this proposal Aave can safely capture a significant amount of that is not currently being captured.

[TEMP CHECK] Add wstUSR to Aave v3 Core Instance

Vote: Yes

Rationale: Aave can boast of a diverse options of stablecoins from various ecosystems, considering the fundamentsld of wstUSR, we are glad to onboard this asset.

[TEMP CHECK] Add USR to Aave v3 Core Instance

Vote: Yes

Rationale: Aave can boast of a diverse options of stablecoins from various ecosystems, considering the fundamentsld of USR, we are glad to onboard this asset.

[TEMP CHECK] Add stS to Aave v3 Sonic Instance

Vote: Yes

Rationale: As an LST which offers exposure to Sonic Network’s staking rewards, stS is a valuable addition to the Aave V3 Sonic Instance.

[TEMP CHECK] Onboard scETH, scUSD, and scBTC to Aave V3 Sonic Instance

Vote: Yes

Rationale: In order to meet the demand for broader collateral and borrowing options on Sonic, we are in support of onboarding scETH, scUSD and scBTC to the Aave V3 Sonic Instance.

[TEMP CHECK] GHO Aave Savings Upgrade

Vote: Yes

Rationale: We are in support of the GHO Savings Rate as a low risk product for the GHO holders to access yield on their GHO Tokens, in order to get GHO to the next stage of growth there needs to be a broader approach to getting users to commit to GHO.

[ARFC] Enhancements in Aave v3 Gnosis Chain Instance

Vote: Yes

Rationale: We are in support of these changes to the Aave V3 Gnosis Instance, these changes will enable better capital efficiency for USDC.e and sDAI which will create more value for users of the Gnosis Instance.

GSMs Migration to stataGSM4626

Vote: Yes

Rationale: We are in support of deploying the DAOs USDC and USDT holdings into the stataUSDC and statUSDT GSMs to generate revenue passively, estimated $593.8k USD in annual revenue would be a beneficial addition to the DAOs balance sheet.

Recreate wrstETH eMode on Base

Vote: Yes

Rationale: From our perspective, wrsETH would be a valuable addition to Aave V3 Base Instance. It is important for Aave to continue to uphold LST diversity as it expands.

Aave V3.3 Celo Activation

Vote: Yes

Rationale: In order to ensure that Aave functions optimally on Celo, we are in support of activating the adapters necessary for the operation of Aave V3 Celo.

[TEMP CHECK] Deploy Aave v3 on Plasma

Vote: Yes

Rationale: We are in support of deploying Aave on the Plasma network. Aave, being available across most ecosystems, continues to grow its diverse deposit and borrower base, which is beneficial for Aave.

Kene_StableLab · March 28, 2025, 10:45am

[TEMP CHECK] Aave Decentralized Acqui-Hire Framework

Vote: No

Rationale: While I see the value in the idea of this proposal, implementing a decentralized acqui-hire framework will prove particularly difficult for Aave due to the various aspects of this proposal that lacks a clear definition.

[TEMP CHECK] Proposal to Rename GHO to USDA for Enhanced Clarity and Adoption

Vote: No

Rationale: We are not in support of this proposal because we do not believe that this proposal makes a clear case for changing the name of the GHO stablecoin; in our opinion, the current name clearly differentiates Aave’s stablecoin in a positive way.

[ARFC] Launch GHO on Gnosis Chain

Vote: Yes

Rationale: Expanding GHO to Gnosis Chain will diversify its utility and user base, leveraging Gnosis Chain’s unique features to enhance GHO’s adoption and functionality within the DeFi ecosystem.

[ARFC] GHO Gas Token Framework

Vote: Yes

Rationale: Establishing a framework for GHO to function as a gas token across multiple networks will increase its utility, promote adoption, and provide users with a seamless transaction experience.

Enable SVR V1 on Aave V3 Ethereum

Vote: Yes

Rationale: We are in support of activating the Smart Value Recapture (SVR) V1 on Aave V3 Ethereum will enhance the protocol’s ability to capture and redistribute value, benefiting stakeholders and strengthening the Aave ecosystem.

[ARFC] Aave Finance Steward Modules Deployment

Vote: Yes

Rationale: Deploying Finance Steward Modules will improve the efficiency and transparency of Aave’s financial operations, ensuring better resource allocation and governance.

[ARFC] wstETH and weETH E-Modes and LT/LTV Adjustments on Ethereum, Arbitrum, Base

Vote: Yes

Rationale: Adjusting E-Modes and Loan-to-Value (LTV) ratios for wstETH and weETH across multiple networks will optimize risk parameters, enhancing capital efficiency and user experience.

Gov v3 VotingMachine / VotingPortal Maintenance

Vote: Yes

Rationale: Regular maintenance of the VotingMachine and VotingPortal is essential to ensure the integrity, security, and smooth operation of Aave’s governance processes.

[TEMP CHECK] Onboard lisUSD to Aave V3 BNB Instance

Vote: Yes

Rationale: Integrating lisUSD into the Aave V3 BNB Instance will expand the range of stablecoin options available to users, promoting diversity and enhancing the platform’s appeal.

[ARFC] Launch GHO on Sonic & Set ACI as Emissions Manager for Rewards

Vote: Yes

Rationale: Launching GHO on Sonic and appointing ACI as the Emissions Manager will facilitate efficient distribution of rewards, incentivizing participation and bolstering GHO’s presence in the Sonic ecosystem.

Stablecoins Interest Rate Curve Update

Vote: Yes

Rationale: Updating the interest rate curves for stablecoins will align borrowing and lending rates with current market conditions, ensuring the competitiveness and sustainability of the Aave platform.

Clinic Steward Activation

Vote: Yes

Rationale: Activating the Clinic Steward will provide a structured approach to addressing and resolving protocol issues, enhancing the overall health and resilience of the Aave ecosystem.

[ARFC] Aavenomics Implementation: Part One

Vote: Yes

Rationale: Implementing the first phase of Aavenomics will introduce value accrual and distribution mechanisms, strengthening the AAVE token’s utility and aligning incentives within the community.

[ARFC-ADDENDUM] Aave DAO & Chainlink Smart Value Recapture (SVR)

Vote: Yes

Rationale: We support activating the Smart Value Recapture (SVR) V1 on Aave V3 Ethereum will enhance the protocol’s ability to capture and redistribute value, benefiting stakeholders and strengthening the Aave ecosystem.

[ARFC] Risk Steward Parameter Updates Phase 3

Vote: Yes

Rationale: We support the proposed updates to the Risk Steward parameters, which aim to enhance the efficiency of risk management within the Aave protocol. The proposal reduces governance overhead while maintaining appropriate safety constraints by allowing for more responsive adjustments to parameters such as Loan to Value (LTV), Liquidation Threshold, and Borrow Rates. Introducing conservative limits and minimum delay periods ensures that changes are implemented cautiously, preserving the protocol’s stability. This initiative reflects a proactive approach to risk management, fostering a more agile and resilient Aave ecosystem.

Kene_StableLab · April 2, 2025, 12:14pm

Finance Steward Deployment: Pool Exposure Module

Vote: Yes

Rationale: Implementing the Pool Exposure Module within the Finance Steward framework will enhance Aave’s capability to monitor and manage risk exposures across various liquidity pools. This deployment is expected to improve the protocol’s financial oversight and ensure more robust risk management practices.

Allow Balancer DAO to Claim Liquidity Mining Rewards (Arbitrum & Base)

Vote: Yes

Rationale: Enabling Balancer DAO to claim liquidity mining rewards from Boosted Pools on Arbitrum and Base networks facilitates the efficient redistribution of rewards to users and the DAO. This action promotes greater collaboration and synergy between Aave and Balancer ecosystems, enhancing overall user benefits.

Onboard rsETH to Arbitrum

Vote: Yes

Rationale: Integrating rsETH into Aave V3 on Arbitrum will diversify the asset offerings, providing users with additional collateral options. Given Arbitrum’s substantial wstETH reserves, onboarding rsETH is anticipated to attract more liquidity and encourage broader user participation.

Onboard eBTC and Add eBTC/WBTC E-Mode

Vote: Yes

Rationale: Introducing eBTC to the Core Instance and establishing a WBTC liquid E-Mode aims to enhance capital efficiency for borrowers utilizing these assets as collateral. This initiative is expected to optimize borrowing capacities and stimulate increased platform utilization.

[TEMP CHECK] Onboard USDtb to Aave v3 Core Instance

Vote: Yes

Rationale: Incorporating USDtb, a stablecoin backed by tokenized U.S. treasury funds, into the Aave v3 Core Instance will offer users a stable and reliable asset for borrowing and lending. This addition is projected to deepen borrow liquidity and support the growth of sUSDe activity on the Core Instance.

[ARFC] Add AAVE token to Aave V3 Base Instance

Vote: Yes

Rationale: Adding the AAVE token to the Aave V3 Base Instance will enhance the platform’s utility by allowing users to leverage AAVE as collateral. This integration is likely to increase the token’s utility and encourage greater engagement within the Aave ecosystem.

Kene_StableLab · April 16, 2025, 9:13am

[ARFC] LRT and wstETH Unification

Vote: Yes

Rationale: This proposal aims to harmonize the Loan-to-Value (LTV) and Liquidation Threshold (LT) parameters for Liquid Restaking Tokens (LRTs) and wstETH across various Aave v3 instances. By aligning these parameters, the proposal promotes a level playing field among LRTs and enhances capital efficiency.

[TEMP CHECK] Onboard tETH to Aave v3 Prime Instance

Vote: Yes

Rationale: Onboarding tETH, a liquid staking token from Treehouse, to the Aave v3 Prime Instance expands the diversity of collateral options available to users. This addition enhances capital efficiency and provides users with more flexibility in their borrowing strategies. By integrating tETH, Aave continues to support the growth of the staking ecosystem and meets the evolving needs of its user base.

[TEMP CHECK] Horizon’s RWA Instance

Vote: Yes

Rationale: By enabling institutions to use tokenized assets as collateral for borrowing stablecoins like USDC and GHO, Horizon bridges the gap between traditional finance and DeFi. The proposal also includes a 50/50 revenue-sharing model with the Aave DAO, which was a good decision to adopt the DAO’s feedback. There are also plans for a dedicated GHO facilitator to enhance GHO adoption. This initiative positions Aave at the forefront of institutional DeFi adoption and opens new revenue streams for the DAO.

April Funding Update

Vote: Yes

Rationale: This proposal ensures that the Aave DAO remains adequately capitalized to meet its operational and strategic obligations. By approving this funding update, we support the continued development and maintenance of the Aave protocol, contributing to its long-term sustainability.

Caps Risk Oracle Activation on Base, Avalanche

Vote: Yes

Rationale: Activating the Caps Risk Oracle on Base and Avalanche networks enhances Aave’s risk management capabilities by allowing dynamic adjustments to supply and borrow caps based on real-time data. This proactive approach helps maintain protocol safety and efficiency across multiple networks.

Removal of Legacy VotingPortals from Governance v3

Vote: Yes

Rationale: Removing outdated VotingPortals from Governance v3 streamlines the governance process and reduces potential security vulnerabilities. This cleanup aligns with best practices for maintaining an efficient and secure governance framework.

[ARFC] GHO Savings Upgrade

Vote: Yes

Rationale: Introducing the GHO Savings Rate (ASR) provides GHO holders with a low-risk yield-bearing option, enhancing the utility and attractiveness of the GHO stablecoin. This upgrade supports the growth and adoption of GHO within the DeFi ecosystem.

[ARFC] Aave Liquidity Committee Funding Phase VI

Vote: Yes

Rationale: Funding Phase VI of the Aave Liquidity Committee ensures continued support for liquidity initiatives that maintain GHO’s peg and overall market stability. This funding is crucial for sustaining deep liquidity and promoting user confidence in the protocol.

[ARFC] stkABPT - Emissions Update

Vote: Yes

Rationale: Adjusting emissions to the stkABPT Safety Module reflects the evolving liquidity landscape and aims to optimize AAVE token distribution. This update supports a more diversified and efficient allocation of incentives across the ecosystem.

[ARFC] Add stS to Aave v3 Sonic Instance

Vote: Yes

Rationale: Onboarding stS (Staked Sonic) to the Aave v3 Sonic Instance allows users to leverage staked assets as collateral while continuing to earn staking rewards. This addition enhances capital efficiency and broadens asset diversity within the Sonic ecosystem.

[ARFC] Renew LlamaRisk as Risk Service Provider - Epoch 3

Vote: Yes

Rationale: Renewing LlamaRisk’s engagement as a risk service provider ensures continuity in expert risk assessment and management. Their contributions are vital for maintaining the protocol’s resilience and adapting to the dynamic DeFi landscape.

[TEMP CHECK] Onboard frxUSD and sfrxUSD to Aave v3 on Sonic Instance

Vote: Yes

Rationale: Integrating frxUSD and sfrxUSD into the Aave v3 Sonic Instance expands the range of stablecoin options available to users, enhancing borrowing and lending opportunities. This onboarding supports greater flexibility and utility within the protocol.

[TEMP CHECK] Onboard eUSDe PT Tokens to Aave v3 Core Instance

Vote: Yes

Rationale: Adding eUSDe Principal Tokens (PT) to the Aave v3 Core Instance introduces fixed-income-like instruments, catering to users seeking predictable yield strategies. This integration diversifies the asset offerings and meets the evolving needs of DeFi participants.

[TEMP CHECK] Onboard eUSDe to Aave v3 Core Instance

Vote: Yes

Rationale: Onboarding eUSDe to the Aave v3 Core Instance provides users with access to a stablecoin backed by tokenized U.S. Treasuries, offering a secure and yield-generating asset. This addition enhances the protocol’s stablecoin diversity and appeal.

[ARFC] Onboard Pendle PT Tokens to Aave V3 Core Instance

Vote: Yes

Rationale: Integrating Pendle’s Principal Tokens (PTs) into Aave V3 allows users to borrow against future yield streams, introducing innovative financial instruments to the protocol. This onboarding aligns with Aave’s commitment to expanding DeFi capabilities.

Request for Bounty Payout - March 2025

Vote: Yes

Rationale: Approving the bounty payouts for valid bug submissions acknowledges the contributions of security researchers and reinforces Aave’s commitment to protocol security. Timely rewards encourage ongoing participation in safeguarding the ecosystem.

Enhancements in Aave v3 Gnosis Chain Instance

Vote: Yes

Rationale: Implementing enhancements to the Gnosis Chain Instance, such as improved capital efficiency for USDC.e and sDAI, optimizes asset utilization and user experience. These changes contribute to the overall robustness of the Aave protocol on Gnosis Chain.

Risk Steward Parameter Updates Phase 3

Vote: Yes

Rationale: Updating the Risk Steward parameters enhances the efficiency of risk management by allowing timely adjustments within predefined boundaries. This approach reduces governance overhead while maintaining protocol safety.

Orbit Program Renewal

Vote: Yes

Rationale: Renewing the Orbit Program continues to incentivize active participation and accountability among Aave delegates. This program has been instrumental in fostering a vibrant and responsive governance ecosystem.

AAVE Buybacks Allocation

Vote: Yes

Rationale: Allocating funds for AAVE token buybacks supports the token’s value and aligns with the broader Aavenomics strategy. This initiative demonstrates a proactive approach to managing the protocol’s treasury and token economics.

[ARFC] Aave v3.4 Candidate

Vote: Yes

Rationale: Advancing to Aave v3.4 introduces critical updates and improvements to the protocol, ensuring it remains at the forefront of DeFi innovation. Supporting this candidate version reflects our commitment to continuous development and user-centric enhancements.

Kene_StableLab · April 28, 2025, 7:51am

Add stS to Aave v3 Sonic Instance

Vote: Yes

Rationale: Onboarding stS (Staked Sonic) to the Aave v3 Sonic Instance allows users to leverage staked assets as collateral while continuing to earn staking rewards. This addition enhances capital efficiency and broadens asset diversity within the Sonic ecosystem.

Onboard PT sUSDe July and PT eUSDe May on Core Instance

Vote: Yes

Rationale: Adding eUSDe Principal Tokens (PT) to the Aave v3 Core Instance introduces fixed-income-like instruments, catering to users seeking predictable yield strategies. This integration diversifies the asset offerings and meets the evolving needs of DeFi participants.

Lower stkABPT Emissions

Vote: Yes

Rationale: Adjusting emissions to the stkABPT Safety Module reflects the evolving liquidity landscape and aims to optimize AAVE token distribution. This update supports a more diversified and efficient allocation of incentives across the ecosystem.

Renew LlamaRisk as Risk Service Provider - epoch 3

Vote: Yes

Rationale: Renewing LlamaRisk’s engagement as a risk service provider ensures continuity in expert risk assessment and management. Their contributions are vital for maintaining the protocol’s resilience and adapting to the dynamic DeFi landscape.

[TEMP CHECK] Deploy Aave v3 on Tron

Vote: Yes

Rationale: We are in support of deploying Aave on the Tron, Aave being available across most ecosystems continues to grow its diverse deposit and borrower base, which is beneficial for Aave.

[ARFC] Onboard eUSDe to Aave v3 Core Instance

Vote: Yes

Rationale: Adding eUSDe Principal Tokens (PT) to the Aave v3 Core Instance introduces fixed-income-like instruments, catering to users seeking predictable yield strategies. This integration diversifies the asset offerings and meets the evolving needs of DeFi participants.

[TEMP CHECK] Aave and ether.fi Cash: A Proposal for Real-World Utility

Vote: Yes

Rationale: We are in support of using Aave to Power ether.fi’s credit card product, from our perspective Aave will continue to find various use cases that create value for the protocol, while creating access to liquidity for users.

[ARFC] Onboard USDtb to Aave v3 Core Instance

Vote: Yes

Rationale: Incorporating USDtb, a stablecoin backed by tokenized U.S. treasury funds, into the Aave v3 Core Instance will offer users a stable and reliable asset for borrowing and lending. This addition is projected to deepen borrowing liquidity and support the growth of sUSDe activity on the Core Instance.

[ARFC] ACI Phase IV – “Road to 80”

Vote: Yes

Rationale: The ACI has provided immense value to the Aave DAO and we are in support of renewing this service provider engagement with the DAO.

[ARFC] Aave DAO <> BGD Labs. Phase 5

Vote: Yes

Rationale: BGD Labs has been a valuable service provider to the Aave Protocol. Therefore, we are in support of continuing BGD Labs’ engagement with Aave.

Aave Liquidity Committee Funding Phase VI

Vote: Yes

Rationale: Funding Phase VI of the Aave Liquidity Committee ensures continued support for liquidity initiatives that maintain GHO’s peg and overall market stability. This funding is crucial for sustaining deep liquidity and promoting user confidence in the protocol.

Add rlUSD to Core Instance

Vote: Yes

Rationale: One of Aave’s key features is its diversity of Stablecoins, therefore we gladly support onboarding rlUSD to Aave V3.

Mantle a.DI path activation

Vote: Yes

Rationale: In order to ensure that Aave functions optimally on Mantle, we are in support of activating the adapters necessary for the operation of Aave V3 Mantle.

Kene_StableLab · May 15, 2025, 10:47am

LRT and wstETH Unification

Vote: Yes

Rationale: This proposal aims to harmonize the Loan-to-Value (LTV) and Liquidation Threshold (LT) parameters for Liquid Restaking Tokens (LRTs) and wstETH across various Aave v3 instances. By aligning these parameters, the proposal promotes a level playing field among LRTs and enhances capital efficiency.

Add AAVE token to Aave V3 Base Instance

Vote: Yes

Rationale: Adding the AAVE token to the Aave V3 Base Instance enhances utility by allowing AAVE holders to use their tokens as collateral or to borrow against them. This integration fosters greater user engagement and expands the token’s use case within the Aave ecosystem on Base.

[ARFC] Deploy 5M USDC for GHO Market Making on Gnosis Chain

Vote: Yes

Rationale: We support deploying 5 million USDC for GHO market-making on Gnosis Chain, this capital deployment will improve GHO liquidity and peg stability across decentralized exchanges. This strategic deployment will support healthy trading volumes and incentivize GHO adoption in a cost-efficient manner.

[ARFC] Onboarding wETH to Aave V3 Celo Instance

Vote: Yes

Rationale: Onboarding wETH to the Aave V3 Celo Instance provides users with access to one of the most liquid and widely used assets in DeFi. This enhances collateral diversity, supports cross-chain liquidity, and further establishes Aave’s presence within the Celo ecosystem.

[ARFC] Deploy Aave on Soneium

Vote: Yes

Rationale: Deploying Aave on the Soneium network aligns with Aave’s multi-chain expansion strategy. Soneium’s architecture offers a new market segment, and Aave’s deployment there will attract a broader user base while driving deposit and borrowing activity on a novel chain.

Extend SVR V1 to more reserves

Vote: Yes

Rationale: Extending Smart Value Recapture (SVR) V1 to additional reserves enables Aave to capture more MEV-related value across a wider asset base. This extension enhances the protocol’s revenue generation while preserving secure and fair execution for users.

stkGHO Emissions

Vote: Yes

Rationale: Enabling stkGHO emissions creates additional utility for GHO holders by allowing them to stake and earn rewards. This helps bootstrap a secure staking layer for GHO and provides a mechanism to incentivize long-term holding and stability of the stablecoin.

Remove USDe Debt Ceiling and Introduce USDe Stablecoins E-mode

Vote: Yes

Rationale: Removing the debt ceiling on USDe and introducing a dedicated e-mode for USDe stablecoins increases capital efficiency while enhancing borrowing conditions. This proposal reflects market maturity for USDe and supports broader integration into the Aave ecosystem.

Onboard USDtb to Aave v3 Core Instance

Vote: Yes

Rationale: Incorporating USDtb, a stablecoin backed by tokenized U.S. treasury funds, into the Aave v3 Core Instance will offer users a stable and reliable asset for borrowing and lending. This addition is projected to deepen borrow liquidity and support the growth of sUSDe activity on the Core Instance.

[TEMP CHECK] Add PEPE as a Supported Asset on AAVE

Vote: Yes

Rationale: From our perspective, despite PEPE being a meme, we are curious to see how our Risk service providers will assess balancing the demand for the asset with its risk profile, there may be an opportunity for Aave to have a market for memes with a distinct set of parameters.

[ARFC] Onboard tETH to Aave v3 Prime Instance

Vote: Yes

Rationale: Onboarding tETH, a liquid staking token from Treehouse, to the Aave v3 Prime Instance expands the diversity of collateral options available to users. This addition enhances capital efficiency and provides users with more flexibility in their borrowing strategies. By integrating tETH, Aave continues to support the growth of the staking ecosystem and meets the evolving needs of its user base.

[ARFC] Interest Rate Curve Risk Oracle

Vote: Yes

Rationale: We are in support of the Interest Rate Oracle which is to set optimal interest rate curves for stablecoins within the Aave protocol. This is a key part of the Aave protocol and we are glad to see Chaos Labs support this.

[ARFC] Horizon’s RWA Instance

Vote: Yes

Rationale: By enabling institutions to use tokenized assets as collateral for borrowing stablecoins like USDC and GHO, Horizon bridges the gap between traditional finance and DeFi. The proposal also includes a 50/50 revenue sharing model with the Aave DAO, which was a good decision to adopt the DAO’s feedback. There are also plans for a dedicated GHO facilitator to enhance GHO adoption. This initiative positions Aave at the forefront of institutional DeFi adoption and opens new revenue streams for the DAO.

May Funding Update

Vote: Yes

Rationale: This proposal will ensure that the Aave DAO is adequately capitalised to meet all of its obligations as they become due, therefore, we are glad to support it.

[ARFC] Aave V3 Deployment on Aptos Mainnet

Vote: Yes

Rationale: We are in support of deploying Aave V3 on the Aptos network in order to expand the Aave Protocol’s Multi-Chain ambitions across various networks.

Onboard PT sUSDe July on Core Instance

Vote: Yes

Rationale: Adding sUSDe Principal Tokens (PT) to the Aave v3 Core Instance introduces fixed-income-like instruments, catering to users seeking predictable yield strategies. This integration diversifies the asset offerings and meets the evolving needs of DeFi participants.

Aave BGD Phase 5

Vote: Yes

Rationale: BGD Labs has been a valuable service provider to the Aave Protocol, therefore we are in support of continuing BGD Labs engagement with Aave.

ACI Phase IV – “Road to 80”

Vote: Yes

Rationale: The ACI has provided immense value to the Aave DAO and we are in support of renewing this service provider engagement with the DAO.

Kene_StableLab · June 3, 2025, 9:54am

May Funding Part B

Vote: Yes

Rationale:

This proposal ensures that the Aave DAO remains adequately capitalized to meet its ongoing operational and strategic commitments. By securing necessary funding, the DAO can continue to support essential initiatives, maintain protocol development, and uphold its financial responsibilities, thereby sustaining the health and growth of the Aave ecosystem.

Aave Umbrella Activation

Vote: Yes

Rationale:

Activating the Aave Umbrella system represents a significant advancement in the protocol’s risk management framework. By enabling users to stake aTokens such as aUSDC or aWETH directly into per-asset safety modules, Umbrella introduces a more capital-efficient and responsive mechanism for covering potential bad debt. In the event of a deficit, the system can automatically burn the staked aTokens to offset losses, eliminating the need for governance intervention and reliance on secondary market liquidity. This approach not only streamlines the process of addressing shortfalls but also enhances the protocol’s resilience by aligning the coverage assets with the liabilities they are meant to secure. Furthermore, Umbrella’s design supports multi-chain deployments, allowing for isolated safety modules tailored to specific networks and assets, thereby reducing systemic risk across the Aave ecosystem. With its objective, on-chain slashing mechanism and flexible reward distribution, Umbrella stands as a forward-thinking solution that strengthens Aave’s commitment to security, decentralization, and efficient capital utilization.

Aave V3.3 Soneium Activation

Vote: Yes

Rationale:

Activating Aave V3.3 on the Soneium network aligns with Aave’s multi-chain expansion strategy, introducing enhanced features such as improved debt management and liquidation processes. This deployment not only broadens Aave’s reach into new blockchain ecosystems but also leverages Soneium’s unique architecture to attract a diverse user base, thereby fostering increased adoption and liquidity within the protocol.

Add FBTC to Aave v3 Main Market on Ethereum

Vote: Yes

Rationale:

Integrating FBTC into the Aave V3 Main Market on Ethereum diversifies the range of collateral options available to users. As a tokenized representation of Bitcoin, FBTC brings the liquidity and stability of Bitcoin into the Aave ecosystem, allowing users to leverage it for borrowing and lending activities, thus enhancing the protocol’s utility and appeal to a broader audience.

Onboarding wETH to Aave V3 Celo Instance

Vote: Yes

Rationale:

Onboarding wETH to the Aave V3 Celo Instance provides users with access to one of the most liquid and widely used assets in DeFi. This enhances collateral diversity, supports cross-chain liquidity, and further establishes Aave’s presence within the Celo ecosystem.

CAPO Adapter Maintenance Update

Vote: Yes

Rationale:

Implementing the CAPO Adapter Maintenance Update ensures the continued reliability and efficiency of Aave’s cross-chain communication infrastructure. By addressing necessary maintenance and updates, this proposal maintains the integrity of protocol operations across different blockchain networks, thereby supporting seamless user experiences and protocol stability.

[TEMP CHECK] Adopt The SEAL Safe Harbor Agreement

Vote: Yes

Rationale:

Adopting the SEAL Safe Harbor Agreement provides a standardized legal framework that can offer clarity and protection for the Aave DAO and its participants. This agreement aims to mitigate regulatory uncertainties and foster a more secure environment for decentralized governance, aligning with best practices in the evolving legal landscape of DeFi.

stkAAVE Emissions

Vote: Yes

Rationale:

Continuing stkAAVE emissions incentivizes users to stake their AAVE tokens, thereby enhancing the protocol’s security through increased participation in the Safety Module. These emissions serve as rewards for stakers who assume the risk of potential slashing, ensuring that the protocol remains resilient against unforeseen shortfall events.

Onboard eUSDe and eUSDe-based PT Token to Aave V3 Core

Vote: Yes

Rationale:

Incorporating eUSDe and its associated Principal Tokens (PT) into the Aave V3 Core expands the protocol’s stablecoin offerings and introduces fixed-income-like instruments. This addition caters to users seeking predictable yield strategies, diversifies asset options, and enhances the overall utility and appeal of the Aave platform.

[ARFC] Aave Umbrella Activation

Vote: Yes

Rationale:

The activation of Aave’s Umbrella system represents a pivotal advancement in the protocol’s risk management architecture. By enabling users to stake aTokens such as aUSDC or aWETH directly into per-asset safety modules, Umbrella introduces a more capital-efficient and responsive mechanism for covering potential bad debt. In the event of a deficit, the system can automatically burn the staked aTokens to offset losses, eliminating the need for governance intervention and reliance on secondary market liquidity. This approach not only streamlines the process of addressing shortfalls but also enhances the protocol’s resilience by aligning the coverage assets with the liabilities they are meant to secure. Furthermore, Umbrella’s design supports multi-chain deployments, allowing for isolated safety modules tailored to specific networks and assets, thereby reducing systemic risk across the Aave ecosystem. With its objective, on-chain slashing mechanism and flexible reward distribution, Umbrella stands as a forward-thinking solution that strengthens Aave’s commitment to security, decentralization, and efficient capital utilization.

Configuration Maintenance

Vote: Yes

Rationale:

Regular configuration maintenance is essential to ensure that the Aave protocol operates optimally. This proposal addresses necessary updates and adjustments to protocol parameters, maintaining system efficiency, security, and alignment with current market conditions, thereby supporting the protocol’s ongoing stability and performance.

[TEMP-CHECK] Onboard wstLINK to Aave v3 Core Instance

Vote: Yes

Rationale:

Onboarding wstLINK to the Aave V3 Core Instance introduces a liquid staking derivative of Chainlink’s LINK token, expanding the range of collateral options available to users. This addition supports the growing demand for staking derivatives and enhances the protocol’s appeal to users seeking diversified asset exposure.

[TEMP CHECK] Aave Events & Sponsorship Budget 2025

Vote: Yes

Rationale:

Allocating a budget for events and sponsorships in 2025 enables the Aave DAO to engage with the broader community, foster partnerships, and promote the protocol’s growth. This investment in outreach and branding supports Aave’s position as a leading DeFi platform and encourages wider adoption and collaboration.

[ARFC] Supply and Borrow Cap Risk Oracle Constraint Specification

Vote: Yes

Rationale:

Implementing a risk oracle constraint specification for supply and borrow caps enhances the protocol’s risk management capabilities. By leveraging real-time data and analytics, this measure ensures that asset caps are set appropriately, mitigating potential risks and maintaining the protocol’s financial stability.

[ARFC] Base Incentive Campaign Funding

Vote: Yes

Rationale:

Funding an incentive campaign on the Base network aims to attract users and liquidity to Aave’s deployment on this blockchain. By offering targeted incentives, the campaign encourages adoption, supports network growth, and strengthens Aave’s multi-chain presence.

Soneium aDI Path Activation

Vote: Yes

Rationale:

Activating the aDI path on the Soneium network ensures that Aave’s deployment on this blockchain is fully operational and integrated. This activation facilitates seamless interactions within the Soneium ecosystem, promoting user engagement and protocol functionality across chains.

Kene_StableLab · July 2, 2025, 11:23am

Upgrade Aave instances to v3.4

Vote: Yes
Rationale: Upgrading to v3.4 introduces critical improvements in gas efficiency, risk parameters, and cross-chain compatibility that enhance protocol performance across all deployments. This infrastructure update maintains Aave’s competitive edge while delivering tangible benefits to users through reduced transaction costs and improved capital efficiency.

[ARFC-Addendum] Update Merit for Round 18

Vote: Yes
Rationale: Updating Merit allocations ensures contributor incentives remain aligned with protocol priorities and recognizes valuable ecosystem contributions. This adjustment demonstrates adaptive governance and efficient resource allocation while maintaining sustainable reward distributions.

[ARFC] stS Loop Incentive Program

Vote: Yes
Rationale: The stS Loop Incentive Program enhances liquidity provision through strategic looping strategies, attracting sophisticated users while deepening market liquidity. This structured approach minimizes mercenary capital risks while supporting sustainable protocol growth and improved utilization rates.

Aave v2 non-Ethereum pools next deprecation steps

Vote: Yes
Rationale: Deprecating v2 non-Ethereum pools consolidates resources on technically advanced v3 deployments, reducing operational overhead and enhancing security. Clear migration pathways ensure smooth user transitions while focusing development efforts on active markets.

Discount Rate Risk Oracle Activation and update manual AGRS

Vote: Yes
Rationale: Activating the Discount Rate Risk Oracle introduces dynamic, data-driven risk parameter adjustments that respond to market conditions in real-time. This enhancement strengthens protocol resilience against volatility while maintaining optimal capital efficiency and reducing manual governance interventions.

Add EURC to Aave V3 Core Instance

Vote: Yes
Rationale: Integrating Circle’s Euro-backed stablecoin expands European market exposure and diversifies offerings beyond USD-denominated assets. This addition captures growing demand for Euro lending/borrowing opportunities while strengthening regulatory compliance in key jurisdictions.

Enable additional SVR oracles

Vote: Yes
Rationale: Additional Secondary Variable Rate oracles enhance price discovery and risk assessment through improved data feeds and redundancy. This infrastructure expansion supports better-informed lending decisions while strengthening resilience against oracle failures.

Onboard tETH to Aave v3 Prime Instance

Vote: Yes
Rationale: Adding tETH to the Prime Instance provides institutional users with capital-efficient liquid staking collateral that maintains Ethereum staking exposure. This integration strengthens Aave’s position in serving sophisticated users with advanced yield strategies.

[TEMP CHECK] Onboard USD1 to Aave V3 Core and BNB Instance

Vote: Yes
Rationale: Multi-chain deployment of USD1 diversifies stablecoin offerings while capturing cross-chain liquidity flows. This approach maximizes market capture potential and reinforces Aave’s commitment to supporting emerging stablecoin protocols.

[TEMP CHECK] Onboard syrupUSDC to Aave V3 Core Instance

Vote: Yes
Rationale: syrupUSDC represents innovative yield-bearing stablecoin design that enhances capital efficiency through native yield generation. Supporting such innovations demonstrates Aave’s adaptability to emerging asset classes.

Aave V3 Aptos Activation

Vote: Yes
Rationale: Expanding to Aptos diversifies beyond EVM chains, leveraging Move-based architecture for enhanced throughput and reduced costs. Early ecosystem presence positions Aave to capture new user segments and benefit from Aptos’s institutional-grade infrastructure.

June Funding Update - Part II

Vote: Yes
Rationale: Continued funding ensures operational capabilities and strategic initiative execution, supporting infrastructure maintenance and service provider compensation. This demonstrates fiscal responsibility while enabling sustained protocol innovation.

[ARFC] GHO CEX Earn Incentive Program

Vote: Yes
Rationale: Incentivizing CEX platforms to offer GHO earning opportunities bridges CeFi-DeFi gaps while expanding reach beyond traditional DeFi users. This strategic initiative increases GHO’s addressable market and strengthens liquidity through broader distribution channels.

GHO Avalanche Launch

Vote: Yes
Rationale: Launching GHO on Avalanche leverages the network’s high performance and established DeFi community to enhance adoption. Cross-chain expansion strengthens GHO’s competitive position while providing seamless value transfer across ecosystems.

Aave Events & Sponsorship Budget 2025

Vote: Yes
Rationale: Strategic investment in conferences, hackathons, and educational programs reinforces Aave’s market leadership while attracting developers and users. Targeted sponsorships cultivate partnerships that drive long-term ecosystem growth.

[ARFC] Addition of USDe to Ethena Principal Token Stablecoin E-Modes

Vote: Yes
Rationale: Specialized E-Modes for USDe optimize capital requirements for delta-neutral strategies, recognizing the importance of innovative stablecoin mechanisms. This enables capital-efficient leveraged strategies for sophisticated users.

Chaos Labs x Aave DAO — Early Renewal Proposal

Vote: Yes
Rationale: Early renewal ensures continuity of critical risk management services that have proven instrumental in maintaining protocol security. Securing favorable terms guarantees uninterrupted data-driven insights and parameter optimization during rapid growth periods.

June Funding Update - Part I

Vote: Yes
Rationale: First-phase funding provides essential operational capital for immediate needs and service provider compensation. Phased approach demonstrates prudent financial management while maintaining development momentum.

[TEMP CHECK] Add XAUt to Aave V3 Core Instance

Vote: Yes
Rationale: Tokenized gold integration addresses demand for non-correlated RWA collateral, positioning Aave at the forefront of real-world asset adoption. This diversification expands appeal to users seeking traditional safe-haven exposure within DeFi.

Onboard wrsETH to ZKsync V3 Instance

Vote: Yes
Rationale: Supporting liquid staking derivatives on ZKsync leverages L2 scalability for reduced costs and enhanced privacy. This deployment facilitates capital-efficient strategies for cost-conscious users while advancing scaling solution adoption.

Asset Parameters Optimization

Vote: Yes
Rationale: Regular parameter maintenance ensures risk settings align with market conditions and utilization patterns. Data-driven optimizations maintain capital efficiency while protecting against emerging risks and preserving protocol stability.

[ARFC] Aave Events & Sponsorship Budget 2025

Vote: Yes
Rationale: Formalizing the budget through ARFC ensures transparent resource allocation for community building and ecosystem development. Strategic event participation and developer support nurture the next generation of DeFi builders while maintaining market leadership.

Kene_StableLab · August 12, 2025, 11:21am

[ARFC] Aave Asset class Allowlist (AAcA) creation

Vote: Yes
Rationale: Creating the Aave Asset class Allowlist establishes a systematic framework for categorizing and onboarding assets based on risk profiles and technical characteristics. This standardized approach streamlines governance processes, enhances risk management clarity, and ensures consistent evaluation criteria across all asset listings while maintaining protocol security standards.

Upgrade Aave instances to v3.5

Vote: Yes
Rationale: The v3.5 upgrade delivers essential protocol enhancements, including refined liquidation mechanisms, improved cross-chain messaging, and optimized gas consumption patterns. These technical improvements strengthen Aave’s infrastructure while providing users with more efficient transactions and enhanced capital utilization

GHO Gnosis Launch

Vote: Yes
Rationale: Expanding GHO to Gnosis Chain leverages the network’s strong stablecoin ecosystem and payment-focused infrastructure to drive adoption. This deployment capitalizes on Gnosis’s low-cost environment and established DeFi community while enhancing GHO’s multi-chain presence and utility in real-world payment scenarios.

Caps Risk Oracle Activation on Optimism, BNB, Gnosis, Polygon

Vote: Yes
Rationale: Activating Caps Risk Oracles across multiple chains enables dynamic, data-driven supply and borrow cap adjustments that respond to real-time market conditions. This automation reduces governance overhead while maintaining optimal risk parameters, enhancing protocol resilience and capital efficiency across all deployments.

Interest Rate Update - WETH and wstETH Ethereum

Vote: Yes
Rationale: Optimizing interest rate curves for WETH and wstETH reflects current market dynamics and utilization patterns, ensuring competitive rates that balance depositor returns with borrower demand. These adjustments maintain Aave’s market leadership in ETH lending while supporting healthy protocol utilization and sustainable yields.

[TEMP CHECK] Update forum features

Vote: Yes
Rationale: Modernizing forum features enhances governance participation and decision-making efficiency through improved user experience and communication tools. These updates support more informed discussions and streamlined proposal processes, strengthening Aave’s decentralized governance infrastructure.

[ARFC] Claiming AAVE Rewards for the Sablier Legacy v1.1 Contract

Vote: Yes
Rationale: Claiming accumulated AAVE rewards from the Sablier Legacy contract ensures proper asset recovery and treasury optimization. This administrative action demonstrates responsible financial management while maximizing available resources for future protocol development and incentive programs.

July 2025 - Funding Update

Vote: Yes
Rationale: July funding allocation maintains operational continuity for essential protocol services, development initiatives, and service provider compensation. This regular funding cycle ensures uninterrupted progress on strategic objectives while demonstrating fiscal discipline and transparent resource management.

Fire drill proposal Avalanche VotingMachine

Vote: Yes
Rationale: This was simply a fire drill on the Avalanche VotingMachine tests cross-chain governance infrastructure and emergency response procedures.

Add USDe to the sUSDe emode Category

Vote: Yes
Rationale: Including USDe in the sUSDe efficiency mode enables capital-efficient strategies between correlated Ethena ecosystem assets. This optimization reduces collateral requirements for users implementing delta-neutral positions while maintaining appropriate risk parameters for these related instruments.

Safety Module Emission Update

Vote: Yes
Rationale: Adjusting Safety Module emissions ensures sustainable staking incentives that balance protocol security with token economics. This calibration maintains adequate coverage for potential shortfall events while optimizing reward distributions to align with current market conditions and staking participation rates.

amend PT-sUSDe september stablecoin emode

Vote: Yes
Rationale: Amending the PT-sUSDe September stablecoin efficiency mode parameters ensures optimal capital efficiency as the principal token approaches maturity. These targeted adjustments maintain appropriate risk controls while maximizing utility for users engaged in fixed-rate strategies.

wS and BTC.b Interest Rate Curve Optimization

Vote: Yes
Rationale: Optimizing interest rate curves for wrapped assets and bridged Bitcoin variants ensures competitive market positioning and healthy utilization rates. These adjustments reflect evolving market dynamics while maintaining attractive yields for depositors and sustainable borrowing costs across Bitcoin-denominated markets.

Onboard USDe September expiry PT tokens on Aave V3 Core Instance

Vote: Yes
Rationale: Adding September expiry USDe principal tokens expands fixed-income opportunities within Aave, catering to users seeking predictable yields. This integration supports the growing tokenized yield market while providing additional collateral options that complement existing stablecoin strategies.

[ARFC] Dynamic Calibration of CAPO Parameters via Risk Oracles

Vote: Yes
Rationale: Implementing dynamic CAPO parameter calibration through risk oracles automates critical risk management functions based on real-time market data. This advancement reduces manual intervention requirements while ensuring protocol parameters remain optimally aligned with market conditions and risk profiles.

[ARFC] Orbit Program Renewal - Q2 2025

Vote: Yes
Rationale: Renewing the Orbit Program continues to incentivize active participation and accountability among Aave delegates. This program has been instrumental in fostering a vibrant and responsive governance ecosystem.

Robot Maintenance

Vote: Yes
Rationale: Regular Aave robot maintenance ensures automated protocol functions operate reliably, including liquidations, parameter updates, and cross-chain communications. This technical upkeep prevents operational disruptions while maintaining the efficiency and security of critical protocol automation infrastructure.

Deprecation of Long-tail Assets

Vote: Yes
Rationale: Removing underutilized long-tail assets reduces protocol complexity and concentrates liquidity in more active markets. This strategic consolidation improves capital efficiency, reduces risk surface area, and focuses resources on assets with meaningful adoption and utility.

stS Loop Incentive Program

Vote: Yes
Rationale: The stS Loop program incentivizes sophisticated strategies that deepen liquidity and improve market efficiency through structured looping mechanisms. This targeted approach attracts professional users while enhancing protocol metrics and supporting sustainable growth without encouraging short-term mercenary behavior.

[ARFC] Deploy a Whitelabel Aave V3 Instance on Ink

Vote: Yes
Rationale: Deploying a whitelabel instance on Ink expands Aave’s institutional reach through customized implementations that maintain core protocol security. This strategic partnership model enables tailored solutions for specific ecosystems while generating additional revenue streams and expanding Aave’s market presence.

[ARFC] Safety Module Emission Update

Vote: Yes
Rationale: Updating Safety Module emissions ensures staking incentives remain competitive and sustainable given current market dynamics. This recalibration maintains robust protocol security through adequate staking participation while optimizing token distribution efficiency.

[TEMP CHECK] Onboard fxSAVE to Aave V3 Core Instance

Vote: Yes
Rationale: Exploring fxSAVE integration introduces innovative forex-backed stablecoin options that diversify collateral beyond traditional crypto assets. This addition addresses the growing demand for multi-currency exposure while supporting Aave’s position in the evolving real-world asset integration landscape.

Onboard sUSDe September expiry PT tokens on Aave V3 Core Instance

Vote: Yes
Rationale: Adding sUSDe September PT tokens provides users with fixed-rate stablecoin opportunities through Ethena’s yield-bearing infrastructure. This integration supports sophisticated yield strategies while expanding the protocol’s suite of time-based financial instruments.

[TEMP CHECK] Onboard xSolvBTC to Aave V3 BOB Instance

Vote: Yes
Rationale: Integrating xSolvBTC on the BOB instance diversifies Bitcoin-denominated collateral options through Solv Protocol’s innovative wrapped asset. This addition enhances cross-chain Bitcoin utility while supporting BOB’s growing DeFi ecosystem with established lending infrastructure.

[TEMP CHECK] Onboard SolvBTC to Aave V3 BOB Instance

Vote: Yes
Rationale: Adding SolvBTC complements the xSolvBTC integration, providing users with flexible Bitcoin exposure options on BOB. This dual approach caters to different risk preferences and use cases while strengthening Aave’s position in the Bitcoin DeFi landscape.

[TEMP CHECK] Onboard openUSDT to Aave V3 BOB Instance

Vote: Yes
Rationale: Onboarding openUSDT to the BOB instance expands stablecoin diversity and provides users with additional stable value options. This integration supports BOB’s multi-asset strategy while enhancing liquidity and trading pair availability within the ecosystem.

[ARFC] Update Signers and SAFE Configuration

Vote: Yes
Rationale: Updating multisig signers and SAFE configuration maintains robust operational security and reflects current contributor participation. These administrative updates ensure proper access controls and governance execution capabilities while adapting to evolving organizational needs.

CEX Earn Funding Proposal

Vote: Yes
Rationale: Funding CEX expands Aave’s reach to traditional exchange users. This initiative drives protocol adoption through familiar interfaces while maintaining decentralization principles and generating sustainable revenue streams.

Chaos Labs x Aave DAO — Early Renewal Proposal

Vote: Yes
Rationale: Early renewal ensures continuity of critical risk management services that have proven instrumental in maintaining protocol security. Securing favorable terms guarantees uninterrupted data-driven insights and parameter optimization during rapid growth periods.

Topic		Replies	Views
Keyrock Delegate Platform Delegate Platforms	34	4868	September 19, 2024
TokenLogic Delegate Platform Delegate Platforms	24	4823	August 17, 2025
Kpk Delegate Platform Delegate Platforms	107	7433	September 4, 2025
EzR3aL Delegate Platform Delegate Platforms	36	3738	July 17, 2025
LBS Blockchain Society Delegate Platform Delegate Platforms	684	17951	February 28, 2024

StableLab Delegate Platform

[ARFC] Aave Asset class Allowlist (AAcA) creation

Upgrade Aave instances to v3.5

GHO Gnosis Launch

Caps Risk Oracle Activation on Optimism, BNB, Gnosis, Polygon

Interest Rate Update - WETH and wstETH Ethereum

[TEMP CHECK] Update forum features

[ARFC] Claiming AAVE Rewards for the Sablier Legacy v1.1 Contract

July 2025 - Funding Update

Fire drill proposal Avalanche VotingMachine

Add USDe to the sUSDe emode Category

Safety Module Emission Update

amend PT-sUSDe september stablecoin emode

wS and BTC.b Interest Rate Curve Optimization

Onboard USDe September expiry PT tokens on Aave V3 Core Instance

[ARFC] Dynamic Calibration of CAPO Parameters via Risk Oracles

[ARFC] Orbit Program Renewal - Q2 2025

Robot Maintenance

Deprecation of Long-tail Assets

stS Loop Incentive Program

[ARFC] Deploy a Whitelabel Aave V3 Instance on Ink

[ARFC] Safety Module Emission Update

[TEMP CHECK] Onboard fxSAVE to Aave V3 Core Instance

Onboard sUSDe September expiry PT tokens on Aave V3 Core Instance

[TEMP CHECK] Onboard xSolvBTC to Aave V3 BOB Instance

[TEMP CHECK] Onboard SolvBTC to Aave V3 BOB Instance

[TEMP CHECK] Onboard openUSDT to Aave V3 BOB Instance

[ARFC] Update Signers and SAFE Configuration

CEX Earn Funding Proposal

Chaos Labs x Aave DAO — Early Renewal Proposal

Related topics