From: ts <ts@cronosurf•com>
To: Christopher Allen <ChristopherA@lifewithalacrity•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:16 -0500 [thread overview]
Message-ID: <54c434c9-2efb-a7aa-1e71-8123a92d3bfd@cronosurf.com> (raw)
In-Reply-To: <CACrqygDK4oKSvY0XXPXH=MmKAvHkmw2CoASwySn0qGteBUYr9Q@mail.gmail.com>
Good day Christopher,
Thanks for your comment! LifeHash looks indeed quite interesting. I can imagine some examples
where it would be very useful, and I guess it could be used as a visual verification for the
address in a wallet as well.
However, for my proposal (Human readable checksum (verification code) to avoid errors) it
could have the following disadvantages:
1. It would be only one standard instead of one standard per crypto network (it should be
different on each of them as described in the proposal). This could be solved with the
inclusion of a network identifier somehow, but would increase the complexity of the
implementation.
2. For this special use case, a simple 3 to 4 digit code is easier to implement than a
graphic, and easier to include in an existing app, with minimal layout changes. The simpler it
is, the more likely it will be for developers to actually implement it.
3. A graphic cannot be communicated by voice (in some situations this could be an easier way
to communicate the verification code)
Greetings,
TS
Christopher Allen wrote on 8/19/21 12:37 PM:
> 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
> <https://github.com/BlockchainCommons/lifehash>)
>
> * [LifeHash Explainer on YouTube](https://www.youtube.com/watch?v=cu0K__KLxKo
> <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
> <https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2021-002-digest.md#object-identity-block>)
>
> -- Christopher Allen
> Principal Architect, Blockchain Commons
>
>
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 [this message]
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=54c434c9-2efb-a7aa-1e71-8123a92d3bfd@cronosurf.com \
--to=ts@cronosurf$(echo .)com \
--cc=ChristopherA@lifewithalacrity$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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