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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pedro@worcel.com>) id 1YsI6p-0007uB-Vk
for bitcoin-development@lists.sourceforge.net;
Tue, 12 May 2015 21:53:04 +0000
X-ACL-Warn:
Received: from mail-lb0-f171.google.com ([209.85.217.171])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YsI6o-0000AY-B7
for bitcoin-development@lists.sourceforge.net;
Tue, 12 May 2015 21:53:03 +0000
Received: by lbbuc2 with SMTP id uc2so16157743lbb.2
for <bitcoin-development@lists.sourceforge.net>;
Tue, 12 May 2015 14:52:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=2IXRZjElp7FaP37O2L5RA+KNLgxpwtNbqQCr4iO/dAA=;
b=m2uWRZo5DGtoQSHHUlv+yg+zKDDmIZF5Vt2KVIPc3SEBqZIyxyxG7isZS/VxP185Au
TZewIVQWfX7jUno4Lcu0QwGFx/abCl3n8a/muOFpIsTP0KAFpty67SxIUX1xtKPtPz6F
Y15ikF9ZlaGCWanQATB1mG7WeKptStUukaQah441S/kiSlHR2brtVsWrffMO2bSBkdj8
AY7bilKxke5SkQvX+BkdOwpnDYb2/POKb+xjUHt0AYlBNT6AK/FsQHINxbJx1d9HsXf+
4XA1gahn1P6QduSgZztRWDtXj+M9n1m+UGMa6PvicJUmJRE85AQnM6Rdx7/9ZTkw51dS
4Q8Q==
X-Gm-Message-State: ALoCoQllHl24umvis7omDsNj9AQpsWZ/nzPudqobWTKZULTv2feIZmehPrIhZBtwwmd9XCgfwfQD
X-Received: by 10.152.88.80 with SMTP id be16mr13366557lab.39.1431465922516;
Tue, 12 May 2015 14:25:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.125.161 with HTTP; Tue, 12 May 2015 14:24:41 -0700 (PDT)
In-Reply-To: <CABsx9T3AxM3et7hgXx3+Rn3BvhQkF-Cn797sHcyztkMpD1UQmA@mail.gmail.com>
References: <5550D8BE.6070207@electrum.org>
<ce3d34c92efd1cf57326e4679550944e@national.shitposting.agency>
<CABsx9T1VgxEJWxrYTs+2hXGnGrSLGJ6mVcAexjXLvK7Vu+e3EA@mail.gmail.com>
<5551F376.4050008@electrum.org>
<CABsx9T1h7p3hDr7ty43uxsYs-oNRpndzg=dowST2tXtogxRm2g@mail.gmail.com>
<555210AF.3090705@electrum.org>
<CABsx9T3AxM3et7hgXx3+Rn3BvhQkF-Cn797sHcyztkMpD1UQmA@mail.gmail.com>
From: Pedro Worcel <pedro@worcel.com>
Date: Wed, 13 May 2015 09:24:41 +1200
Message-ID: <CAPS+U98sh6BmuGHWOffrmTpaM3CNfhBUWdmgACb9++jU6M1fmQ@mail.gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3564ed1ed4d0515e92172
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1YsI6o-0000AY-B7
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Long-term mining incentives
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2015 21:53:04 -0000
--001a11c3564ed1ed4d0515e92172
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Disclaimer: I don't know anything about Bitcoin.
> =E2=80=8B2) Proof-of-idle supported (I wish Tadge Dryja would publish his
proof-of-idle idea....)
> 3) Fees purely as transaction-spam-prevention measure, chain security via
alternative consensus algorithm (in this scenario there is very little
mining).
I don't understand why you would casually mention moving away from Proof of
Work, I thought that was the big breakthrough that made Bitcoin possible at
all?
Thanks,
Pedro
2015-05-13 4:10 GMT+12:00 Gavin Andresen <gavinandresen@gmail.com>:
> Added back the list, I didn't mean to reply privately:
>
> Fair enough, I'll try to find time in the next month or three to write up
> four plausible future scenarios for how mining incentives might work:
>
> 1) Fee-supported with very large blocks containing lots of tiny-fee
> transactions
> =E2=80=8B=E2=80=8B
> 2) Proof-of-idle supported (I wish Tadge Dryja would publish his
> proof-of-idle idea....)
> 3) Fees purely as transaction-spam-prevention measure, chain security via
> alternative consensus algorithm (in this scenario there is very little
> mining).
> 4) Fee supported with small blocks containing high-fee transactions movin=
g
> coins to/from sidechains.
>
> Would that be helpful, or do you have some reason for thinking that we
> should pick just one and focus all of our efforts on making that one
> scenario happen?
>
> I always think it is better, when possible, not to "bet on one horse."
>
>
> On Tue, May 12, 2015 at 10:39 AM, Thomas Voegtlin <thomasv@electrum.org>
> wrote:
>
>> Le 12/05/2015 15:44, Gavin Andresen a =C3=A9crit :
>> > Ok, here's my scenario:
>> >
>> > https://blog.bitcoinfoundation.org/a-scalability-roadmap/
>> >
>> > It might be wrong. I welcome other people to present their road maps.
>> >
>>
>> [answering to you only because you answered to me and not to the list;
>> feel free to repost this to the list though]
>>
>> Yes, that's exactly the kind of roadmap I am asking for. But your blog
>> post does not say anything about long term mining incentives, it only
>> talks about scalability. My point is that we need the same kind of thing
>> for miners incentives.
>>
>
>
>
> --
> --
> Gavin Andresen
>
>
> -------------------------------------------------------------------------=
-----
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--001a11c3564ed1ed4d0515e92172
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif">Disclaimer: I don't know anything about Bitcoin.<br><br>>=
; =E2=80=8B2) Proof-of-idle supported (I wish Tadge Dryja would publish his=
proof-of-idle idea....)<div>> 3)
Fees purely as transaction-spam-prevention measure, chain security via=20
alternative consensus algorithm (in this scenario there is very little=20
mining).</div></div><div class=3D"gmail_default" style=3D"font-family:verda=
na,sans-serif"><br>I don't understand why you would casually mention mo=
ving away from Proof of Work, I thought that was the big breakthrough that =
made Bitcoin possible at all?<br><br></div><div class=3D"gmail_default" sty=
le=3D"font-family:verdana,sans-serif">Thanks,<br></div><div class=3D"gmail_=
default" style=3D"font-family:verdana,sans-serif">Pedro<br></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">2015-05-13 4:10 GMT+12:00 G=
avin Andresen <span dir=3D"ltr"><<a href=3D"mailto:gavinandresen@gmail.c=
om" target=3D"_blank">gavinandresen@gmail.com</a>></span>:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Added back th=
e list, I didn't mean to reply privately:</div><div><br></div>Fair enou=
gh, I'll try to find time in the next month or three to write up four p=
lausible future scenarios for how mining incentives might work:<div><br></d=
iv><div>1) Fee-supported with very large blocks containing lots of tiny-fee=
transactions</div><div><div class=3D"gmail_default" style=3D"font-family:v=
erdana,sans-serif;display:inline">=E2=80=8B=E2=80=8B</div>2) Proof-of-idle =
supported (I wish Tadge Dryja would publish his proof-of-idle idea....)</di=
v><div>3) Fees purely as transaction-spam-prevention measure, chain securit=
y via alternative consensus algorithm (in this scenario there is very littl=
e mining).</div><div>4) Fee supported with small blocks containing high-fee=
transactions moving coins to/from sidechains.</div><div><br></div><div>Wou=
ld that be helpful, or do you have some reason for thinking that we should =
pick just one and focus all of our efforts on making that one scenario happ=
en?</div><div><br></div><div>I always think it is better, when possible, no=
t to "bet on one horse."</div><div><br></div><div class=3D"gmail_=
extra"><br><div class=3D"gmail_quote">On Tue, May 12, 2015 at 10:39 AM, Tho=
mas Voegtlin <span dir=3D"ltr"><<a href=3D"mailto:thomasv@electrum.org" =
target=3D"_blank">thomasv@electrum.org</a>></span> wrote:<br><blockquote=
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><span>Le 12/05/2015 15:44, Gavin And=
resen a =C3=A9crit :<br>
> Ok, here's my scenario:<br>
><br>
> <a href=3D"https://blog.bitcoinfoundation.org/a-scalability-roadmap/" =
target=3D"_blank">https://blog.bitcoinfoundation.org/a-scalability-roadmap/=
</a><br>
><br>
> It might be wrong. I welcome other people to present their road maps.<=
br>
><br>
<br>
</span>[answering to you only because you answered to me and not to the lis=
t;<br>
feel free to repost this to the list though]<br>
<br>
Yes, that's exactly the kind of roadmap I am asking for. But your blog<=
br>
post does not say anything about long term mining incentives, it only<br>
talks about scalability. My point is that we need the same kind of thing<br=
>
for miners incentives.<span><font color=3D"#888888"><br>
</font></span></blockquote></div><span><font color=3D"#888888"><br><br clea=
r=3D"all"><div><br></div>-- <br><div>--<br>Gavin Andresen<br></div>
</font></span></div></div>
<br>-----------------------------------------------------------------------=
-------<br>
One dashboard for servers and applications across Physical-Virtual-Cloud<br=
>
Widest out-of-the-box monitoring support with 50+ applications<br>
Performance metrics, stats and reports that give you Actionable Insights<br=
>
Deep dive visibility with transaction tracing using APM Insight.<br>
<a href=3D"http://ad.doubleclick.net/ddm/clk/290420510;117567292;y" target=
=3D"_blank">http://ad.doubleclick.net/ddm/clk/290420510;117567292;y</a><br>=
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div></div>
--001a11c3564ed1ed4d0515e92172--
|
