Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z4vQl-0007Ap-Ub for bitcoin-development@lists.sourceforge.net; Tue, 16 Jun 2015 18:17:51 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.148.102 as permitted sender) client-ip=62.13.148.102; envelope-from=pete@petertodd.org; helo=outmail148102.authsmtp.net; Received: from outmail148102.authsmtp.net ([62.13.148.102]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Z4vQk-0005hH-Qe for bitcoin-development@lists.sourceforge.net; Tue, 16 Jun 2015 18:17:51 +0000 Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) by punt16.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5GIHdWL046669; Tue, 16 Jun 2015 19:17:39 +0100 (BST) Received: from muck ([212.183.128.96]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5GIHXZs012852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 16 Jun 2015 19:17:35 +0100 (BST) Date: Tue, 16 Jun 2015 19:17:24 +0100 From: Peter Todd To: Jeff Garzik Message-ID: <20150616181724.GA4055@muck> References: <557D2571.601@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH" Content-Disposition: inline In-Reply-To: X-Server-Quench: f6cfe6be-1453-11e5-b396-002590a15da7 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdwQUEkAaAgsB AmMbWl1eUVp7WmU7 aQtTcwRVYVRPXQ10 WU5WR1pVCwQmRRl2 f2Z2OFpydgdOfXw+ ZENiWHgVCkIpIxN7 EBtJFGkDZnphaTUa TRJbfgVJcANIexZF O1F6ACIKLwdSbGoL NQ4vNDcwO3BTJTpY RgYVKF8UXXNDJTU1 QxEEEn0FHFEOQCQ1 ZwMnNl5UJ1sbOUU7 MF06Mf9/ X-Authentic-SMTP: 61633532353630.1023:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 212.183.128.96/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1Z4vQk-0005hH-Qe Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Scaling Bitcoin with Subchains X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jun 2015 18:17:52 -0000 --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 15, 2015 at 01:15:14PM -0400, Jeff Garzik wrote: > On Mon, Jun 15, 2015 at 1:09 PM, Pieter Wuille > wrote: >=20 > > 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 a= nd > > conplexity. > > >=20 > 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. >=20 > 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. To be clear, it depends on what kind of sidechain. My off-chain transaction notions are federated sidechains with an economic incentive to not commit fraud using fidelity bonds; they were definitely proposed as a scaling solution. Merge-mined sidechains are not a scaling solution any more than SPV is a scaling solution because they don't solve the scaling problem for miners. Some kind of treechain like sidechain / subchains where what part of the tree miners can mine is constrained to preserve fairness could be both a scaling solution, and decentralized, but no-one has come up with a solid design yet that's ready for production. (my treechains don't qualify for transactions yet; maybe for other proof-of-publication uses) Keep in mind that other than preserving mining decentralization/resisting censorship, we've known how to scale up blockchains for ages w/ things like (U)TXO commitments and fraud proofs. --=20 'peter'[:-1]@petertodd.org 0000000000000000127ab1d576dc851f374424f1269c4700ccaba2c42d97e778 --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQGrBAEBCACVBQJVgGgxXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw MDAwMDAwMDAwMDAwMDAxMjdhYjFkNTc2ZGM4NTFmMzc0NDI0ZjEyNjljNDcwMGNj YWJhMmM0MmQ5N2U3NzgvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udwXbwgAjT11UTC6xhr1KOinDK8hXq8B FH6LgXYFgTIlUSWSqAoiYJF3hDRf7DmfMJzgISum/kgWPrbCQKtDQH4droFrCrOR mIG8N7BYXXr20J8WSWeHgwhzB60T/TgB44NWUp6Fo66ubGu0C2oqMBi+3ORGKjCk JZXhc7Pk5YYCCSPpSVyx5+eM070ycAA5lsbcREOXdBihbnArllIZtmvUnW2qXOr6 pxtTa/psejBLtz1lI4Zw6Ih+J9peaU264S1FbM4ZPuDtTM4+QzqRPoMK2qA4CKSu AEStFDAphZvDSgujnnu9xIxREfXjsEfhMzcbLXmJTIbn/iL5tUn/sArurI1xqg== =99Pg -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH--