Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id EEC177A4 for ; Tue, 26 Sep 2017 01:15:11 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-yw0-f181.google.com (mail-yw0-f181.google.com [209.85.161.181]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1CE3E3D5 for ; Tue, 26 Sep 2017 01:15:11 +0000 (UTC) Received: by mail-yw0-f181.google.com with SMTP id w22so6029014ywa.13 for ; Mon, 25 Sep 2017 18:15:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KLtgQjfHaVXb/m+X/HVASh1e4TOhfV9acD8r7LGRRaY=; b=Zg7e9AnCuc3j8nJikdHx0PdbAd1VXDddjQ+F+pN3TVWTODjom5bN589rJOE6eIkpPg 1or5rRvSA42VOuJdfUURrHQFqTFWl0pKbEBREEp4t3iMKoJH4xoYzyXLE0HSik6hcMUU KmgqDVxf0P/teBZ7fzjpOEGivhruRw911R7u9NucwGYnP2SFRnGmsvAohetmTLC0UC4r XZ9rHV4UcDkM7oRGClo34iLOn51DHMmbG1Zlf5sbase3c5VG4g16cF6RsHBDm1vQ5GaD BljXlES28KbTgKV0dZVn8UBqNqYeflFmZylyfdeZcW+nv0mkjefR5HukEhfBqMc4u57t ZloQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KLtgQjfHaVXb/m+X/HVASh1e4TOhfV9acD8r7LGRRaY=; b=I8pzIw1q/H5NwySclcaUgtXpwCmjw0nk1zUVhKLMSKzIdj0IEbjGtVDovEZ2+MvDpr 8VStlsSphnO49gvTfnUgaGTbc2zuZzpazgDx2i+EORa4Oemaqa6//bSYlP+nDqRxr6UX sMGwnJZ/EWKjEWONOLurzNFY0I5Wflt5HviLXgGqHF8aHb8fDYU/2z1ufOm0mG1ABCgs C0nmL2g8kXW7ChpuLAEPTLXpzmzxRuYa0wTL41vVWjmTm/We1yKSuPdIERyZdxTAJNHz G+jdBBEFN98Ti0s2JIKfWKwag4YeX41bg+Vlpr3c3EEBC3xNEIY50h42QWSgOQkyH+St R0Gg== X-Gm-Message-State: AHPjjUifylcQBEloAyGIN+5MnWtgbuAgL0wEfIKrPeEJ4KtrfAEZ0CBo 7VhquS7xjEXwTZJUiJ7UmbZNwaPVJB/gzDK3gho= X-Google-Smtp-Source: AOwi7QCqIqSKMg/a68sY4LQ7xX7nuoc3GJj4tp9gFQxeKez3CEM15RcEpYBVmOGjVTW07xIg2picvl6LPTX+rphseLk= X-Received: by 10.129.212.65 with SMTP id g1mr1746287ywl.32.1506388510110; Mon, 25 Sep 2017 18:15:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.45.77 with HTTP; Mon, 25 Sep 2017 18:15:09 -0700 (PDT) In-Reply-To: <7lMVV5tc0S5aSzZV8305yOhRd8AWufZhxToS31hmq6SGpiMC2eLZsvHYcsyj_HzFo6ip5p6CtKXRiHxxRVM3IHsCnm8qXWJT_iheDM3HYZU=@protonmail.com> References: <7lMVV5tc0S5aSzZV8305yOhRd8AWufZhxToS31hmq6SGpiMC2eLZsvHYcsyj_HzFo6ip5p6CtKXRiHxxRVM3IHsCnm8qXWJT_iheDM3HYZU=@protonmail.com> From: Patrick Sharp Date: Mon, 25 Sep 2017 19:15:09 -0600 Message-ID: To: ZmnSCPxj Content-Type: multipart/alternative; boundary="089e082242dc09f893055a0d68e8" X-Spam-Status: No, score=0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Tue, 26 Sep 2017 02:05:46 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] idea post: bitcoin side chain implementation X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2017 01:15:12 -0000 --089e082242dc09f893055a0d68e8 Content-Type: text/plain; charset="UTF-8" By magic I meant that that it happens all by itself without any extra configuring. Thank you for your responses. I have been enlightened. As ZmnSCPxj has pointed out lightning network and pruning accomplishes everything I set out to accomplish. And sharding is exactly what I had in mind. I will keep this in the back of my mind and perhaps even attempt will implement it if it still seems worth doing later. You guys are totally awesome!!! I here by withdraw my proposal for the time being. -patrick On Mon, Sep 25, 2017 at 6:35 PM, ZmnSCPxj wrote: > Good morning Patrick, > > > >Non official chains suffer from the fact that few if any miners are going > to mine them so they lack security on par with the main chain. > > That is why most sidechain proposals use some kind of merge mining, where > a commitment to another chain's block is published on the Bitcoin chain. > Drivechain has "blind" merge mining, my recent "mainstake" proposal > publishses entire sidechain block headers on the mainchain. These > techniques provide security that is nearer to mainchain security. > > >And more over most > >users aren't going to use them because its not magic. > > No technology is magic, so I do not understand this sentence. > > >If my ultimate goal is official side chains that include part of the > reward such security is at parity between all chains and that the official > software > >automatically enable users to distribute their burden, would my course of > action be to build an external proof-of-concept side chain of side chains? > >or do you doubt that official reward splitting chains will ever find > their way into bitcoin core? > > I think it would be better to term your system as "sharding" rather than > "sidechain". > > If and when we are able to actually agree upon some kind of > sidechain-enabling proposal that is acceptable to the majority of Bitcoin > Core developers, then yes, you should make a sidechain that is capable of > sharding. Sharding a distributed ledger while ensuring correct operation > is a hard problem; in particular it is almost impossible to protect against > double-spending unless you can see all officially-added-to-the-chain > transactions. > > See: https://petertodd.org/2015/why-scaling-bitcoin-with- > sharding-is-very-hard > > Regards, > ZmnSCPxj > --089e082242dc09f893055a0d68e8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
By magic I meant that that it happens all by itself withou= t any extra configuring.

Thank you for your responses. I= have been enlightened. As=C2=A0ZmnSCPxj h= as pointed out lightning network and pruning=C2=A0accomplishes everything I= set out to accomplish. And sharding is exactly what I had in mind. I will = keep this in the back of my mind and perhaps even attempt will implement it= if it still seems worth doing later.

You guy= s are totally awesome!!!

I here by withdraw= my proposal for the time being.

-patrick

<= div class=3D"gmail_quote">On Mon, Sep 25, 2017 at 6:35 PM, ZmnSCPxj <ZmnSCPxj@protonmail.com> wrote:
Good morning Patrick,

<= div>
>Non official chains suffer from the fact that few if= any miners are going to mine them so they lack security on par with the ma= in chain.

That is why most sidechain pr= oposals use some kind of merge mining, where a commitment to another chain&= #39;s block is published on the Bitcoin chain.=C2=A0 Drivechain has "b= lind" merge mining, my recent "mainstake" proposal publishse= s entire sidechain block headers on the mainchain.=C2=A0 These techniques p= rovide security that is nearer to mainchain security.

>And more over most
>users a= ren't going to use them because its not magic.

=
No technology is magic, so I do not understand this sentence.

>If my ultimate goal is off= icial side chains that include part of the reward such security is at parit= y between all chains and that the official software
>auto= matically enable users to distribute their burden, would my course of actio= n be to build an external proof-of-concept side chain of side chains?
>or do you doubt that official reward splitting chains will eve= r find their way into bitcoin core?

I t= hink it would be better to term your system as "sharding" rather = than "sidechain".

If and when we are= able to actually agree upon some kind of sidechain-enabling proposal that = is acceptable to the majority of Bitcoin Core developers, then yes, you sho= uld make a sidechain that is capable of sharding.=C2=A0 Sharding a distribu= ted ledger while ensuring correct operation is a hard problem; in particula= r it is almost impossible to protect against double-spending unless you can= see all officially-added-to-the-chain transactions.


Regards,
ZmnSCPxj

--089e082242dc09f893055a0d68e8--