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.