summaryrefslogtreecommitdiff
path: root/bb/0471328a97da5ad5e62079a7888a7b3e43d0fc
blob: 70169f5a1e95ef1de054c5ffd8c113ba113feb2a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
Return-Path: <bitcoin-dev@wuille.net>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id B931DC000E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 29 Aug 2021 14:42:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id A4E25400FD
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 29 Aug 2021 14:42:26 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.597
X-Spam-Level: 
X-Spam-Status: No, score=0.597 tagged_above=-999 required=5
 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001,
 SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=wuille.net
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 fIh4dZJ98EgL
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 29 Aug 2021 14:42:21 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from mail-41103.protonmail.ch (mail-41103.protonmail.ch
 [185.70.41.103])
 by smtp2.osuosl.org (Postfix) with ESMTPS id C64ED4011F
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 29 Aug 2021 14:42:21 +0000 (UTC)
Received: from mail-0301.mail-europe.com (mail-0301.mail-europe.com
 [188.165.51.139])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (4096 bits))
 (No client certificate requested)
 by mail-41103.protonmail.ch (Postfix) with ESMTPS id 4GyGPl3qNhz4x4Ck
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 29 Aug 2021 14:42:19 +0000 (UTC)
Authentication-Results: mail-41103.protonmail.ch;
 dkim=pass (2048-bit key) header.d=wuille.net header.i=@wuille.net
 header.b="A+ehTiIp"
Date: Sun, 29 Aug 2021 14:42:07 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wuille.net;
 s=protonmail; t=1630248129;
 bh=/pSk/6Gq/gPMQgUZeA/+xK6cLmuyq+VSmfxnc8d+/4k=;
 h=Date:To:From:Reply-To:Subject:In-Reply-To:References:From;
 b=A+ehTiIpW5OaoYc9QA2sSRDEdaXU6sPtUw7Bjyfs+xBpFz+fuP1vYMDMiY6hk4Smm
 H6W2dkJ//ldVGjcFNswxpRgkvM0Z8w1Wf4RRVXtj/VcSe2Frp9dWQkPaC3ujU49idy
 ay3vBBA4dR1tS636Ih1fKGLrwq+cZeIX8ByVhqEJJVzNxX22zv5r+zFeWPBJsIhi6N
 8555BhIToVmEvLVSI5C2gZ+/ft9tNCvugWZsqEQ4mmt160zBHbVnZ3TXX4emh9GI8y
 RdupQG6tgOob8S4LaUjQWZsG7bK6ALjNZAlaTzoT8NUHYlQjnruUmul92hEu/vfIWa
 UdCmu9g0l9StA==
To: ts <ts@cronosurf.com>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: Pieter Wuille <bitcoin-dev@wuille.net>
Reply-To: Pieter Wuille <bitcoin-dev@wuille.net>
Message-ID: <ZJqjnpWzG9qKb0N02X9WLkBM2hRWk7w0hmAXlIuHj1bQZptdxVJzdVGXAwSPjkM187aRo5GkQq4oSnCurryxKRkWTeA5HgNL9VxmFMoTpF4=@wuille.net>
In-Reply-To: <8565f40b-2f32-cf31-6c47-971a6e57cb41@cronosurf.com>
References: <f31bc6b0-f9b3-be4c-190c-fc292821b24b@cronosurf.com>
 <aO1qYUmtGXPJupl0ol3E221AR4XKwqriqk3Y5fVS2_asquaV8Vaxkb4Ffq2EiVMrR5bb4cXAzxAV3cOciaYsuqJoFXoc6vTOoveKURVTmLU=@protonmail.com>
 <8565f40b-2f32-cf31-6c47-971a6e57cb41@cronosurf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Sun, 29 Aug 2021 16:26:37 +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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Aug 2021 14:42:26 -0000

On Thursday, August 19th, 2021 at 1:02 PM, ts via bitcoin-dev <bitcoin-dev@=
lists.linuxfoundation.org> wrote:

> > In any case --- the last 5 characters of a bech32 string are already a =
human-readable 5-digit code, with fairly good properties, why is it not usa=
ble for this case?

Side note: it's actually the last six characters.

>
> Well, because
>
> a) most people don't know that
>
> b) it is specific to bech32
>
> c) it is not easily readable being the last digits of a long address (alt=
hough this could be

I think this is a misconception. For the purpose of verifying that you have=
 the *right* address (rather than just a valid one), the checksum, or even =
the knowledge that a checksum is present, is completely irrelevant.

In honestly-generated addresses, every character except the prefix (the ~2 =
first characters for P2PKH and P2SH, and the ~4 first characters for BIP173=
/BIP350 native segwit addresses) has exactly the same amount of entropy. In=
stead of adding say a 4 character code, just tell people to compare any 4 c=
haracters of their choosing. Or more - I would hope people are already comp=
aring (much) more than 4 characters already.

It doesn't matter if the characters being compared are checksum characters =
or data characters. In honestly-generated addresses, both are equally rando=
m.

Adding a special 4 character "external" checksum IMO would instead encourag=
e people to perhaps just compare those 4 characters instead of the rest (or=
 at least, focus mostly on those). That could easily worsen how well compar=
isons are done in practice...

Cheers,

--
Pieter