Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D8017A84 for ; Tue, 10 Oct 2017 20:57:06 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pf0-f169.google.com (mail-pf0-f169.google.com [209.85.192.169]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2679F151 for ; Tue, 10 Oct 2017 20:57:06 +0000 (UTC) Received: by mail-pf0-f169.google.com with SMTP id e64so210801pfk.9 for ; Tue, 10 Oct 2017 13:57:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=SRqyGrF6GPZ9bSK1kZa+tNDtesN3sWPkk6JC2KXxDBA=; b=ImKQFBNalSpeEbMYn7zO81RvVmjgcPk/FeCWUuomN18ib7l5tgLfDvLcarKL/KcGjm Hc11e/fIKu4QlIx0XnkCb+J6+zCPo/fk/b3Z6Adeqhy5eTz9GFBeVgsCyGgeImT8XqZd gCKRe2tJD5nZPqMWrpafD4VnglPCbL6/0IyMvDntqR4vCcUfmlDoaT8M+b9vPgENmdpT hEZIz8MKehrEHWOO1C2wYCvgxnvkHJ3S3sj+lFR1KuCzJ//me5HAg5GASqVwf48mCXZx HQyme54fPpmiDia6+g2YQR8rKQhSjPXRCVs956NVxBy39XMnAZgMTiVVaqJ2uJEWjFeb VEsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=SRqyGrF6GPZ9bSK1kZa+tNDtesN3sWPkk6JC2KXxDBA=; b=TUOjgGyQlKLqHzdrJyNd8CHP4tccf1/b8Vo5jlkYrflN5f+QjZ1xmiLo1mc3lEJyaK vVkO8cU5Vp3EGeo3yb4bxTZ51FewNgYhQzSrJ+TSEgMV5CGmkt91F4Jy9qshOXSP2qZT bIStqXRTGP+H+lMpgzQYzHXq7Fp2hiW3E3B9MQmSrFp0t0cvzvuV22GLH9djehzp84Eu RY1RJoNooHecFLlJskQ814UoDiDdzDF/V52gZUklCGUoutQKmfEInnKcHDd1rHmoCJQ2 1XBAgEMSmjS9StFmtdtuAMuVqZgYxvygzjqirKyCqZaqQWUpatVYGrtWXC1U6TcVuH+J Ya9Q== X-Gm-Message-State: AMCzsaUV38SqvC5/4d8cnWcBEU1tAznhmuqC9/wdMV5ezl6yeogjwODG /whEPSEsSCtapXNLzr3KiovtAhFo X-Google-Smtp-Source: AOwi7QAJfQPubkupkdoLoqAMz8nqj4BSTlUIPK446MOSRJcyOzSHo3VQtedJqqOfR+n50pbbzdofxA== X-Received: by 10.98.69.134 with SMTP id n6mr1468397pfi.245.1507669025461; Tue, 10 Oct 2017 13:57:05 -0700 (PDT) Received: from ?IPv6:2601:640:8001:4c28:79ee:a006:acff:f68c? ([2601:640:8001:4c28:79ee:a006:acff:f68c]) by smtp.gmail.com with ESMTPSA id o13sm20635837pfh.91.2017.10.10.13.57.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Oct 2017 13:57:04 -0700 (PDT) From: James Hudon Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Date: Tue, 10 Oct 2017 13:57:03 -0700 References: <16D7672F-AA36-47D7-AAEF-E767B9CE09FF@taoeffect.com> <55CAABF4-4FB8-4230-8E51-014C1D347D72@taoeffect.com> To: Tao Effect , Bitcoin Protocol Discussion In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3445.1.7) X-Spam-Status: No, score=0.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,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, 10 Oct 2017 20:59:15 +0000 Subject: Re: [bitcoin-dev] Generalized sharding protocol for decentralized scaling without Miners owning our BTC 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, 10 Oct 2017 20:57:06 -0000 You're asking for newly minted bitcoin to go to you but you burned the = bitcoin used in the peg. You're effectively losing your money and then = stealing from the miners to gain it back. The miners had to issue your = amount of bitcoin 2 times (once for your original bitcoin, again to make = you whole). Why would they agree to this? -- hudon > On Oct 10, 2017, at 13:43, Tao Effect via bitcoin-dev = wrote: >=20 > What? >=20 > That is not correct. >=20 > There is a fixed amount of Bitcoin, as I said. >=20 > The only difference is what chain it is on. >=20 > It is precisely because there is a fixed amount that when you = burn-to-withdraw you mint on another chain. >=20 > I will not respond to any more emails unless they=E2=80=99re from core = developers. Gotta run. >=20 > -- > Sent from my mobile device. > Please do not email me anything that you are not comfortable also = sharing with the NSA. >=20 >> On Oct 10, 2017, at 1:23 PM, James Hudon = wrote: >>=20 >> You're asking for newly minted bitcoin to go to you but you burned = the bitcoin used in the peg. You're effectively losing your money and = then stealing from the miners to gain it back. The miners had to issue = your amount of bitcoin 2 times (once for your original bitcoin, again to = make you whole). Why would they agree to this? >> -- >> hudon >>=20 >>> On Oct 10, 2017, at 13:13, Tao Effect via bitcoin-dev = wrote: >>>=20 >>> It would not change the number of Bitcoins in existence. >>>=20 >>> -- >>> Sent from my mobile device. >>> Please do not email me anything that you are not comfortable also = sharing with the NSA. >>>=20 >>>> On Oct 10, 2017, at 12:50 PM, CryptAxe wrote: >>>>=20 >>>> Your method would change the number of Bitcoins in existence. Why?=20= >>>>=20 >>>> On Oct 10, 2017 12:47 PM, "Tao Effect via bitcoin-dev" = wrote: >>>> Is that what passes for a technical argument these days? Sheesh. >>>>=20 >>>> Whereas in Drivechain users are forced to give up their coins to a = single group for whatever sidechains they interact with, the generic = sharding algo lets them (1) keep their coins, (2) trust whatever group = they want to trust (the miners of the various sidechains). >>>>=20 >>>> Drivechain offers objectively worse security. >>>>=20 >>>> -- >>>> Sent from my mobile device. >>>> Please do not email me anything that you are not comfortable also = sharing with the NSA. >>>>=20 >>>>> On Oct 10, 2017, at 8:09 AM, Paul Sztorc via bitcoin-dev = wrote: >>>>>=20 >>>>> I think this response speaks for itself. >>>>>=20 >>>>>> On 10/10/2017 10:09 AM, Tao Effect wrote: >>>>>> Hi Paul, >>>>>>=20 >>>>>> I thought it was clear, but apparently you are getting stuck on = the semantics of the word "burn". >>>>>>=20 >>>>>> The "burning" applies to the original coins you had. >>>>>>=20 >>>>>> When you transfer them back, you get newly minted coins, = equivalent to the amount you "burned" on the chain you're transferring = from =E2=80=95 as stated in the OP. >>>>>>=20 >>>>>> If you don't like the word "burn", pick another one. >>>>>>=20 >>>>>> -- >>>>>> Please do not email me anything that you are not comfortable also = sharing with the NSA. >>>>>>=20 >>>>>>> On Oct 10, 2017, at 4:20 AM, Paul Sztorc = wrote: >>>>>>>=20 >>>>>>> Haha, no. Because you "burned" the coins. >>>>>>>=20 >>>>>>> On Oct 10, 2017 1:20 AM, "Tao Effect" = wrote: >>>>>>> Paul, >>>>>>>=20 >>>>>>> It's a two-way peg. >>>>>>>=20 >>>>>>> There's nothing preventing transfers back to the main chain. >>>>>>>=20 >>>>>>> They work in the exact same manner. >>>>>>>=20 >>>>>>> Cheers, >>>>>>> Greg >>>>>>>=20 >>>>>>> -- >>>>>>> Please do not email me anything that you are not comfortable = also sharing with the NSA. >>>>>>>=20 >>>>>>>> On Oct 9, 2017, at 6:39 PM, Paul Sztorc = wrote: >>>>>>>>=20 >>>>>>>> That is only a one-way peg, not a two-way. >>>>>>>>=20 >>>>>>>> In fact, that is exactly what drivechain does, if one chooses = parameters for the drivechain that make it impossible for any = side-to-main transfer to succeed. >>>>>>>>=20 >>>>>>>> One-way pegs have strong first-mover disadvantages. >>>>>>>>=20 >>>>>>>> Paul >>>>>>>>=20 >>>>>>>> On Oct 9, 2017 9:24 PM, "Tao Effect via bitcoin-dev" = wrote: >>>>>>>> Dear list, >>>>>>>>=20 >>>>>>>> In previous arguments over Drivechain (and Drivechain-like = proposals) I promised that better scaling proposals =E2=80=95 that do = not sacrifice Bitcoin's security =E2=80=95 would come along. >>>>>>>>=20 >>>>>>>> I planned to do a detailed writeup, but have decided to just = send off this email with what I have, because I'm unlikely to have time = to write up a detailed proposal. >>>>>>>>=20 >>>>>>>> The idea is very simple (and by no means novel*), and I'm sure = others have mentioned either exactly it, or similar ideas (e.g. burning = coins) before. >>>>>>>>=20 >>>>>>>> This is a generic sharding protocol for all blockchains, = including Bitcoin. >>>>>>>>=20 >>>>>>>> Users simply say: "My coins on Chain A are going to be sent to = Chain B". >>>>>>>>=20 >>>>>>>> Then they burn the coins on Chain A, and create a minting = transaction on Chain B. The details of how to ensure that coins do not = get lost needs to be worked out, but I'm fairly certain the folks on = this list can figure out those details. >>>>>>>>=20 >>>>>>>> - Thin clients, nodes, and miners, can all very easily verify = that said action took place, and therefore accept the "newly minted" = coins on B as valid. >>>>>>>> - Users client software now also knows where to look for the = other coins (if for some reason it needs to). >>>>>>>>=20 >>>>>>>> This doesn't even need much modification to the Bitcoin = protocol as most of the verification is done client-side. >>>>>>>>=20 >>>>>>>> It is fully decentralized, and there's no need to give our = ownership of our coins to miners to get scale. >>>>>>>>=20 >>>>>>>> My sincere apologies if this has been brought up before (in = which case, I would be very grateful for a link to the proposal). >>>>>>>>=20 >>>>>>>> Cheers, >>>>>>>> Greg Slepak >>>>>>>>=20 >>>>>>>> * This idea is similar in spirit to Interledger. >>>>>>>>=20 >>>>>>>> -- >>>>>>>> Please do not email me anything that you are not comfortable = also sharing with the NSA. >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> _______________________________________________ >>>>>>>> bitcoin-dev mailing list >>>>>>>> bitcoin-dev@lists.linuxfoundation.org >>>>>>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >>>>>>>>=20 >>>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>>=20 >>>>> _______________________________________________ >>>>> bitcoin-dev mailing list >>>>> bitcoin-dev@lists.linuxfoundation.org >>>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >>>>=20 >>>> _______________________________________________ >>>> bitcoin-dev mailing list >>>> bitcoin-dev@lists.linuxfoundation.org >>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >>>>=20 >>> _______________________________________________ >>> bitcoin-dev mailing list >>> bitcoin-dev@lists.linuxfoundation.org >>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >>=20 >=20 > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev