From: ts <ts@cronosurf•com>
To: Karl <gmkarl@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Human readable checksum (verification code) to avoid errors on BTC public addresses
Date: Fri, 20 Aug 2021 23:52:26 -0500 [thread overview]
Message-ID: <f1bfc456-4adc-2f3a-5598-b0d7947f8de0@cronosurf.com> (raw)
In-Reply-To: <CALL-=e4BJvr21W=MY-xG9i+CSvSmKC2UsO9A=B4DKq-WV6_-Bg@mail.gmail.com>
Hello Karl,
Yes, I agree in general. But while the visual checksum could be sometimes more interesting and
even useful, I guess that the technically simpler solution might be more likely to be adopted.
And also less prone to error. Just a thought.
Cheers,
TS
Karl wrote on 8/19/21 4:05 PM:
> Something that could work really well here could be having a norm of using the checksum for
> bright colors, weights, sizes, capitalizations, and/or spacing of the characters of the
> address, making different addresses more clearly visually distinct.
>
> Ethereum uses mixed case to do this a little bit:
> https://eips.ethereum.org/EIPS/eip-55#implementation
> <https://eips.ethereum.org/EIPS/eip-55#implementation>
>
> It seems to me the checksum at the end of the address is sufficient for differentiating error,
> but making a checksum more visually distinctive is indeed an opportunity to add another
> digest, reducing collisions and such.
next prev parent reply other threads:[~2021-08-21 4:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 4:23 ts
2021-08-16 10:34 ` ZmnSCPxj
2021-08-19 17:02 ` ts
2021-08-19 17:37 ` Christopher Allen
2021-08-21 4:52 ` ts
2021-08-19 21:05 ` Karl
2021-08-21 4:52 ` ts [this message]
2021-08-29 14:42 ` Pieter Wuille
2021-08-31 2:17 ` ts
2021-08-28 21:17 ` ts
2021-08-29 14:24 ` Pieter Wuille
2021-08-31 2:16 ` ts
2021-08-31 8:47 ` Marek Palatinus
2021-09-03 5:08 ` ts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1bfc456-4adc-2f3a-5598-b0d7947f8de0@cronosurf.com \
--to=ts@cronosurf$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gmkarl@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox