public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Karl <gmkarl@gmail.com>
To: ts <ts@cronosurf.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: Thu, 19 Aug 2021 17:05:28 -0400	[thread overview]
Message-ID: <CALL-=e4BJvr21W=MY-xG9i+CSvSmKC2UsO9A=B4DKq-WV6_-Bg@mail.gmail.com> (raw)
In-Reply-To: <8565f40b-2f32-cf31-6c47-971a6e57cb41@cronosurf.com>

[-- Attachment #1: Type: text/plain, Size: 574 bytes --]

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

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.

[-- Attachment #2: Type: text/html, Size: 768 bytes --]

  parent reply	other threads:[~2021-08-19 21:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16  4:23 [bitcoin-dev] Human readable checksum (verification code) to avoid errors on BTC public addresses 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 [this message]
2021-08-21  4:52       ` ts
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='CALL-=e4BJvr21W=MY-xG9i+CSvSmKC2UsO9A=B4DKq-WV6_-Bg@mail.gmail.com' \
    --to=gmkarl@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=ts@cronosurf.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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