Bitcoin Address Types Explained: What to Check Before You Send

Why Bitcoin Address Types Matter When Sending

Bitcoin address types map directly to different output script types that control how funds are locked on the blockchain. Each type evolved through protocol upgrades, altering the data required in a transaction and therefore its total size in virtual bytes.

Because transaction fees are calculated from weight units, the script type chosen by the sender determines the cost of moving bitcoin. Newer formats place more data in the witness field, which receives a discount, resulting in lower fees for the same economic transfer. Senders therefore benefit from selecting a compatible modern address when creating an outgoing transaction.

All four address types remain fully interoperable on the Bitcoin network. A legacy address can send to a Taproot address and vice versa without restriction, as the protocol places no limits on output scripts. The recipient’s address format does not constrain what the sender can do; only the sender’s own wallet software and the script it builds affect size and cost.

Practical problems arise when wallets or services fail to recognize an unfamiliar address format. Users must verify that their sending wallet supports the exact prefix and encoding of the destination address before broadcasting. Failure to do so can produce an invalid transaction or force an unnecessary conversion step that increases both size and fees. Understanding these mappings helps traders avoid such mismatches while still taking advantage of the fee savings available from witness-based scripts.

Legacy P2PKH Addresses Starting with 1

Legacy addresses follow the P2PKH script type and constitute the original Bitcoin format introduced in 2009 with the genesis block. They begin with the digit 1 and employ Base58Check encoding to produce the familiar human-readable string.

Because these addresses predate the 2017 SegWit activation, spending from them generates no witness data. A typical single-input, two-output transaction therefore occupies approximately 226 vbytes and serves as the 100 % baseline for relative fee comparisons.

The absence of the witness discount directly increases the weight units counted toward the block-weight limit, resulting in higher fees whenever Legacy inputs are used. All address formats remain fully interoperable on the Bitcoin network, so a sender can still transmit funds to a Legacy address; only the sender’s own input type determines the size penalty incurred.

Derivation paths for Legacy addresses follow the BIP 44 standard. Although new UTXOs of this type now represent less than 5 % of outputs created in mid-2026, older coins locked in P2PKH scripts continue to exist and must be spent using the larger transaction format.

P2SH Addresses Starting with 3

Pay-to-Script-Hash addresses beginning with 3 were introduced in 2012 via BIP 16. The change let senders reference the hash of a redeem script rather than embedding the full script in every transaction, enabling practical multisig and other conditional spends that had previously been cumbersome.

Developers later reused the same prefix for nested SegWit. A P2SH-P2WPKH output wraps a native SegWit script inside the older P2SH structure, giving older wallets partial access to smaller transaction sizes without requiring a full upgrade to Bech32 support.

Size and fee impact fall between legacy and native formats. A typical single-input, two-output nested SegWit transaction measures 166–170 vbytes, producing roughly 24–39 percent savings versus the 226 vbytes of a legacy P2PKH spend, per 2026 data from Self Custody Labs and Spark. P2SH still accounts for 5–8 percent of new UTXOs in mid-2026 estimates, reflecting continued use for multisig and compatibility.

Every address type remains fully interoperable, so a P2SH address can receive from or send to any other format without restriction from the network itself.

Native SegWit bc1q Addresses

Native SegWit addresses use the Bech32 encoding format defined in BIP 173 and begin with bc1q. They correspond to pay-to-witness-public-key-hash (P2WPKH) outputs and became available after the SegWit soft fork activated in August 2017. Because witness data receives a discount in weight units, a typical single-input, two-output transaction using these addresses measures roughly 141 vbytes, delivering an approximate 38 percent fee reduction compared with a Legacy P2PKH transaction of similar structure.

Current network data shows SegWit inputs appearing in 85 to 95 percent of transactions as of 2026, according to both bitcoin.com and Spark analyses. This dominance reflects broad wallet and exchange support, with most modern software defaulting to bc1q generation. The Bech32 checksum also catches more transcription errors than the older Base58Check scheme used by addresses starting with 1 or 3.

Any address type can send to a bc1q recipient without restriction, and the sender’s choice affects only size and cost. When preparing a transaction, users should confirm that the destination address matches the bc1q prefix exactly; the stronger error detection in Bech32 reduces the chance of sending funds to an invalid address, but it does not eliminate the need to double-check the full string before broadcasting.

Taproot bc1p Addresses and Their Advantages

Taproot addresses begin with bc1p and rely on Bech32m encoding specified in BIP 350. The upgrade activated at block 709,632 in November 2021 through BIPs 340, 341, and 342.

Schnorr signatures replace the older ECDSA scheme with fixed-length signatures that enable key aggregation through MuSig. MAST allows complex spending conditions to remain hidden; on-chain they appear identical to ordinary key-path spends, improving privacy for scripted transactions.

Key-path Taproot transactions measure roughly 132–211 vbytes in common single-input, two-output cases. This produces an extra 15 percent per-input saving versus native SegWit P2WPKH outputs and up to 39–61 percent versus legacy P2PKH, per 2026 comparisons from Self Custody Labs and Spark.

Taproot input share has settled in the 15–35 percent range across 2026 sources. Glassnode data referenced by bitcoin.com showed approximately 29 percent as of March 2026, while other on-chain reviews reported 30–35 percent sustained by mid-2026 after an earlier peak above 40 percent in 2024.

The same activation enabled Ordinals, Runes, and inscription protocols that temporarily lifted usage. Modern wallets now generate bc1p addresses by default or on request, though a minority of older exchanges still delay full withdrawal support.

Fee and Size Comparison Table

Transaction costs in Bitcoin depend heavily on the address type chosen by the sender. The table below compares the four primary types using approximate sizes for a single-input, two-output transaction and relative savings against the Legacy baseline, drawn from Self Custody Labs (August 2026), Spark (2026), and bitcoin.com (September 2026 update). Adoption figures reflect mid-2026 estimates of new UTXO output shares from on-chain analysis.

SegWit inputs overall reached 85–95% of transactions by 2026 according to bitcoin.com and Spark reports, while Taproot input share estimates ranged between 15–35% depending on the exact observation window. These differences arise because older coins still dominate the UTXO set by value even as newer outputs favor bc1q and bc1p formats. Note that Taproot sizes can exceed Native SegWit in complex multi-input cases, yet key-path spends still deliver the largest per-input discount when conditions allow. Source data for sizes and savings percentages come directly from the cited 2026 references and should be re-checked against current mempool conditions before large transfers.

What to Verify Before Sending Bitcoin

Before broadcasting any transaction, confirm the recipient address begins with the correct prefix for its type: 1 for Legacy P2PKH, 3 for P2SH, bc1q for native SegWit, or bc1p for Taproot. A mismatch here sends coins to an invalid script that the recipient wallet may never recognize.

Next, verify that your sending wallet can construct outputs for the target address type. Most current wallets handle bc1q by default and offer Taproot as an option, yet older software may lack bc1p support entirely. Sending from an unsupported wallet forces you to first move funds elsewhere, adding an extra on-chain step and fees.

Review the fee impact of your own inputs. A single-input, two-output transaction using Legacy P2PKH inputs measures roughly 226 vB, while the same transaction drops to 141 vB with native SegWit inputs and around 132 vB with Taproot key-path spends. Those reductions translate to 38 percent lower fees versus Legacy at identical sat-per-vbyte rates, according to size tables published in September 2026. If your current UTXOs sit in higher-weight inputs, a registration-free swap can convert them into native SegWit or Taproot outputs without creating an account for most swaps.

Finally, note that identity verification may be requested in specific compliance situations even on services that otherwise require no KYC for most swaps. Performing this check once prevents both lost funds and unexpected delays when the network is busy.

Best Practices and Common Sending Pitfalls

Generate a fresh address for every incoming transaction to limit address reuse and improve on-chain privacy. Most wallets follow this pattern by default, and older addresses stay valid indefinitely even if new ones are created.

Pay attention to derivation paths when restoring wallets or moving between software. BIP 44, 49, 84 and 86 each map to a specific address type; selecting the wrong path can produce a Legacy address even on modern software and force you to pay higher fees.

Some older exchanges and services still do not support Taproot withdrawals. In those cases the platform may convert your withdrawal to a Legacy or nested SegWit output, erasing the fee savings that bc1p addresses normally provide. Verify the destination address format before initiating the send and, where possible, withdraw to a wallet you control that accepts Taproot.

Default to native SegWit or Taproot in your own wallet settings to avoid unnecessary Legacy transaction sizes. Many wallets now set bc1q as the standard output, but older installations or custom configurations can still default to addresses starting with 1. Changing the setting once prevents repeated overpayment of fees on every outgoing transaction.

Double-check the first few and last few characters of any address you paste, and confirm the prefix matches the type the recipient expects. A simple mismatch between bc1q and bc1p will not break the transaction, yet it can silently route funds through a less efficient script if your wallet does not automatically optimise.

FAQ

Can I send Bitcoin from a legacy address to a Taproot address?

All Bitcoin address types remain fully interoperable. A sender using a P2PKH address starting with 1 can pay a recipient using a bc1p Taproot address without restrictions from the network.

How much do fees differ across address types?

A single-input two-output Legacy transaction weighs roughly 226 vB. Native SegWit drops this to about 141 vB for a 38 percent saving, while Taproot key-path spends range from 132 to 211 vB depending on the exact inputs and outputs, according to 2026 data from Self Custody Labs and Spark.

What share of transactions now use SegWit addresses?

SegWit inputs appear in 85 to 90 percent of transactions as of September 2026 per bitcoin.com, with other 2026 analyses placing the figure between 90 and 95 percent.

How common are Taproot addresses in 2026?

Taproot inputs reached around 29 percent in March 2026 according to Glassnode data cited by bitcoin.com, with mid-2026 on-chain estimates ranging from 30 to 35 percent after earlier volatility.

Do older wallets still work with newer address formats?

Most modern wallets default to native SegWit bc1q addresses and treat Taproot as an optional upgrade. Older services may not yet support bc1p withdrawals, though compatibility continues to expand.

When might a swap service ask for identity verification?

Xgram does not require KYC for most cryptocurrency swaps. Transactions flagged by compliance procedures may still trigger additional review and identity verification.

Should I check the recipient address type before sending?

Yes. Confirming the exact prefix and format prevents sending to an unsupported address on older platforms and lets you choose the lowest-fee input type available in your wallet.