Why it exists
BIP 350 introduces Bech32m for native witness addresses with versions 1 through 16. It preserves the familiar Bech32 structure while correcting a checksum weakness relevant to variable-length addresses. Taproot is the most familiar use: a mainnet Taproot address normally starts bc1p.
How it works
Bech32m changes the checksum constant, not the underlying public key or Bitcoin consensus rules. A decoder must examine both the witness version and the checksum variant. Version 0 uses original Bech32; higher versions require Bech32m.
An address that passes a checksum but pairs the wrong variant with its witness version must be rejected. The wallet also checks the network prefix and witness-program length. These checks happen before constructing a transaction; they do not require access to the recipient’s private keys.
A practical example
Consider two receive requests: a native SegWit address starting bc1q and a Taproot address starting bc1p. A compatible sender validates the former with Bech32 and the latter with Bech32m. It must not “repair” one by swapping characters until some checksum passes, because the intended destination would be uncertain.
What to keep in mind
An older wallet may refuse a valid Bech32m destination. That is a compatibility issue, not a reason to alter the address manually. A valid higher-version encoding also does not prove that its spending rules are activated or that the recipient can recover it.
Status & implementation
BIP 350 is Deployed. Bitcoin Core 22.0 explicitly implemented the version-dependent Bech32m address checks. Taproot spending semantics come from BIP 341; address encoding and consensus activation are separate pieces.
Specification status: Deployed · Sources checked 13 November 2026
