[Bitcoin-ml] Upgrading CashAddr in order to improve user experience

Lucas Clemente Vella lvella at gmail.com
Fri Feb 23 15:30:19 UTC 2018


One user complained on Reddit that the new CashAddr that it is
ambiguous, because lowcase 'L' looks like '1' and uppercase 'i'. I
dare say there is the same problem with 'o' and '0'. It is a problem
because most users won't bother to know what characters comprises the
base32 encoding.

My proposed solution is simple: treat 'i', 'L' and '1' as the same
encoded value of 31 when parsing input, but always record and display
as 'L' (use lowercase or uppercase as recommended).

Same thing with 'o' and '0': treat both as the same character with
encoded value of 15 when parsing, but always display 0.

We can make the adjustment in CashAddr spec and bump the version to 1.1.

-- 
Lucas Clemente Vella
lvella at gmail.com


More information about the bitcoin-ml mailing list