A Stable Rate Built on Variable Yield
Stable Vaults are designed for businesses that want to offer stablecoin earning without exposing customers to lending pools, bridges, variable APYs, or yield strategy selection. A platform chooses the stablecoins it accepts, the strategies it permits, who can deposit, and the rate it offers to each customer segment. The user receives a position in a SubVault that accrues at a configured per-second rate.
The important distinction is that the rate paid to a user is not a direct pass-through of the rate earned by the underlying Aave market. Lending rates can change with utilization. Stable Vaults place that variability inside the vault system, where an offchain manager rebalances capital between approved strategies to meet the rates assigned across SubVaults. A platform can therefore offer different rates for loyalty tiers, campaigns, subscription plans, or other product rules.
That makes the product closer to embedded savings infrastructure than a conventional DeFi vault. The integrator owns the customer experience and revenue model. Aave supplies the contracts, accounting, strategy adapters, and operational boundaries. This is a deliberate shift from Aave as a destination for onchain lending toward Aave as a back end for financial applications.
How the System Is Arranged
The Accounting Chain is the record of user balances, withdrawals, and system surplus. In the Aave App deployment, that chain is Arbitrum. Earning Chains host strategies and publish balance snapshots back to the Accounting Chain through a Chainlink-powered oracle flow. Ethereum mainnet is the initial Earning Chain described in the documentation.
On deposit, the Stable Vault checks the asset price, mints shares into the user’s assigned SubVault, and sends capital through a Funds Handler to an Allocator. The Allocator holds idle balances, routes funds into approved ERC-4626 strategies, and uses a dedicated swapper for asset conversions. Approved strategies can include Aave V4 markets, Aave V3 markets, Savings GHO, and third-party ERC-4626 vaults selected by the integrator.
Withdrawals use two steps. A user requests a withdrawal, burns shares, and receives IOUs representing a claim in the vault’s denomination currency. The principal portion is always redeemable as IOUs. Interest can be converted into IOUs only when the system has sufficient trusted surplus. At execution, the user selects an approved output asset and the policy applies any withdrawal fee.
Multi-Asset, Multi-Chain, and Controlled Access
The vault treats approved stablecoins as equivalent after deposit. A USDC depositor can redeem into USDT, GHO, or another approved asset, subject to available liquidity on the destination chain. That reduces the need to maintain a separate product for each stablecoin, but it makes the Asset Registry and liquidity management central to the product’s operation.
Integrators define the trusted surface. They approve assets, yield strategies, and bridges. Managers can rebalance or move funds only within those lists. The separation is useful for a fintech that wants to delegate day-to-day allocation while retaining control over the counterparties and assets its customers can touch.
The Product Question
Stable Vaults give fintechs a way to offer a simpler yield proposition while keeping the underlying strategy stack flexible. The trade-off is clear: users gain a stable-rate interface, but the operator must manage allocation, liquidity, bridge execution, and the gap between promised rates and variable strategy returns. The product will be judged less by its architecture than by whether integrators can sustain those operational responsibilities at scale.
Not financial advice. Stablecoin yield products involve smart contract, liquidity, asset, and operational risks.
