Sign in
Article Learn

Bitcoin address types: 1, 3, bc1q, bc1p and how to check them

Bitcoin address types explained: Legacy, P2SH, Native SegWit and Taproot, which is cheapest to spend, and how to verify an address before you send BTC.

Bitcoin address types: 1, 3, bc1q, bc1p and how to check them
Contents
  1. What is a bitcoin address?
  2. The four bitcoin address formats at a glance
  3. Which address type has the lowest fees?
  4. What this looks like on November 2, 2026
  5. How to verify a bitcoin address before sending
  6. Common mistakes
  7. Limitations
  8. FAQ

There are four main bitcoin address types, and you can tell them apart by the first characters: 1 is Legacy (P2PKH), 3 is P2SH (usually wrapped SegWit or multisig), bc1q is Native SegWit, and bc1p is Taproot. They are fully compatible — you can send from any type to any other. What differs is transaction size (and therefore the fee) and how well the format catches typos. For everyday use, receive to bc1q or bc1p, and always verify the whole address before you hit send.

What is a bitcoin address?

Bitcoin doesn't keep balances in accounts. The blockchain records transaction outputs, each locked by a spending condition such as "provide a signature from the key whose hash is this." An address is simply a human-friendly encoding of that condition. Your wallet derives it from a public key, which in turn comes from your seed phrase.

That's why the Bitcoin Wiki calls it an invoice address: a one-time label for a single incoming payment. An address doesn't really "hold" a balance, and you never send "from" an address — you spend specific coins that were received to it. Modern wallets generate a fresh address for every payment, because reusing addresses links your transactions together and hurts privacy.

The four bitcoin address formats at a glance

Starts with Name Script type Encoding Introduced
1… Legacy P2PKH Base58Check 2009, at launch
3… P2SH / "Nested SegWit" P2SH (incl. P2SH-P2WPKH) Base58Check 2012, BIP-16
bc1q… Native SegWit P2WPKH / P2WSH Bech32 2017, BIP-173
bc1p… Taproot P2TR Bech32m 2021, BIP-350

Legacy (1…) is the original format. It still works, but the signature sits inside the main transaction body, making it the heaviest and most expensive to spend.

P2SH (3…) arrived with BIP-16 in January 2012. The sender pays to the hash of an arbitrary script, and the receiver reveals the script when spending. That made multisig practical and, after SegWit, gave older services a "wrapped" SegWit address they could pay. You can't tell from a 3 address alone whether it's multisig or wrapped SegWit.

Native SegWit (bc1q…) was specified in BIP-173 by Pieter Wuille and Greg Maxwell in 2017. Signatures move into the "witness," which counts four times less toward fees. It's the default in many wallets — Trezor Suite, for example, creates a SegWit account by default.

Taproot (bc1p…) activated at block 709,632 on November 14, 2021 (Bitcoin Optech, block explorer). It uses Schnorr signatures, so a simple payment and a complex script look the same on-chain — good for privacy and multisig.

A few prefixes people confuse with mainnet addresses: tb1…, m…, n… and 2… are testnet (coins with no market value); lnbc… is a Lightning invoice, not an on-chain address; sp1q… is a Silent Payments address under BIP-352, still supported by only a handful of wallets.

Which address type has the lowest fees?

Bitcoin fees depend on transaction size in virtual bytes (vB) times the fee rate in sats per vB — not on the amount sent (see our guide to mempool and fees). The Bitcoin Optech size calculator lists the size of each input and output type. Take a typical payment: one input, two outputs (recipient plus change), all the same type. The totals below are our calculation from those figures.

Format Size, vB Savings vs Legacy Fee at 1 sat/vB Fee at 20 sat/vB
Legacy (1) 226 — 226 sats ≈ $0.18 4,520 sats ≈ $3.53
P2SH-SegWit (3) ~166 27% ~166 sats ≈ $0.13 ~3,315 sats ≈ $2.59
Native SegWit (bc1q) ~141 38% ~141 sats ≈ $0.11 ~2,815 sats ≈ $2.20
Taproot (bc1p) ~154 32% ~154 sats ≈ $0.12 ~3,085 sats ≈ $2.41

Dollar values use a BTC price of $78,114 as of 08:00 UTC on November 2, 2026 (our data).

A Taproot input is smaller than a SegWit one (57.75 vs 68.25 vB), but a Taproot output is larger (43 vs 31 vB). So for a simple payment Native SegWit is still slightly cheaper, while Taproot pulls ahead once a transaction has three or more inputs, and in multisig setups.

What this looks like on November 2, 2026

As of 08:00 UTC on November 2, 2026, the fast fee rate in our data was 1 sat/vB at block height 974,230 (live values are in the Numbers panel). At that rate the gap between formats is a few cents: $0.18 for Legacy versus $0.11 for Native SegWit. But mempool congestion can push rates up by an order of magnitude or more. At 20 sat/vB the same Legacy payment costs $3.53 against $2.20. If you regularly consolidate many small deposits, the gap scales with the number of inputs: every Legacy input is 148 vB, every Native SegWit input about 68.

The practical takeaway: receive to bc1q or bc1p. Coins sitting on 1 and 3 addresses are perfectly safe — they just cost more to move.

How to verify a bitcoin address before sending

Every format has a built-in checksum: the last few characters are computed from the rest. For Base58 addresses (1 and 3), a random typo slips through roughly 1 time in 2³² (Bitcoin Wiki). Bech32 is stronger: per BIP-173 it is guaranteed to detect any error affecting up to 4 characters. It also drops lookalike characters (1, b, i, o) and is case-insensitive. Bech32 did have one flaw — if an address ends in p, inserting or deleting q characters right before it doesn't break the checksum. BIP-350 fixed that with Bech32m, which Taproot addresses use.

A checksum stops typos, not substitution — a scammer's address is valid too. A safe routine:

  1. Copy the address from the source — the recipient's wallet app or the exchange deposit page, never from your transaction history or a chat.
  2. Check the network. When withdrawing BTC from an exchange, pick the Bitcoin network. Addresses on other networks (BEP-20, ERC-20) look different (0x…) and send coins to a different blockchain.
  3. Compare the full address in chunks of 4⁠–⁠5 characters, not just the first and last few.
  4. On a hardware wallet, trust the device screen. Malware can alter what your computer shows.
  5. For large amounts, send a test payment and wait until the recipient confirms it arrived. Then copy the address again from the source — not from the test transaction in your history.
  6. Use a QR code or a bitcoin: link (BIP-21) so the address never touches your clipboard.

Common mistakes

  • Clipboard hijacking. "Clipper" malware watches your clipboard and swaps a copied address for the attacker's, often one that matches the first and last characters. If the pasted address differs from the copied one by even a single character, stop.
  • Address poisoning. A scammer sends you a tiny payment from an address that looks like one you use, hoping you'll copy it from your history next time. The Blockchain Address Poisoning study counted 270 million such attacks on 17 million victims over two years on Ethereum and BSC, with at least $83.8 million lost. The trick works on any chain where people copy addresses from history, bitcoin included. More schemes in our guide to crypto scams.
  • An older service rejects bc1p. Some exchanges and wallets still can't send to Taproot. Give them a bc1q address instead, and if that fails too, a 3 address (Trezor's advice).
  • A restored wallet shows zero. Often the wallet is simply scanning a different address type. Switch the account type (Legacy, SegWit, Taproot) and the coins reappear.
  • Paying a testnet address or a Lightning invoice where an on-chain address was expected. Decent wallets block this; hand-built transactions and homemade scripts may not.

Limitations

No address format protects you from the core risk: sending to an address you believe is right but isn't. Bitcoin transactions can't be reversed, and there's no help desk that can claw funds back. The fee table is a simplification — real size depends on the number of inputs and outputs, and multisig or complex scripts differ. Taproot also doesn't make payments anonymous: amounts and links between addresses remain visible on-chain. For long-term storage, where your keys live matters more than the address format (see cold wallets).

FAQ

Can I send from a bc1 address to one starting with 1 or 3? Yes. All formats are compatible at the network level; sender and recipient don't need the same type.

Which bitcoin address type should I use in 2026? For everyday payments, Native SegWit (bc1q): nearly every service supports it and it's cheap. Taproot (bc1p) is more efficient with many inputs and for multisig, as long as the services you use can pay to it.

Is it OK to reuse the same address? It works, but it hurts privacy — anyone can see all your incoming payments. Wallets issue a new address for each payment, and all of them are recoverable from one seed phrase.

What happens if I mistype one character? Almost certainly the wallet will refuse to send because the checksum won't match. The real danger isn't a typo but a fully valid address that has been swapped.

Live price and network fees are on the Bitcoin page and in the market overview.

This is not investment advice.

Morning brief and news on TelegramEvery morning at 9:00 AM ET, before the US open: price, 24h scenario, squeeze risk. Key news around the clock.
Coins
Category
Tags
#bitcoin address#SegWit#Taproot#security#fees
Ryan Mitchell
On-chain and mining

Breaks down blockchain and mining data: hashrate, difficulty, holder and whale behavior.

Comments

Read next