StableLab Delegate Platform

Delegate Platforms
101

Add Fluid Protocol to flashBorrowers
Vote: Yes
Rationale: Whitelisting Fluid Protocol for flash borrowing expands Aave’s integration ecosystem and enables advanced DeFi composability. This integration supports capital-efficient strategies while maintaining strict security requirements through the established flashBorrower whitelist mechanism.

[ARFC] Deploy Aave v3 on Plasma
Vote: Yes
Rationale: Deploying on Plasma extends Aave’s multi-chain presence to an emerging ecosystem with strong institutional backing. This strategic expansion captures new liquidity sources while leveraging Plasma’s high-throughput infrastructure for enhanced user experience and reduced transaction costs.

[TEMP CHECK] Onboard USDG to Aave V3 Core Instance
Vote: Yes
Rationale: Adding USDG diversifies stablecoin offerings with a regulated, fiat-backed option that appeals to compliance-conscious users. This integration strengthens Aave’s position in bridging traditional finance with DeFi while expanding stable asset choices for risk-averse participants.

Onboard USDe November expiry PT tokens on Aave V3 Core Instance
Vote: Yes
Rationale: November expiry USDe PT tokens continue Aave’s support for fixed-rate instruments through Pendle’s ecosystem. This addition provides users with predictable yield opportunities while deepening liquidity for term-structured products within the protocol.

[ARFC] Aave v2 Deprecation - Update
Vote: Yes
Rationale: Progressing v2 deprecation consolidates resources on superior v3 infrastructure while maintaining user safety through gradual transition. This update ensures clear communication and migration pathways, reducing operational complexity while focusing development on active deployments.

[ARFC] Add Fluid Protocol to flashBorrowers
Vote: Yes
Rationale: Formally adding Fluid Protocol to the flashBorrower whitelist enables innovative lending strategies and arbitrage opportunities. This integration demonstrates Aave’s commitment to fostering DeFi innovation while maintaining appropriate access controls for flash loan functionality.

[ARFC] Aave v2 deprecation (tech) - next phase
Vote: Yes
Rationale: Implementing technical deprecation steps ensures systematic wind-down of v2 operations without disrupting user positions. This phased approach prioritizes security and user protection while efficiently transitioning resources to modern v3 infrastructure.

Multi eMode Update and Creation - rsETH, ezETH, wstETH and weETH
Vote: Yes
Rationale: Creating specialized eModes for correlated ETH derivatives optimizes capital efficiency for liquid staking strategies. These configurations recognize the growing LST ecosystem while maintaining appropriate risk parameters for highly correlated asset pairs.

Onboard sUSDe November expiry PT tokens on Aave V3 Core Instance
Vote: Yes
Rationale: Adding November sUSDe PT tokens expands fixed-income opportunities with Ethena’s yield-bearing stablecoin infrastructure. This integration caters to sophisticated users seeking predictable returns while diversifying Aave’s time-based instrument offerings.

[ARFC] Launch GHO on Plasma & Set ACI as Emissions Manager for Rewards
Vote: Yes
Rationale: Launching GHO on Plasma expands the stablecoin’s reach while leveraging ACI’s proven expertise in incentive management. This strategic deployment captures new user bases and enhances GHO adoption through targeted emission strategies.

[ARFC] Launch GHO on Linea & Set ACI as Emissions Manager for Rewards
Vote: Yes
Rationale: Deploying GHO on Linea leverages ConsenSys’s zkEVM technology for cost-efficient transactions and institutional connectivity. ACI’s emission management ensures optimal incentive distribution to bootstrap liquidity and drive sustainable adoption.

[TEMP CHECK] Add MetaMask USD (mUSD) to Aave v3 Core Instance on Ethereum and Linea
Vote: Yes
Rationale: Integrating MetaMask’s native stablecoin strengthens ties with the leading wallet provider while offering users familiar, trusted stable assets. Multi-chain deployment maximizes reach and reinforces Aave’s position as the premier lending venue.

Add XAUt to Aave v3 Core Instance
Vote: Yes
Rationale: Tokenized gold integration provides non-correlated collateral during market volatility and advances RWA adoption. This addition appeals to traditional investors seeking commodity exposure within DeFi’s efficiency and composability framework.

Onboard tBTC to Aave v3 on Base
Vote: Yes
Rationale: Adding Threshold’s decentralized Bitcoin wrapper on Base expands BTC collateral options in Coinbase’s ecosystem. This integration supports Bitcoin DeFi growth while maintaining decentralization principles through threshold signatures.

Ink aDI path activation
Vote: Yes
Rationale: Activating the aDI path ensures full operational capability for the Ink deployment, enabling cross-chain governance and efficient protocol management. This technical requirement maintains consistent infrastructure across all Aave instances.

[ARFC] Automation of the Slope2 Parameter via Risk Oracles
Vote: Yes
Rationale: Automating Slope2 parameters through risk oracles reduces manual intervention while ensuring interest rates dynamically respond to utilization changes. This enhancement improves capital efficiency and maintains optimal lending conditions across market cycles.

Horizon RWA Instance Activation
Vote: Yes
Rationale: Activating the Horizon RWA instance marks a significant milestone in institutional DeFi adoption, enabling regulated real-world asset lending. This specialized deployment opens new revenue streams while maintaining compliance standards for traditional finance integration.

Onboard tBTC to Aave v3 on Arbitrum
Vote: Yes
Rationale: Expanding tBTC to Arbitrum provides users with decentralized Bitcoin collateral on Ethereum’s leading L2. This deployment enhances cross-chain Bitcoin utility while benefiting from Arbitrum’s low costs and high throughput.

Claiming AAVE Rewards for the Sablier Legacy v1.1 Contract
Vote: Yes
Rationale: Recovering accumulated rewards from legacy contracts demonstrates prudent treasury management and resource optimization. This administrative action ensures all protocol-owned assets are properly claimed and utilized for ecosystem development.

[ARFC] Launch GHO on Ink & set ACI as Emissions Manager for Rewards
Vote: Yes
Rationale: Deploying GHO on Ink extends the stablecoin to institutional-focused environments while leveraging ACI’s emission expertise. This strategic expansion supports GHO’s growth trajectory through targeted incentives in specialized markets.

[ARFC] Onboard tBTC to Aave v3 on Base
Vote: Yes
Rationale: Formalizing tBTC integration on Base through the ARFC process ensures proper risk assessment and parameter configuration. This addition strengthens Bitcoin collateral diversity while supporting Base’s emerging DeFi ecosystem.

[ARFC] Add XAUt to Aave v3 Core Instance
Vote: Yes
Rationale: Progressing XAUt through formal governance validates community support for commodity-backed collateral. This RWA integration diversifies protocol risk while attracting traditional finance participants seeking regulated asset exposure.

Onboard rsETH to Aave V3 Linea Instance
Vote: Yes
Rationale: Adding Kelp’s rsETH to Linea provides users with restaking collateral options on the zkEVM. This integration supports the evolving restaking ecosystem while expanding liquid staking derivative choices across L2 deployments.

LBTC and eBTC Price Feeds Update
Vote: Yes
Rationale: Updating price feeds for Bitcoin variants ensures accurate valuations and liquidation thresholds. This technical maintenance protects protocol solvency while supporting the growing ecosystem of wrapped Bitcoin representations.

Fire drill proposal Ethereum VotingMachine
Vote: Yes
Rationale: Testing Ethereum VotingMachine functionality validates governance infrastructure resilience and emergency procedures. This proactive security measure ensures rapid response capabilities while maintaining decentralized decision-making integrity.

[TEMP CHECK] Onboard tUSDe December expiry PT tokens on Aave V3 Core
Vote: Yes
Rationale: Exploring December tUSDe PT tokens continues support for term-structured products with extended maturities. This addition provides users with longer-dated fixed-income opportunities while deepening Aave’s yield tokenization market.

[TEMP CHECK] Onboard LsETH to Aave V3 Core Instance
Vote: Yes
Rationale: Evaluating Liquid Staked ETH integration expands liquid staking options with another innovative protocol. This diversity in LST offerings enhances user choice while maintaining competitive dynamics in the staking derivative market.

Add ezETH to Aave v3 Core Instance
Vote: Yes
Rationale: Integrating Renzo’s ezETH provides users with restaking collateral that captures additional yield layers. This addition supports the growing restaking narrative while offering enhanced returns for ETH-denominated strategies.

Add tETH to Core Instance Ethereum
Vote: Yes
Rationale: Adding Threshold ETH diversifies liquid staking options with a decentralized, permissionless alternative. This integration strengthens Aave’s LST ecosystem while providing users with governance-minimized staking solutions.

102

Deprecation of Low Demand Volatile Assets on Aave V3 Instances
Vote: Yes
Rationale: Removing underutilized volatile assets streamlines protocol operations and concentrates liquidity in active markets. This strategic consolidation reduces risk exposure, simplifies maintenance overhead, and improves capital efficiency by focusing resources on assets with meaningful adoption.

XPL Onboarding
Vote: Yes
Rationale: Onboarding XPL expands Aave’s asset diversity and captures emerging market opportunities. This integration demonstrates continued protocol innovation while maintaining strict risk parameters and providing users with access to new collateral options.

Orbit Program Renewal - Q3 and Q4 2025
Vote: Yes
Rationale: Continuing the Orbit Program maintains vital delegate engagement and accountability mechanisms that strengthen governance quality. This renewal ensures sustained participation incentives while fostering informed decision-making across the Aave ecosystem.

Reinstate Supply and Borrow Caps on Aave V3 Gnosis Instance
Vote: Yes
Rationale: Reinstating caps on Gnosis reflects prudent risk management based on current market conditions and utilization patterns. This adjustment protects protocol stability while maintaining appropriate growth parameters for the Gnosis deployment.

Safety Module Emissions Update
Vote: Yes
Rationale: Adjusting Safety Module emissions ensures sustainable staking incentives that balance security coverage with token economics. This calibration maintains adequate protection against shortfall events while optimizing reward distributions for current market dynamics.

Aave BGD Phase 6 & Project E agreement
Vote: Yes
Rationale: Extending BGD Labs’ engagement ensures continuity of critical protocol development and maintenance services. Their proven expertise in Aave infrastructure and Project E advancement justifies continued collaboration for protocol evolution and security.

Security Services for Aave v4 <> Certora
Vote: Yes
Rationale: Engaging Certora for v4 security services provides industry-leading formal verification for next-generation protocol architecture. This proactive security investment protects users and maintains Aave’s reputation for robust, audited infrastructure.

Security Services for Aave Current Infrastructure <> Certora
Vote: Yes
Rationale: Maintaining Certora’s security coverage for existing infrastructure ensures continuous protection while v4 development progresses. This dual-track approach prevents security gaps during the transition period between protocol versions.

Service Provider Compensation Reform for V4 Alignment
Vote: Yes
Rationale: Reforming compensation structures aligns service provider incentives with v4 development milestones and long-term protocol success. This strategic adjustment ensures efficient resource allocation while attracting top talent for critical infrastructure work.

Addition of cbBTC/Stablecoin E-Mode to Aave V3 Base Instance
Vote: Yes
Rationale: Creating specialized E-Mode for Coinbase’s wrapped Bitcoin enables capital-efficient strategies on Base network. This configuration leverages institutional-grade infrastructure while maintaining appropriate risk parameters for correlated asset pairs.

USDC (old) deprecation on Gnosis Chain Instance
Vote: Yes
Rationale: Deprecating legacy USDC implementation reduces confusion and consolidates liquidity in the updated version. This technical cleanup ensures users interact with current infrastructure while maintaining smooth migration pathways.

[ARFC] Aave V4 Security Funding
Vote: Yes
Rationale: Allocating dedicated security funding for v4 development demonstrates commitment to robust protocol architecture. This investment in comprehensive audits and formal verification protects future users while maintaining Aave’s security-first approach.

Extend Ahab Funding
Vote: Yes
Rationale: Continuing Ahab’s funding supports essential protocol analytics and monitoring services. Their specialized expertise in Aave metrics and risk assessment justifies extended engagement for maintaining operational excellence.

[ARFC] Aave DAO <> BGD Labs. Phase 6 & Project E
Vote: Yes
Rationale: Formalizing BGD’s continued engagement through governance ensures transparent service provider relationships. Their technical leadership on core protocol development and Project E innovation remains crucial for Aave’s competitive positioning.

[ARFC] AAVE Buybacks program: An update
Vote: Yes
Rationale: Updating the buyback program parameters ensures efficient treasury management and value accrual mechanisms. This adjustment reflects current market conditions while maintaining sustainable tokenomics that benefit long-term holders.

[ARFC] Orbit Program Renewal - Q3 and Q4 2025
Vote: Yes
Rationale: The ARFC stage confirms community support for continued delegate incentivization through the Orbit Program. This structured approach to governance participation maintains high-quality decision-making and active ecosystem engagement.

Onboard sUSDe and USDe to Aave V3 Avalanche Instance
Vote: Yes
Rationale: Expanding Ethena ecosystem assets to Avalanche captures cross-chain yield opportunities and enhances stablecoin diversity. This deployment leverages Avalanche’s high throughput for efficient delta-neutral strategies.

Add Fluid Protocol to flashBorrowers on Plasma
Vote: Yes
Rationale: Whitelisting Fluid on Plasma extends flash loan capabilities to emerging deployments, enabling advanced arbitrage and liquidation strategies. This integration supports ecosystem development while maintaining controlled access to critical functionality.

Slope2 Risk Oracle Activation On Core Ethereum, Linea
Vote: Yes
Rationale: Activating automated Slope2 parameters on key deployments enhances interest rate responsiveness to utilization changes. This oracle-driven approach reduces governance overhead while maintaining optimal lending conditions across market cycles.

[ARFC] Security Services for Aave Current Infrastructure <> Certora
Vote: Yes
Rationale: The ARFC stage validates community support for maintaining Certora’s security services on existing infrastructure. Continuous formal verification protects current users while development teams focus on v4 architecture.

[ARFC] Evolving Resilience: Security Services for Aave v4 <> Certora
Vote: Yes
Rationale: Securing Certora’s expertise for v4 development ensures cutting-edge formal verification from design through deployment. This early engagement enables security-by-design principles that strengthen next-generation protocol architecture.

[ARFC-Addendum] Update Merit for Round 33 - Adding Gate.io
Vote: Yes
Rationale: Including Gate.io in Merit distributions recognizes their contribution to GHO liquidity and ecosystem growth. This addition incentivizes continued exchange support while expanding Aave’s presence in key markets.

Onboard syrupUSDT to Aave V3 Plasma Instance
Vote: Yes
Rationale: Adding yield-bearing USDT variant to Plasma provides users with enhanced stablecoin options on the new deployment. This integration supports capital efficiency while maintaining exposure to the dominant stablecoin.

[ARFC] USDC (old) deprecation on Gnosis Chain Instance
Vote: Yes
Rationale: Progressing legacy USDC deprecation through formal governance ensures community alignment on technical improvements. This cleanup reduces operational complexity while directing users to updated infrastructure.

[ARFC] Service Provider Compensation Reform for V4 Alignment
Vote: Yes
Rationale: The ARFC stage confirms stakeholder support for compensation restructuring that aligns with v4 development goals. This reform ensures competitive retention of critical service providers during the protocol transition.

Onboard wrsETH to Aave v3 Plasma Instance
Vote: Yes
Rationale: Integrating wrapped rsETH on Plasma expands liquid staking options on the institutional-focused deployment. This addition provides sophisticated users with restaking exposure while maintaining familiar Aave infrastructure.

Onboard sUSDe and USDe January expiry PT tokens on Aave V3 Plasma Instance
Vote: Yes
Rationale: Adding January expiry tokens to Plasma extends fixed-income opportunities to institutional users. These longer-dated instruments support sophisticated yield strategies while deepening term structure markets.

[TEMP CHECK] Onboard frxUSD to Aave v3 Ethereum Core Instance
Vote: Yes
Rationale: Exploring Frax’s algorithmic stablecoin integration diversifies collateral options with innovative stability mechanisms. This addition supports protocol experimentation while maintaining risk controls for algorithmic assets.

[ARFC] Extend Ahab Funding
Vote: Yes
Rationale: The ARFC process validates continued support for Ahab’s analytical services that enhance protocol transparency. Their specialized monitoring capabilities remain essential for risk management and operational insights.

[ARFC] TokenLogic - Phase II
Vote: Yes
Rationale: Renewing TokenLogic’s engagement continues valuable treasury management and strategic advisory services. Their proven track record in optimizing protocol economics justifies extended collaboration for sustainable growth.

Gho Plasma Launch
Vote: Yes
Rationale: Deploying GHO on Plasma extends the native stablecoin to institutional environments with enhanced compliance features. This strategic expansion captures new user segments while maintaining GHO’s decentralized principles.

Allow PyUSD as collateral
Vote: Yes
Rationale: Enabling PayPal’s stablecoin as collateral bridges traditional finance users into DeFi lending markets. This integration leverages PyUSD’s regulatory clarity and distribution network for expanded protocol adoption.

Adopt The SEAL Safe Harbor Agreement
Vote: Yes
Rationale: Implementing standardized legal frameworks provides clarity for DAO operations and participant protections. This proactive approach to regulatory compliance strengthens Aave’s institutional readiness while maintaining decentralized governance.

Full Deprecation of DPI Across Aave Deployments
Vote: Yes
Rationale: Removing DeFi Pulse Index reflects low utilization and concentration risks from index composition changes. This deprecation simplifies protocol operations while encouraging migration to more liquid collateral options.

[TEMP CHECK] Onboard USDai & sUSDai to Aave V3 Plasma & Arbitrum Instance
Vote: Yes
Rationale: Exploring Instadapp’s stablecoin ecosystem integration provides users with additional yield-bearing options across L2s. This multi-chain approach captures emerging stablecoin innovations while maintaining protocol diversity.

[ARFC] Aave v3.6 candidate
Vote: Yes
Rationale: The v3.6 candidate introduces incremental improvements in gas optimization and risk management features. This iterative upgrade maintains protocol competitiveness while preparing infrastructure for v4 transition.

Claim Aave v2 stkAAVE rewards
Vote: Yes
Rationale: Claiming accumulated rewards ensures proper treasury management and resource optimization. This administrative action recovers protocol-owned assets for redeployment in current incentive programs.

Steward Deployment: MainnetSwapSteward and RewardsSteward
Vote: Yes
Rationale: Deploying automated steward contracts reduces governance overhead for routine parameter adjustments and reward distributions. This infrastructure enhancement improves operational efficiency while maintaining security controls.

[ARFC] Safety Module & Umbrella Emission Update
Vote: Yes
Rationale: Coordinating emissions across Safety Module and Umbrella systems optimizes security incentives for evolving risk profiles. This holistic approach ensures adequate coverage while managing token distribution efficiency.

pyUSD Parameters Optimization
Vote: Yes
Rationale: Adjusting PyUSD parameters based on utilization data ensures competitive positioning and appropriate risk settings. These optimizations reflect market adoption patterns while maintaining conservative collateral requirements.

Aave v2 Deprecation - Update
Vote: Yes
Rationale: Continuing v2 deprecation milestones maintains momentum toward full migration while protecting remaining users. This systematic approach ensures orderly transition without forcing premature position closures.

Aave Liquidity Committee Funding Phase VII
Vote: Yes
Rationale: Extending Liquidity Committee funding maintains strategic market-making and incentive programs across deployments. Their expertise in liquidity optimization remains crucial for protocol growth and efficient markets.

Bob Network aDI path activation
Vote: Yes
Rationale: Activating cross-chain governance infrastructure on BOB network ensures consistent protocol management. This technical requirement enables efficient parameter updates and maintains operational standards across deployments.

[ARFC] Add MetaMask USD (mUSD) to Aave v3 Core Instance on Ethereum and Linea
Vote: Yes
Rationale: Progressing mUSD through governance confirms community support for MetaMask’s stablecoin integration. This partnership strengthens wallet-to-protocol connectivity while expanding stable collateral options.

[ARFC-Addendum] Update Merit for Round 30
Vote: Yes
Rationale: Merit round updates ensure accurate distribution based on actual contributions and performance metrics. This adjustment maintains program integrity while recognizing valuable ecosystem participation.

[ARFC] Endorse the Asset Classification Framework (AAcA)
Vote: Yes
Rationale: Formally endorsing the classification framework establishes clear asset onboarding criteria and risk categorization. This standardization improves governance efficiency while maintaining consistent evaluation standards.

[ARFC] Aave Liquidity Committee Funding Phase VII
Vote: Yes
Rationale: The ARFC stage validates continued support for Liquidity Committee operations across strategic markets. Their proven expertise in incentive optimization justifies extended funding for protocol growth.

GHO Ink Launch
Vote: Yes
Rationale: Launching GHO on Ink expands the stablecoin to specialized institutional environments with unique compliance features. This deployment captures regulated market segments while advancing GHO adoption.

[TEMP CHECK] Deploy Aave v3 on X Layer
Vote: Yes
Rationale: Exploring deployment on X Layer evaluates new scaling solutions for potential market expansion. This assessment considers technical capabilities and ecosystem development for strategic positioning.

Aave V3.5 Plasma Activation
Vote: Yes
Rationale: Upgrading Plasma to v3.5 ensures deployment parity with latest protocol improvements and security enhancements. This activation maintains consistent infrastructure standards across all Aave instances.

Aave V2 deprecation
Vote: Yes
Rationale: Formalizing v2 deprecation timeline provides clear migration expectations while focusing resources on modern infrastructure. This decisive action improves protocol efficiency and reduces technical debt.

[ARFC] Safety Module & Umbrella Emission Update
Vote: Yes
Rationale: The ARFC process ensures community alignment on coordinated emission strategies across security mechanisms. This integrated approach optimizes incentive efficiency while maintaining robust protocol protection.

[ARFC] Steward Deployment: MainnetSwapSteward and RewardsSteward
Vote: Yes
Rationale: Governance approval for steward contracts confirms support for automated parameter management infrastructure. These efficiency improvements reduce operational overhead while maintaining decentralized control.

Plasma aDI path activation
Vote: Yes
Rationale: Enabling cross-chain messaging on Plasma completes deployment infrastructure for seamless governance execution. This activation ensures consistent protocol management across the institutional-focused instance.

Raise sUSDe and USDe November expiry PT tokens caps on Aave V3 Core Instance
Vote: Yes
Rationale: Increasing caps responds to strong demand for fixed-income products while maintaining conservative risk parameters. This adjustment supports market growth without compromising protocol security.

Add EURC to Avalanche V3 Instance
Vote: Yes
Rationale: Expanding EURC to Avalanche provides Euro exposure on high-throughput infrastructure for cost-efficient operations. This deployment captures cross-chain stablecoin demand while diversifying currency options.

Risk Parameter Adjustments for Aave V3 Scroll Instance
Vote: Yes
Rationale: Optimizing Scroll parameters based on initial deployment data ensures appropriate risk settings for the zkEVM environment. These adjustments reflect actual usage patterns while maintaining conservative security margins.

Request for Bounty Payout - August 2025
Vote: Yes
Rationale: Approving legitimate bounty payments incentivizes continued security research and vulnerability disclosure. This commitment to bug bounty programs strengthens protocol security through community engagement.

[ARFC] Adopt The SEAL Safe Harbor Agreement
Vote: Yes
Rationale: The ARFC stage confirms stakeholder support for implementing standardized legal protections. This framework provides regulatory clarity while preserving decentralized governance principles.

Increase rsETH Supply Cap on Aave V3 Linea Instance
Vote: Yes
Rationale: Raising rsETH caps accommodates growing demand for liquid staking collateral on Linea’s zkEVM. This adjustment supports user growth while maintaining appropriate risk controls for the deployment.

September Funding Update
Vote: Yes
Rationale: Monthly funding ensures operational continuity for service providers and development initiatives. This regular allocation maintains protocol momentum while demonstrating transparent treasury management.

GHO Facilitator Replacement
Vote: Yes
Rationale: Upgrading GHO facilitator infrastructure improves minting efficiency and enables enhanced features for the native stablecoin. This technical improvement supports GHO’s evolution and competitive positioning.