Exchanging ETH for BTC involves two separate blockchain transfers: you send ETH to the deposit address specified in the order, and the exchange sends BTC to your chosen receiving address. Before either transfer, verify the asset, network, addresses, quoted amount, fees, and confirmation requirements. A mismatch at any of these points is a reason to stop rather than guess.
Operation state map: from ETH to confirmed BTC
- Task: exchange ETH and receive BTC.
- Transition condition: ETH is the asset you hold and BTC is the asset you intend to receive.
- Check: confirm that the ETH-to-BTC direction is currently available. Support for both assets does not guarantee that every pair, network, or direction is open at a particular moment.
- Stop if: the interface shows another input asset, another output asset, or an unavailable direction.
- Input data: amount, networks, and BTC receiving address.
- Transition condition: the amount is within the currently displayed limits, and you can send ETH through the exact deposit network offered in the order.
- Check: obtain a fresh BTC address from the wallet or account where you want to receive the payout. Verify that the selected output is an on-chain Bitcoin network supported by both the exchange route and the receiving wallet.
- Stop if: the wallet identifies the address as belonging to another asset or network, the amount is outside the displayed limits, or the required network is not supported at either end.
- Verification: quote and order details.
- Transition condition: the order displays the exchange rate or calculation method, expected BTC amount, applicable fees, and any quote conditions.
- Check: read whether the quote may change before the deposit is detected and whether the order has an expiry condition. Review any verification or compliance requirements shown for this direction before creating the order.
- Stop if: the expected result is unclear, the quoted amount no longer meets your task, or required checks cannot be completed.
- Action: create the order and send ETH.
- Transition condition: the deposit asset and network still match your wallet, and the complete deposit address has been copied from the active order.
- Check: compare the address shown by your wallet with the order, including more than a shortened prefix and suffix. Confirm the ETH amount and wallet network before signing.
- Stop if: the wallet changes networks unexpectedly, replaces the address, shows an unfamiliar contract interaction, or displays transaction details that differ from the order.
- Waiting: ETH deposit confirmation and exchange processing.
- Transition condition: your wallet provides an Ethereum transaction hash.
- Check: use that hash in a suitable blockchain explorer and verify the sending address, destination, amount, network, and transaction status. An Ethereum transaction is first broadcast, then included in a block; its block may later become finalized. [1]
- Stop and diagnose if: no hash exists, the transaction remains pending, the explorer shows failure, or the destination differs from the order deposit address.
- Confirmed result: BTC payout received.
- Transition condition: the exchange reports a BTC payout and provides a transaction identifier, where available.
- Check: verify independently that the Bitcoin transaction pays the address you supplied and that your receiving wallet recognizes it. A Bitcoin transaction gains its first confirmation when it is included in a block and gains additional confirmations as later blocks are added. [2]
- Stop and open a recovery route if: the exchange marks the order complete but the payout transaction cannot be found, pays another address, or does not match the recorded order details.
Check the rate and expected BTC amount
The headline ETH/BTC rate is only one part of the calculation. Before sending ETH, identify the input amount, expected BTC payout, service charge if separately stated, and any network fees shown. The fee charged by your ETH wallet for sending the deposit is also separate from the exchange calculation unless the order explicitly says otherwise.
Do not calculate the result from a market chart alone. The amount displayed in the order is more relevant because it can reflect the service’s current pricing method, fees, limits, and quote conditions. Cryptocurrency prices can change while an order is being prepared or processed, so check whether the displayed result is fixed under stated conditions or may be recalculated. If the order does not explain this, pause before transferring funds.
Record the order identifier, the quoted input and output amounts, and the applicable conditions. This creates a reference for diagnosing a later discrepancy without treating an estimate as a guaranteed final amount.
Choose the correct asset and network
Select ETH as the deposit asset and BTC as the receiving asset. Then treat each network selection as a separate decision. “ETH” identifies the asset, but the order must also specify how the deposit is to be sent. Use only the network displayed for that active order and supported by your sending wallet. An address that looks technically valid is not proof that the selected chain is correct; similar address formats may be used in different EVM-based environments, which can make the destination ambiguous without network context. [3]
For the payout, obtain a Bitcoin receiving address from the destination wallet and confirm that its deposit method matches the output network offered in the order. Do not choose a network merely because it appears cheaper or faster. If your wallet offers several ways to receive BTC, use the one that corresponds exactly to the exchange route. If the names do not match clearly, contact the relevant service before creating the order.
Verify the BTC receiving address and Memo or Tag field
Copy the BTC address directly from the wallet that should receive the funds. Compare the complete address after pasting it into the order. Checking only the first and last few characters is insufficient because malicious software or address-poisoning attempts can present lookalike addresses. Bitcoin safety guidance recommends verifying the entire receiving address before an irreversible transfer. [4]
A normal on-chain Bitcoin payout is directed to a Bitcoin address. Do not invent a Memo, Tag, payment identifier, or other extra value. If the exchange order or receiving platform explicitly requires an additional field, copy it exactly and verify its purpose with that platform. If no such field is displayed, leave it unused rather than entering a wallet name, order number, or note.
The receiving address is a control point: once the exchange broadcasts the BTC payout, changing the address in your wallet or in a separate browser tab cannot redirect that transaction. Confirm that you control the destination or that the custodial platform currently accepts deposits to it. Bitcoin transactions cannot be reversed by a central authority; a confirmed payment can generally be returned only through cooperation from the recipient. [5]
Final checks before sending ETH
- The order direction reads ETH to BTC.
- The ETH deposit network matches the active network in your sending wallet.
- The deposit address comes from the current order, not an old order, message, advertisement, or transaction history.
- The BTC receiving address was generated or confirmed by the intended destination wallet.
- The input amount, expected output, fees, limits, and quote conditions are visible and acceptable.
- Any applicable verification or compliance requirements have been reviewed. Requirements can vary by direction and by the results of compliance checks.
- The website and order page are authentic, and nobody has requested your seed phrase, private key, or remote access to your device.
After these checks, you can create an ETH-to-BTC exchange order and review its current terms. Recheck the generated deposit details against your wallet immediately before signing. The order page, not a general guide, must provide the current address, network, amount conditions, and required confirmation policy.
Sending ETH is the first irreversible action in this route. Ethereum transactions require a destination address and network fee, and a transfer sent to the wrong address cannot normally be reversed by the network. [1] Save the transaction hash after broadcasting; it is the main reference for proving what was sent and where.
What confirmations mean during the exchange
The ETH deposit may appear in an explorer before the exchange credits it. “Pending,” “included in a block,” “confirmed by the service,” and “finalized” are related but different states. The exchange decides how many confirmations or what finality condition it requires before processing the deposit, so do not assume a universal threshold.
The BTC payout has its own confirmation sequence. A receiving wallet may show an incoming transaction before its first confirmation. After inclusion in a Bitcoin block, later blocks add confirmations and reduce the possibility of reversal. Block production is probabilistic, so a displayed average is not a deadline, and the first confirmation can take longer when a transaction’s fee is below what the network is currently prioritizing. [5]
The exchange order can therefore be processing even when your ETH wallet says “successful,” and your BTC wallet can show an incoming payout before considering it fully available. Use the status definitions and confirmation requirements shown by the relevant exchange and receiving wallet rather than comparing only their labels.
If the deposit or payout is delayed or incorrect
No Ethereum transaction hash
If the wallet provides no transaction hash, the transfer may not have been broadcast. Check the wallet activity, selected network, available ETH balance, and whether enough ETH was available for the network fee. Do not send a second deposit until you know whether the first transaction exists.
ETH transaction is pending
Open the transaction in an Ethereum explorer and verify that it is on the required network. A transaction can remain pending when the selected fee is below current network requirements. [6] Follow only the options offered by your wallet, and avoid third parties claiming they can guarantee recovery or confirmation.
ETH is confirmed, but the order has not updated
Compare the explorer record with the order: network, receiving address, amount, and transaction hash. Also check whether the exchange requires more confirmations or an additional compliance review. Contact support through the service’s verified interface and provide the order identifier and transaction hash. Never provide a seed phrase or private key.
The wrong ETH network or address was used
Stop sending further funds. Record the transaction hash and contact the party controlling the destination address, if identifiable. Recovery may be technically impossible or may depend on whether the recipient supports the network and has a recovery process. Ethereum itself cannot reverse a completed transfer. [6]
A BTC transaction exists but is unconfirmed
Verify that the transaction identifier appears in a Bitcoin explorer and that one of its outputs matches your receiving address. If it is valid but unconfirmed, continue monitoring it and follow the exchange’s support process if the delay becomes inconsistent with the order status. Do not assume that creating another exchange order will accelerate the original payout.
The order says complete, but the BTC destination is wrong
Compare the payout transaction with the address saved when the order was created. If the transaction pays the address entered in the order, the exchange may have followed those instructions even if that address was entered incorrectly. Contact the receiving platform or address controller where possible, but do not expect a guaranteed return. Bitcoin payments are irreversible at protocol level. [5]
When the route is complete
The verifiable completion state is a BTC payout transaction to the intended receiving address, recognized by the destination wallet and carrying the level of confirmation required for your intended use. Keep the order identifier, ETH deposit hash, and BTC payout transaction identifier until the result is settled.
Some uncertainty may remain around confirmation timing, a quote that is subject to recalculation, compliance review, or the receiving platform’s crediting policy. None of these should be replaced with assumptions. If the asset, network, address, or order terms stop matching the original ETH-to-BTC task, pause the route and resolve the mismatch before making another irreversible transfer.