From: Christopher Allen <ChristopherA@lifewithalacrity.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 10:37:29 -0700 [thread overview]
Message-ID: <CACrqygDK4oKSvY0XXPXH=MmKAvHkmw2CoASwySn0qGteBUYr9Q@mail.gmail.com> (raw)
In-Reply-To: <8565f40b-2f32-cf31-6c47-971a6e57cb41@cronosurf.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
As an alternative, you might want to consider LifeHash, which includes a
visual indicator as well as a readable fingerprint value.
LifeHash is an open source visual hashing algorithm that we use for all our
projects. Lifehash has a number of desirable qualities, including high
complexity, good aesthetics, a printer-friendly (CMYK) color gamut and
robustness when transformed to grayscale.
* [LifeHask Overview and links to reference code](
https://github.com/BlockchainCommons/lifehash)
* [LifeHash Explainer on YouTube](
https://www.youtube.com/watch?v=cu0K__KLxKo)
* [Our LifeHash UX best practices - The Object Identity Block](
https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2021-002-digest.md#object-identity-block
)
-- Christopher Allen
Principal Architect, Blockchain Commons
[-- Attachment #2: Type: text/html, Size: 1244 bytes --]
next prev parent reply other threads:[~2021-08-19 17:38 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 [this message]
2021-08-21 4:52 ` ts
2021-08-19 21:05 ` Karl
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='CACrqygDK4oKSvY0XXPXH=MmKAvHkmw2CoASwySn0qGteBUYr9Q@mail.gmail.com' \
--to=christophera@lifewithalacrity.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