Aave - EncryptedGuru

Current reading

Supply is not savings, and borrow capacity is not free liquidity.

Protocol: Aave, a decentralized non-custodial liquidity protocol
Market: V3 reserves or V4 Liquidity Hubs and Spokes; each deployment has its own parameters
Position: Supplied collateral, debt, interest, and health factor
Reading rule: Live parameters and exact contract addresses before action

This is research and systems documentation, not financial, lending, tax, or investment advice. Rates, assets, networks, parameters, interfaces, and third-party services can change.

Documentation review: 30 Sep 2026. V3/V4 deployments, tokenized-equity collateral, and the newly documented Aave App account model were reviewed; live market parameters, rates, eligibility, and app behavior must be rechecked at action time.

Read official Aave docs Open live parameters

Decision frame / before conviction

Follow the position before you price the yield.

Aave becomes legible when the position is followed from supply to exit, with live risk parameters and wallet control kept separate from the interface.

Open the capital decision record

01 / Problem

Onchain liquidity with conditions

Aave coordinates supply and borrow markets. The decision is whether the position's liquidity, risk, costs, and exit path justify its variable output.

02 / Layer

Protocol / app / governance

Aave is the protocol, the Aave App is the interface, and AAVE is the governance token. A familiar app does not collapse those boundaries.

03 / Verified

Mechanics, not live conditions

Official material now spans V3 reserves and V4 Hubs and Spokes. Rates, reserve or spoke parameters, addresses, liquidity, and app behavior still need current checks.

04 / Dependencies

Contracts, oracle, market, network

Smart contracts, V3 reserves or V4 hubs and spokes, price data, collateral liquidity, liquidation rules, chain deployments, bridges, asset issuers, legal eligibility, RPCs, and wallet or frontend behavior shape the position.

05 / Control

Keys, approvals, position

You control the wallet key, approvals, and position actions. You do not control oracle output, governance changes, liquidation conditions, or market liquidity.

06 / Exit + review

Repay, withdraw, re-check

Before action, verify the exact reserve, health factor, available liquidity, rate, network, recipient, and repayment or withdrawal route. Re-check before each material change.

Action layer

Ready to review the Aave App entry?

Open the disclosed referral entry only after checking the current official app, network, wallet permissions, market terms, and liquidation conditions. The referral is not evidence of protocol safety or yield.

Open Aave App

First principles

What the official Aave material supports.

01

Pooled liquidity

Suppliers and borrowers interact with smart-contract markets. A supplied asset can earn interest, while access to it remains subject to liquidity, reserve configuration, and the position's collateral state.

02

Collateral first

Aave's core borrowing model is overcollateralized: supplied collateral supports a smaller borrowing position, with each reserve carrying its own thresholds, caps, and risk settings.

03

Utilization moves rates

Interest rates respond to market utilization. Supplier yield is connected to borrower interest and reserve mechanics, so an advertised rate is a variable market output, not a fixed promise.

04

Health factor is live

Collateral value, debt, oracle prices, and liquidation thresholds determine health. When a position falls below the relevant safety boundary, it may become eligible for liquidation.

Architecture

Aave is a stack of trust boundaries, not one riskless balance.

01 Contracts and reserves

V3 markets expose reserve-level configuration; V4 organizes shared liquidity in Hubs connected to Spokes with their own assets and risk parameters. The exact version, deployment, asset, network, and current parameter matter more than a familiar interface.

02 Oracles and prices

Collateral valuation and liquidation logic depend on price data. Oracle behavior, asset liquidity, market conditions, and stale or unexpected prices are part of the position's security model.

03 Risk controls

E-Mode, Isolation Mode, and Siloed Borrowing change which assets and positions can interact. A risk control described in the docs is not a promise that every market exposes the same configuration.

04 Network and interface

Chain deployments, bridges, wallets, RPC providers, frontends, and account abstractions add separate failure and custody boundaries. “Aave” does not erase the risk of the route used to reach it.

Market expansion / asset boundaries

One protocol name now spans very different collateral and chain risks.

Aave's official documentation lists a live V4 instance on Arc, while Aave Labs has separately announced tokenized-equity collateral on V4 Base. These are distinct deployments and asset models, not a single interchangeable market.

Arc / V4 market

Aave's documentation changelog records the Arc instance as activated on 16 Sep 2026, with a Core Hub and Main and Forex Spokes listing USDC, EURC, cirBTC, and WETH. Verify current caps, parameters, governance controls, and network assumptions in the live market rather than carrying them across from Ethereum or Avalanche.

Check Aave's deployment changelog

Base / tokenized equity collateral

Aave Labs says seven Coinbase tokenized U.S. technology stocks can be posted as collateral to borrow USDC in a dedicated V4 Equities Hub. The announcement describes certificates issued by Coinbase Onchain SPV, with underlying shares held by Alpaca Securities in segregated accounts in the issuer's name; availability is limited to eligible non-U.S. persons and jurisdictions. This is not the same as a wallet holding unrestricted, directly transferable shares.

The announcement also describes Chainlink 24/5 equity feeds that retain the last published price while U.S. markets are closed, and reserve pauses for corporate actions. Continuous onchain access therefore does not mean continuously refreshed equity pricing or uninterrupted position changes.

Read Aave Labs' market description and disclosures

Evidence boundary: these are deployment and product descriptions published by Aave Labs/Aave documentation, not independent legal, issuer, custodian, oracle, or market-depth audits. Check the exact asset, jurisdiction, live oracle state, collateral factor, supply/borrow caps, and exit path before acting.

Aave App / account architecture

Recovery improves access and adds dependencies to the control path.

Aave Labs describes the App as self-custodial. Its published design combines a device-created signer key, encrypted backup, and a smart contract account. That is a different trust path from connecting a wallet directly to the Aave protocol.

Signer and backup

Aave says the EOA key is created on the user's device, encrypted with the user's password and email or phone credential, then stored in encrypted form by Aave's backend. Signing authority still depends on the key, while recovery and access also depend on authentication and backend availability.

Two recovery paths

Device recovery requires a previously signed-in device. The optional biometric path uses CoinCover: Aave describes a face scan and encrypted key shares split between CoinCover and Aave, with an OTP step. Convenience therefore introduces identity, provider, and recovery-process dependencies.

Smart account permissions

The App uses Alchemy's Modular Account v2. Aave says the smart account can grant scoped permissions, including moving stablecoins into a vault after arrival; withdrawal destinations are pre-authorized. Check each permission and destination rather than treating “self-custody” as “no delegated action.”

Evidence boundary: this summarizes Aave Labs' account-design article published 15 Sep 2026. It is not an independent cryptographic, privacy, or recovery audit; confirm the current flow and permissions in the App before use.

Read Aave Labs' account architecture explanation

Assistant tooling / authorization

An assistant can prepare a transaction; your wallet still needs to authorize it.

Aave Labs' official MCP server reads V3 and V4 data and prepares unsigned transactions. Its article says the user's wallet signs. That keeps signing with the user, but does not certify the assistant's interpretation, the transaction inputs, or the endpoint.

Review the exact network, account, contract, asset, amount, recipient, permissions, and expected position change in the wallet. A simulation is a useful preview, not a guarantee of execution or safety.

Read the official MCP documentation

01Read

Confirm the live market, reserve or spoke, rates, caps, and position data.

02Prepare

Inspect the unsigned transaction and simulate the expected effect where supported.

03Authorize

Use the wallet as the final control surface; never sign from an unreviewed prompt alone.

Position lifecycle

The transaction is only one moment in the position.

A safe reading follows the complete lifecycle: what enters the market, what backs the debt, which live variables can move, and what action restores or exits the position.

Supply

Supplying normally creates an interest-bearing position represented by aTokens. Withdrawal depends on available liquidity and whether the supplied asset is supporting an active borrow.

Borrow

Borrowing creates debt and consumes collateral capacity. Interest accrues according to the market's current model, while the health factor changes as prices, debt, or collateral change.

Monitor and exit

Repayment can restore capacity; withdrawal can reduce safety. Before acting, re-check the exact reserve, health factor, available liquidity, rate, network, and transaction recipient.

Recommended entry

Start with the Aave App only after verifying the market.

I have a personal Aave App referral link. It is an entrypoint for the interface, not a recommendation to supply, borrow, stake, or trade.

Referral path 999F66 Open Aave App

Personal referral link from EncryptedGuru. Aave determines eligibility, supported networks, market parameters, fees, app behavior, and any referral treatment. Never approve an unknown spender or sign a transaction without independently checking the exact domain, chain, contract, amount, and recipient.

Risk surface

Audits lower uncertainty; they do not remove risk.

Aave's own risk material identifies multiple layers: smart-contract vulnerabilities, oracle behavior, collateral and liquidity conditions, bad debt, networks, and bridges. External reviews and a bug bounty are useful controls, but neither turns a live protocol position into a guaranteed outcome.

01

Smart contracts

Code can contain unknown defects, unexpected interactions, or governance-approved changes. Use the current security and changelog material for the exact deployment.

02

Oracle and market risk

Price movement, thin liquidity, volatility, and oracle conditions can change collateral value and liquidation eligibility faster than a user expects.

03

Liquidation and bad debt

Liquidation is a protocol mechanism, not a support promise. Market gaps, collateral correlation, caps, and liquidity can affect recovery and losses.

04

Network and bridge

A bridge, RPC, wallet, frontend, or wrong-chain transaction can introduce risks outside the core market contracts. Verify the route as well as the protocol.

AAVE / GHO / safety layer

Protocol governance, stablecoin design, and protection mechanisms remain separate questions.

01 / AAVE

Governance is not ownership

Official documentation describes AAVE as the native governance token, with AAVE and stkAAVE holders able to vote or delegate. Governance power is not a promise of price, yield, or value capture.

02 / GHO

Stablecoin is not cash

GHO is described as an overcollateralized, native Aave stablecoin with governance, facilitators, and supply limits. Its design and current parameters still require independent review.

03 / UMBRELLA

Coverage is scoped

Aave documents Umbrella as a modular onchain mechanism for certain bad-debt coverage. Rewards, eligibility, slashing, and coverage boundaries are not the same as guaranteed insurance.

Operating rules

EncryptedGuru Aave discipline

Use the official Aave domains and current documentation for app access, network deployments, contract addresses, reserve parameters, and governance changes.
Keep Aave the protocol, the Aave App the interface, and AAVE the governance token as separate labels in research notes and decisions.
Treat supply APY, borrow rates, rewards, GHO claims, safety mechanisms, and referral benefits as variable or scoped claims requiring current verification.
Before supplying, borrowing, repaying, or withdrawing, verify the exact network, market, reserve, wallet, recipient, amount, health factor, and available liquidity.
Never enter a seed phrase, private key, recovery code, or payment credential into a site reached from a social post or referral link.
Re-check official risk, security, address, and parameter pages before acting; smart-contract, oracle, market, network, bridge, and provider conditions can change.

Source path

Read the primary material in layers.

Aave documentation overview Official framing for the protocol, products, and developer resources Aave V3 overview Supply, borrowing, collateral, health factor, liquidation, and risk modes Aave V4 on Ethereum Official overview of Liquidity Hubs, Spokes, and the Aave Pro interface Aave V4 on Avalanche Official deployment update; network and market availability remain version-specific Aave V4 deployment changelog Official record of V4 Arc activation and other version-specific deployments Coinbase tokenized equities on Aave V4 Base Equities Hub collateral, oracle cadence, corporate actions, and eligibility limits Aave App account architecture Signer, encrypted backup, recovery options, and smart account permissions Aave MCP server Read data and prepare unsigned V3/V4 transactions for wallet review Aave MCP documentation Current tool surface for live reads, previews, and transaction preparation Liquidity pool mechanics Official supply, withdraw, borrow, repay, utilization, and liquidity concepts Live risk parameters Current reserve and market configuration must be checked before action Official contract addresses Check the exact deployment, network, version, and address Protocol risks Official discussion of smart-contract, oracle, collateral, liquidity, network, and bridge risk Aave security resources Security assessments, bug bounty, addresses, access controls, and changelog paths AAVE governance token Read governance, delegation, staking, and current ecosystem documentation separately GHO ecosystem documentation Native stablecoin design, governance, facilitators, and current limits Aave App referral entry — user-provided Personal referral link; provider terms, eligibility, and any referral treatment apply