1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
|
Return-Path: <truthcoin@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 16FFFAAC
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 10 Oct 2017 01:39:37 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com
[209.85.215.46])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id AEFF14D9
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 10 Oct 2017 01:39:35 +0000 (UTC)
Received: by mail-lf0-f46.google.com with SMTP id k40so9751628lfi.4
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 09 Oct 2017 18:39:35 -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;
bh=0YYM3smPw36lSu6NIECtE2XpGjhc2NJXtwwkwAWPiSU=;
b=TMqT7MMlI+OgF5f1XYqDeLBQQCT1mzAUnPSZocYux4RGDBC+QiE7PHS6Gih8x3IN7Y
o5wEzwIXUOUAGLH8JIdAzFM7HLSkaTbwxKXx/pKvtOYxSLd4OwI99riRcxFQuusjiKl9
jqivlAAHUxkUeeTJCeHvrOHFobM3hXkoOLdM1icDhH37EGidFHfmWVVzphF72AHDr5Hb
b5xl3ZxzXkEzXp72SbAoSPv9/quQsXtdmfdfuMzVtQ+ZpUOKKBA7SW5Qw3zPTNb2xn1m
8ONNovv+skxW6GaIjK/dwVYD4nX0i3wqkFw3lBI/WqZjgISQDRlRIW5Fo9OZcx0aowsw
1nLA==
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;
bh=0YYM3smPw36lSu6NIECtE2XpGjhc2NJXtwwkwAWPiSU=;
b=LVCUN7hNxLeJY40cw9b5h0dAZvHPdkisuM/OWGIBmnkc5Cp1EA7N8M6GdoZNhjNK7a
b7hUNg0dOl/ZV6hsoguDlNClKU8k2xiThNrRIUKJoDVmfkN/AOS+OEEFekd4dsKYSIaV
fIBc9Xwo+AY4U7RHv3MZRglOYzRqxAE4MBYi/OsxBp6jzdlhEjA4etoTqYHgkjvgJnw2
4sHLO/0QIx/ZmlYH6amrlt3F57t4F25asB2VL6mvvGwI67dywNlKl9gpYBNkBmMnv5kL
lqJZ0IKuoQgjUNY+fXkP1pygRWEJujtnxOklj/aZispLGHnfDPfN6SLtc2Uucs7XJ6IZ
KVpw==
X-Gm-Message-State: AMCzsaUfNxd1f0haqbua1idpzSw4lyIbHLgKanE4IgAA1YbLYne5YkHR
Rv+Ytr60EyFfzmHRrMOiWVYwqqFIR2aqxbWHqUorRg==
X-Google-Smtp-Source: AOwi7QDAeRfELdSolslFjyUJsdr+EMns0EVdF0SFmz9F7HK/cgp4f1mefp6HDCDjSlTZ3JukZRWj/qVdUTV8HyuTkTk=
X-Received: by 10.46.91.25 with SMTP id p25mr5108891ljb.46.1507599573825; Mon,
09 Oct 2017 18:39:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.15.160 with HTTP; Mon, 9 Oct 2017 18:39:33 -0700 (PDT)
Received: by 10.25.15.160 with HTTP; Mon, 9 Oct 2017 18:39:33 -0700 (PDT)
In-Reply-To: <16D7672F-AA36-47D7-AAEF-E767B9CE09FF@taoeffect.com>
References: <16D7672F-AA36-47D7-AAEF-E767B9CE09FF@taoeffect.com>
From: Paul Sztorc <truthcoin@gmail.com>
Date: Mon, 9 Oct 2017 21:39:33 -0400
Message-ID: <CA+XQW1jf-6HCic4beV5GSix8KRzJ-7nTc-ePipfs=ouwvHX0jA@mail.gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
Tao Effect <contact@taoeffect.com>
Content-Type: multipart/alternative; boundary="001a114c17c60fbb26055b27612f"
X-Spam-Status: No, score=0.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU,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
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 <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:39:37 -0000
--001a114c17c60fbb26055b27612f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
That is only a one-way peg, not a two-way.
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.
One-way pegs have strong first-mover disadvantages.
Paul
On Oct 9, 2017 9:24 PM, "Tao Effect via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
Dear list,
In previous arguments over Drivechain (and Drivechain-like proposals) I
promised that better scaling proposals =E2=80=94 that do not sacrifice Bitc=
oin'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 w=
ith
the NSA.
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--001a114c17c60fbb26055b27612f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto"><div>That is only a one-way peg, not a two-way.</div><div=
dir=3D"auto"><br></div><div dir=3D"auto">In fact, that is exactly what dri=
vechain does, if one chooses parameters for the drivechain that make it imp=
ossible for any side-to-main transfer to succeed.</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">One-way pegs have strong first-mover disadvantage=
s.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Paul<br><div class=3D=
"gmail_extra" dir=3D"auto"><br><div class=3D"gmail_quote">On Oct 9, 2017 9:=
24 PM, "Tao Effect via bitcoin-dev" <<a href=3D"mailto:bitcoin=
-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&g=
t; wrote:<br type=3D"attribution"><blockquote class=3D"quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"wo=
rd-wrap:break-word"><div style=3D"word-wrap:break-word">Dear list,<div><br>=
</div><div>In previous arguments over Drivechain (and Drivechain-like propo=
sals) I promised that better scaling proposals =E2=80=94 that do not sacrif=
ice Bitcoin's security =E2=80=94 would come along.</div><div><br></div>=
<div>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><br></div><div>The idea is very simple (=
and by no means novel*), and I'm sure others have mentioned either exac=
tly it, or similar ideas (e.g. burning coins) before.</div><div><br></div><=
div>This is a generic sharding protocol for all blockchains, including Bitc=
oin.</div><div><br></div><div>Users simply say: "My coins on Chain A a=
re going to be sent to Chain B".</div><div><br></div><div>Then they bu=
rn the coins on Chain A, and create a minting transaction on Chain B. The d=
etails 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 deta=
ils.</div><div><br></div><div>- Thin clients, nodes, and miners, can all ve=
ry easily verify that said action took place, and therefore accept the &quo=
t;newly minted" coins on B as valid.</div><div>- Users client software=
now also knows where to look for the other coins (if for some reason it ne=
eds to).</div><div><br></div><div>This doesn't even need much modificat=
ion to the Bitcoin protocol as most of the verification is done client-side=
.</div><div><br></div><div>It is fully decentralized, and there's no ne=
ed to give our ownership of our coins to miners to get scale.</div><div><br=
></div><div>My sincere apologies if this has been brought up before (in whi=
ch case, I would be very grateful for a link to the proposal).</div><div><b=
r></div><div>Cheers,</div><div>Greg Slepak</div><div><br></div><div>* This =
idea is similar in spirit to Interledger.</div><div><br></div><div><div><di=
v><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:no=
rmal;text-align:start;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px;font-variant-ligatures:normal;font-variant-numeric:norma=
l;font-variant-alternates:normal;font-variant-east-asian:normal;line-height=
:normal">--</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;let=
ter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;whi=
te-space:normal;word-spacing:0px;font-variant-ligatures:normal;font-variant=
-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:norm=
al;line-height:normal"><span style=3D"color:rgb(0,0,0);font-family:Helvetic=
a;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:nor=
mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n=
one;white-space:normal;word-spacing:0px;font-variant-ligatures:normal;font-=
variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asi=
an:normal;line-height:normal">Please do not email me anything that you are =
not comfortable also sharing</span><span style=3D"color:rgb(0,0,0);font-fam=
ily:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;fon=
t-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text=
-transform:none;white-space:normal;word-spacing:0px;font-variant-ligatures:=
normal;font-variant-numeric:normal;font-variant-alternates:normal;font-vari=
ant-east-asian:normal;line-height:normal">=C2=A0with the NSA.</span>
</div>
<br></div></div></div></div><br>______________________________<wbr>________=
_________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
<br></blockquote></div><br></div></div></div>
--001a114c17c60fbb26055b27612f--
|
