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
|
Return-Path: <luke@dashjr.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 39527C24
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 Jan 2018 14:23:17 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id D4ADD14E
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 Jan 2018 14:23:16 +0000 (UTC)
Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265::71])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id E86B538A0C5D
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 Jan 2018 14:23:06 +0000 (UTC)
X-Hashcash: 1:25:180104:bitcoin-dev@lists.linuxfoundation.org::4q7dUIopSDAKFSiK:azz1N
From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org
Date: Thu, 4 Jan 2018 14:23:05 +0000
User-Agent: KMail/1.13.7 (Linux/4.12.12-gentoo; KDE/4.14.37; x86_64; ; )
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201801041423.05959.luke@dashjr.org>
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,
T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: [bitcoin-dev] =?iso-8859-1?q?Bech32_and_P2SH=B2?=
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
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: Thu, 04 Jan 2018 14:23:17 -0000
I know I'm super-late to bring this up, but was there a reason Bech32 omitt=
ed=20
the previously-discussed P2SH=B2 improvements? Since deployment isn't too=20
widespread yet, maybe it'd be worth a quick revision to add this?
=46or those unfamiliar with the concept, the idea is to have the address in=
clude=20
the *single* SHA256 hash of the public key or script, rather than=20
RIPEMD160(SHA256(pubkey)) or SHA256(SHA256(script)). The sender would then=
=20
perform the second hash to produce the output. Doing this would in the futu=
re=20
enable relaying the "middle-hash" as a way to prove the final hash is in fa=
ct=20
a hash itself, thereby proving it is not embedded data spam.
Bech32 seems like a huge missed opportunity to add this, since everyone wil=
l=20
probably be upgrading to it at some point.
Luke
|
