A phone, laptop and signing device arranged as three different ways to use a Bitcoin wallet, editorial illustration
BIP 173 / ADDRESSES

Recognize a native SegWit address.

Bech32 encodes witness addresses with a human-readable prefix and a checksum.

Read the explanation
← All standards

Why it exists

BIP 173 defines Bech32, the readable encoding behind native version-0 SegWit addresses. It gives wallets a compact way to communicate a witness program with a network prefix and an error-detecting checksum. The address is a representation of a payment destination, not the destination’s private key.

How it works

A Bech32 address combines a human-readable prefix, the separator 1, a data section and a six-character checksum. For mainnet Bitcoin the prefix is bc. A version-0 witness address normally begins bc1q; test networks use different prefixes.

The wallet decodes the witness version and program, verifies length rules and checksum, and constructs the corresponding output script. Mixed uppercase and lowercase text is invalid. The checksum is designed to detect common transcription errors, helping a wallet reject a damaged address instead of sending to an unintended script.

PUT IT IN CONTEXT

A practical example

Imagine copying a receive address from a native SegWit wallet into a second wallet. If one character is accidentally changed, the sender should reject the string. If the original address is intact, it can decode to a version-0 program for a public-key hash or script hash, without asking the recipient for a redeem script.

What to keep in mind

A checksum cannot establish who owns an address. Malware can substitute a different, perfectly valid address. BIP 350 requires Bech32m for witness versions 1 and above; using Bech32 indiscriminately for every bc1 address is incorrect.

Status & implementation

BIP 173 is Deployed. Bitcoin Core’s descriptor documentation distinguishes version-0 wpkh()/wsh() outputs from tr() outputs. Wallet support should be checked for the specific output type, not inferred solely from the bc1 prefix.

Specification status: Deployed · Sources checked 13 November 2026

Read the sources

Put the standard in context.

Explore the practical guide

Find your next answer.

Search the complete field guide · Esc to close