summaryrefslogtreecommitdiff
path: root/46/42fff6200f750df883ce6d9991b33a353515b4
blob: 227ac9cce3c8eb4e8d7d08e073455c28d80f26c1 (plain)
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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <dave@hashingit.com>) id 1YrmCw-0006AU-Kp
	for bitcoin-development@lists.sourceforge.net;
	Mon, 11 May 2015 11:49:14 +0000
Received-SPF: softfail (sog-mx-2.v43.ch3.sourceforge.com: transitioning domain
	of hashingit.com does not designate 89.145.69.228 as permitted
	sender) client-ip=89.145.69.228;
	envelope-from=dave@hashingit.com; helo=heron.directrouter.co.uk;
Received: from heron.directrouter.co.uk ([89.145.69.228])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1YrmCu-0001x4-OI
	for bitcoin-development@lists.sourceforge.net;
	Mon, 11 May 2015 11:49:14 +0000
Received: from host109-155-54-156.range109-155.btcentralplus.com
	([109.155.54.156]:55488 helo=[192.168.1.82])
	by heron.directrouter.co.uk with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256)
	(Exim 4.85) (envelope-from <dave@hashingit.com>)
	id 1YrmCn-001wYZ-6J; Mon, 11 May 2015 11:49:05 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Dave Hudson <dave@hashingit.com>
In-Reply-To: <66648462658adebb5e5be7fcba65e670@national.shitposting.agency>
Date: Mon, 11 May 2015 12:49:03 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF13D23D-1F04-4970-A80A-4892374E5247@hashingit.com>
References: <55505441.3010906@certimix.com>
	<20150511103402.GA21748@savin.petertodd.org>
	<66648462658adebb5e5be7fcba65e670@national.shitposting.agency>
To: insecurity@national.shitposting.agency
X-Mailer: Apple Mail (2.2098)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - heron.directrouter.co.uk
X-AntiAbuse: Original Domain - lists.sourceforge.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - hashingit.com
X-Get-Message-Sender-Via: heron.directrouter.co.uk: authenticated_id:
	dave@hashingit.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 1.5 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	1.0 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail)
	0.5 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YrmCu-0001x4-OI
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Reducing the block rate instead of
	increasing the maximum block size
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, 11 May 2015 11:49:14 -0000


> On 11 May 2015, at 12:10, insecurity@national.shitposting.agency =
wrote:
>=20
> On 2015-05-11 10:34, Peter Todd wrote:
>> How do you see that blacklisting actually being done?
>=20
> Same way ghash.io was banned from the network when used Finney attacks
> against BetCoin Dice.
>=20
> As Andreas Antonopoulos says, if any of the miners do anything bad, we
> just ban them from mining. Any sort of attack like this only lasts 10
> minutes as a result. Stop worrying so much.

This doesn't work because a large-scale miner can trivially make =
themselves look like a very large number of much smaller scale miners. =
Their ability to minimize variance comes from the cumulative totals they =
control so 10 pools of 1% of the network cumulatively have the same =
variance as 1 pool with 10% of the network. It's also very easy for =
miners to relay blocks via different addresses and the cost is minimal. =
The biggest cost would be in DDoS prevention and a miner that actually =
split their pool into lots of small fragments would actually give =
themselves the ability to do quite a lot of DDoS mitigation anyway. If =
no-one is doing this right now it's simply because they've not had the =
right incentives to make it worthwhile; if the incentives make it =
worthwhile then this is pretty trivial to do.

This is one area where anonymity on behalf of transaction validators and =
block makers essentially makes it pretty-much impossible to maintain any =
sort of sanctions against antisocial behaviour.=