BIP 350 guide covering its Deployed status, new checksum constant, Bech32 for v0, Bech32m for v1-v16, strict decoding, compatibility and test vectors.
This guide explains BIP 350 Bech32m format for v1+ witness addresses in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
BIP 350 Bech32m format for v1+ witness addresses: The BIP is Deployed, Applications and Specification and replaces BIP 173 for version 1 and later witness addresses.
A node operator is checking BIP 350 Bech32m format for v1+ witness addresses. After decoding, require Bech32 for witness version 0 and Bech32m for versions 1 through 16.
The BIP is Deployed, Applications and Specification and replaces BIP 173 for version 1 and later witness addresses. It does not replace Bech32 for version 0 outputs.
Bech32m keeps the Bech32 character set and human-readable part but changes the final polymod constant from 1 to 0x2bc830a3 to address an insertion weakness.
After decoding, require Bech32 for witness version 0 and Bech32m for versions 1 through 16. Reject a checksum that is valid but belongs to the wrong version family.
Witness versions must be 0 to 16 and programs 2 to 40 bytes; version 0 is further restricted to 20 or 32 bytes. Reject mixed case, bad padding and wrong network HRP.
A checksum detects classes of transcription error; it does not authenticate the payee, network intent or wallet ownership. Confirm material addresses through a second trusted channel.
The deliberate forward-compatibility break stopped older faulty senders from treating version 1 addresses as ordinary Bech32. Software must upgrade before offering v1 payment support.
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
BIP 350 Bech32m format for v1+ witness addresses: The BIP is Deployed, Applications and Specification and replaces BIP 173 for version 1 and later witness addresses.
The BIP is Deployed, Applications and Specification and replaces BIP 173 for version 1 and later witness addresses.
Bech32m keeps the Bech32 character set and human-readable part but changes the final polymod constant from 1 to 0x2bc830a3 to address an insertion weakness.
After decoding, require Bech32 for witness version 0 and Bech32m for versions 1 through 16.
BIP 350’s central rule is simple but unforgiving: witness version 0 uses Bech32, while versions 1 through 16 use Bech32m. Decoders must verify that relationship after checksum validation.
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
BIP 450 guide to Draft Formosa themed mnemonic stories, entropy and checksum mapping, theme JSON, BIP39 conversion, passphrases and recovery safety.
BIP 393 guide to Draft descriptor annotations for birth height, gap limit and Silent Payment max label, checksum rules, parsing and recovery safety.
BIP 392 guide to Draft sp() descriptors, spscan and spspend encodings, watch-only and full-wallet forms, key origins, recovery and validation.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.