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
127
128
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 0148B954
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 2 Sep 2016 05:47:21 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail148102.authsmtp.net (outmail148102.authsmtp.net
[62.13.148.102])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 33D7810E
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 2 Sep 2016 05:47:19 +0000 (UTC)
Received: from mail-c232.authsmtp.com (mail-c232.authsmtp.com [62.13.128.232])
by punt20.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u825lIKo086234;
Fri, 2 Sep 2016 06:47:18 +0100 (BST)
Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com
[52.5.185.120]) (authenticated bits=0)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id u825lFkr059716
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Fri, 2 Sep 2016 06:47:16 +0100 (BST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
by petertodd.org (Postfix) with ESMTPSA id 5F8FC400B1;
Fri, 2 Sep 2016 05:43:53 +0000 (UTC)
Received: by localhost (Postfix, from userid 1000)
id 8793520528; Fri, 2 Sep 2016 05:47:14 +0000 (UTC)
Date: Fri, 2 Sep 2016 05:47:14 +0000
From: Peter Todd <pete@petertodd.org>
To: Johnson Lau <jl2012@xbt.hk>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20160902054714.GA1685@fedora-21-dvm>
References: <1317364559.64256.1472791258452@privateemail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ"
Content-Disposition: inline
In-Reply-To: <1317364559.64256.1472791258452@privateemail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Server-Quench: b4be5950-70d0-11e6-829e-00151795d556
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdgAUC1AEAgsB AmAbW1JeVFp7WGU7 bghPaBtcak9QXgdq
T0pMXVMcUQ1qBEB3 XVweVxB1dgMIfn9w ZQgwWiIOWU1/dVt6
QhpUCGwHMGF9YGIW BV1YdwJRcQRDe0tA b1YxNiYHcQ5VPz4z
GA41ejw8IwAXDilK CissFQBabUsCGj86 SFgdHCkvVUEYQiAi
Zwc6I1UfVEsVP0A/ N0dDEVcRNxsfAwdf G0BREUcA
X-Authentic-SMTP: 61633532353630.1037:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 52.5.185.120/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] New BIP: Dealing with dummy stack element
malleability
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: Fri, 02 Sep 2016 05:47:21 -0000
--mP3DRpeJDSE+ciuQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Sep 02, 2016 at 12:40:58AM -0400, Johnson Lau via bitcoin-dev wrote:
> Deployment
>=20
> This BIP will be deployed by "version bits" BIP9 using the same parameter=
s for BIP141 and BIP143, with the name "segwit" and using bit 1.
>=20
> For Bitcoin mainnet, the BIP9 starttime is midnight TBD UTC (Epoch timest=
amp TBD) and BIP9 timeout is midnight TBD UTC (Epoch timestamp TBD).
>=20
> For Bitcoin testnet, the BIP9 starttime is midnight 1 May 2016 UTC (Epoch=
timestamp 1462060800) and BIP9 timeout is midnight 1 May 2017 UTC (Epoch t=
imestamp 1493596800).
>=20
> Compatibility
>=20
> The reference client has produced compatible signatures from the beginnin=
g, and the NULLDUMMY rule has been enforced as relay policy by the referenc=
e client since v0.10.0. There has been no transactions violating the requir=
ement being added to the chain since at least August 2015. In addition, eve=
ry non-compliant signature can trivially be converted into a compliant one,=
so there is no loss of functionality by this requirement.
This should say "for all scriptPubKey types in actual use, non-compliant
signatures can trivially be converted into compliant ones"
You can of course create a scriptPubKey where that's not possible, but
fortunately no-one appears to do that.
Also, as original author of NULLDUMMY, thanks for finally making it into a
soft-fork!
--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
--mP3DRpeJDSE+ciuQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJXyRJfAAoJEGOZARBE6K+yRJAH/0ffhDA5HGGQs20pHOlocQPS
7Jot5/SJVelIocLuCosNGhZAaUkNRjgEK/bNEz3aC8MENJEG3fSXfie7AYql1aS3
a1FOD+vszP6gWQBvu7Zyty1bTqrXMNfrW2kt1/EFeiIr55AWzeyPhJoJ9j3qOkhx
Qx2kzFXYm9Fe6jifM7jGlRoQeV+mH7oLUyyhfGEb7F8BlG3zooHvHV2UPtr6EGex
msKGqKqFZTuochsOo2Q9bUb2t6eSm214fCN4mNe9IqqqzOaxUY1d/yWCqEq+e+qM
bKcAVYLfcJKcTAiUTQ1DDEQJh3KN1qEf7xyPvz7m5rxHqRWZXW36Y5JtfnlRpQ8=
=rFAv
-----END PGP SIGNATURE-----
--mP3DRpeJDSE+ciuQ--
|
