Sending a token to another wallet is a short routine: copy an address, choose a network, and sign. The step that costs people money is the network, because a token sent on a chain the receiver is not watching lands where they cannot see it. Tokens that live on several chains carry that risk.
AAVE moves like any other Ethereum token, so the routine is the one you would use for ETH or a stablecoin, with two extra checks: the network the AAVE sits on, and enough ETH to pay the fee. To start, you need AAVE in an account, which you get when you buy AAVE on an exchange, and a receiving address, which comes from your AAVE wallet setup.
What is an AAVE transfer?
An AAVE transfer is an on-chain payment that moves AAVE from one address to another on a single network. Your wallet signs it, and the network adds it to a block. AAVE is the governance token of the Aave Protocol and an ERC-20 token on Ethereum (source: Aave, AAVE Token).
ERC-20 is the common token standard on Ethereum. It defines a transfer function that moves tokens from one account to another (source: Ethereum, ERC-20 Token Standard). When you press Send on an AAVE balance, that is the function your wallet calls. The wallet itself is an interface to the blockchain, where the balance is actually stored. It shows that balance and signs the transfers you approve, which is why the same account can open on more than one device (source: Ethereum, How to use a wallet).
AAVE also runs on more than one network. Besides Ethereum Mainnet, official AAVE deployments exist on Arbitrum, Base, Optimism, and Polygon, which makes 5 networks in all, and each one has its own AAVE contract address. Those deployments connect to Ethereum through canonical bridges. Moving AAVE to or from Ethereum depends on the bridge for that network being available (source: Aave, AAVE Token).
A transfer and a bridge are easy to confuse, and the difference decides which tool you need. A transfer keeps AAVE on the network it is already on and changes only the owner of the balance. A bridge keeps the owner and changes the network, through a separate bridge contract and a separate step. When you pay someone, move AAVE to your own wallet, or withdraw it from an exchange, you are making a transfer, and it only works when both sides use the same network.
How to match the network before you copy an AAVE address
Matching the network means the sender and the receiver agree on the same chain before anyone copies an address. Set the receiving wallet or deposit screen to the network you want first, then copy the address it shows, and then set the sending side to that same network, because the address alone does not name a chain.
The reason is the address format. Ethereum addresses always start with 0x, and a wallet with a recovery phrase uses the same address on every chain built on the Ethereum Virtual Machine (EVM), the software that runs Ethereum smart contracts. When you send tokens, the receiver has to use the same network as you, because the versions of a token on different networks cannot stand in for each other (source: Ethereum, How to use a wallet). One 0x address can therefore hold AAVE on more than one of its networks at once, and each of those balances is separate.
| Check | What you should see |
|---|---|
| Receiving side | The network you chose is selected on the receive or deposit screen |
| Sending side | The same network is selected before you paste the address |
| Token | AAVE on that network, with its official contract |
| Address | Copied just now from the receiving screen |
Say the network by name in every message you send about the payment. Ethereum Mainnet together with the address is a full instruction, while a request to send some AAVE is only half of one. When the two sides name different networks, stop and fix it before anyone signs, because once a transfer is confirmed you cannot cancel it (source: Ethereum, How to use a wallet).
Exchanges follow the same rule. Their deposit and withdrawal screens each have a network menu, and that menu has to show the same network as the wallet on the other side. If you copy an address from an old message or an earlier transfer, you skip the one moment when the receiving screen shows you its network, so copy a fresh address each time.
How to receive AAVE on the correct network
To receive AAVE, open your wallet or the exchange deposit screen, choose the network you want the AAVE to arrive on, and copy the address it shows. Send that address and the network name together in one message, then watch your balance or a block explorer until the transfer confirms.
In most wallet apps, receiving takes five steps:
- Open your wallet app and select the network, for example Ethereum Mainnet.
- Tap Receive, or the similar button your wallet uses.
- Copy the address, or show the QR code so the sender can scan it.
- Send the sender the address and the network name in the same message.
- Keep the wallet on that network until the AAVE shows up.
Copying or scanning is safer than typing, since a typed address can carry a small error that sends the funds somewhere else. Sharing the address is safe, because it works like a bank account number that people need in order to pay you (source: Ethereum, How to use a wallet).
Receiving costs you nothing, since the sender pays the fee. If you plan to move that AAVE again later, add a little ETH to the same address on the same network now, because an AAVE balance cannot pay the fee for its own transfer.
When the sender is an exchange, the network you give them is the one they choose on their withdrawal screen. When the sender is another wallet, ask them to confirm their network before they sign. Either way, the AAVE arrives on the network the sender picked, whatever network your wallet happens to display.
After the balance appears, check that the token is real AAVE and that its contract matches the official one for that network. Lookalike tokens can copy the name and ticker of a real asset, and fake AAVE token scams rely on holders who check the ticker and skip the contract.
How to send AAVE step by step
Sending AAVE is a token transfer that you sign in your wallet: you pick the network, paste the address, enter the amount, check the fee, and confirm. Each step has one thing to verify, and the final read of the confirm screen is the check that protects the money.
- Check that you hold AAVE on the network you plan to use, and that the receiver expects that same network.
- Check that you hold enough ETH on that network to pay the fee.
- Open your AAVE balance and tap Send.
- Paste the address from the receiver's current receive screen, or scan their QR code.
- Enter the amount. For a new address, send a small test amount first and wait until the receiver confirms it arrived.
- On the confirm screen, read the network, the token, the amount, the first and last characters of the address, and the fee, then sign.
- Copy the transaction hash your wallet shows, so you can track the transfer.
Your wallet signs the transfer and broadcasts it to the network. The AAVE only moves once a validator picks the transfer up and includes it in a block (source: Ethereum, Transactions). The order matches how you send and receive any crypto.
Send AAVE only to a wallet address or an exchange deposit address. A plain transfer to a smart contract that was built without ERC-20 handling can lock the tokens there for good, because the standard gives that contract no way to notice the deposit (source: Ethereum, ERC-20 Token Standard). If you meant to supply AAVE to the Aave lending protocol or repay a loan, use the screen inside that app, which moves the tokens through the right function for you.
If the AAVE you want to send is held on an exchange, the send is a withdrawal, and the network rule is the same. Readers who want another way to trade AAVE before moving it can use BloFin, where AAVE/USDT Spot credits real AAVE to your account that you can later withdraw. The AAVEUSDT Perpetual is a contract on the price, so it holds no token to withdraw.
A BloFin withdrawal runs in this order: hover over Assets and select Withdraw, search for AAVE, choose the network that matches the receiving wallet, paste the address, and enter the amount. The withdrawal screen shows the network fee before you confirm, and that amount depends on the asset and network. Then click Withdraw, enter your email code and your Google Authenticator code, check everything on the final screen, and confirm the withdrawal. If an exact figure must arrive, add that fee to the amount, because it comes out of the withdrawal.
Before you buy AAVE that you plan to send on, check your trading rate on the BloFin fee schedule, so you know the full cost of the purchase before the withdrawal adds its network fee.
Ethereum gas fees when you move AAVE
Every AAVE transfer on Ethereum costs gas, and you pay that fee in ETH, never in AAVE. Gas measures the computing work a transfer needs. The fee equals the gas used times the price per unit of gas (source: Ethereum, Gas and fees).
Gas prices are quoted in gwei, a small unit of ether. One gwei equals 0.000000001 ETH. Gas fees are usually priced in gwei because the numbers stay short and easy to compare (source: Investopedia, Gwei).
The price per unit has two parts. The protocol sets the base fee, which moves up or down with demand. The priority fee is a tip you add so that a validator picks your transfer sooner. A plain ETH transfer uses 21,000 units of gas. At a base fee of 10 gwei and a tip of 2 gwei, the full fee works out like this (source: Ethereum, Gas and fees).
| Step | Calculation | Result |
|---|---|---|
| Gas used | Plain ETH transfer | 21,000 units |
| Price per unit | 10 + 2 | 12 gwei |
| Fee in gwei | 21,000 × 12 | 252,000 gwei |
| Fee in ETH | 252,000 × 0.000000001 | 0.000252 ETH |
An AAVE transfer calls the AAVE token contract, and calls to smart contracts take more computing work than a simple payment, so they need a higher gas limit than 21,000 (source: Ethereum, Gas and fees). At the same 12 gwei price, your AAVE send costs more than the 0.000252 ETH of a plain ETH transfer, in proportion to the extra gas your wallet estimates for it.
The fee changes with how busy the network is. Most wallets fill in a suggested fee for you, which you then confirm (source: Ethereum, How to use a wallet). If the quoted fee is larger than the ETH you hold, the transfer cannot go out until you add ETH to the same address on the same network. On the other AAVE networks, check which token that network charges gas in before you send, because the ETH you hold on Ethereum Mainnet only covers fees there.
How to confirm an AAVE transfer on a block explorer
You confirm an AAVE transfer by searching its transaction hash on a block explorer for the network you used. The explorer shows whether the transfer is pending, failed, or a success. It also lists the From and To addresses and the tokens moved, along with the fee paid (source: Ethereum, Block explorers).
- Copy the transaction hash from your wallet. For a BloFin withdrawal, open Assets, then Withdrawal History, where each entry lists the TXID.
- Open the explorer for the network you used. Etherscan covers Ethereum Mainnet, and each of the other networks has its own explorer.
- Paste the hash, or your address, into the search bar.
- Read the status, the From and To addresses, and the AAVE amount under Tokens Transferred.
A transfer passes through a few stages before it is settled. Once you submit it, it gets a hash and waits in a pool of pending transfers until a validator puts it in a block. Over time that block becomes justified and then finalized. After that point, changing it would take an attack costing many billions of dollars (source: Ethereum, Transactions).
Withdrawal History on BloFin gives each withdrawal's TXID next to its status, its network, and the address it went to. When the explorer shows a confirmed transfer that has not reached an exchange or another platform, that platform's support team is the one who can trace it. A TXID with no on-chain record at all after a BloFin withdrawal is a question for BloFin support.
Hold off on a second send while the first hash still shows pending, so you never pay twice for one payment.
Chain mismatch risk for AAVE transfers
Chain mismatch happens when AAVE leaves on one network while the receiver watches another. The transfer succeeds on chain, yet the balance looks missing, because it sits at the right address on the wrong network. Whether you can get it back depends on who controls that address on the chain where the AAVE landed.
Picture a withdrawal from an exchange to your own wallet where you pick Arbitrum on the withdrawal screen while your wallet shows Ethereum Mainnet. Your wallet uses the same 0x address on both chains, so the AAVE is safe at your address on Arbitrum. Add Arbitrum to your wallet, switch to it, and the balance appears. Moving it to Ethereum later needs a bridge and some gas on Arbitrum, which is the real cost of the mistake.
The hard case is an exchange deposit address. If you send AAVE to an exchange on a network that exchange does not accept for AAVE, the tokens sit at an address the exchange controls on a chain it does not watch, and only its support team can say whether recovery is possible. That is the case where checking the deposit page before you send saves the money.
Bitcoin and some other chains follow separate network rules and need a different address format (source: Ethereum, How to use a wallet). An Ethereum address has no meaning on those chains.
| What you see | Likely cause | First check |
|---|---|---|
| Explorer shows success, wallet shows nothing | Wallet set to another network | Switch the wallet network |
| Exchange deposit missing | Network the exchange does not accept | Withdrawal network versus the deposit page |
| AAVE balance you did not expect | Lookalike token | Contract address on the explorer |
The same rule applies when you supply AAVE to the Aave Protocol, because the network of the Aave market you use decides where your tokens sit.
Pre-send checklist before you move AAVE
Run this checklist before every AAVE transfer to a new address or on a new network. It puts the network match, the ETH fee, the address check, and the tracking plan into a fixed order you can repeat, so nothing depends on memory while the confirm screen is open.
- Name the network in one sentence, such as Ethereum Mainnet to my hardware wallet.
- Ask the receiver to repeat the same network back to you.
- Set your sending wallet or withdrawal screen to that network.
- Confirm the token is AAVE on that network, with the official contract.
- Check that your ETH balance covers the wallet's fee estimate with room to spare.
- Paste a fresh address and compare its first and last six characters on the confirm screen.
- Send a small test amount to any new address and wait for the receiver to confirm it.
- Save the transaction hash and know which explorer you will open.
- Decide where the AAVE will live afterward, since storing AAVE safely depends on the wallet type and the network.
If anything on the confirm screen looks rushed or unfamiliar, reject the signature and start again from the first line. The list is complete when you can answer every line without guessing.
Looking to trade AAVE tokens on BloFin? To get started, you'll need to first create a BloFin account, fund your account with cryptocurrency, then open the AAVE/USDT Spot trading page or the AAVEUSDT Perpetual page.
Frequently asked questions
How long does an AAVE transfer take on Ethereum?
Ethereum adds a new block every 12 seconds, although a slot can sometimes go empty when its chosen validator is offline (source: Ethereum, Blocks). How soon your transfer joins a block depends on the tip you add and on how busy the network is. Some block explorers show current gas prices for slow, average, and fast transfers, each with an estimated wait, so you can choose a tip that matches how quickly the AAVE needs to arrive (source: Ethereum, Block explorers).
Why does the fee estimate change before you confirm?
The base fee resets with every block and can rise or fall by up to 12.5% depending on how full the previous block was, so an estimate from a minute ago may already be out of date. You can set a maximum fee per unit of gas, and the transfer goes through as long as that maximum covers the base fee plus the tip, with the difference returned to you (source: Ethereum, Gas and fees). A sudden jump usually means a burst of demand, and the base fee falls again once blocks drop below their target size.
What is the AAVE contract address on Ethereum?
On Ethereum Mainnet, AAVE uses the contract 0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9, listed on Etherscan as Aave Token (AAVE) with 18 decimals and a maximum total supply of 16,000,000 AAVE (source: Etherscan, Aave Token (AAVE)). The 18 decimals let a balance split into very small fractions, which is why a wallet can show a long run of digits after the point. The other four networks each use a different address, so compare against the list for the network you are on (source: Aave, AAVE Token).
What happens to the gas fee if an AAVE transfer fails?
The fee is charged whether a transfer succeeds or fails. If a transfer runs out of gas partway through the token contract, the network reverses the change but keeps all the gas you supplied. A gas limit set too low is rejected before it reaches a block and costs nothing. Of the fee you do pay, the base fee is burned, which removes it from circulation, while the tip goes to the validator (source: Ethereum, Gas and fees). A failed AAVE send can cost ETH and move no AAVE, so read the error before you retry.
Why do apps ask for an approval before they take AAVE?
Apps use an approval because the ERC-20 transfer function was never designed for depositing into contracts. You first approve an amount that the app's contract may spend from your account, and the contract then pulls the tokens with a second function called transferFrom, which lets it record the deposit. Plain transfers into contracts that cannot handle tokens had cost holders at least $83,656,418 in lost ERC-20 tokens as of June 20, 2024 (source: Ethereum, ERC-20 Token Standard). Approve only the apps and amounts you mean to use.
Do I need to send AAVE to someone so they can vote for me?
Delegation gives another address your voting power, so no transfer is needed. Holders of AAVE and of stkAAVE, which is AAVE staked in the Aave safety module, can vote on governance proposals or delegate that voting power to others, and those votes shape decisions on deployments, parameter changes, and new features (source: Aave, AAVE Token). If someone asks you to send them AAVE before they can vote on your behalf, treat it as a warning sign, since delegation does that job while the tokens stay in your wallet.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Primary sources include Aave token documentation, Etherscan, Investopedia, ethereum.org guides on wallets, gas, transactions, blocks, block explorers, and the ERC-20 token standard, and the BloFin Academy withdrawal guide. All facts independently verified against cited documentation current as of October 2026.
This article is for informational and educational purposes only. It is not financial, investment, trading, or legal advice. Cryptocurrency can lose value. Borrowing on Aave can lead to liquidation if the health factor drops below 1. Spot AAVE/USDT buys the token. An AAVEUSDT Perpetual is a contract on the price. Do your own research. Consider your circumstances before using any protocol or trading any asset.