BIP 173 states that the Bech32 checksum used by native SegWit addresses guarantees detection of any error affecting at most 4 characters; BIP 350 later described a weakness with inserted or deleted characters, which it says does not affect version 0 addresses because they are restricted to two specific lengths.
Sources and checks
T1BIP 173, Base32 address format for native v0-16 witness outputsBIP, says this directly
guarantees detection of any error affecting at most 4 characters
Specification, Bech32, checksum, read 2026-11-20
T1BIP 350, Bech32m format for v1+ witness addressesBIP, says this directly
whenever the final character is a 'p', inserting or deleting any number of 'q' characters immediately preceding it does not invalidate the checksum.
Motivation, read 2026-11-20
T1BIP 350, Bech32m format for v1+ witness addressesBIP, says this directly
This does not affect existing uses of witness version 0 BIP173 addresses due to their restriction to two specific lengths,
Motivation, read 2026-11-20
T2Bitcoin Optech topic, Bech32(m)Bitcoin Optech, supports part of it
includes an error-correction code that can catch almost all address typos
Topic description, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 4/4
History
Nothing is edited silently; every revision keeps what it replaced.
- 20 Nov 2026, 16:42 UTCblock 976,753
Published Revision 1, run 2026-11-20-seed-segwit