StableLab Delegate Platform

Delegate Platforms
81

[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.

82

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.

1 Like
83

[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.

84

[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.

85

[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.

86

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.

87

[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.

88

[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.

89

[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.

90

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

We apologize for any inconvenience that this may cause.

91

[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.

92

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.

93

[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.

94

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.