path: root/7d/c0d194b07dc2f91ba3c4f9dc3ef75946380ca9

Return-Path: <contact@taoeffect.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 46C6DA59
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 10 Oct 2017 01:02:35 +0000 (UTC)
X-Greylist: delayed 00:57:42 by SQLgrey-1.7.6
Received: from homiemail-a62.g.dreamhost.com (homie.mail.dreamhost.com
	[208.97.132.208])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C18FA4B5
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 10 Oct 2017 01:02:34 +0000 (UTC)
Received: from homiemail-a62.g.dreamhost.com (localhost [127.0.0.1])
	by homiemail-a62.g.dreamhost.com (Postfix) with ESMTP id 493FC63407D
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon,  9 Oct 2017 18:02:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=taoeffect.com; h=from
	:content-type:mime-version:subject:message-id:date:to; s=
	taoeffect.com; bh=BJYtct9agj/MmXz2pQ7qCdSBUq0=; b=onOsZIdZ9CbFuX
	vF+1uIMi44MIdP7g5sQftcqMJaPq1WioVpf4p43rlvP9qyy4k8697xkaQrhMkk0A
	TSJTeQ0/epa27G6wzqN3emCiIHxgdHeaKkvO8K6S2Y2jAp8z5ai7H5smSV5cMfCD
	7QybLGjw8vIRIzv/x4u6kO3pETjtM=
Received: from [192.168.254.44] (unknown [47.156.153.15])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: contact@taoeffect.com)
	by homiemail-a62.g.dreamhost.com (Postfix) with ESMTPSA id 41E0163407C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon,  9 Oct 2017 18:02:34 -0700 (PDT)
From: Tao Effect <contact@taoeffect.com>
Content-Type: multipart/signed;
	boundary="Apple-Mail=_212CD704-210C-4434-A1D6-E0EAD0505F6E";
	protocol="application/pgp-signature"; micalg=pgp-sha512
X-Mao-Original-Outgoing-Id: 529290158.100027-862ae11fa9a79a8f131feaefdd120391
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <16D7672F-AA36-47D7-AAEF-E767B9CE09FF@taoeffect.com>
Date: Mon, 9 Oct 2017 18:02:38 -0700
To: Paul Sztorc via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
X-Mailer: Apple Mail (2.3273)
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE 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 01:23:31 +0000
Subject: [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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Oct 2017 01:02:35 -0000


--Apple-Mail=_212CD704-210C-4434-A1D6-E0EAD0505F6E
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_19ECDE4E-EB67-4376-976F-F2593EF623D0"


--Apple-Mail=_19ECDE4E-EB67-4376-976F-F2593EF623D0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Dear list,

In previous arguments over Drivechain (and Drivechain-like proposals) I =
promised that better scaling proposals =E2=80=94 that do not sacrifice =
Bitcoin's security =E2=80=94 would come along.

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.

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.

This is a generic sharding protocol for all blockchains, including =
Bitcoin.

Users simply say: "My coins on Chain A are going to be sent to Chain B".

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.

- 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).

This doesn't even need much modification to the Bitcoin protocol as most =
of the verification is done client-side.

It is fully decentralized, and there's no need to give our ownership of =
our coins to miners to get scale.

My sincere apologies if this has been brought up before (in which case, =
I would be very grateful for a link to the proposal).

Cheers,
Greg Slepak

* This idea is similar in spirit to Interledger.

--
Please do not email me anything that you are not comfortable also =
sharing with the NSA.


--Apple-Mail=_19ECDE4E-EB67-4376-976F-F2593EF623D0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8" class=3D""><meta http-equiv=3D"Content-Type" =
content=3D"text/html charset=3Dutf-8" class=3D""><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D"">Dear list,<div class=3D""><br =
class=3D""></div><div class=3D"">In previous arguments over Drivechain =
(and Drivechain-like proposals) I promised that better scaling proposals =
=E2=80=94 that do not sacrifice Bitcoin's security =E2=80=94 would come =
along.</div><div class=3D""><br class=3D""></div><div class=3D"">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.</div><div class=3D""><br class=3D""></div><div =
class=3D"">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.</div><div class=3D""><br class=3D""></div><div =
class=3D"">This is a generic sharding protocol for all blockchains, =
including Bitcoin.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Users simply say: "My coins on Chain A are going to be sent =
to Chain B".</div><div class=3D""><br class=3D""></div><div =
class=3D"">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.</div><div class=3D""><br =
class=3D""></div><div class=3D"">- 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.</div><div class=3D"">- Users =
client software now also knows where to look for the other coins (if for =
some reason it needs to).</div><div class=3D""><br class=3D""></div><div =
class=3D"">This doesn't even need much modification to the Bitcoin =
protocol as most of the verification is done client-side.</div><div =
class=3D""><br class=3D""></div><div class=3D"">It is fully =
decentralized, and there's no need to give our ownership of our coins to =
miners to get scale.</div><div class=3D""><br class=3D""></div><div =
class=3D"">My sincere apologies if this has been brought up before (in =
which case, I would be very grateful for a link to the =
proposal).</div><div class=3D""><br class=3D""></div><div =
class=3D"">Cheers,</div><div class=3D"">Greg Slepak</div><div =
class=3D""><br class=3D""></div><div class=3D"">* This idea is similar =
in spirit to Interledger.</div><div class=3D""><br class=3D""></div><div =
class=3D""><div class=3D""><div class=3D""><span style=3D"color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal; orphans: 2; =
widows: 2;" class=3D"">--</span><br style=3D"color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal; orphans: 2; =
widows: 2;" class=3D""><span style=3D"color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal; orphans: 2; =
widows: 2;" class=3D"">Please do not email me anything that you are not =
comfortable also sharing</span><span style=3D"color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal; orphans: 2; =
widows: 2;" class=3D"">&nbsp;with the NSA.</span>
</div>

<br class=3D""></div></div></div></body></html>=

--Apple-Mail=_19ECDE4E-EB67-4376-976F-F2593EF623D0--

--Apple-Mail=_212CD704-210C-4434-A1D6-E0EAD0505F6E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEgYtgnomHliYDCUth7GcgK+kJUkcFAlncHC4ACgkQ7GcgK+kJ
UkeO6A//X2IV21YQg1EztexcbbtY5I+z6f0c8VDOUTGJJ/Jm21eE4YvIYpytat6P
3u+WcWk7ld2/jieSG0igM9E61alH0UZXhVcdW6r1RWB4tCVxdDKOB5uA4CSgV0N4
BW3sOS4D1XidlAVFw6sLO/+sPISAnpjyCU3KdTPvRyr6SaQHbL74RTCyKRv4XboH
BBoZQIlR1TLSwxCcTbiGvFaZAN0rbEaVc/zVMSG/G6JGMxN6T7p8oBv0TITMCvIA
rMK+/y+UhscQCFNpr/9RfsjNQm7LBXffD/YEBh51gqeLXgOflMtD5OLU7+jkGHht
5anuo8gkfIhnTjOxiPbP5VmQTNK4lxqI+Z5FSeooKGt2CtSIRrI1hqcNjYsdsGSW
rJQdHzyxF1z9Mon9b4fo5aftWz6HEDXXOextcoueBmoY+oswaiOopn+fKd2oLGZe
kbWrplgVldT74tJzbe5FYW8Fm36ud4B2EWrTNCrJC2rYrDdfWQQ388ESfYgz2Zwx
8kWOkcP/KRy7rOhQ+dLAxeyqkEXtTPvFtAqNNPcyhoAY8kOCtnIjaZU1sdPdmRJs
FDmFbCPCJBMBsUljcsP3WRtqBeUYxjMH+YKNYcYegJwSwDNUttd/OclEWp1FNJYL
H+lv9aPRmviuImxN3RAOs3JEwEpmp6QyyPTi5fSfLGuzOqN4JQo=
=VAzy
-----END PGP SIGNATURE-----

--Apple-Mail=_212CD704-210C-4434-A1D6-E0EAD0505F6E--