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

[Matias Alejo Garcia]

Please note that copy-pasting an address or QR scanning it is not affected
by this issue.  Also, note that cashaddr has a (strong) checksum that would
prevent this issue: if the user types it wrong; or if a malware modifies
it, the checksum will not verify).

I'm afraid the change you propose is not minor, because it will need to be
implemented, in a coordinated way, by every wallet, exchange, etc that
currently use cashaddr.

On Fri, Feb 23, 2018 at 12:30 PM, Lucas Clemente Vella via bitcoin-ml <
bitcoin-ml at lists.linuxfoundation.org> wrote:

> 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
> _______________________________________________
> bitcoin-ml mailing list
> bitcoin-ml at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-ml
>



-- 
Matías Alejo Garcia
@ematiu
Roads? Where we're going, we don't need roads!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-ml/attachments/20180223/9afe3142/attachment.html>