Exchange Avalanche (AVAX) to Ethereum

An internal Avalanche cross-chain move is not necessarily the payment to an exchange. Identify the deposit transaction separately from the wallet’s export and import records.

Identify which event the wallet history describes

  1. An export between Avalanche chains

    Read the source and destination chains in the wallet record. Core’s current cross-chain guide explains that this operation involves an export followed by an import. An export reference is therefore not a complete substitute for proof that the exchange deposit recipient received AVAX. Keep it as a wallet-preparation record if that is what it represents.

  2. An import into the destination chain

    Check whether the intended wallet preparation has completed and what funds are available on that chain. Do not infer that importing into your own account automatically pays an exchange. The receiving account and the current order’s deposit address are separate roles. Compare the actual destinations rather than choosing whichever transaction has the newest timestamp.

  3. A payment to the current exchange deposit

    Find the record whose recipient matches the supplied deposit instruction. Confirm its network, amount and outcome. This is the funding evidence relevant to the AVAX input. When a source platform uses its own withdrawal interface instead, obtain its actual outgoing transaction record rather than inventing an export/import sequence it did not show.

Attach a purpose to each reference

Record in handWhat it can establishWhat it does not establish alone
Wallet exportA move out of a particular Avalanche chainCompleted import or exchange deposit
Wallet importReceipt on the destination chain of that movePayment to a different recipient
AVAX deposit transactionThe actual transfer to the exchange funding recipientETH delivery to your final account
ETH payout transactionThe output transfer on its selected receiving networkThe meaning of an earlier wallet-preparation record
One process can produce several references. Name the chain and purpose beside each instead of treating every hash as the same payment.

Use the current interface without assuming the label describes an exchange

Core’s guide, dated August 2026, places transfers between Avalanche’s X, P and C chains in its Swap interface. In that documented flow, AVAX is selected on both sides with different chains, and completion requires export and import transactions. A button labelled Swap is therefore not sufficient evidence that AVAX has been converted to ETH or paid to KOT.CASH. Read the actual input, output and recipients shown by the application.

If wallet preparation is unresolved, keep it separate from the order review. Do not make a second exchange deposit in response to an incomplete wallet import. Use the wallet’s official instructions or support to investigate the preparation record, while providing the exchange with the real funding reference if payment was made. For the ETH output, also verify the selected receiving network with your recipient. A familiar address does not identify which network’s balance should increase after the payout.

Wallet preparation versus exchange funding

Core shows a successful AVAX export. Has the exchange been paid?
Not on that evidence alone. Determine whether the record is wallet preparation, whether its import completed and whether an actual payment reached the current exchange deposit recipient.
Does using Core’s Swap screen mean I already exchanged AVAX for ETH?
No. That screen can also move AVAX between Avalanche chains. Read the assets, chains and destination in the actual operation rather than inferring conversion from the interface label.

Avalanche cross-chain documentation

Reviewed:

AVAX to ETH: separate wallet transfers from funding | KOT.CASH