Bitcoin on its own network and a Bitcoin-linked token on another chain can appear similar in a wallet. They use different ledgers, destination formats and security assumptions.
This guide explains native BTC versus BTCB, the four familiar mainnet address families, fee calculation and what confirmations actually measure. The goal is to make the asset and network clear before interpreting a fee quote or transaction status.
Bitcoin at a glance
- Native asset: BTC on Bitcoin mainnet
- A balance is made up of unspent transaction outputs, commonly called UTXOs.
- Other-chain representation: BTCB is a separate token on BNB Smart Chain
- A Bitcoin-linked price does not make the token a native Bitcoin UTXO or remove its issuer and custody dependencies.
- Fee unit: Satoshis per virtual byte (sat/vB)
- The fee depends on transaction virtual size and fee rate, rather than simply the amount of BTC moved.
- Confirmation: Inclusion in a block, followed by additional blocks
- Bitcoin targets an average block interval of about ten minutes. Actual waits vary; a network average is not a schedule.
- Destination checks: Network, address and software support
- Recognizing a mainnet address prefix does not prove who controls it or that a particular wallet supports sending to it.
- Lightning: A separate Bitcoin payment mechanism
- Lightning requests require compatible software; they are not interchangeable with ordinary mainnet addresses.
Native Bitcoin versus BTCB: what changes?
Native BTC is accounted for by Bitcoin's consensus rules. A wallet controls the ability to spend particular transaction outputs; the balance displayed by the wallet summarizes those outputs. A transfer creates new outputs and consumes earlier ones.
BTCB on BNB Smart Chain is a token representation with a Bitcoin price target. Binance describes its backing arrangement in its own BTCB materials. That description is an issuer claim, not an independent assurance that every reserve, redemption path or market price remains unchanged today.
Native BTC
Recorded on Bitcoin, with fees denominated in BTC and destination formats such as 1…, 3…, bc1q… and bc1p…. A self-custody holder relies on Bitcoin's rules and their own key security rather than a wrapper's redemption mechanism.
BTCB on BSC
Recorded by a token contract on BSC, which uses EVM-style addresses. Ordinary on-chain execution uses BNB for gas. In addition to key security, the holder depends on the token arrangement and the host network.
Changing a wallet's selected network does not move native BTC onto BSC. A separate conversion or bridging mechanism would have its own terms and risks. Nor does a service recognizing native Bitcoin imply that it recognizes BTCB. Treat those as distinct asset-and-network combinations.
A lower network quote alone cannot settle this comparison. A token's market price, liquidity, redemption conditions and custody dependencies can matter more than one transfer's cost. No fixed transaction size or dollar threshold makes one representation universally preferable.
Sources: Bitcoin transaction outputs, Binance's BTCB explanation and BNB Smart Chain documentation.
How native Bitcoin fees work
Unconfirmed transactions are held in nodes' memory pools, or mempools. There is no single universal queue: different nodes may know about different transactions and apply different retention rules. Miners choose transactions for their blocks, with fee rates and transaction dependencies influencing that choice.
sat/vB measures a rate, not a total
A satoshi is one hundred-millionth of a bitcoin. A virtual byte measures transaction size after Bitcoin's witness weighting rules. More inputs, outputs or complex spending conditions can change the virtual size, so the amount of BTC sent does not determine the fee by itself.
A worked example, not a live quote
Assume a transaction of 140 vB and a fee rate of 10 sat/vB:
140 × 10 = 1,400 satoshis = 0.000014 BTC.
At a hypothetical BTC price of $70,000, the fee would be $0.98. At 100 sat/vB, the same 140 vB example would cost 14,000 satoshis, or $9.80 at that same assumed price. Actual transactions and prices differ.
Why estimates change
Demand for block space changes between estimation and inclusion. A wallet's fee estimate is a prediction based on recent observations; it cannot reserve a place in a particular future block. A higher fee may improve the chance of earlier inclusion without creating a deadline.
Read the full fee amount as well as the rate. A transaction using many small UTXOs can be larger than one spending a single output. Two wallets may also construct different transactions or estimate different confirmation targets, so a comparison requires more than the displayed sat/vB number.
Network fee versus provider charge
When a custodian constructs a transaction, its charge to a customer need not equal that customer's share of the blockchain fee. It may batch several outputs or apply a pricing policy of its own. Keep those two figures separate and use the current quote for the actual operation.
Sources: Bitcoin fee units and estimation, mempool messages and BIP 141 transaction weight.
Four familiar Bitcoin mainnet address formats
These prefixes help identify common output families. They do not verify the owner, prove that an address belongs to a service or establish that a wallet supports the complete format.
- P2PKH —
1… - Legacy pay-to-public-key-hash. The address encodes a public-key hash using Base58Check. It remains a Bitcoin output type; whether software exposes it is a wallet-level choice.
- P2SH —
3… - Pay-to-script-hash. The address identifies a script hash. That script may be multisignature, wrapped SegWit or another supported construction; the prefix alone does not identify SegWit.
- SegWit v0 / Bech32 —
bc1q… - Native version-0 witness address. These addresses use the Bech32 checksum defined in BIP 173. The sending application must recognize the format.
- Taproot / Bech32m —
bc1p… - Version-1 witness address used for Taproot. It uses Bech32m, described in BIP 350. A sender must support this encoding; do not manually alter a prefix to make an address appear compatible.
Do not try to convert an address by replacing its first characters. The checksum and encoded destination are part of the complete string. Bitcoin test networks also use different conventions; an example address from test documentation is not a mainnet destination.
Address type can affect the size of a later spending transaction, but no prefix guarantees the lowest total fee for every transaction. Input selection, number of outputs and the current fee rate remain relevant.
Sources: P2PKH and P2SH, BIP 173 (Bech32) and BIP 350 (Bech32m).
What a confirmation counts
Broadcast means a transaction has been sent to peers. It may already have a transaction identifier before inclusion in a block. One confirmation means inclusion in the current chain; each block built after that block adds another confirmation.
The familiar ten-minute interval is an average target, not a timer for each transaction. A transaction may wait before its first confirmation, and subsequent block intervals vary. Six confirmations describes a position in a chain, not a promise that sixty minutes have passed.
A chain reorganization can replace recent blocks and change a transaction's confirmation count. Additional confirmations reduce reversal risk without creating an absolute guarantee. Services decide their own acceptance thresholds; the network does not impose a universal account-crediting rule.
Source: Bitcoin's confirmation and double-spend explanation. Historical examples in that guide should not be read as current service policies.
Wallet compatibility and wrong-network prevention
A wallet's Bitcoin account and its EVM account are different contexts, even if both appear in one app. Check the full asset name, network and, for a token, the contract identity. A plain 0x destination does not become a native Bitcoin destination because a wallet labels a balance BTC.
Use the current receive information from the intended destination and let the wallet validate the full address. If the software rejects a format, investigate its documented support rather than changing the string. Compare the address shown for approval against the trusted source; clipboard replacement can leave a syntactically valid but unintended destination.
Hardware signing devices can provide a separate screen for review, but the user still needs to read it and secure the backup. A custodial wallet instead relies on the provider's signing and account controls. Neither setup makes a wrong address safe.
Where Lightning fits
Lightning is a Bitcoin payment network using channels and a compatible payment-request workflow. A Lightning request is not an ordinary Bitcoin mainnet address. Availability depends on both ends and their software; this guide makes no claim about a particular service's Lightning support.
For protocol details, see the Lightning payment-request specification.
Interpreting a transaction problem
The transaction is still unconfirmed
Check whether the wallet has broadcast it, whether an explorer on the correct network can see it, its fee rate and any unconfirmed parent transactions. Low fees are one possible explanation; a missing broadcast or a dependency can also matter.
Some wallets support fee replacement (RBF). In other situations, spending an available unconfirmed output with a sufficiently high fee can make a parent-and-child package more attractive to miners (CPFP). Availability depends on wallet features, spendable outputs and node policy. These mechanisms add cost and do not guarantee inclusion; use the wallet's own documentation rather than signing a stranger's proposed transaction.
It disappeared from one explorer
Mempool eviction or expiry at one node is not a confirmed cancellation or a timed refund. Another node can still retain the transaction, and it can be rebroadcast. Check the transaction and the inputs in your own wallet before treating the amount as safely available for a different purpose.
The chain shows a confirmation but an account does not
An explorer can establish an on-chain output and its confirmation count. It cannot prove which customer account a service has associated with it or what that service currently accepts. Compare the network, complete destination and asset against the receiving service's current records; use its verified support route if clarification is needed.
The destination was wrong
A confirmed Bitcoin transaction cannot be reversed by an explorer or wallet vendor. A valid but unintended address is different from an address rejected before broadcast. Preserve the public transaction identifier and verify what actually occurred; do not rely on promised recovery or expose signing keys.
Sources: BIP 125 fee replacement and Bitcoin transaction verification.
Frequently Asked Questions
Is BTCB the same asset as native Bitcoin?
No. BTCB on BNB Smart Chain is a Bitcoin-linked token. Native BTC exists on Bitcoin's own ledger. The token adds dependencies on its issuer, backing arrangements, token contracts and host chain; a price peg is not a guarantee of identical value or redemption.
Does every address beginning with 3 use SegWit?
No. On Bitcoin mainnet, 3 is the familiar P2SH prefix. P2SH means pay-to-script-hash and can represent different scripts, including but not limited to wrapped SegWit.
Does bc1 mean every wallet can send to the address?
No. bc1 is associated with Bitcoin mainnet witness addresses, but the particular encoding and witness version still matter to the sending software. A wallet must validate and support the complete address.
How much is 1,400 satoshis at a hypothetical BTC price of $70,000?
1,400 satoshis is 0.000014 BTC. At the stated hypothetical price, that equals $0.98. This is a unit-conversion example, not a current BTC price or a live fee estimate.
Does six confirmations mean exactly an hour?
No. Confirmations count blocks rather than elapsed time. The first confirmation also depends on inclusion. Block intervals vary, so a confirmation target cannot guarantee a clock time.
Does a transaction automatically refund after fourteen days?
No. Mempool retention is node policy, not a network-wide refund timer. A transaction can disappear from one node while other nodes retain or rebroadcast it. Check the wallet's transaction and input status before assuming the transaction can no longer confirm.
Can a 0x address receive native Bitcoin?
A plain EVM 0x address is not a native Bitcoin address. A token such as BTCB uses another chain. A network selector, token name or matching price does not turn those two destination types into the same thing.
Can a block explorer recover a mistaken transfer?
No. An explorer can display public chain records. It does not control destination keys or reverse a confirmed transaction. Do not provide a recovery phrase or private key to an alleged recovery service.