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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <daryl@daryltucker.com>) id 1UPBWn-0003Zc-NR
for bitcoin-development@lists.sourceforge.net;
Mon, 08 Apr 2013 12:50:29 +0000
X-ACL-Warn:
Received: from 50-56-76-114.static.cloud-ips.com ([50.56.76.114]
helo=neoretro.net)
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1UPBWj-0000Tm-3q
for bitcoin-development@lists.sourceforge.net;
Mon, 08 Apr 2013 12:50:29 +0000
Received: from [10.1.1.115] (ip98-162-173-107.pn.at.cox.net [98.162.173.107])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by neoretro.net (Postfix) with ESMTPSA id 314E28585F
for <bitcoin-development@lists.sourceforge.net>;
Mon, 8 Apr 2013 07:32:33 -0500 (CDT)
Message-ID: <5162B8DE.2030708@daryltucker.com>
Date: Mon, 08 Apr 2013 07:32:30 -0500
From: Daryl Tucker <daryl@daryltucker.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CAKaEYhLqnzrhdJNTSBccDA68Mb-hUnaZaCa9Gn43FuVpa410sg@mail.gmail.com>
<CANEZrP3S7b+uh2LW4vH=53opopLJRmmJ-_Uad6yEQxZ3kHW47A@mail.gmail.com>
<CAKaEYhJ9-ksVXFhnzNvWHR2QoPc72uzesvsxn7ryebvt6+zxJg@mail.gmail.com>
<20130405121251.GA18254@savin>
In-Reply-To: <20130405121251.GA18254@savin>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 TVD_RCVD_IP TVD_RCVD_IP
X-Headers-End: 1UPBWj-0000Tm-3q
Subject: Re: [Bitcoin-development] A mining pool at 46%
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: Mon, 08 Apr 2013 12:50:30 -0000
BTC Guild's response:
51% Mitigation Plan
I want to start by thanking all users, new and old, for making BTC
Guild become what it is today. I never expected a service that
originally started on a mining PC in my dining room in April 2011 to
go this far.
However, recently BTC Guild has started to become "too big". Users of
Bitcoin are becoming scared that BTC Guild, either directly or through
hacking/coercion, could be used to attack the network as it gets
closer to 51% of the network. If this were to happen, it is likely
many people would lose confidence in Bitcoin, as a single entity could
control the network if it wanted to do so.
I have put forward a proposal of my plans on how to mitigate this
threat, but unfortunately nothing can be done without users taking
some initiative as well. The following are the actions that will be
taken if certain thresholds are crossed:
More than 40% of the Network [last 2016 blocks]
PPS fee will be raised from 5% to 7% on all new accounts. Old accounts
will also be increased (PPS ONLY) to 7% after a difficulty change. If
the pool eventually drops back under 40% for more than 72 hours, these
fees will be turned back down to 5% after the next difficulty change.
More than 45% of the Network [last 2016 blocks]
Getwork based pools will be completely removed within 24 hours. All
users on getwork have been warned in the past that it is a unsupported
and not advised method of connecting. This should remove ~15% of BTC
Guild's hash rate immediately.
More than 40% of the Network again [last 2016 blocks]
PPLNS fee will be raised from 3% to 4% after a 72 hour warning. This
fee will be reduced back to 3% once the pool drops back under 40% for
more than 72 hours.
If you have questions or comments, please leave them on the forum
thread related to this issue:
https://bitcointalk.org/index.php?topic=168108.0
https://www.btcguild.com/index.php?page=home
On 04/05/2013 07:12 AM, Peter Todd wrote:
> On Fri, Apr 05, 2013 at 12:13:23PM +0200, Melvin Carvalho wrote:
>> Totally see the logic of this, and it makes sense. But I dont
>> think the only risk is in terms of double spend, but rather
>>
>> 1) vandalize the block chain which may be difficult to unwind?
>
> Vandalize the chain how? By delibrately triggering bugs? (like the
> old OP_CHECKSIG abuse problem) Regardless of whether or not the
> vulnerability requires multiple blocks in a row, the underlying
> problem should be fixed.
>
> By putting illegal data into it? Fundementally we have no way to
> prevent people from doing that other than by making it expensive.
> An attacker having a lot of hashing power just means they can do so
> faster and a bit cheaper.
>
>
>
> ------------------------------------------------------------------------------
>
>
Minimize network downtime and maximize team effectiveness.
> Reduce network management and security costs.Learn how to hire the
> most talented Cisco Certified professionals. Visit the Employer
> Resources Portal
> http://www.cisco.com/web/learning/employer_resources/index.html
>
>
>
> _______________________________________________ Bitcoin-development
> mailing list Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Daryl Tucker
daryl@daryltucker.com
|
