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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1Xleg5-0004vK-2k
for bitcoin-development@lists.sourceforge.net;
Tue, 04 Nov 2014 14:01:45 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.44 as permitted sender)
client-ip=209.85.213.44; envelope-from=gavinandresen@gmail.com;
helo=mail-yh0-f44.google.com;
Received: from mail-yh0-f44.google.com ([209.85.213.44])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Xleg3-0007IE-Cv
for bitcoin-development@lists.sourceforge.net;
Tue, 04 Nov 2014 14:01:45 +0000
Received: by mail-yh0-f44.google.com with SMTP id i57so3558054yha.31
for <bitcoin-development@lists.sourceforge.net>;
Tue, 04 Nov 2014 06:01:38 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.170.55.4 with SMTP id 4mr47376512ykx.37.1415109697850; Tue,
04 Nov 2014 06:01:37 -0800 (PST)
Received: by 10.170.133.82 with HTTP; Tue, 4 Nov 2014 06:01:37 -0800 (PST)
In-Reply-To: <CAPg+sBjygohgFf2hE9cGH3ZmV0MaeniZDDNO+hFxOxo-s_d81A@mail.gmail.com>
References: <CAPg+sBjygohgFf2hE9cGH3ZmV0MaeniZDDNO+hFxOxo-s_d81A@mail.gmail.com>
Date: Tue, 4 Nov 2014 09:01:37 -0500
Message-ID: <CABsx9T1qCJf6a0qkPFQu_GJM=yDBJADVSK_sRgiSVgho04dCsA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=001a1139a77edbebc7050708e691
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Xleg3-0007IE-Cv
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP62 and future script upgrades
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 14:01:45 -0000
--001a1139a77edbebc7050708e691
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Nov 4, 2014 at 8:29 AM, Pieter Wuille <pieter.wuille@gmail.com>
wrote:
> Luke suggested on the pull request to not apply this rule on every
> transaction with nVersion >= 3, which indeed solves the problem. I
> believe this can easily be generalized: make the (non mandatory) BIP62
> rules only apply to transaction with strict nVersion==3, and not to
> higher ones.
>
I agree; soft-forking is a useful way of rolling out upgrades, we shouldn't
prohibit it.
--
--
Gavin Andresen
--001a1139a77edbebc7050708e691
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Nov 4, 2014 at 8:29 AM, Pieter Wuille <span dir=3D"ltr"><<a href=3D"=
mailto:pieter.wuille@gmail.com" target=3D"_blank">pieter.wuille@gmail.com</=
a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=3D":yu" clas=
s=3D"a3s" style=3D"overflow:hidden">Luke suggested on the pull request to n=
ot apply this rule on every<br>
transaction with nVersion >=3D 3, which indeed solves the problem. I<br>
believe this can easily be generalized: make the (non mandatory) BIP62<br>
rules only apply to transaction with strict nVersion=3D=3D3, and not to<br>
higher ones.</div></blockquote></div><br>I agree; soft-forking is a useful =
way of rolling out upgrades, we shouldn't prohibit it.<br clear=3D"all"=
><div><br></div>-- <br><div class=3D"gmail_signature">--<br>Gavin Andresen<=
br></div><div class=3D"gmail_signature"><br></div>
</div></div>
--001a1139a77edbebc7050708e691--
|
