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; 
MIME-Version: 1.0
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
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?=
Precedence: list

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