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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tier.nolan@gmail.com>) id 1Z3KSp-0004E7-8V
for bitcoin-development@lists.sourceforge.net;
Fri, 12 Jun 2015 08:37:23 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.178 as permitted sender)
client-ip=209.85.220.178; envelope-from=tier.nolan@gmail.com;
helo=mail-qk0-f178.google.com;
Received: from mail-qk0-f178.google.com ([209.85.220.178])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z3KSo-00030Z-Hi
for bitcoin-development@lists.sourceforge.net;
Fri, 12 Jun 2015 08:37:23 +0000
Received: by qkhg32 with SMTP id g32so14333229qkh.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 12 Jun 2015 01:37:17 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.55.19.82 with SMTP id d79mr28104184qkh.21.1434098237107;
Fri, 12 Jun 2015 01:37:17 -0700 (PDT)
Received: by 10.140.85.241 with HTTP; Fri, 12 Jun 2015 01:37:17 -0700 (PDT)
In-Reply-To: <20150612004058.GA14749@muck>
References: <20150612004058.GA14749@muck>
Date: Fri, 12 Jun 2015 09:37:17 +0100
Message-ID: <CAE-z3OXMp6494BXeD0FcKPSriHHr+F6grH=tdhk45Ni1+FQ6ZQ@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a114008caff10d205184e03d5
X-Spam-Score: 3.3 (+++)
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
2.7 MALFORMED_FREEMAIL Bad headers on message from free email service
X-Headers-End: 1Z3KSo-00030Z-Hi
Subject: Re: [Bitcoin-development] Miners: You'll (very likely) need to
upgrade your Bitcoin Core node soon to support BIP66
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: Fri, 12 Jun 2015 08:37:23 -0000
--001a114008caff10d205184e03d5
Content-Type: text/plain; charset=UTF-8
Once the 75% threshold is reached, miners who haven't updated are at risk
of mining on invalid blocks.
If someone produces a version 3 block that violates the new rules, then
miners who haven't upgraded will end up wasting mining power building on
that block.
This could be used as an expensive way to attack miners who haven't
upgraded. It is low risk of happening, since creating an invalid version 3
block costs 25BTC in hashing power and the miner who does it ends up
creating an invalid block.
--001a114008caff10d205184e03d5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div>Once the 75% threshold is reached, miners who ha=
ven't updated are at risk of mining on invalid blocks.<br><br></div>If =
someone produces a version 3 block that violates the new rules, then miners=
who haven't upgraded will end up wasting mining power building on that=
block.<br><br></div>This could be used as an expensive way to attack miner=
s who haven't upgraded.=C2=A0 It is low risk of happening, since creati=
ng an invalid version 3 block costs 25BTC in hashing power and the miner wh=
o does it ends up creating an invalid block.<br></div>
--001a114008caff10d205184e03d5--
|
