Date: Sat, 6 Feb 2016 17:22:21 -0500
From: Peter Todd <pete@petertodd.org>
To: Gavin Andresen <gavinandresen@gmail.com>
Message-ID: <20160206222221.GA12092@muck>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/"
Content-Disposition: inline
In-Reply-To: <CABsx9T2AUwDdz3JowpQYeusDgCBwfNFCDz0Kfut9ffT6gSaGeQ@mail.gmail.com>
	<CABsx9T2LuMZciXpMiY24+rPzhj1VT6j=HJ5STtnQmnfnA_XFUw@mail.gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP proposal: Increase block size limit to 2
 megabytes
Precedence: list


--TB36FDmn/VVEgNH/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 06, 2016 at 10:37:30AM -0500, Gavin Andresen via bitcoin-dev wr=
ote:
> 2) People are committing to spinning up thousands of supports-2mb-nodes
> during the grace period.

Why wouldn't an attacker be able to counter-sybil-attack that effort?

Who are these people?


On Sat, Feb 06, 2016 at 12:45:14PM -0500, Gavin Andresen via bitcoin-dev wr=
ote:
> Would Blockstream be willing to help out by running a dozen or two extra
> full nodes?

I'll remind everyone that Bitcoin Core does not condone participation in
network attacks to push controversial protcol changes through. I also
checked with Adam Back, who confirmed Blockstream as a company shares
those views.


For those readers unfamiliar with Sybil attacks, basically what the
above does is prevents nodes from being able to finding peers with
accurate information about what blockchains exist - the above can be
used to prevent nodes from learning about the longest chain for
instance, or the existance of substantial support for a minority chain.
This is why we've advocated giving users sufficient time to actively
opt-in to protocol changes.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
000000000000000008320874843f282f554aa2436290642fcfa81e5a01d78698

--TB36FDmn/VVEgNH/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQGrBAEBCACVBQJWtnIaXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwODMyMDg3NDg0M2YyODJmNTU0YWEyNDM2MjkwNjQyZmNm
YTgxZTVhMDFkNzg2OTgvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udz2xwf/SPxpCi+ItFDN6LDframY78Kx
DJvXCSCOLrvXZNAaEa3yT5m9yMQg4/lUGINAWtVE8Qtm/KUQjozMciRgZcbioP8Z
i1Q8AhSoZmVysXUuz88CGTRrto0rb+MK045HQelbS4A/2xy9bAC1WXwT/GfohNJk
yM07otAAQUy7RYiFX9xFu4Lf/O61EFEUMGI89tve38cMyBkEZcunOfysTS1kXvJc
PJ13Tpck3QhSu0mNHTA+d++4YRpN0g2ay/BDVo6+/rEJbpNsy433qW8j0U3zmHXy
WIrF4+Fsy+cnjKJnOC+vdOLNFqI92FfnHvMfsWLiP4nh3QUSbFWFY86um1VeSA==
=urXf
-----END PGP SIGNATURE-----

--TB36FDmn/VVEgNH/--