Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed;
	boundary="Apple-Mail=_41289139-49EF-4329-A8B9-CB3E57DF4011";
	protocol="application/pgp-signature"; micalg=pgp-sha512
From: Eric Lombrozo <elombrozo@gmail.com>
In-Reply-To: <DA1298CE-1C3B-4153-A72D-A0F89D6F1833@mac.com>
Date: Thu, 23 Jul 2015 11:21:25 -0700
Message-Id: <C7DED50B-0881-4015-8BA6-EAE30EDFB7C5@gmail.com>
References: <CAPg+sBgs-ouEMu=LOVCmOyCGwfM1Ygxooz0shyvAuHDGGZYfJw@mail.gmail.com>
	<CAPg+sBgugLSVEwDLXhgey86_rM2fTjGWXFuXsiZioJKCZiHiNg@mail.gmail.com>
	<CADm_WcbnQQGZoQ92twfUvbzqGwu__xLn+BYOkHPZY_YT1pFrbA@mail.gmail.com>
	<CAPWm=eW8RgrG1CMEAMN4GeiMjZecFvNtZB_Y4rZNeofWSD0=Wg@mail.gmail.com>
	<CADm_WcYCUHs9Qe_T6WJOCUSK6stXYD8v6z5JcGHfRMURoOSFTA@mail.gmail.com>
	<CABm2gDq3JyZx0QCRDbcNSLSOBKdpi4h_7VN1XL8N42U38+eBAA@mail.gmail.com>
	<55B113AF.40500@thinlink.com>
	<CABsx9T1MTc-GmuQyFN1vaFK=CDWV_L214Pi9nR6jLMouQQD0fw@mail.gmail.com>
	<trinity-f82ce2cb-7260-4b58-a577-9a1b6afad214-1437670245144@3capp-mailcom-bs02>
	<DA1298CE-1C3B-4153-A72D-A0F89D6F1833@mac.com>
To: Robert Learney <robertlearney@mac.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Core and hard forks
Precedence: list


--Apple-Mail=_41289139-49EF-4329-A8B9-CB3E57DF4011
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_7BA288CB-7143-4C2D-BDF5-8B3F2B93485A"


--Apple-Mail=_7BA288CB-7143-4C2D-BDF5-8B3F2B93485A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Jul 23, 2015, at 10:14 AM, Robert Learney via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>=20
> That=E2=80=99s not exactly what=E2=80=99s happened though, is it =
Cipher? Gavin put forward 20Mb then after analysis and discussion has =
moved to 8Mb, whereas the other camp of core developers is firmly stuck =
in the =E2=80=981Mb or bust=E2=80=99 group.

The issue isn=E2=80=99t really whether it=E2=80=99s 1MB or 2MB or 4MB or =
8MB or whatever. First of all, the burden of justifying this change =
should be on those proposing a hardfork. The default is to not have a =
hard fork. Second of all, it=E2=80=99s not really about *whether* the =
block size is increased=E2=80=A6but about *when* and *how* it is =
increased. There=E2=80=99s a good argument to be made that right now it =
is more important to address issues such as the fact that validation is =
so expensive (which as others and myself have pointed out has led to a =
collapse of the security model in the past, requiring manual =
intervention to temporarily =E2=80=9Cfix=E2=80=9D)=E2=80=A6and the fact =
that we don=E2=80=99t yet have great solutions to dealing with fees, =
which are a crucial component of the design of the protocol.

--Apple-Mail=_7BA288CB-7143-4C2D-BDF5-8B3F2B93485A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jul 23, 2015, at 10:14 AM, Robert Learney via bitcoin-dev =
&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" =
class=3D"">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">That=E2=80=99s not exactly what=E2=80=99s =
happened though, is it Cipher? Gavin put forward 20Mb then after =
analysis and discussion has moved to 8Mb, whereas the other camp of core =
developers is firmly stuck in the =E2=80=981Mb or bust=E2=80=99 =
group.</span></div></blockquote></div><br class=3D""><div class=3D"">The =
issue isn=E2=80=99t really whether it=E2=80=99s 1MB or 2MB or 4MB or 8MB =
or whatever. First of all, the burden of justifying this change should =
be on those proposing a hardfork. The default is to not have a hard =
fork. Second of all, it=E2=80=99s not really about *whether* the block =
size is increased=E2=80=A6but about *when* and *how* it is increased. =
There=E2=80=99s a good argument to be made that right now it is more =
important to address issues such as the fact that validation is so =
expensive (which as others and myself have pointed out has led to a =
collapse of the security model in the past, requiring manual =
intervention to temporarily =E2=80=9Cfix=E2=80=9D)=E2=80=A6and the fact =
that we don=E2=80=99t yet have great solutions to dealing with fees, =
which are a crucial component of the design of the =
protocol.</div></body></html>=

--Apple-Mail=_7BA288CB-7143-4C2D-BDF5-8B3F2B93485A--

--Apple-Mail=_41289139-49EF-4329-A8B9-CB3E57DF4011
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJVsTClAAoJEJNAI64YFENUDSIP/1lGC3/ao2x317NFNC2OJ3Ns
2hDVmWvEkv8VSSEMpZC4TO1Esi/Mq2B9E67KsxpxHhRFxiekbG8+ag7s5lxMIzQQ
IeSAmCgQ7w0pS7uQ8ucHeZ7GLXBzJ/FxOIepSCX4wl54q0/ZFi8x17WJhZiyrOif
3jCJfzeDa7ereiJ/Jperp2Ok/IQ/kXrOovEPJCwcwMTo5U4arX3qXRXPuXH64jXu
VU7DQa9ocUHXZWMETadlrogAXXGtanOGITBefWkgSh+ew9tPSRIwG1uFeLHWuvHH
41zuADlMl+Z/I+R/gyyJhQ2VDB0d7DaSDZpIOB62gJvVgZEY3pfuuGBvjuDnPbNp
Zbelb8NHPq3Npr2PPBuYxvbMCmL64Us0K+WawaDo0iezFx9/dy4R8qgtvAWf0j0Z
nwb1F1NPcgNVnygvEwFDNPiY+0IPD2lEfiymPVJ5iSRLX0iBltKJ2feF/LDdXEjr
cNuc3PCVIewH1uXkXK1aa0YHa0Y7pcuurwVUy3Xt6Q/cU8czZqA0mBS4D+DMI/Xx
T7WlVxjbeGzvlZDFIFvfo6MdU8rBGApv9rPWYZ306Yw7Ac4JJC2ISLnsK11e3asC
Puwv6YApfOGZKe7FEk6BI3tEZsql7aC24KzToFbGESMfTJoyE2KCm7YmqtO9kx7E
1EJEFJ3VgocUrzNSOYXq
=65tZ
-----END PGP SIGNATURE-----

--Apple-Mail=_41289139-49EF-4329-A8B9-CB3E57DF4011--