Aave is a Supply-Market Route from Position Entry to Withdrawal

Published on 5 August 2026

Aave is entered as a supplier by connecting an Ethereum-compatible wallet, selecting the correct network and market, choosing an accepted ERC-20 asset, authorizing its transfer, and confirming the deposit. The completed position appears for the same wallet, chain, and market, then accrues at that market's variable supply rate until the supplier withdraws available underlying liquidity. The decisive choice is the exact market record, not merely the asset ticker.

The market-selection mistake that creates the wrong position

A supply position is identified by protocol version, chain, asset contract, and market, rather than by a ticker alone. In Aave V4, a market label combines two parts - a Spoke and a Liquidity Hub - so USDC supplied through Main Core is a different position from USDC shown under another Hub or an older V3 deployment. Both transactions can be valid while leading to different accounting records.

Match the wallet network to the deployment before entering an amount. Ethereum uses chain ID 1, Avalanche C-Chain uses 43114, and a V3 position on Arbitrum One sits under chain ID 42161; switching a front-end view moves none of them. Record the version, chain, Spoke, Hub, and token contract together, because those fields lead directly into the wallet and asset checks.

Wallet readiness before the first signature

Wallet readiness means the intended account is connected, the selected chain is active, the asset is spendable there, and a native token is present for transaction execution. An EVM account address is 20 bytes, normally displayed as 40 hexadecimal characters after the 0x prefix. A MetaMask account created from a phrase uses 12 words, while Ledger devices generate a 24-word BIP-39 recovery phrase, which is discussed in Aave liquidation.

Aave Pro receives requests from the connected signer; WalletConnect relays a session, while a Safe smart account collects its configured M-of-N owner approvals. The recovery method belongs to the signer setup, not to the supply position, so changing wallet software does not change the onchain owner address.

Reading the deposit row before choosing a reserve

A deposit row answers whether a specific asset is accepted in a specific market and whether capacity remains for the intended amount. In Aave Pro, the Deposit page exposes the asset, market, displayed APY, total deposits, available liquidity, and remaining capacity; filters such as Core, Plus, and Prime narrow the Hub. The asset detail view then separates markets that share a ticker.

Token precision is fixed even while rates and capacity move: native USDC uses 6 decimals, WBTC uses 8, and WETH uses 18. Compare the contract address as well as the symbol, since wrapped or bridged forms are separate ERC-20 contracts. If the submitted amount exceeds remaining capacity, the atomic deposit does not create a partial position; select an amount the chosen market accepts.

What the authorization prompt actually permits

An ERC-20 approval authorizes a spender to transfer a stated token amount; it does not create a supply position. The standard approve call has two arguments, the spender and allowance. With no sufficient allowance, the wallet shows an approval transaction, a permit signature, or a supported batch before the deposit confirmation, so a successful first prompt must not be mistaken for the completed position.

• Confirm the active network and chain ID.
• Match the ERC-20 contract to the selected asset.
• Read the spender shown in the authorization.
• Compare the allowance with the intended deposit amount.

Version-specific contract shapes explain why prompts differ. The V3 Pool supply call has four inputs - asset, amount, beneficiary, and a 16-bit referral code, with 0 used for a direct call - whereas the V4 Spoke supply path identifies a reserve, amount, and user address. Tokens supporting EIP-2612 can express approval through an EIP-712 signature with a deadline; the deposit still requires onchain confirmation.

Proving that the supplied position exists

A confirmed supply position has three matching records: a successful transaction receipt, the intended market on the dashboard, and an increased protocol balance for the connected address. An EVM transaction hash is 32 bytes, rendered as 64 hexadecimal characters after the 0x prefix. Preserve that identifier with the chain and market label, because the same wallet can hold positions across several deployments.

Position accounting differs by version. V4 records supplied shares in the selected Spoke while the linked Hub holds the underlying liquidity; it does not require a V3-style aToken to appear in the wallet. V3 mints the corresponding aToken at a 1:1 underlying amount on entry, after which the balance reflects accrued interest. A dashboard index can update after the receipt, but the confirmed onchain state determines whether entry succeeded.

How the supply balance changes between entry and exit

The supply balance represents the underlying principal plus accrued supplier interest inside the selected market. Borrow utilization and the market's interest-rate parameters change the displayed supply rate, so the entry APY is not locked for the life of the position. V4 converts between underlying amounts and internal shares, while V3 presents the growing claim through aTokens; neither route converts the supplied asset into AAVE.

Raw V3 rate data uses ray precision, where one ray equals 10 ²⁷ , and front ends commonly annualize per-second values over 31,536,000 seconds. That is why an explorer's integer and a dashboard percentage look different despite representing the same market state. No separate claim action is required: accrued value remains in the position and is included when the underlying asset is withdrawn.

A clean withdrawal back to the wallet

A withdrawal reverses the selected supply position by reducing its shares or receipt tokens and returning the underlying asset to the destination address. Choose the exact chain and market row used at entry, enter a partial amount or the full balance, review the receiving account, and confirm the transaction. The request settles atomically only when enough uncommitted liquidity is available for that asset.

In V4, the Spoke reduces the user's supplied shares while the Hub releases underlying liquidity. In V3, the Pool withdrawal has three inputs - asset, amount, and recipient - and burns the equivalent aTokens; the 256-bit maximum value is the contract sentinel for withdrawing the full balance. A same-token WETH withdrawal needs no ERC-20 approval, while the WrappedTokenGateway can unwrap WETH and deliver native ETH in one transaction.

The protocol sets no minimum holding period for an open supply-only position. After confirmation, check that the underlying wallet balance rose, the dashboard amount fell to the intended remainder, and the receipt names the expected chain and contract. An earlier token allowance is separate state and is not automatically removed by withdrawing.

When a supply-only position matches the goal

A supply-only position matches a plan to retain exposure to a supported token, receive its variable market yield, and keep an onchain exit path in the same underlying asset. It requires comfort with a changing rate, market-specific capacity, and chain-specific liquidity. It does not move assets across networks or turn a floating supply rate into a fixed return.

The clearest first entry uses a familiar asset, a deliberately selected Spoke-and-Hub label, and an amount small enough to make the confirmation path easy to inspect. Later deposits to the same wallet, chain, asset, and market add to that position. When the intended exit is already known - same deployment, named beneficiary, and expected underlying token - the route from authorization to withdrawal stays auditable.