summaryrefslogtreecommitdiff
path: root/6e/eef3c200a9dad5e0a02673dbab18aa9ef357c0
blob: fd57b49a4f7eba5ae747f11f2e1435863ff179c2 (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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <insecurity@national.shitposting.agency>)
	id 1YrlbE-0006yl-R8 for bitcoin-development@lists.sourceforge.net;
	Mon, 11 May 2015 11:10:16 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of
	national.shitposting.agency designates 75.102.27.230 as
	permitted sender) client-ip=75.102.27.230;
	envelope-from=insecurity@national.shitposting.agency;
	helo=mail.cock.li; 
Received: from cock.li ([75.102.27.230] helo=mail.cock.li)
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1YrlbD-0002ei-1s
	for bitcoin-development@lists.sourceforge.net;
	Mon, 11 May 2015 11:10:16 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 11 May 2015 11:10:09 +0000
From: insecurity@national.shitposting.agency
To: pete@petertodd.org
In-Reply-To: <20150511103402.GA21748@savin.petertodd.org>
References: <55505441.3010906@certimix.com>
	<20150511103402.GA21748@savin.petertodd.org>
Message-ID: <66648462658adebb5e5be7fcba65e670@national.shitposting.agency>
X-Sender: insecurity@national.shitposting.agency
User-Agent: Roundcube Webmail/0.9.5
X-Spam-Score: -1.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 SPF_PASS               SPF: sender matches SPF record
X-Headers-End: 1YrlbD-0002ei-1s
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:10:16 -0000

On 2015-05-11 10:34, Peter Todd wrote:
> How do you see that blacklisting actually being done?

Same way ghash.io was banned from the network when used Finney attacks
against BetCoin Dice.

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.

https://youtu.be/ncPyMUfNyVM?t=20s