Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 28CF7C000E for ; Thu, 19 Aug 2021 21:05:47 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 18F4A8104C for ; Thu, 19 Aug 2021 21:05:47 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lTPNISmJPDNO for ; Thu, 19 Aug 2021 21:05:43 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) by smtp1.osuosl.org (Postfix) with ESMTPS id D715881002 for ; Thu, 19 Aug 2021 21:05:42 +0000 (UTC) Received: by mail-lj1-x232.google.com with SMTP id s3so13639026ljp.11 for ; Thu, 19 Aug 2021 14:05:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=SgvdlOA8tWyvM9e+T/ojtei76i4UlkpKvQ+Mawy7fEs=; b=qFyvNFvT6RedsLtDtqOXOw8Ivb5XyKdkadsmwyjBu6iTEoxk4YCGqNmE3xia0slwAg zoqb+UPCjAGtEg4E2GZWiZfY0DSYvR2kZuqbvCVw5OFOr7g9ugrb6Onkt/thJMQ3MDdg 4mcNUQTJ3HpNmZUintjeOl2XnGqPFZ8mMW8euG+RLCDYzzJ38q6pGg46GFWwSiIzxWXC 1lQzNL5drqeRSDX84rnCpxgVVRdLUtpUEGUPg+HXcUspAMu1PdAQ79PfzB2l0Ek/4o+W piNx8++0VGylhpkMyhCeaIvNnrUIGxCILz2qSJH0hwvEP4r7IPnfUHF41NtukfMx1tKx oanA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=SgvdlOA8tWyvM9e+T/ojtei76i4UlkpKvQ+Mawy7fEs=; b=B3YZH/RPugMCxBNuct8oZfvQGWitsnfaEzqtsM8evKUM1tFb4pDHgpWIh3CaxF+gIQ nM+jXAPM3XmD0IRtVTKnMf/sHZqr66tAXADHPVczPvpVS+74Ov0UmZX2/8iuW4Y98PjP zeFXyGSrjUHqHHu7p+Ib2mvRw8sxD4rGfp9kRrxYUeY8l+rNF5iLCsqq8WywxSChxPiV Rm3VPRr8QO2NGagNy9+jjUW5qdx/fddtJXgOrsbnoHKjT2vDithcS3jt/jOUyFpHB/PA iJAeU0XGho0BXmwbHroNPA7fN1mrD5QXHrxmmLOULN9vkwjRFHorwgmZulzcXQpfsnZ4 xeHw== X-Gm-Message-State: AOAM532XdekWO9B+Mx4C1zlhJdrkg5r+p4KScTVY04SPozO6wjoZdT58 1iiR3z+8lYBklfCEfpqpwnAJ2bOZ9WHKW4K6AXs= X-Google-Smtp-Source: ABdhPJyORhNui7hZxsobxRM5JCrffXbnu3n2PebZVQ3eezu0+oQ0jtbGWl9ThkoVPuZnhoscQ1APEQWAcYzxsY8rWQ4= X-Received: by 2002:a05:651c:10a2:: with SMTP id k2mr13740373ljn.262.1629407140660; Thu, 19 Aug 2021 14:05:40 -0700 (PDT) MIME-Version: 1.0 References: <8565f40b-2f32-cf31-6c47-971a6e57cb41@cronosurf.com> In-Reply-To: <8565f40b-2f32-cf31-6c47-971a6e57cb41@cronosurf.com> From: Karl Date: Thu, 19 Aug 2021 17:05:28 -0400 Message-ID: To: ts , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000d04ae105c9efe9e4" X-Mailman-Approved-At: Thu, 19 Aug 2021 23:17:29 +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: Thu, 19 Aug 2021 21:05:47 -0000 --000000000000d04ae105c9efe9e4 Content-Type: text/plain; charset="UTF-8" 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. --000000000000d04ae105c9efe9e4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Something that could work really well here could be = having a norm of using the checksum for bright colors, weights, sizes, capi= talizations, and/or spacing of the characters of the address, making differ= ent addresses more clearly visually distinct.

Ethereum uses mixed case to do this a little bit:=C2= =A0https:/= /eips.ethereum.org/EIPS/eip-55#implementation
It seems to me the checksum at the end of the add= ress is sufficient for differentiating error, but making a checksum more vi= sually distinctive is indeed an opportunity to add another digest, reducing= collisions and such.
--000000000000d04ae105c9efe9e4--