Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 209.85.218.54 as permitted sender)
	client-ip=209.85.218.54; envelope-from=jgarzik@bitpay.com;
	helo=mail-oi0-f54.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAPg+sBjrSed4r+8-d2RGBVhbzaXxX+o=qqw2u-2jpF2RUqmEmA@mail.gmail.com>
References: <CAL8tG==LG=xC_DzOaghbGGKab4=UVpGLQV7781pU4wg+WnFdMg@mail.gmail.com>
	<CAPg+sBjqQ66f1Rmhi9HOBYP5BDjBHvTNPpUN-y3o-KX8dXBMhg@mail.gmail.com>
	<557D2571.601@gmail.com>
	<CAL8tG=kEv9AfQM+1Rv+tqBujFEjCp+BsjQ-1s7eJC-usogFFqw@mail.gmail.com>
	<CAPg+sBjrSed4r+8-d2RGBVhbzaXxX+o=qqw2u-2jpF2RUqmEmA@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Mon, 15 Jun 2015 13:15:14 -0400
Message-ID: <CAJHLa0OJg2hC4Ab4Yxy3ekH4WXD9hqHore8+sbF9r1r2SwT_zg@mail.gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=001a113b0a0819505a0518919bc9
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Scaling Bitcoin with Subchains
Precedence: list

--001a113b0a0819505a0518919bc9
Content-Type: text/plain; charset=UTF-8

On Mon, Jun 15, 2015 at 1:09 PM, Pieter Wuille <pieter.wuille@gmail.com>
wrote:

> It's simple: either you care about validation, and you must validate
> everything, or you don't, and you don't validate anything. Sidechains do
> not offer you a useful compromise here, as well as adding huge delays and
> conplexity.
>

As noted to Adam last night - although I agree it adds complexity - side
chains are one solution that will indeed help with scaling long term.
Similar to the graph you see with git repos and merges, having aggregation
chains that arbitrarily fork and then rejoin the main chain are both
feasible and useful.

That code & future is a ways away from production, so doesn't help us
here.  Still, let's not dismiss it as a solution either.

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

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

<div dir=3D"ltr">On Mon, Jun 15, 2015 at 1:09 PM, Pieter Wuille <span dir=
=3D"ltr">&lt;<a href=3D"mailto:pieter.wuille@gmail.com" target=3D"_blank">p=
ieter.wuille@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr">It=
&#39;s simple: either you care about validation, and you must validate ever=
ything, or you don&#39;t, and you don&#39;t validate anything. Sidechains d=
o not offer you a useful compromise here, as well as adding huge delays and=
 conplexity.</p></blockquote></div><div class=3D"gmail_extra"><br></div>As =
noted to Adam last night - although I agree it adds complexity - side chain=
s are one solution that will indeed help with scaling long term.=C2=A0 Simi=
lar to the graph you see with git repos and merges, having aggregation chai=
ns that arbitrarily fork and then rejoin the main chain are both feasible a=
nd useful.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_ex=
tra">That code &amp; future is a ways away from production, so doesn&#39;t =
help us here.=C2=A0 Still, let&#39;s not dismiss it as a solution either.<b=
r clear=3D"all"><div><br></div>-- <br><div class=3D"gmail_signature">Jeff G=
arzik<br>Bitcoin core developer and open source evangelist<br>BitPay, Inc. =
=C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"_blank">https=
://bitpay.com/</a></div>
</div></div>

--001a113b0a0819505a0518919bc9--