From mboxrd@z Thu Jan 1 00:00:00 1970 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 1Z4Y1s-00062Q-BF for bitcoin-development@lists.sourceforge.net; Mon, 15 Jun 2015 17:18:36 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.176 as permitted sender) client-ip=209.85.212.176; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f176.google.com; Received: from mail-wi0-f176.google.com ([209.85.212.176]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z4Y1n-0005iB-8A for bitcoin-development@lists.sourceforge.net; Mon, 15 Jun 2015 17:18:36 +0000 Received: by wifx6 with SMTP id x6so85631602wif.0 for ; Mon, 15 Jun 2015 10:18:25 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.181.11.193 with SMTP id ek1mr33576811wid.15.1434388705165; Mon, 15 Jun 2015 10:18:25 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.28.14.196 with HTTP; Mon, 15 Jun 2015 10:18:25 -0700 (PDT) In-Reply-To: References: <557D2571.601@gmail.com> Date: Mon, 15 Jun 2015 19:18:25 +0200 X-Google-Sender-Auth: Yw672EehJgsk1gXnopmDVsE4OGs Message-ID: From: Mike Hearn To: Pieter Wuille Content-Type: multipart/alternative; boundary=f46d043bdeda3dc72d051891a5ff X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Z4Y1n-0005iB-8A 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: Mon, 15 Jun 2015 17:18:36 -0000 --f46d043bdeda3dc72d051891a5ff Content-Type: text/plain; charset=UTF-8 > > It's simple: either you care about validation, and you must validate > everything, or you don't, and you don't validate anything. > Pedantically: you could validate a random subset of all scripts, to give yourself probabilistic verification rather than full vs SPV. If enough people do it with a large enough subset the probability of a problem being detected goes up a lot. You still pay the cost of the database updates. But your main point is of course completely right, that side chains are not a way to scale up. --f46d043bdeda3dc72d051891a5ff Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It's simple: either you care = about validation, and you must validate everything, or you don't, and y= ou don't validate anything.

Pedantically: you coul= d validate a random subset of all scripts, to give yourself probabilistic v= erification rather than full vs SPV. If enough people do it with a large en= ough subset the probability of a problem being detected goes up a lot. You = still pay the cost of the database updates.

But yo= ur main point is of course completely right, that side chains are not a way= to scale up.=C2=A0
--f46d043bdeda3dc72d051891a5ff--