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