Bech32 / Bech32m

Bech32 is the address format used by native SegWit Bitcoin addresses, which start with bc1q. Bech32m is a corrected variant used by Taproot addresses, which start with bc1p. Both carry a checksum that catches most typing mistakes, but the format says nothing about who owns an address or how risky it is.

What Bech32 and Bech32m are

Bech32 is a way of writing an address as letters and digits with a built-in checksum. Bitcoin Improvement Proposal 173 introduced it for native SegWit addresses.[1] A Bech32 address has three parts:

  • A human-readable part that names the network: bc on Bitcoin mainnet and tb on testnet.[1]
  • The separator, which is always the digit 1.[1]
  • The data part, written in a 32-character alphabet that leaves out 1, b, i and o because they are easy to confuse.[1]

Native SegWit (version 0) addresses are always 42 or 62 characters long.[1] Later, BIP-350 introduced Bech32m for newer address versions, including Taproot. Version 0 addresses keep using Bech32; versions 1 to 16 use Bech32m.[2] That is why a SegWit address starts with bc1q and a Taproot address with bc1p.

Litecoin uses the same scheme with its own prefix: ltc for normal addresses and ltcmweb for addresses on its MWEB privacy layer.[3]

How the checksum protects you

The checksum is guaranteed to detect any error that affects up to four characters.[1] A wallet that checks it will refuse an address with a typo instead of sending coins to the wrong place. The format also forbids mixing upper and lower case in one address: decoders must reject such strings.[1]

Bech32m exists because Bech32 had a flaw. If an address ends in p, inserting or deleting q characters just before it does not break the checksum.[2] Bech32m changes one constant to fix this. Old wallets that only know Bech32 reject Bech32m addresses, so they cannot send to an address they are unable to validate.[2]

Bech32 in an AML check

A checker uses the prefix to recognise the network and the address type. That is all the format tells it. A bc1q or bc1p address is not safer or riskier than an old address starting with 1 or 3: the risk comes from the coins’ history and from who controls the address, which a checker estimates through attribution and exposure. Paste the full address, including the bc1 part, or the check may fail or find the wrong address.

What it means for you

  • A valid checksum is not proof of the right address. It catches typos, not a different, valid address. Scammers rely on this in address poisoning, where a lookalike address appears in your history.
  • Copy, then compare. Check the first and last several characters, and the middle too, before you send.
  • If your wallet rejects a bc1p address, it may not support Taproot yet. Update it rather than editing the address.

To screen a Bitcoin or Litecoin address, see our Bitcoin and Litecoin pages and the service rankings.

General information, not legal or financial advice. Rules differ by country and change; check the linked sources.

FAQ

What is the difference between bc1q and bc1p?

bc1q is a native SegWit address written in Bech32. bc1p is a Taproot address written in Bech32m. Both are valid Bitcoin addresses.

Can I write a Bech32 address in capital letters?

Yes, all uppercase is allowed, for example in QR codes, but you must not mix upper and lower case in one address.

Does a bc1 address mean the wallet is safe?

No. The format only describes how the address is written. Run an AML check to see where the coins came from.

Sources

  1. Bitcoin BIPs — BIP-173: Base32 address format for native v0-16 witness outputs. Checked 19 Nov 2026.
  2. Bitcoin BIPs — BIP-350: Bech32m format for v1+ witness addresses. Checked 19 Nov 2026.
  3. Litecoin Core — chainparams.cpp (address version bytes). Checked 19 Nov 2026.