Bech32 detects as much as 4 errors (within the sense that, if you happen to make as much as 4 substitution errors, the ensuing string is assured to have an incorrect checksum). However error detection is just not the identical as error finding: simply figuring out {that a} bech32 is inaccurate doesn’t imply you possibly can inform the place the errors have been made.
Bech32 additionally permits correcting as much as 2 substitution errors. That’s, if you already know not more than 2 substitution errors have been made, you possibly can for any given string compute what the unique, legitimate, string was. The javascript code on the web site you hyperlink to has code to do that, however for security causes, it deliberately doesn’t reveal what errors it discovered, solely the place.
The reason being that correcting is harmful. If the person made greater than 2 substitution errors, the error correction algorithm might properly nonetheless discover two errors to “right”, within the sense that it will assemble a legitimate tackle, however it is going to not be the person’s tackle. An inattentive person might properly simply make the corrections urged by the algorithm, and ship funds into the void. As a substitute, the correction algorithm remains to be used below the hood, however solely the situation of its errors is revealed, forcing the person to nonetheless go verify whether or not main supply they acquired the tackle by way of, however maybe with further give attention to the actual places the algorithm believes are the probably positions errors have been made.
