Defilama is a control panel for chain selection, position checks and a clean exit

Defilama and Aave divide screening from execution

Put another way, Defilama and Aave serve different stages: the dashboard compares deployments while the Aave V3 interface submits supply and withdrawal transactions.

On Defilama, the relevant evidence is the selected chain, protocol category, TVL composition and yield-pool row. Aave’s interface then works with a specific reserve and wallet account on that chain. A supply sends the underlying asset into the Aave pool and credits a corresponding aToken to the same address. A withdrawal burns the aToken and returns available underlying liquidity. Uniswap follows another execution path: swaps exchange tokens, while liquidity positions represent pool ownership. Keep the operational boundary clear. Screen with analytics, execute one named protocol action and verify the resulting on-chain state. For this first round trip, the named action is one Aave V3 supply.

Which chain should you choose for a first position?

Choose the chain where the protocol, exact asset and wallet already align, then use Defilama metrics to compare only those matching deployments.

Chain TVL needs interpretation before it supports that choice. Defilama assigns protocol TVL to the chain where the user deposits and interacts. It excludes native validator staking from chain TVL by default and keeps bridge TVL outside each chain’s total. Price movement also changes the reported dollar value without any deposit entering or leaving. Compare activity, pool depth and protocol deployment together; a large aggregate alone does not establish that the selected asset has usable liquidity on that market. Open the protocol row and confirm that its chain breakdown contains the intended deployment.

Network identifiers remove name ambiguity. Ethereum Mainnet uses chain ID 1, OP Mainnet uses 10, Arbitrum One uses 42161, Base uses 8453, Polygon PoS uses 137, BNB Smart Chain uses 56 and Avalanche C-Chain uses 43114. Match the wallet’s displayed network to one of those identifiers before connecting. A protocol may deploy on several of them with separate contracts and reserves.

Preflight wallet and asset checks

The preflight check pairs one recoverable wallet account with the exact network and token contract selected during Defilama screening earlier.

Network identity

MetaMask and Rabby show the active EVM network before connecting. BIP-39 defines mnemonic lengths of 12, 15, 18, 21 or 24 words, each carrying a checksum. Store that recovery material offline; Defilama needs only public market data. The same EVM account can display across multiple chains, so a repeated address does not prove that the network is correct.

Token identity

Ticker matches are insufficient across chains. Native USDC uses 6 decimals, while WETH uses 18 and one wei equals 10 ⁻¹⁸ ETH. ERC-20 exposes decimals as optional uint8. An EVM address holds 20 bytes or 160 bits and renders as 40 hexadecimal digits after 0x, making a full address 42 characters. Record the token and protocol addresses.

Finish preflight by confirming the selected token, chain and native execution asset in the wallet. Keep the action to one deposit on one deployment. A watchlist records chosen markets; the protocol interface and explorer later supply position evidence. Use the same account from entry through exit.

A seven-stage route from screen to exit

A seven-stage route keeps Defilama research, wallet execution, on-chain confirmation and final withdrawal tied to one recoverable record from start to finish.

Write the selected values before signing anything. The record should survive interface changes because chain IDs, contract addresses and transaction hashes point to the on-chain objects directly. Use the table in order; do not skip from a yield row to a wallet prompt without capturing the protocol and network. Seven stages create a compact audit trail, while the final column identifies the artifact that restores context when an interface no longer remembers the session.

The process record belongs to the position, not to a browser session. Keep it until the exit receipt and final wallet balance agree (covered in Defilama choosing comparison ).

How do you open one primary position?

Open one primary position by carrying the selected chain, asset and protocol from Defilama into a single deposit action without changing markets.

Use the protocol profile to identify the intended application, then reconnect the same account and inspect the wallet network again. In Aave V3, choose the same reserve screened earlier and submit Supply. A standard ERC-20 route first requests an allowance, which authorizes the Pool contract to transfer up to the stated amount. ERC-20 represents that remaining allowance as a 256-bit unsigned integer. The next request submits the supply call. Some integrations use permit-style authorization to combine or alter this sequence, so judge the requested function and spender address rather than counting prompts.

Pause if the wallet switches the chain, token or contract. Return to the recorded Defilama row and rebuild the route with the intended Aave V3 deployment.

Transaction confirmation and receipt records

Transaction confirmation requires a successful explorer receipt plus a matching sender, destination contract and protocol state change for the same account.

Explorer receipt

An EVM transaction hash contains 32 bytes and displays as 64 hexadecimal digits after its 0x prefix. That makes 66 visible characters. Etherscan serves Ethereum Mainnet, Arbiscan serves Arbitrum One and Basescan serves Base. Paste the saved hash into the explorer for the recorded chain. Check success status, sender, destination contract, transferred token and block inclusion.

Protocol state

Return to Aave’s dashboard with the same wallet and network. The Your Supplies area should show the reserve, while the wallet or explorer shows its aToken balance. Contract-call calldata begins with a 4-byte function selector, but the wallet summary is easier to inspect. Match the supply function, underlying asset and receiver account. Save the block number beside the transaction hash.

Use two independent views. The explorer proves that the chain accepted a specific call from a specific address; the protocol view interprets the resulting contract state. A transfer can reflect approval or routing, so compare the entered amount, credited position and remaining wallet balance. When both records agree, the position gains a durable Aave V3 identity.

Where should the position appear after confirmation?

The confirmed position should appear in the originating protocol interface and in the on-chain token or account state tied to your wallet.

On Aave V3, a supply credits an aToken that represents the address’s pool share and accrues interest through its balance. A Yearn V3 ERC-4626 vault credits shares that redeem for underlying assets under its accounting. A Uniswap V3 liquidity position instead uses an ERC-721 position token with a token ID. These representations differ. A wallet asset list shows only the token layer, so it can hide protocol context. Use the protocol dashboard and explorer to confirm the representation that the protocol creates.

Defilama’s portfolio watchlist tracks selected protocols and chains for monitoring; it is not the settlement record for a wallet address. Treat its row as market context and keep the on-chain receipt as the position record. The decisive match is account, chain, deployment and resulting token state.

A clean exit through the originating protocol

A clean exit reverses the original deposit on the same chain, then confirms the underlying asset in the same wallet account.

Reverse the original action

Open the position in Aave’s Your Supplies view, select Withdraw and choose the underlying asset. A same-asset WETH withdrawal needs no fresh approval; Aave burns the aToken and returns available WETH. Its WrappedTokenGateway unwraps WETH to ETH within one withdrawal transaction when selected. For a Yearn V3 ERC-4626 vault, redeem shares through that vault. For a Uniswap V3 position, decrease liquidity and collect the owed tokens.

Close the record

Save the exit hash beside the entry hash and inspect it on the matching explorer. Confirm the sender, protocol contract, asset transfer and receipt status. Then check that the position balance fell and the underlying wallet balance rose by the intended amounts. A full exit leaves no position units; remaining pool proceeds require another protocol action.

Keep chain context fixed until every step settles. Switching from Base to Ethereum Mainnet creates a different contract state even when the wallet shows the same EVM address. Withdrawing WETH and expecting ETH also creates a mismatch unless the path includes unwrapping. Keep the Defilama selection, position identifier, entry receipt, exit receipt and final token balance together. Those five items close one Aave V3 round trip.

Chain, token and interface boundary failures

Boundary failures arise when a Defilama selection and the execution screen refer to different chains, contracts or stored position representations.

An empty protocol dashboard after a successful transaction signals a viewing mismatch. Compare the wallet address and chain ID with the saved record, then compare the protocol and token contracts. Ethereum Mainnet chain ID 1 and Base chain ID 8453 show the same 42-character account format, yet each network stores separate balances. A ticker also repeats across deployments; USDC’s 6-decimal precision does not make every contract interchangeable. Correct the viewing context before repeating an action.

Interface caching creates another boundary. Refresh the protocol view, reconnect the same account and check the explorer. If the receipt succeeded but the position stays absent, inspect its logs for the position token or protocol event. Rabby and MetaMask can label the same ERC-20 differently, while the contract address stays exact. Recovery ends at the recorded 32-byte hash.

Maintenance after the first round trip

Ongoing maintenance keeps the Defilama screening record aligned with the live protocol position until the entry and exit artifacts reconcile.

Revisit the saved protocol and chain rather than searching by ticker. Defilama’s Now, 7-day and 30-day yield views provide changing market context, while the receipt fixes what your account did. TVL falls when token prices fall even if nobody withdraws, so it cannot replace a balance check. Review active ERC-20 allowances after an exit and reduce unused authorization. Keep BIP-39 recovery material separate from public addresses, chain IDs and transaction hashes.

A complete cycle becomes the template for the next one: one recorded market, one protocol action, two receipt hashes and a verified final balance. Repeat the procedure only after those records agree for Aave V3 on the selected chain.