summaryrefslogtreecommitdiff
path: root/d2/22207f6ec629a2b61d85660b89dc44b643b21f
blob: acbeb28b0fefcf0fae857bc610ab65ebf83c8c42 (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
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 <eth3rs@gmail.com>) id 1Ya4M2-0001dN-3v
	for bitcoin-development@lists.sourceforge.net;
	Mon, 23 Mar 2015 15:33:26 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.169 as permitted sender)
	client-ip=209.85.212.169; envelope-from=eth3rs@gmail.com;
	helo=mail-wi0-f169.google.com; 
Received: from mail-wi0-f169.google.com ([209.85.212.169])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Ya4M0-0001Al-7V
	for bitcoin-development@lists.sourceforge.net;
	Mon, 23 Mar 2015 15:33:26 +0000
Received: by wibg7 with SMTP id g7so50680888wib.1
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 23 Mar 2015 08:33:18 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.74.47 with SMTP id q15mr20048988wiv.90.1427124798260;
	Mon, 23 Mar 2015 08:33:18 -0700 (PDT)
Received: by 10.180.88.73 with HTTP; Mon, 23 Mar 2015 08:33:18 -0700 (PDT)
Date: Mon, 23 Mar 2015 11:33:18 -0400
Message-ID: <CAEM=y+UYpqUurdQDOZaN958VFKdV3mpYShEYEOnOCL86eLq=Tg@mail.gmail.com>
From: Ethan Heilman <eth3rs@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.6 (-)
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
	(eth3rs[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-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
X-Headers-End: 1Ya4M0-0001Al-7V
Subject: [Bitcoin-development] =?utf-8?q?Research_on_partitioning_Bitcoind?=
	=?utf-8?q?_nodes=3A_=22Eclipse_Attacks_on_Bitcoin=E2=80=99s_Peer-t?=
	=?utf-8?q?o-Peer_Network=22?=
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, 23 Mar 2015 15:33:26 -0000

Hi All,

There has been much discussion lately on the dev list about
misbehaving peers and attacks on the P2P network. We'd like to share
our research on partitioning Bitcoind nodes from the rest of the
network.

Eclipse Attacks on Bitcoin=E2=80=99s Peer-to-Peer Network
Abstract: We present eclipse attacks on bitcoin's peer-to-peer
network. Our attack allows an adversary controlling a sufficient
number of IP addresses to monopolize all connections to and from a
victim bitcoin node. The attacker can then exploit the victim for
attacks on bitcoin's mining and consensus system, including
N-confirmation double spending, selfish mining, and adversarial forks
in the blockchain. We take a detailed look at bitcoin=E2=80=99s peer-to-pee=
r
network, and quantify the resources involved in our attack via
probabilistic analysis, Monte Carlo simulations, measurements and
experiments with live bitcoin nodes. Finally, we present
countermeasures, inspired by botnet architectures, that are designed
to raise the bar for eclipse attacks while preserving the openness and
decentralization of bitcoin=E2=80=99s current network architecture.

Full paper available here:
http://cs-people.bu.edu/heilman/eclipse/

Thanks,
Ethan