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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tier.nolan@gmail.com>) id 1Z6ctB-0001m6-IZ
for bitcoin-development@lists.sourceforge.net;
Sun, 21 Jun 2015 10:54:13 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.175 as permitted sender)
client-ip=209.85.220.175; envelope-from=tier.nolan@gmail.com;
helo=mail-qk0-f175.google.com;
Received: from mail-qk0-f175.google.com ([209.85.220.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z6ctA-0001LV-Lf
for bitcoin-development@lists.sourceforge.net;
Sun, 21 Jun 2015 10:54:13 +0000
Received: by qkhu186 with SMTP id u186so85965811qkh.0
for <bitcoin-development@lists.sourceforge.net>;
Sun, 21 Jun 2015 03:54:07 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.55.26.162 with SMTP id l34mr1573962qkh.21.1434884047252;
Sun, 21 Jun 2015 03:54:07 -0700 (PDT)
Received: by 10.140.85.241 with HTTP; Sun, 21 Jun 2015 03:54:07 -0700 (PDT)
In-Reply-To: <CABm2gDrs6XwG5imH3pFFDB71kx2dSfhR7kjc6Pw8hvDKqGvTPQ@mail.gmail.com>
References: <CABm2gDqPBPiDG1BUAipEsLfyE1VFyvdqdoxtYjkKvGDvBQ8qMg@mail.gmail.com>
<CAE-z3OVM8vwjo_-FOggSoOWR78w=Rmm+GS7Xv9uSK0jdx1_zdw@mail.gmail.com>
<CABm2gDrs6XwG5imH3pFFDB71kx2dSfhR7kjc6Pw8hvDKqGvTPQ@mail.gmail.com>
Date: Sun, 21 Jun 2015 11:54:07 +0100
Message-ID: <CAE-z3OVgQFaFAWUJhDLzyMAE2AXoGHTy0NbUADDAZW9-veX8XA@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11441460ee31e3051904f99b
X-Spam-Score: 0.5 (/)
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
(tier.nolan[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.2 MISSING_HEADERS Missing To: header
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
-0.1 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1Z6ctA-0001LV-Lf
Subject: Re: [Bitcoin-development] [BIP draft] Motivation and deployment of
consensus rules changes ([soft/hard]forks)
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: Sun, 21 Jun 2015 10:54:13 -0000
--001a11441460ee31e3051904f99b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Sun, Jun 21, 2015 at 11:31 AM, Jorge Tim=C3=B3n <jtimon@jtimon.cc> wrote=
:
> You mean the timewarp fix can be coded as a softfork instead of a
> hardfork? How so?
>
The easiest would be a rule requiring that all blocks are within 1 day of
the median of the previous 11 blocks. At the moment, you need to be
greater than that value. This would add a condition at the other end.
It wouldn't be a total fix, but it would protect against the exploit.
A stricter soft fork would be that the two blocks in question have to have
the same timestamp. This would force the off by 1 and the correct value to
give the same result.
If that's the case, do you have a better candidate?
>
I think it is fine, since fixing it "right" does require a hard fork,
especially if it is only to show a non controversial hard fork.
--001a11441460ee31e3051904f99b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
un, Jun 21, 2015 at 11:31 AM, Jorge Tim=C3=B3n <span dir=3D"ltr"><<a hre=
f=3D"mailto:jtimon@jtimon.cc" target=3D"_blank">jtimon@jtimon.cc</a>></s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><span>
</span>You mean the timewarp fix can be coded as a softfork instead of a<br=
>
hardfork? How so?<br></blockquote><div><br></div><div>The easiest would be =
a rule requiring that all blocks are within 1 day of the median of the prev=
ious 11 blocks.=C2=A0 At the moment, you need to be greater than that value=
.=C2=A0 This would add a condition at the other end.<br><br></div><div>It w=
ouldn't be a total fix, but it would protect against the exploit.<br><b=
r></div><div>A stricter soft fork would be that the two blocks in question =
have to have the same timestamp.=C2=A0 This would force the off by 1 and th=
e correct value to give the same result.<br></div><div><br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
If that's the case, do you have a better candidate?<br>
</blockquote></div><br></div><div class=3D"gmail_extra">I think it is fine,=
since fixing it "right" does require a hard fork, especially if =
it is only to show a non controversial hard fork.<br></div></div>
--001a11441460ee31e3051904f99b--
|
