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
|
Return-Path: <bitcoin-dev@wuille.net>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
by lists.linuxfoundation.org (Postfix) with ESMTP id CEA2EC000E
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 29 Aug 2021 14:32:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id B7F1B40193
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 29 Aug 2021 14:32:32 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.598
X-Spam-Level:
X-Spam-Status: No, score=0.598 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, 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 xl-XDVCKapZn
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 29 Aug 2021 14:32:27 +0000 (UTC)
X-Greylist: delayed 00:07:33 by SQLgrey-1.8.0
Received: from mail-4327.protonmail.ch (mail-4327.protonmail.ch [185.70.43.27])
by smtp2.osuosl.org (Postfix) with ESMTPS id 81A054011F
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 29 Aug 2021 14:32:27 +0000 (UTC)
Received: from mail-0201.mail-europe.com (mail-0201.mail-europe.com
[51.77.79.158])
(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-4321.protonmail.ch (Postfix) with ESMTPS id 4GyG2M09vzz4xCDs
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 29 Aug 2021 14:25:30 +0000 (UTC)
Authentication-Results: mail-4321.protonmail.ch;
dkim=pass (2048-bit key) header.d=wuille.net header.i=@wuille.net
header.b="hCFYnijl"
Date: Sun, 29 Aug 2021 14:24:48 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wuille.net;
s=protonmail; t=1630247090;
bh=QTjnyBzpO5AkMFbwtDsYL9/AsdU1nUoXpVTtff7ZXkc=;
h=Date:To:From:Reply-To:Subject:In-Reply-To:References:From;
b=hCFYnijlT44fXnhRjATuaqsW7Ju+x53obW5dYdGXyfdID+l3n6Kn9r5/1C9Ep+zSr
4fYXjn+6YpxOYyKtG0UQPpyKjrsjwEWlTTbxez6QgUhzpf4tDRcNj+ZpYNX4djPsS0
yam8VBDS1bMTHpTXw4g6grBdYyKOQphWimdejgRFUDNOKvm89Gevzbg6dT+N3OKtam
PjPolK5ucobJR2yPX+JypjHjVhtq+vK0AYA1Jmq+ql41VhSF+h0mGDcwzY1Zb3klPT
VAydNOcqVzvOv8XZIXhfb3IUoDOJjC/bw6iZz1tBB+x3+lyDpPvFYfDPRJQXHruHrl
bORXzZFFpUmAw==
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: <3isqiyeCtgJdzEvbbm3ZoS6h1_4l3YjtPypqJAPto5cp2K1BebmgEdVGLGTYt2j803RnfaiIbFxjGdPIac8vHHpMmelwStYm0om_szvX7xc=@wuille.net>
In-Reply-To: <6f69f132-211f-9d42-8023-c3b0264af439@cronosurf.com>
References: <f31bc6b0-f9b3-be4c-190c-fc292821b24b@cronosurf.com>
<6f69f132-211f-9d42-8023-c3b0264af439@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:32:32 -0000
On Saturday, August 28th, 2021 at 5:17 PM, ts via bitcoin-dev <bitcoin-dev@=
lists.linuxfoundation.org> wrote:
> Following up on my original proposal, I would like to get some more feedb=
ack of the community
>
> to see if this could be realized at some point. Also, any recommendations=
as to who to contact
>
> to get things rolling?
I honestly don't understand the point of what you're suggesting.
* If you're concerned about random typos, this is something already automat=
ically protected against through the checksum (both base58check or bech32/b=
ech32m).
* If you're concerned about accidentally entering the wrong - but honestly =
created - address, comparing any few characters of the address is just as g=
ood as any other. It doesn't even require the presence of a checksum. Looki=
ng at the last N characters, or the middle N, or anything except the first =
few, will do, and is just as good as an "external" checksum added at the en=
d. For randomly-generated addresses (as honest ones are), each of those has=
exactly as much entropy.
* If you're concerned about maliciously constructed addresses, which are de=
signed to look similar in specific places, an attacker can just as easily m=
ake the external checksum collide (and having one might even worsen this, a=
s now the attacker can focus on exactly that, rather than needing to focus =
on every other character).
Things would be different if you'd suggest a checksum in another medium tha=
n text (e.g. a visual/drawing/colorcoding one). But I don't see any added v=
alue for an additional text-based checksum when addresses are already text =
themselves. This is even disregarding the difficulty of getting the ecosyst=
em to adopt such changes.
Cheers,
--
Pieter
|
