A fixed-rate BTC exchange prioritizes certainty about the quoted output, while a floating-rate exchange leaves the final output exposed to market movement during processing. That distinction sounds simple, but the practical result also depends on quote expiry, Bitcoin confirmation timing, the amount actually deposited, liquidity, network costs and the exchange provider’s rules. This analysis explains those mechanisms without comparing live offers or assuming that a particular pair, network or rate mode is currently available.
How the Claims Were Checked
The evidence hierarchy gives priority to Bitcoin Core and Bitcoin project documentation for transaction mechanics, provider documentation for the contractual meaning of fixed and floating quotes, and regulatory or intergovernmental publications for volatility, compliance and jurisdictional risk.
Provider documents establish how that provider structures its own exchanges; they do not prove that every service follows the same timing, pricing or refund rules. Dynamic conditions such as a quote, required confirmations, available direction, compliance request and network status must therefore be checked again when an exchange request is created. Source dates are recorded in the claim registry so that older general guidance is not mistaken for a current commercial term.
What Fixed and Floating Rates Actually Mean
Fixed rate: conditional quote certainty
In a fixed-rate exchange, the provider locks a quoted conversion rate or receiving amount for a limited period. ChangeNOW describes its fixed-rate exchange as preserving the rate displayed at the beginning when the deposit is made within its stated window. SideShift similarly documents a fixed quote that expires after a defined period. The exact window is provider-specific and can change, so neither example establishes the terms of another exchange service. [1]
“Fixed” does not mean that every part of the transaction is unconditional. The quote may depend on the correct deposit amount arriving at the designated address, on-time detection or confirmation, supported network use and satisfaction of any applicable compliance procedure. Late, incomplete or mismatched deposits may be recalculated, refunded or handled manually according to the provider’s current rules.
A provider also assumes short-term price risk when it promises a specified output despite market movement. ChangeNOW states that its fixed-rate flow includes a reserve for exchange-rate fluctuations. This supports the narrower conclusion that fixed-rate protection may be reflected in the quoted rate; it does not prove a universal surcharge or quantify the difference for any other service. [1]
Floating rate: estimated output until execution
A floating-rate exchange displays an estimate rather than an unconditional receiving amount. SideShift documents a variable rate that is not locked until deposit, while SimpleSwap states that its floating output is determined using the market rate available when the swap is processed. Under such models, the final output can be above or below the initial estimate. [2]
The estimate can change because the BTC conversion price moves, available liquidity changes, network-related costs are updated or processing takes longer than expected. A floating rate therefore transfers more short-term market risk to the user, but it can also avoid paying for quote protection that turns out not to be needed. It cannot be described as automatically cheaper or more favorable without comparing the complete live quotes.
The calculation behind the choice
The following is a conceptual calculation, not a live quotation:
Estimated output = deposited BTC × applicable execution rate − disclosed exchange and delivery costs.
Under a fixed model, the applicable rate is generally the accepted quote if all quote conditions are met. Under a floating model, it is generally the rate determined later under the provider’s execution rules. The useful comparison is therefore the final asset amount expected at the destination wallet, not an isolated headline rate.
| Decision factor | Fixed rate | Floating rate |
|---|---|---|
| Receiving amount | Quoted amount may be preserved if all lock conditions are satisfied | Initial amount is an estimate and may change before execution |
| Exposure to BTC price movement | Provider generally absorbs movement during the valid lock window | User generally remains exposed until the rate is determined |
| Time sensitivity | Usually high because the quote expires | Often more flexible, although the request can still have operational limits |
| Pricing trade-off | May incorporate a buffer for the provider’s rate risk | May track current execution conditions more closely |
| Best comparison metric | Net amount delivered if quote conditions are met | Estimated net amount plus the possible effect of execution delay |
| Main uncertainty | Whether the deposit satisfies the quote conditions | What rate and costs will apply when processing occurs |
Why Bitcoin Confirmation Timing Matters
Sending BTC to an exchange address does not necessarily mean that the exchange can process it immediately. A transaction begins unconfirmed, and a service may wait for one or more blockchain confirmations before treating the deposit as received. Bitcoin documentation explains that confirmation confidence increases as additional blocks are built over the block containing the transaction. [3]
Confirmation time is not a guaranteed countdown. Bitcoin Core’s estimatesmartfee function produces an approximate fee rate for a target number of blocks “if possible,” and its result depends on observed transaction and block data. The existence of an estimator, rather than a guaranteed schedule, is relevant to fixed quotes: a wallet fee chosen for the deposit can affect whether the transaction confirms before the quote expires. [4]
This creates a practical asymmetry. With a floating exchange, a delay mainly increases exposure to a later execution rate. With a fixed exchange, the same delay can also cause the lock conditions to fail. Paying a higher Bitcoin network fee may improve confirmation priority, but no fee selection can guarantee inclusion in a particular block.
Claim Registry
| Claim | Verification status | Primary source type and name | Publication or update date | Limitation | What could change the conclusion |
|---|---|---|---|---|---|
| A fixed-rate BTC exchange can preserve the displayed output during a limited quote window. | Confirmed as a provider model; conditional in application | Provider help documentation: “What is a fixed rate exchange?” by ChangeNOW [1] | Updated January 28, 2026 | The documented window and conditions belong to that provider. They cannot be transferred to another service. | Revised provider terms, a different exchange direction, late deposit, incorrect amount, unsupported network or compliance intervention. |
| A floating-rate output may differ from the estimate because the applicable rate is determined later. | Confirmed as a common provider model | Provider API documentation: “How Crypto Shifts Work” by SideShift; provider FAQ by SimpleSwap [2] | No publication date displayed on the cited pages | Providers use different execution moments, liquidity sources and cost calculations. | A change to the provider’s execution policy or the introduction of a different rate mode. |
| Fixed-rate protection may be incorporated into the quote rather than charged as a separately named fee. | Confirmed for the cited provider; unknown as a universal rule | Provider help documentation: ChangeNOW fixed-rate explanation [1] | Updated January 28, 2026 | The source does not establish how another exchange prices rate risk. | A provider may use a separate fee, spread, liquidity arrangement or another pricing structure. |
| Bitcoin transaction fee estimates and confirmation targets are approximate rather than guaranteed. | Confirmed | Technical documentation: Bitcoin Core 31.0 RPC documentation and release notes [4] | Bitcoin Core 31.0 released April 19, 2026 | Software estimation describes probable fee requirements; miners still choose transactions for blocks. | Network demand, transaction structure, wallet fee policy, replacement behavior and future Bitcoin Core changes. |
| BTC volatility can materially affect a floating exchange while processing is underway. | Confirmed as a general risk; magnitude unknown for an individual exchange | Regulatory customer advisory: CFTC, “Understand the Risks of Virtual Currency Trading” [5] | December 15, 2017 | The advisory confirms volatility but does not measure current movement or predict a particular transaction’s outcome. | Actual market conditions during the interval between quote creation and execution. |
| Verification and information requirements can differ by country and provider risk assessment. | Confirmed generally; transaction-specific outcome is conditional | Intergovernmental standards and implementation update: FATF virtual asset materials [6] | Latest cited targeted update published June 26, 2025 | FATF sets international standards, while national implementation and provider procedures differ. | Changes in local law, sanctions, provider policy, transaction direction, wallet risk indicators or compliance findings. |
| The analyzed exchange service’s current lock duration, confirmation threshold, rate buffer and late-deposit procedure. | Unknown from the supplied facts | No qualifying primary source supplied | Not available | Values from competing providers would not prove this service’s current conditions. | The live request screen, current service terms or transaction-specific support instructions. |
How to Compare Two BTC Exchange Quotes
A rate label alone is insufficient. The comparison should use the same deposit amount, asset direction and destination network, then account for every amount shown before confirmation.
- Check the net receiving amount. Determine how much of the destination asset is expected to reach the wallet, rather than comparing only the displayed BTC price.
- Identify which amount is fixed. A service may lock the rate, the output amount or a quote based on an exact input. Those formulations are not necessarily interchangeable.
- Read the expiry condition. Establish whether the BTC transaction must merely be broadcast, detected, received or confirmed before the timer ends.
- Separate wallet and exchange costs. The fee paid by the sending wallet to the Bitcoin network may sit outside the exchange quote. The destination-chain delivery cost may be included, deducted or shown separately.
- Check deposit tolerances. Sending more or less BTC than specified can change how the request is processed.
- Confirm the network and address. The asset ticker alone does not prove that the selected network is compatible with the receiving wallet.
- Review verification conditions. Requirements may depend on the operation direction and the result of compliance checks. Current conditions should be reviewed before funds are sent.
- Save the request details. Keep the request identifier, quoted amount, expiry information, deposit address and transaction ID until the exchange is completed.
When Each Rate Structure Is More Relevant
A fixed quote is more relevant when a specific receiving amount is operationally necessary. Examples include paying an invoice denominated in another asset or moving an exact amount to a wallet. Its usefulness depends on the sender being able to satisfy the deadline and all other quote conditions.
A floating quote is more relevant when timing flexibility matters more than output certainty. It leaves open the possibility of receiving either more or less than estimated. Choosing it is therefore an acceptance of short-term execution uncertainty, not a prediction that BTC will move in a favorable direction.
For small exchanges, differences in network and delivery costs can outweigh a modest rate difference. For larger exchanges, even a small movement in the conversion rate can matter more in absolute terms. No universal threshold separates the two cases because current quotes, transaction structure and provider rules are dynamic.
Risk Controls Before Sending BTC
Bitcoin payments cannot be unilaterally reversed after they have been sent; a refund requires action by the recipient. Bitcoin guidance consequently recommends verifying the destination before transmission. [7]
- Copy the deposit address from the active request and compare the full address after pasting it into the wallet.
- Confirm that BTC is being sent on the exact network requested by the service.
- Do not reuse an address from an old exchange request unless the provider explicitly confirms that it remains valid.
- Open the service through a known, independently verified route rather than an unsolicited message, advertisement or support account.
- Never disclose a seed phrase or private key to complete an exchange or compliance check.
- If the fixed-rate timer is close to expiring, do not assume that broadcasting the transaction preserves the quote; check the stated acceptance condition.
- Inspect the transaction in a suitable Bitcoin blockchain explorer after broadcast and retain the transaction ID.
- Pause if the asset, network, amount, address or quote terms differ from the intended request.
Phishing is a separate risk from rate selection. The CFTC identifies hacking and phishing among virtual-currency risks, while Bitcoin security guidance warns about fake exchanges, fraudulent support and malware that substitutes an attacker’s address during copying. [5]
Procedure for Rechecking Dynamic Information
- Create a fresh request rather than relying on a screenshot or earlier quote.
- Verify that the required BTC exchange direction and destination network are currently available.
- Record whether the displayed amount is fixed or estimated and note the quote expiry.
- Check the exact event required before expiry: broadcast, detection, receipt or blockchain confirmation.
- Review the current minimum, maximum, fee presentation and deposit-amount rules shown for that request without assuming they match previous exchanges.
- Confirm any verification requirements before sending. A compliance review can affect processing regardless of the selected rate mode.
- Check current Bitcoin fee conditions through the wallet or a reputable blockchain data source, recognizing that confirmation estimates remain probabilistic.
- Recompare the final output if the request expires or any term changes. Do not send to an expired address solely because it appeared in an earlier request.
After completing these checks, the service interface can be used to check currently available BTC exchange directions and rate options. This commercial link is a practical next step, not evidence for any claim in the analysis.
Bottom Line
The choice is between two different allocations of short-term uncertainty. A valid fixed quote shifts defined market-movement risk to the provider but adds deadline and eligibility conditions. A floating quote reduces dependence on a brief lock window but leaves the final output exposed to the rate and costs applied during processing.
The decisive comparison is the net amount delivered under the actual request terms. Before sending BTC, verify the lock condition, confirmation requirement, network, address, cost treatment and compliance rules. If any of those details is unavailable, the result of the exchange cannot be calculated reliably from the “fixed” or “floating” label alone.
