Short conclusion: exchanging BTC for ETH can involve costs on both blockchains, but their fee figures cannot be compared directly. Bitcoin charges for transaction space measured in virtual bytes, while Ethereum charges for computational work measured in gas. The cheaper network at a particular moment can be identified only by combining live network estimates with the actual transaction structure and the exchanger’s current quote. Protocol documentation alone cannot establish the final amount of ETH the user will receive.
How the claims were checked
The technical claims below rely primarily on Bitcoin Core source code and release documentation, the Ethereum developer documentation, and the finalized EIP-1559 specification. These sources define how protocol-level fees are represented and calculated. Dynamic fee levels were deliberately not copied into the analysis because they can change between opening an exchange form, sending BTC, and receiving ETH.
Freshness was treated differently for stable and dynamic information. A protocol formula remains useful until a network upgrade changes it, whereas a recommended fee rate is only a short-lived estimate. Exchange charges, supported directions, limits, verification requirements, and the quoted output must therefore be checked in the order form immediately before creating a request.
What happens during a BTC-to-ETH exchange
A typical exchange has three economically distinct stages. First, BTC is transferred to a specified Bitcoin address. Second, the conversion is priced by the service. Third, ETH is delivered to an Ethereum address. The precise operational model may differ: a provider can show charges separately, include some costs in its rate, deduct them from the output, or use its own withdrawal schedule. Consequently, the network fee shown by a wallet is not necessarily the same as the exchanger’s total charge.
On Bitcoin, the fee rate is expressed in satoshis per virtual byte, or sat/vB. Bitcoin Core calculates a fee from the selected fee rate and the transaction’s virtual size. A transaction with more inputs or outputs generally occupies more block space, so sending the same BTC amount can have different costs depending on how the wallet constructs the transaction. [1]
The simplified Bitcoin calculation is:
Bitcoin network fee = transaction virtual size × fee rate.
The transferred BTC amount is not a factor in this formula. Network demand matters because transactions compete for limited block space; a higher fee rate generally targets faster inclusion, while a lower rate can require a longer wait. Fee estimation remains a prediction rather than a guarantee. [2]
On Ethereum, the execution fee is based on gas used and the effective price of each gas unit. Under EIP-1559, that price contains a protocol-defined base fee and a priority fee offered to the validator. The sender can also specify a maximum fee per gas, but an unused part of that maximum is not automatically treated as the final charge. [3]
The simplified Ethereum calculation is:
Ethereum network fee = gas used × (base fee + priority fee), subject to the transaction’s fee settings.
A plain ETH transfer has a different gas profile from a smart-contract interaction. This distinction matters when reading fee trackers: an estimate for transferring ETH should not be assumed to represent the cost of a token swap, bridge transaction, or other contract call. Ethereum’s base fee also responds to block usage, while the priority fee reflects the sender’s urgency and current competition for inclusion. [3]
Claims Register
| Claim | Verification status | Primary source type and name | Publication or update date | Limitation | What could change the conclusion |
|---|---|---|---|---|---|
| Bitcoin fees are calculated from a fee rate in sat/vB and transaction virtual size. | Confirmed | Bitcoin Core source code, feerate.h [1] | The displayed source snapshot does not provide a reliable page-level update date. | The formula does not reveal the virtual size of a transaction that has not yet been constructed. | Wallet input selection, address and output types, the number of inputs and outputs, and the selected fee rate. |
| Ethereum execution fees depend on gas used, the base fee, and the priority fee. | Confirmed | Ethereum developer documentation, Gas and fees; finalized EIP-1559 specification [3] | Ethereum documentation updated June 24, 2026; EIP-1559 created April 13, 2019. | The formula does not predict the gas usage or inclusion block of a future transaction. | Transaction type, gas consumed, base fee in the inclusion block, priority fee, wallet settings, or a protocol upgrade. |
| A high maximum Ethereum fee is not necessarily the amount ultimately paid. | Confirmed | Ethereum developer documentation and EIP-1559 specification [3] | June 24, 2026, for the documentation; April 13, 2019, for the EIP creation date. | The wallet interface may present the maximum, estimate, and final fee differently. | The effective base fee, priority fee, gas consumed, and transaction configuration. |
| Bitcoin Core fee estimates can use different estimation modes, which may produce different suggested rates. | Confirmed, implementation-dependent | Bitcoin Core 28.0 release notes [4] | Bitcoin Core 28.x release date: October 2, 2024. [5] | One wallet or service does not necessarily use Bitcoin Core or the same estimation settings. | Wallet software, confirmation target, estimation mode, mempool conditions, and later software releases. |
| Either Bitcoin or Ethereum is always the cheaper side of a BTC-to-ETH exchange. | Not supported | No protocol specification can establish a permanent winner; both costs depend on changing demand and transaction characteristics. | Not applicable | BTC fees and ETH fees use different units and must be converted to a common value at the same point in time. | Network congestion, transaction construction, asset prices, required confirmation speed, and the provider’s charging model. |
| The all-in cost and final ETH output can be calculated from blockchain fees alone. | Unknown until a live quote is available | A current service order form and its applicable terms are required; no current primary service quote was supplied. | Not applicable | Protocol sources do not define the provider’s rate, spread, service charge, limits, or output policy. | The quoted rate, quote validity, service charges, network costs, minimum amount, and compliance requirements. |
| A particular BTC-to-ETH direction and selected networks are currently available. | Requires current confirmation | The service’s live order interface is the necessary operational source. | Must be checked immediately before the operation. | Support for BTC and ETH does not prove that every pair, network, amount, or direction is available. | Maintenance, liquidity, compliance controls, limits, or changes to supported directions. |
How to compare the costs before exchanging
Start with the amount the recipient is expected to receive, rather than comparing a sat/vB number with a gwei number. Those units describe different resources and are denominated in different assets. A useful comparison converts every visible charge into one common unit at approximately the same time, while keeping estimates separate from confirmed deductions.
- Inspect the BTC sending transaction. Check the total Bitcoin network fee displayed by the wallet, not only its fee rate. If BTC is being withdrawn from another platform, determine whether the displayed withdrawal charge is a platform charge, an on-chain estimate, or a combination of both.
- Read the exchange quote. Record the BTC amount to be sent and the expected ETH output. Check whether the quote identifies a service charge or network deduction and whether it can change before the deposit receives the required confirmations.
- Confirm the destination network. A standard Ethereum mainnet address format alone does not prove that the selected withdrawal network is correct. The network named by the sending service must match the network supported by the receiving wallet.
- Compare effective outcomes. The relevant figure is the difference between the starting value and the value of ETH actually deliverable under the quote, including any separately displayed sending or withdrawal costs.
- Repeat the check before sending. A cached fee estimate or an earlier quote may no longer describe current conditions.
A conditional calculation can organize the comparison without pretending that unknown values are fixed:
Estimated all-in cost = BTC sending cost + conversion cost or spread + ETH delivery charge, if separately applied.
This is an accounting framework, not a protocol formula. Some providers may combine components in the quoted output, so adding an assumed Ethereum gas fee again could double-count a cost. Conversely, looking only at the BTC wallet fee can omit the conversion spread or an output-side deduction.
Practical meaning for an ordinary user
For a small exchange, fixed or weakly amount-dependent charges can represent a larger percentage of the transferred value. Consolidating many Bitcoin inputs may also enlarge the source transaction even when the BTC amount is modest. On the Ethereum side, the decisive question is whether the service is making a plain ETH transfer or using a more complex operation; the user should rely on the provider’s quoted output rather than infer its internal gas consumption.
Waiting for lower network demand may reduce an estimate, but delay introduces another variable: the BTC/ETH exchange rate can move while the user waits. No general rule proves that postponing the transaction lowers the total economic cost. This analysis compares fee mechanisms and verification steps; it does not predict either asset’s price or recommend whether to exchange.
After reviewing the evidence and calculation method, the next operational step is to check the currently available BTC-to-ETH direction and quoted conditions. This link is for obtaining current service information and is not evidence for the technical claims above. Verification requirements may depend on the operation and the outcome of compliance checks, so the applicable conditions should be reviewed before creating a request.
Risks and a repeat-check procedure
- Wrong network or address: sending BTC to an Ethereum address, selecting an unsupported network, or copying the wrong destination can cause irreversible loss. Confirm the asset, network, complete address, and any additional destination data shown by the receiving service.
- Irreversibility: a confirmed blockchain transaction normally cannot be cancelled by asking the recipient, wallet developer, miner, or validator to reverse it.
- Volatility: the fiat value and BTC/ETH ratio can change while deposits are awaiting confirmations. An estimated output should not be treated as fixed unless the service explicitly states the applicable quote conditions.
- Fee changes: Bitcoin fee-rate recommendations and Ethereum base and priority fees can change quickly as demand changes. An estimate observed earlier may not apply when the transaction is broadcast.
- Phishing: obtain the deposit address from the genuine order page, avoid addresses sent through unsolicited messages, and compare the full address rather than only its first and last characters.
- Regional rules: access, identity checks, reporting duties, and tax treatment differ across countries and may also depend on the transaction. Current local requirements should be checked with an appropriate official or qualified source.
Immediately before confirming the exchange, refresh the quote, verify pair and network availability, check the exact BTC wallet fee, read the expected ETH output, and review any displayed service deductions. Recheck the destination address after pasting it and preserve the order details and transaction identifiers. If a material field is missing or ambiguous, do not replace it with an assumed fee or an estimate from an unrelated transaction type.