Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z4YiE-0002aC-AQ for bitcoin-development@lists.sourceforge.net; Mon, 15 Jun 2015 18:02:22 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.214.171 as permitted sender) client-ip=209.85.214.171; envelope-from=jgarzik@bitpay.com; helo=mail-ob0-f171.google.com; Received: from mail-ob0-f171.google.com ([209.85.214.171]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z4YiD-00059g-9k for bitcoin-development@lists.sourceforge.net; Mon, 15 Jun 2015 18:02:22 +0000 Received: by obbgp2 with SMTP id gp2so69569448obb.2 for ; Mon, 15 Jun 2015 11:02:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=/iKVzayJ+16dT07kVKCburFipbq7nlkQWdwdPRWrLmk=; b=RREi2dFLDuZEvFm5U0lPAURqNtWTNI8TmtFQ0VH3BwOyt4rkesiMq+l09rMz2IN1nt dW3xMpAOHVQvI0nqeChVpvEi8G8RNnXhNVyRWrSxion7rLZnWsF6u1b4emRJZlgIFpz8 DIz6zBOU7NW4d9uiNYDkGblhxILbcVk9yQ+nA2/IJQRolyADEAHBJ77vyHpIU1Noq29Q ijT1vnJwWNfg8ZP8v8VGT4YaCscOwB+tdN9PIxPapZ0IkNkFrD9jKY4oBSp+4eor30cR bAhBXDjP/1v6JguCQC3xu9xAAzjijoRYV6ti//H0+46kdsUpw5I232f9KPhB166j42H/ uxEQ== X-Gm-Message-State: ALoCoQk2tbEMeHapW+JaTX28CVb2/HOR6/XFeI/4v+WGev6k41utBcWJcPeN1t3+qxnnk5IqNjjl X-Received: by 10.182.87.36 with SMTP id u4mr1109808obz.50.1434391335845; Mon, 15 Jun 2015 11:02:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.108.149 with HTTP; Mon, 15 Jun 2015 11:01:55 -0700 (PDT) In-Reply-To: References: <557D2571.601@gmail.com> From: Jeff Garzik Date: Mon, 15 Jun 2015 14:01:55 -0400 Message-ID: To: Mike Hearn Content-Type: multipart/alternative; boundary=089e013d0ddc0ad94a051892425b X-Spam-Score: -0.6 (/) 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 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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: 1Z4YiD-00059g-9k 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 18:02:22 -0000 --089e013d0ddc0ad94a051892425b Content-Type: text/plain; charset=UTF-8 Side chains are a way to scale and shard horizontally while still retaining primary security parameters of the main chain. The future is an Internet of chains, a forest of chains with bitcoin as the root chain for: factom / proofofexistence, ChainDB, Blockstream side chains, merge mined side chains, and more. A multi-chain design is much more scalable in general. On Mon, Jun 15, 2015 at 1:18 PM, Mike Hearn wrote: > 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. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/ --089e013d0ddc0ad94a051892425b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Side chains are a way to scale and shard horizontally whil= e still retaining primary security parameters of the main chain.

The future is an Internet of chains, a forest of chains with bitco= in as the root chain for: factom / proofofexistence, ChainDB, Blockstream s= ide chains, merge mined side chains, and more.=C2=A0 A multi-chain design i= s much more scalable in general.



On = Mon, Jun 15, 2015 at 1:18 PM, Mike Hearn <mike@plan99.net> wro= te:

It's simple: either you care about validation, an= d you must validate everything, or you don't, and you don't validat= e anything.

Pedantically: you could validate a = random subset of all scripts, to give yourself probabilistic verification r= ather than full vs SPV. If enough people do it with a large enough subset t= he 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.= =C2=A0

-----------------------------------------------------------------------= -------

_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/= listinfo/bitcoin-development




--
Jeff Garzik
Bitcoin core developer and open sourc= e evangelist
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0https://bitpay.com/
--089e013d0ddc0ad94a051892425b--