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
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
|
Return-Path: <criley@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id DF546491
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 26 Aug 2017 21:42:19 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ua0-f193.google.com (mail-ua0-f193.google.com
[209.85.217.193])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 21DBED4
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 26 Aug 2017 21:42:19 +0000 (UTC)
Received: by mail-ua0-f193.google.com with SMTP id x18so1279282uah.5
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 26 Aug 2017 14:42:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=from:content-transfer-encoding:mime-version:date:subject:message-id
:references:in-reply-to:to;
bh=LViGGtsal08wFIBRQirTyEUGHpvcd+lKRInBEdWFNSI=;
b=vHw9f2k09R/4kR5k5mtXDhmj1TIWvDkgmAAI3y+CDZxD6mt/1hBm3RLlLn5uajcdJe
j0XF5QRbR5NpkSotmEugDaY/IGmmLD2M2uHVEdK1JycSZCYHHlxfyzFWzFMX1fcO4Ind
Rrn0iM0aoNtTSlq6N9i818e159zDmSaNbhOogm8szDl1piwnOvB4Qkg82H0cXJ/znbXa
XUil3oJsMehpBjqbyvjbr2U9tvt0lHZlwHVMyUyP5qXCy7IZMQmCksswviXGM2D0hg6Q
ehGdTJCoIOBOfPyFYwhCwkC9K8rZcluyGZzEdOk+ZTLMXw7cWHmZqwmlE/rc3Cc4LLBW
aGEw==
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:date
:subject:message-id:references:in-reply-to:to;
bh=LViGGtsal08wFIBRQirTyEUGHpvcd+lKRInBEdWFNSI=;
b=bKRAzI34sBwTkTbB4W5AY1rxB9yaD9d8Y0eUk+5IhHZvOLUf8ye2T1OEMyjB6Lca7W
z6u90VFWFiTLmkAr9ge+POmSMVC6YxA17Q1bpuLGYyVbdSFom+a9VmioiwcO/yYE/ycs
ynzCL73e43NoKdB2Q/Y47xoGmPD48MtgTLt7ZoBXg1OIZpblgpDnbNk7qasB9MMF6abj
Nkrz3Ykad5M9QFRnoQWTDMT44iBpWhZPrsT2kWbsFUlcPTJYdSnv6arOV2aw9xJ8oIVa
Yxerl8UcQAy9Dc+TvWd7/9XBdnxjsiYGLFC/GCSK2oXRjj50bIl1EXIBKF20zPUshkRz
NzeA==
X-Gm-Message-State: AHYfb5isE9DuB4qurcqTd3UPO1JKs22QPzUglWz9Nf42JUqc1ss7Da5e
3xqVr7VJgEJFBw==
X-Received: by 10.176.23.77 with SMTP id k13mr1548622uaf.128.1503783738237;
Sat, 26 Aug 2017 14:42:18 -0700 (PDT)
Received: from [192.168.1.18] (c-73-53-249-28.hsd1.fl.comcast.net.
[73.53.249.28]) by smtp.gmail.com with ESMTPSA id
f123sm2110957vke.32.2017.08.26.14.42.17
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Sat, 26 Aug 2017 14:42:17 -0700 (PDT)
From: Christian Riley <criley@gmail.com>
Content-Type: multipart/alternative;
boundary=Apple-Mail-98ECC027-4FD5-488A-B789-24D5E0DB2BB7
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Sat, 26 Aug 2017 17:42:16 -0400
Message-Id: <DEC1CF18-5425-41C2-88DF-399BD32CD6F1@gmail.com>
References: <CACQPdjpPTHKQaY5NOvhEvSX1X3Jc9X4fcO7=Qy6Epwbftg4NOQ@mail.gmail.com>
In-Reply-To: <CACQPdjpPTHKQaY5NOvhEvSX1X3Jc9X4fcO7=Qy6Epwbftg4NOQ@mail.gmail.com>
To: Adam Tamir Shem-Tov <tshachaf@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
X-Mailer: iPad Mail (14G60)
X-Spam-Status: No, score=0.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, MIME_QP_LONG_LINE,
RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM,
TVD_PH_BODY_ACCOUNTS_PRE 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: Sat, 26 Aug 2017 21:44:18 +0000
Subject: Re: [bitcoin-dev] Solving the Scalability Problem Part II - Adam
Shem-Tov
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: Sat, 26 Aug 2017 21:42:20 -0000
--Apple-Mail-98ECC027-4FD5-488A-B789-24D5E0DB2BB7
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
There have been a number of similar (identical?) proposals over the years, s=
ome were discussed in these threads:
https://bitcointalk.org/index.php?topic=3D56226.0
https://bitcointalk.org/index.php?topic=3D505.0
https://bitcointalk.org/index.php?topic=3D473.0
https://bitcointalk.org/index.php?topic=3D52859.0
https://bitcointalk.org/index.php?topic=3D12376.0
https://bitcointalk.org/index.php?topic=3D74559.15
> On Aug 26, 2017, at 5:01 PM, Adam Tamir Shem-Tov via bitcoin-dev <bitcoin-=
dev@lists.linuxfoundation.org> wrote:
>=20
> <B>Solving the Scalability Problem Part II</B>
> --------------------------------------------------------------------
> <BR>
> In the previous post I showed a way to minimize the blocks on the block ch=
ain, to lower the amount of space it takes on the hard drive, without losing=
any relevant information.
> I added a note, saying that the transaction chain needs to be rewritten, b=
ut I did not give much detail to it.<BR>
> Here is how that would work:<BR>
> <B>The Genesis Account:</B>
> -----------------------------------------<BR>
> The problem with changing the transaction and block chain, is that it cann=
ot be done without knowing the private key of the sender of the of the funds=
for each account. There is however a way to circumvent that problem. That i=
s to create a special account called the =E2=80=9CGenesis Account=E2=80=9D, t=
his account=E2=80=99s Private Key and Public Key will be available to everyo=
ne.<BR>
> But this account will not be able to send or receive any funds in a normal=
block, it will be blocked--blacklisted. So no one can intentionally use it.=
The only time this account will be used is in the pruning block, a.k.a Exod=
us Block.<BR>
> When creating the new pruned block chain and transaction chain, all the fu=
nds that are now in accounts must be legitimate, and it would be difficult t=
o legitimize them unless they were sent from a legitimate account, with a pu=
blic key, and a private key which can be verified. That is where the Genesis=
account comes in. All funds in the Exodus Block will show as though they or=
iginated and were sent from the Genesis Account using its privatekey to gene=
rate each transaction.<BR>
> The funds which are sent, must match exactly the funds existing in the mos=
t updated ledger in block 1000 (the last block as stated in my previous post=
).<BR>
> In this way the Exodus Block can be verified, and the Genesis Account cann=
ot give free money to anyway, because if someone tried to, it would fail ver=
ification.<BR>
> <BR>
> Now the next problem is that the number of Bitcoins keeps expanding and so=
the funds in the Genesis Account need to expand as well. That can be done b=
y showing as though this account is the account which is mining the coins, a=
nd it will be the only account in the Exodus Block which =E2=80=9Cmines=E2=80=
=9D the coins, and receives the mining bonus. In the Exodus Block all coins m=
ined by the real miners will show as though they were mined by Genesis and s=
ent to the miners through a regular transaction.
> <BR>
> Adam Shem-Tov
>=20
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--Apple-Mail-98ECC027-4FD5-488A-B789-24D5E0DB2BB7
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><div><span style=3D"background-color: r=
gba(255, 255, 255, 0);">There have been a number of similar (identical?) pro=
posals over the years, some were discussed in these threads:</span></div><di=
v><a href=3D"https://bitcointalk.org/index.php?topic=3D56226.0" style=3D"bac=
kground-color: rgba(255, 255, 255, 0);"><font color=3D"#000000">https://bitc=
ointalk.org/index.php?topic=3D56226.0</font></a></div><div><a href=3D"https:=
//bitcointalk.org/index.php?topic=3D505.0" style=3D"background-color: rgba(2=
55, 255, 255, 0);"><font color=3D"#000000">https://bitcointalk.org/index.php=
?topic=3D505.0</font></a></div><div><a href=3D"https://bitcointalk.org/index=
.php?topic=3D473.0" style=3D"background-color: rgba(255, 255, 255, 0);"><fon=
t color=3D"#000000">https://bitcointalk.org/index.php?topic=3D473.0</font></=
a></div><div><a href=3D"https://bitcointalk.org/index.php?topic=3D52859.0" s=
tyle=3D"background-color: rgba(255, 255, 255, 0);"><font color=3D"#000000">h=
ttps://bitcointalk.org/index.php?topic=3D52859.0</font></a></div><div><a hre=
f=3D"https://bitcointalk.org/index.php?topic=3D12376.0" style=3D"background-=
color: rgba(255, 255, 255, 0);"><font color=3D"#000000">https://bitcointalk.=
org/index.php?topic=3D12376.0</font></a></div><div><div id=3D"AppleMailSigna=
ture"><a href=3D"https://bitcointalk.org/index.php?topic=3D74559.15" style=3D=
"background-color: rgba(255, 255, 255, 0);"><font color=3D"#000000">https://=
bitcointalk.org/index.php?topic=3D74559.15</font></a></div></div><br></div><=
div><br>On Aug 26, 2017, at 5:01 PM, Adam Tamir Shem-Tov via bitcoin-dev <=
;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a>> wrote:<br><br></div><blockquote type=3D"cite"><d=
iv><div dir=3D"ltr">
=09
=09
=09
=09
<p style=3D"margin-bottom:0in;line-height:100%"><B>Solving the
Scalability Problem Part
II</B><br>
--------------------------------------------------------------------<br>
<BR><br>
In
the previous post I showed a way to minimize the blocks on the block
chain, to lower the amount of space it takes on the hard drive,
without losing any relevant information.<br>
I added a note, saying
that the transaction chain needs to be rewritten, but I did not give
much detail to it.<BR><br>
Here is how that would
work:<BR><br>
<B>The Genesis
Account:</B><br>
-----------------------------------------<BR><br>
The
problem with changing the transaction and block chain, is that it
cannot be done without knowing the private key of the sender of the
of the funds for each account. There is however a way to circumvent
that problem. That is to create a special account called the =E2=80=9CGenesi=
s
Account=E2=80=9D, this account=E2=80=99s Private Key and Public Key will be
available to everyone.<BR><br>
But this account will not be
able to send or receive any funds in a normal block, it will be
blocked--blacklisted. So no one can intentionally use it. The only
time this account will be used is in the pruning block, a.k.a Exodus
Block.<BR><br>
When creating the new pruned block chain and
transaction chain, all the funds that are now in accounts must be
legitimate, and it would be difficult to legitimize them unless they
were sent from a legitimate account, with a public key, and a private
key which can be verified. That is where the Genesis account comes
in. All funds in the Exodus Block will show as though they originated
and were sent from the Genesis Account using its privatekey to
generate each transaction.<BR><br>
The funds which are sent,
must match exactly the funds existing in the most updated ledger in
block 1000 (the last block as stated in my previous post).<BR><br>
In
this way the Exodus Block can be verified, and the Genesis Account
cannot give free money to anyway, because if someone tried to, it
would fail verification.<BR></p>
<p style=3D"margin-bottom:0in;line-height:100%"><BR><br>
Now
the next problem is that the number of Bitcoins keeps expanding and
so the funds in the Genesis Account need to expand as well. That can
be done by showing as though this account is the account which is
mining the coins, and it will be the only account in the Exodus Block
which =E2=80=9Cmines=E2=80=9D the coins, and receives the mining bonus. In t=
he
Exodus Block all coins mined by the real miners will show as though
they were mined by Genesis and sent to the miners through a regular
transaction.</p>
<p style=3D"margin-bottom:0in;line-height:100%"><BR></p>
<p style=3D"margin-bottom:0in;line-height:100%">Adam Shem-Tov</p>
<p style=3D"margin-bottom:0in;line-height:100%"><br>
</p>
</div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>bitcoin-dev mailing list</span><=
br><span><a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-de=
v@lists.linuxfoundation.org</a></span><br><span><a href=3D"https://lists.lin=
uxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation=
.org/mailman/listinfo/bitcoin-dev</a></span><br></div></blockquote></body></=
html>=
--Apple-Mail-98ECC027-4FD5-488A-B789-24D5E0DB2BB7--
|
