From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id CE939C000E for ; Sat, 21 Aug 2021 04:52:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id B72AB4013B for ; Sat, 21 Aug 2021 04:52:26 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PchoO7iOtgfE for ; Sat, 21 Aug 2021 04:52:25 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from premium29-m.web-hosting.com (premium29-m.web-hosting.com [68.65.120.189]) by smtp2.osuosl.org (Postfix) with ESMTPS id 8F5B3400D0 for ; Sat, 21 Aug 2021 04:52:25 +0000 (UTC) Received: from [189.174.9.220] (port=55332 helo=[192.168.1.88]) by premium29.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1mHIzS-000klQ-Ak; Sat, 21 Aug 2021 00:52:24 -0400 To: Christopher Allen , Bitcoin Protocol Discussion References: <8565f40b-2f32-cf31-6c47-971a6e57cb41@cronosurf.com> From: ts Message-ID: <54c434c9-2efb-a7aa-1e71-8123a92d3bfd@cronosurf.com> Date: Fri, 20 Aug 2021 23:52:16 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - premium29.web-hosting.com X-AntiAbuse: Original Domain - lists.linuxfoundation.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - cronosurf.com X-Get-Message-Sender-Via: premium29.web-hosting.com: authenticated_id: ts@cronosurf.com X-Authenticated-Sender: premium29.web-hosting.com: ts@cronosurf.com X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched X-Mailman-Approved-At: Sat, 21 Aug 2021 07:50:26 +0000 Subject: Re: [bitcoin-dev] Human readable checksum (verification code) to avoid errors on BTC public addresses X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Aug 2021 04:52:26 -0000 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 > ) > > * [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 > >