Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.77 as permitted sender)
	client-ip=62.13.149.77; envelope-from=pete@petertodd.org;
	helo=outmail149077.authsmtp.com; 
Date: Sun, 18 Aug 2013 21:34:37 -0400
From: Peter Todd <pete@petertodd.org>
To: Gavin Andresen <gavinandresen@gmail.com>
Message-ID: <20130819013437.GA21524@savin>
References: <20130819001357.GA4281@savin>
	<CABsx9T3MFqmLchc1Uu20BhiVKsYWFtt0eneVSey846y2hdQ7Rg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw"
Content-Disposition: inline
In-Reply-To: <CABsx9T3MFqmLchc1Uu20BhiVKsYWFtt0eneVSey846y2hdQ7Rg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bloom io attack effectiveness
Precedence: list


--GvXjxJ+pjyke8COw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 19, 2013 at 10:59:18AM +1000, Gavin Andresen wrote:
> Peter said:
> "In any case given that SPV peers don't contribute back to the network
> they should obviously be heavily deprioritized and served only with
> whatever resources a node has spare."
>=20
> This seems very much like a "cut off your nose to spite your face" soluti=
on.
>=20
> SPV peers are INCREDIBLY IMPORTANT to the growth of Bitcoin; much more
> important than nodes that have the bandwidth and disk I/O capability of
> being a full node.  Bitcoin will be just fine if there are never more than
> 10,000 big, beefy, full nodes forming the backbone of the network, but wi=
ll
> be NOTHING if we don't support tens of millions of lightweight SPV device=
s.
>=20
> Ok, that's an exaggeration, Bitcoin would be just fine in an Electrum mod=
el
> where tens of millions of lightweight devices rely 100% on a full node to
> operate. But I would prefer the more decentralized, less-trust-required S=
PV
> model.

Don't read too much into what I said; under normal circumstances when a
Bitcoin node isn't being attacked, there will be plenty of spare
capacity for SPV nodes. All I'm suggesting is that we make sure serving
those nodes doesn't come at the expense of maintaining consensus -
mainly distributing new blocks around the network so the blockchain
keeps moving forward. (something many SPV peers can help with anyway)

I'd much rather my Android wallet take a long time to sync up, than
blocks get re-organized because miners found themselves separated from
one another, let along someone clever using that to do double-spend
attacks during those re-orgs. After all, I can always find a private
node to connect to that won't be overloaded because it doesn't accept
connections from anonymous users. It's also easy to just use really
basic measures to limit abuse, like "sign up with your bitcointalk"
account, or "pay 10 cents for an account to discourage spammers"

Anyway all things less likely to be needed if attackers know all they
are going to manage to do is inconvenience people temporarily because
the network itself will keep running.

--=20
'peter'[:-1]@petertodd.org

--GvXjxJ+pjyke8COw
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBCAAGBQJSEXYtAAoJECSBQD2l8JH7lzcIALAY0o1yZ4JZcj/JmbaODrsW
96b4NGYv/4cMltqhPijuKn23MIvuG7JjaNu9f4J6Bmt5jOSnIyVPz5XZzsjWD3EW
IFFGZ3GYg5C5Dwp7Yf4l40WCGkm+gQWO2Vs+RF/inpdorYNuOkMoMhUk52ki5Qu0
r0XO29sLEH8LtQNCEem6OfzVadSnCdEQysOI4UIJmQQfclPjrqpFcthqAczgJCrp
dEq48M1ZuBtBuMSWFHx2HEAPaJEdp0ut9+1jhod+PtYb6HcHgmPQ3U00j9ymcUgX
yn3xTA7Wfz+5NMAs/jybLC4Sz/PivZNCCh7jx1DUObsXYe/3mZ+KOBSxhK3ywgc=
=R7RY
-----END PGP SIGNATURE-----

--GvXjxJ+pjyke8COw--