Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 209.85.214.177 as permitted sender)
	client-ip=209.85.214.177; envelope-from=jgarzik@bitpay.com;
	helo=mail-ob0-f177.google.com; 
MIME-Version: 1.0
In-Reply-To: <554C1410.7050406@thinlink.com>
References: <554A91BE.6060105@bluematt.me>
	<CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>
	<CABm2gDpDvk2VsQ+mJ-BoeBKmvu9jBXNujZEFKuCStRNjFL6VOA@mail.gmail.com>
	<CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com>
	<CABm2gDqd6iHRUDKZWWTudcC1QkYa+rCuHjz7pMC2K1Db8wpgfA@mail.gmail.com>
	<CANEZrP1CU0kB0vXeXUX1L8byaT-Zf2xg+3N+GeNthi_i6bn1qw@mail.gmail.com>
	<CABsx9T2Nxvr4fqREMw3_LXftzsxrUAR1+9sVMa8_EpTnH1nN1Q@mail.gmail.com>
	<554BA032.4040405@bluematt.me>
	<CANEZrP3yM9wsSPNgpOsXDk-DjUy5PW2XuRTvK2AyCNbVJ5hZHw@mail.gmail.com>
	<CADJgMzti7ROH90APiwg4NOAT5+Av=4i295b8VN0sbSLr4+WWRw@mail.gmail.com>
	<CANEZrP39jWHLF02z-81Z4+9X1vH5+hMuS=-3ED81=Q1o9U=DKw@mail.gmail.com>
	<554BBDA2.7040508@gmail.com>
	<CAJHLa0NcxOHkrtW2=-JgfsXQJkCO8Ym7icBwMx_2RsaWcPBnTw@mail.gmail.com>
	<554C1410.7050406@thinlink.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Thu, 7 May 2015 22:09:42 -0400
Message-ID: <CAJHLa0PeEd19ooHbOHUMxX9-5=iyUng-9GWnQFOn_F3aXxVWLQ@mail.gmail.com>
To: Tom Harding <tomh@thinlink.com>
Content-Type: multipart/alternative; boundary=089e0160cf38b55efd0515888653
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Block Size Increase
Precedence: list

--089e0160cf38b55efd0515888653
Content-Type: text/plain; charset=UTF-8

On Thu, May 7, 2015 at 9:40 PM, Tom Harding <tomh@thinlink.com> wrote:

> On 5/7/2015 12:54 PM, Jeff Garzik wrote:
> > 2) Where do you want to go?  Should bitcoin scale up to handle all the
> > world's coffees?
>
> Alan was very clear.  Right now, he wants to go exactly where Gavin's
> concrete proposal suggests.
>

G proposed 20MB blocks, AFAIK - 140 tps
A proposed 100MB blocks - 700 tps
For ref,
Paypal is around 115 tps
VISA is around 2000 tps (perhaps 4000 tps peak)

I ask again:  where do we want to go?   This is the existential question
behind block size.

Are we trying to build a system that can handle Paypal volumes?  VISA
volumes?

It's not a snarky or sarcastic question:  Are we building a system to
handle all the world's coffees?  Is bitcoin's main chain and network -
Layer 1 - going to receive direct connections from 500m mobile phones,
broadcasting transactions?

We must answer these questions to inform the change being discussed today,
in order to decide what makes the most sense as a new limit.  Any
responsible project of this magnitude must have a better story than "zomg
1MB, therefore I picked 20MB out of a hat"  Must be able to answer /why/
the new limit was picked.

As G notes, changing the block size is simply kicking the can down the
road: http://gavinandresen.ninja/it-must-be-done-but-is-not-a-panacea
Necessarily one must ask, today, what happens when we get to the end of
that newly paved road.

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/

--089e0160cf38b55efd0515888653
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, May 7, 2015 at 9:40 PM, Tom Harding <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:tomh@thinlink.com" target=3D"_blank">tomh@thinlink.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"=
">On 5/7/2015 12:54 PM, Jeff Garzik wrote:<br>
</span><span class=3D"">&gt; 2) Where do you want to go?=C2=A0 Should bitco=
in scale up to handle all the<br>
&gt; world&#39;s coffees?<br>
<br>
</span>Alan was very clear.=C2=A0 Right now, he wants to go exactly where G=
avin&#39;s<br>
concrete proposal suggests.<br></blockquote></div><br></div><div class=3D"g=
mail_extra">G proposed 20MB blocks, AFAIK - 140 tps<br></div><div class=3D"=
gmail_extra">A proposed 100MB blocks - 700 tps<br></div><div class=3D"gmail=
_extra">For ref,<br></div><div class=3D"gmail_extra">Paypal is around 115 t=
ps<br></div><div class=3D"gmail_extra">VISA is around 2000 tps (perhaps 400=
0 tps peak)<br><br></div><div class=3D"gmail_extra">I ask again:=C2=A0 wher=
e do we want to go?=C2=A0=C2=A0 This is the existential question behind blo=
ck size.<br><br></div><div class=3D"gmail_extra">Are we trying to build a s=
ystem that can handle Paypal volumes?=C2=A0 VISA volumes?<br><br></div><div=
 class=3D"gmail_extra">It&#39;s not a snarky or sarcastic question:=C2=A0 A=
re we building a system to handle all the world&#39;s coffees?=C2=A0 Is bit=
coin&#39;s main chain and network - Layer 1 - going to receive direct conne=
ctions from 500m mobile phones, broadcasting transactions?<br><br></div><di=
v class=3D"gmail_extra">We must answer these questions to inform the change=
 being discussed today, in order to decide what makes the most sense as a n=
ew limit.=C2=A0 Any responsible project of this magnitude must have a bette=
r story than &quot;zomg 1MB, therefore I picked 20MB out of a hat&quot;=C2=
=A0 Must be able to answer /why/ the new limit was picked.<br><br></div><di=
v class=3D"gmail_extra">As G notes, changing the block size is simply kicki=
ng the can down the road: <a href=3D"http://gavinandresen.ninja/it-must-be-=
done-but-is-not-a-panacea">http://gavinandresen.ninja/it-must-be-done-but-i=
s-not-a-panacea</a>=C2=A0=C2=A0 Necessarily one must ask, today, what happe=
ns when we get to the end of that newly paved road.<br></div><div class=3D"=
gmail_extra"><br></div><div class=3D"gmail_extra">-- <br><div class=3D"gmai=
l_signature">Jeff Garzik<br>Bitcoin core developer and open source evangeli=
st<br>BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" targ=
et=3D"_blank">https://bitpay.com/</a></div>
</div></div>

--089e0160cf38b55efd0515888653--