When a MarketExchange BTC order shows a Bitcoin address beginning with 1, 3, bc1q, or bc1p, the key question is not which format looks newer. Before you sign, match the exact address string on the live order to what your wallet can send or accept on Bitcoin mainnet, paste it unchanged, and stop if the format or network does not match. This avoids forcing a converter, sending on another chain, or turning a correct order into a recovery problem.
Summary: Bitcoin mainnet uses several address formats, and a wallet may support some while rejecting others. Read the exact BTC string required by the order, confirm your wallet can use that format on Bitcoin mainnet, and paste the full string without conversion. If the wallet rejects it or the network is not Bitcoin mainnet, stop and recreate the order with an address format your wallet actually supports.
The familiar prefixes are useful signals, not instructions to rewrite an address. A string beginning with 1 is a Legacy P2PKH form, 3 is a P2SH form commonly used for nested SegWit, bc1q is native SegWit using Bech32, and bc1p is a Taproot address using Bech32m. A Bitcoin mainnet address beginning with tb1 is testnet, while lnbc identifies a Lightning invoice rather than an on-chain Bitcoin address.
How to Read a Bitcoin Address Prefix Before a Swap
Do: Open the live MarketExchange order and identify the exact BTC string before opening your wallet’s Send or Receive screen. If the order is receiving your BTC, inspect the deposit address you must pay. If the order is paying BTC to your wallet, inspect the payout or recipient address involved.
| Prefix | What it indicates | Pre-send action |
|---|---|---|
| 1 | Legacy P2PKH address format | Paste the complete string and verify your wallet can pay or accept it. |
| 3 | P2SH address format, including common nested SegWit use | Use the complete order or Receive string without changing it. |
| bc1q | Bitcoin mainnet witness version 0, native SegWit, Bech32 | Confirm the sending wallet supports this destination format. |
| bc1p | Bitcoin mainnet witness version 1, Taproot, Bech32m | Confirm the sending wallet supports this format specifically. |
| tb1 | Bitcoin testnet Bech32 address | Stop. Do not use it as a Bitcoin mainnet MarketExchange destination. |
| lnbc | Lightning invoice, not an on-chain BTC address | Stop and check the payment method and order instructions. |
Do not: use a testnet tb1 address, a Lightning lnbc invoice, or a wrapped-BTC destination on BEP-20 or ERC-20 simply because the asset label says BTC. This checklist is for Bitcoin mainnet on-chain BTC.
How to Check Wallet Support for the Exact BTC Format
- Open the live MarketExchange order and confirm which side of the order contains BTC.
- Identify whether the BTC address is the deposit destination you must pay or the payout address where BTC will be received.
- Read the prefix of the complete string. Note whether it starts with 1, 3, bc1q, or bc1p. Treat tb1 and lnbc as stop signals for this on-chain mainnet flow.
- Open the wallet on Bitcoin mainnet and check that its Send or Receive flow accepts the exact address format.
- Paste the complete string directly from the live order or the wallet’s Receive screen. Do not type it manually, trim it, re-case it, or otherwise edit it.
- Check the wallet’s validation result before entering the final amount or signing. A recognized address on Bitcoin mainnet can proceed to the normal destination and amount review.
- Stop if the wallet says the address format is unsupported, invalid, or belongs to another network. Do not force the transaction or use a converter to bypass the rejection.
The workflow is: live order → read the BTC prefix → confirm wallet support on Bitcoin mainnet → paste the full string → review → sign. If any stage fails, stop, do not convert, and recreate the order or obtain a wallet-supported destination before confirming again.
For the broader exchange flow, start with the MarketExchange exchange guides. For an unresolved address or order issue, use official MarketExchange support rather than sending another payment to diagnose the first.
Why You Should Not Convert Bech32 to Legacy
Do: Copy the address exactly as supplied by the order or wallet. Bitcoin address formats are not interchangeable text encodings of one universal address. Native SegWit and Legacy represent different on-chain output types, so a supposed conversion can change what the destination means.
Do not: paste a MarketExchange address into a random “bc1 to 1” or “Bech32 to Legacy” converter. Do not remove characters, insert characters, change the case of part of a Bech32 string, or accept a site’s suggested “corrected” address. If the required format is unsupported, obtain a supported address from the wallet or recreate the order instead.
When to Use a Separate Small Test Order
Do: If you have never paid an address format before and genuinely want to establish that your wallet supports the route, make the test a separate small order. Use the same asset and intended network, then follow that order’s own instructions.
Do not: divide an existing Fixed order into a “test” payment and a remainder. MarketExchange’s terms state that a Fixed exchange can be recalculated, refunded subject to applicable conditions and fees, or rejected if the user sends late, sends the wrong amount, uses the wrong network, or sends multiple transactions. A test belongs in its own order, not as a partial payment to a Fixed deposit.
Checklist: Stop on a Mismatch Before Signing
Do: Stop before signing when the address format, network, or payment method does not match. If you are sending BTC to a MarketExchange deposit and the wallet only supports a different destination format, start again with an order and deposit address that your wallet can actually use. If MarketExchange is sending BTC to your wallet and the displayed payout destination is not supported by that wallet, obtain a suitable Receive address from your wallet and use a new order where appropriate.
Do not: force-send because the interface offers a bypass, because a converter says the address can be changed, or because another article says that Bitcoin address formats are generally interoperable. Protocol-level compatibility does not make an unsupported wallet UI safe to bypass.
If the order is already live and the wallet rejects its BTC destination, the clean decision path is: stop → do not broadcast → create or obtain a destination your wallet supports → create a new order if the required address changes. MarketExchange assigns each transaction a unique identifier, so do not assume an old deposit address can simply be reused for a new order.
If you already sent and need to establish what happened, use the transaction ID and the relevant order details rather than sending another payment blindly. For related transaction-ID checks, use the MarketExchange transaction-ID guide.
Frequently asked questions
Can I send BTC from a bc1 address to a 1 address?
Yes, at the Bitcoin protocol level, different Bitcoin output types can be used across transactions. The practical condition is that the sending wallet must support the destination it is asked to pay. For a MarketExchange order, use the exact destination displayed by the order.
Can Bitcoin be lost if I send to the wrong address format?
Yes, an incorrectly modified destination can create a loss of funds. A format mismatch that the wallet rejects is a stop-and-fix situation before broadcast. A manually converted, truncated, mistyped, or wrong-network destination can be much harder or impossible to recover. Do not broadcast a transaction just to test whether a converter worked.
Is Taproot the same as Bech32?
Taproot uses Bech32m, not the original Bech32 checksum format. In the common address forms, bc1q identifies witness version 0 and uses Bech32, while bc1p identifies witness version 1 and uses Bech32m. Both can start with bc1, but bc1q and bc1p should be treated as distinct formats when checking wallet support.
What should I do if my wallet says a bc1 address is unsupported?
Stop before signing and do not convert the address. Check that the wallet is on Bitcoin mainnet and that its Bitcoin send flow supports the exact destination. If it does not, obtain a wallet-supported destination where the wallet is the recipient, or recreate the MarketExchange order with a deposit address your sending wallet can pay. Do not edit the bc1 string yourself.
Can I use a tb1 address for a Bitcoin swap?
Not for a Bitcoin mainnet MarketExchange deposit or payout. The tb1 prefix identifies Bitcoin testnet in the Bech32 format. Stop and check the wallet’s network and Receive or Send screen. A mainnet order needs the correct Bitcoin mainnet route.
Is an lnbc invoice the same as a bc1 Bitcoin address?
No. An lnbc string is a Lightning invoice, while bc1 is used by on-chain Bitcoin address formats. Do not paste a Lightning invoice into an on-chain BTC address field or treat a Lightning payment as an on-chain test.
What if I already sent the wrong amount or used multiple test transfers?
Stop sending additional funds and check the live order status and transaction evidence. MarketExchange’s Fixed-rate terms state that late, wrong-amount, wrong-network, or multiple-transaction deposits may be recalculated, refunded subject to the terms, or rejected when technically impossible. Do not send another payment to “balance” the order without instructions. If you need help, contact MarketExchange support with the order and transaction details.
Disclaimer: The material in this article is not financial or investment advice. Everything stated here reflects the author's personal view and should not be treated as a recommendation to trade or invest. We make no warranties regarding the accuracy, reliability or completeness of the information presented. Cryptocurrency markets are highly volatile and can move unpredictably. Before committing any funds, every investor, trader or crypto user should study several independent sources and check the regulations that apply in their own jurisdiction.