Date: Tue, 23 Jun 2015 15:28:38 -0400
From: Peter Todd <pete@petertodd.org>
To: Gavin Andresen <gavinandresen@gmail.com>
Message-ID: <20150623192838.GG30235@muck>
References: <CABsx9T2HegqOBqd1jijk1bZBE6N+NH8x6nfwbaoLBACVf8-WBQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="eVzOFob/8UvintSX"
Content-Disposition: inline
In-Reply-To: <CABsx9T2HegqOBqd1jijk1bZBE6N+NH8x6nfwbaoLBACVf8-WBQ@mail.gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Draft BIP : fixed-schedule block size increase
Precedence: list


--eVzOFob/8UvintSX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 22, 2015 at 02:18:19PM -0400, Gavin Andresen wrote:
> =3D=3DRationale=3D=3D
>=20
> The initial size of 8,000,000 bytes was chosen after testing the current
> reference implementation code with larger block sizes and receiving
> feedback from miners stuck behind bandwidth-constrained networks (in
> particular, Chinese miners behind the Great Firewall of China).
>=20
> The doubling interval was chosen based on long-term growth trends for CPU
> power, storage, and Internet bandwidth. The 20-year limit was chosen
> because exponential growth cannot continue forever.

Wladimir noted that 'The original presented intention of block size
increase was a one-time "scaling" to grant time for more decentralizing
solutions to develop'

Comments?

In particular, if bandwidth scaling doesn't go according to your plan,
e.g. the exponential exponent is too large, perhaps due to technological
growth not keeping pace, or the political realities of actual bandwidth
deployment making theoretical technological growth irrelevant, what
mechanism will prevent centralization? (if any)

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

--eVzOFob/8UvintSX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

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

iQGrBAEBCACVBQJVibNjXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwOGMwYmUxNmUxNTJmODZhYjNhMjcxYTEzYzNmNDFjNTYy
MjhkNzI5OTBhYmY3YmQvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udx3Nwf+P7rvhuIjCxcIVqomoJrcev2p
rbNywwk7GfiUEe10EPafJJfdozkKRIRj8IkHpVQ6QSUCyQgk1XRu2bL/rwIZfWXX
HCqRDYtWezcm7SLhdnyxihk66uvZ5QvmDfi3WBKFriJUruHVipW5DYS4rACVO1S7
P75GYJcukOIBFwNqIOG+CMK4s0E24xk6XEJysMKN3qXU3raVPAd7dpRFcsJMHBqp
0sFbyrI/t15nL3sHwIUfTztCNRxqzOEh6JIeJr/Eq7GIgJPh8QsQ5I+j+Uodv8t9
/XI1VbnIQ4KrtBVUqtckAjs8mQs8mwvYWr6sBIqavpgBHh9hzOW71J1II0vhxw==
=PMMc
-----END PGP SIGNATURE-----

--eVzOFob/8UvintSX--