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
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
|
Return-Path: <vitteaymeric@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 39BE0949
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 May 2017 13:37:41 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 12873E5
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 May 2017 13:37:39 +0000 (UTC)
Received: by mail-wm0-f44.google.com with SMTP id m123so16058959wma.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 04 May 2017 06:37:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to; bh=pRkCXhrH7bddRPgGO6jQ4axAV9fOBAe/K3aqc+Q2wUw=;
b=jb98dvDvqUIqrZ3PoafRqextLqyUoPTozXBkWyhlb+WWWoQd/MqMQ31zZb4qiDUyMc
ojRoPBDtCFHSkP7VaYXgzO/lOu2jrfH94zSk198B6fVNVmWNED0CeIToN/7j6B268PV+
WqpsGtDJQlo57AR/L/g38yeaMOQ3GQwIhLkYKfldESNZQLFzn002nOkGNd2c+Us56Jp6
Rwmbopq17aZ1gxSgHyyjxx7PzRFGbDigPXKVHPBAqiOE0Kece/oON63ayTS5N89u24tE
ue8ZvwmFK9bY+mlWfBIzYojOHWJsg0AhiDjjWuG1PaiW7ILQggQILJAmiLRAwTFpQ+GU
Z9DA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to;
bh=pRkCXhrH7bddRPgGO6jQ4axAV9fOBAe/K3aqc+Q2wUw=;
b=tE+1AyyBIcQUmxN5d919Fzry94OStan4zqOVhDdkIH72VmW0bshKlXcOf39zDBF78Y
BEazhhcuStcKsxoDdHVBPlFsKRUg0y6psUYxM/KMXMewn4K+EefbgnwuVs4g/ZJB1+j0
bC7IfuxEWjRHWWkRc+3ESaoO/5nnWM9DQg2yY3qq4bHIFpyy7JVOSz+yxI5zdceAKF0X
xk3Xr7ZsobNhlDciWpAoCwGpRlDaMDGHjPcFPnNsTIqnSjjg6DwpXDLZUUwMEiiFOqv4
cN5q1v1bGYy9NU4ahP9MuwG0fS5Mz3cBmRtpA4kf5tM/zLbgrNkvRT8PiUIhX0UckHzk
z29w==
X-Gm-Message-State: AN3rC/7OrsnubcPhKV/V+hrMuHUj+8/Q5tBVcAmbGxM0+b+2FxHffad9
yzi36y2kujuUkgyn
X-Received: by 10.28.197.11 with SMTP id v11mr2043218wmf.84.1493905058439;
Thu, 04 May 2017 06:37:38 -0700 (PDT)
Received: from [192.168.1.10] (ANice-654-1-42-58.w83-201.abo.wanadoo.fr.
[83.201.101.58]) by smtp.googlemail.com with ESMTPSA id
k7sm3212522wrk.45.2017.05.04.06.37.37
for <bitcoin-dev@lists.linuxfoundation.org>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 04 May 2017 06:37:37 -0700 (PDT)
To: bitcoin-dev@lists.linuxfoundation.org
References: <CAJowKg+snAUjbCFkTybNqiJCy=d_M3s5k376y1B=rVqD8WCOXA@mail.gmail.com>
<CAOxie=GNQtoJLEoY=aHGT5m1RFFmrqVi5p6BMnT-sRkHjkhGcw@mail.gmail.com>
<1493894309.1179269.965498864.6244705A@webmail.messagingengine.com>
From: Aymeric Vitte <vitteaymeric@gmail.com>
Message-ID: <02b56878-c4e5-d1b9-07f4-317663f543b5@gmail.com>
Date: Thu, 4 May 2017 15:37:43 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:45.0) Gecko/20100101
Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <1493894309.1179269.965498864.6244705A@webmail.messagingengine.com>
Content-Type: multipart/alternative;
boundary="------------812ABCBB7415E348EBCE50D8"
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE,
RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Full node "tip" function
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: Thu, 04 May 2017 13:37:41 -0000
This is a multi-part message in MIME format.
--------------812ABCBB7415E348EBCE50D8
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Strange idea, incentiving people to run full nodes should certainly not
depend on miners, should certainly not involve another wasteful pow and
should certainly not encourage any collusion between participants like
miners are doing (ie full nodes pools for example or miners creating
full nodes pools)
Le 04/05/2017 à 12:38, Tomas via bitcoin-dev a écrit :
> The ones that *could* pay non-mining full nodes are miners/pools, by
> outsourcing transaction selection using a different PoW. By doing so
> they could buy proof-of-uncensored-selection and proof-of-goodwill for
> a small fee.
>
> We would allow full nodes to generate and broadcast a template block
> which:
>
> * Does not contain a valid header yet
> * Contains the transaction selection
> * Contains a coinbase output with a predetermined part of the block
> reward (say 0.5%) to themselves
> * Contains a nonce for PoW of a predetermined currently ASIC resistant
> hash function behind a OP_RETURN.
>
> The template with the highest PoW since the last block would be
> leading. A miner/pool can then choose to use this instead of their
> own, adding the rest of the reward and the SHA nonce themselves. That
> way they would set up a competition among full nodes.
>
> This would of course be voluntary but provable, so maybe in a pool's
> interest to do this via naming and shaming.
>
> Tomas
> bitcrust
>
> On Wed, May 3, 2017, at 23:43, Ben Thompson via bitcoin-dev wrote:
>> I feel like this would be pointless as the vast majority of users
>> would likely download the blockchain from a node that was not
>> enforcing a tip requirement as it would seem like unnecessary cost as
>> in protocols such as BitTorrent there is no such tips in sharing
>> files and the blockchain distribution is in eccense the same thing.
>> However perhaps I am underestimating the generosity of node operators
>> but I feel that adding a cost to the blockchain (assuming that all
>> users add a tip requirement) would lead to centralisation.
>>
>> On Wed, 3 May 2017, 22:21 Erik Aronesty via bitcoin-dev,
>> <bitcoin-dev@lists.linuxfoundation.org
>> <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
>>
>> IDEA:
>> - Full nodes advertise a bitcoin address. Users that need to
>> download the block chain from that node can be encouraged to send
>> a tip to the peers that served them (by % served). Recommended
>> tip of 10mbit should be fine.
>>
>> - A full nodes can *require* a tip to download the blockchain.
>> If they do, users that don't specify a tip cannot use them.
>>
>> CONS:
>>
>> For some people, this may represent a barrier to hosting their
>> own full node. After all, if you have to pay $15 just to get a
>> copy of the blockchain, that just adds to the already expensive
>> prospect of hosting a full node.
>> PROS:
>>
>> As long as you manage to stay online, you should get your money
>> back and more. This is the an incentive for quality, long term
>> hosting.
>> In the long term, this should cause stable nodes to stick around
>> longer. It also discourages "installation spam" attacks on the
>> network.
>> Fees for other node operations can be considered if this is
>> successful.
>>
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--
Zcash wallets made simple: https://github.com/Ayms/zcash-wallets
Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets
Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
--------------812ABCBB7415E348EBCE50D8
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Strange idea, incentiving people to run full nodes should
certainly not depend on miners, should certainly not involve
another wasteful pow and should certainly not encourage any
collusion between participants like miners are doing (ie full
nodes pools for example or miners creating full nodes pools)<br>
</p>
<br>
<div class="moz-cite-prefix">Le 04/05/2017 à 12:38, Tomas via
bitcoin-dev a écrit :<br>
</div>
<blockquote
cite="mid:1493894309.1179269.965498864.6244705A@webmail.messagingengine.com"
type="cite">
<title></title>
<div>The ones that *could* pay non-mining full nodes are
miners/pools, by outsourcing transaction selection using a
different PoW. By doing so they could buy
proof-of-uncensored-selection and proof-of-goodwill for a small
fee.<br>
</div>
<div><br>
</div>
<div>We would allow full nodes to generate and broadcast a
template block which:<br>
</div>
<div><br>
</div>
<div>* Does not contain a valid header yet<br>
</div>
<div>* Contains the transaction selection<br>
</div>
<div>* Contains a coinbase output with a predetermined part of the
block reward (say 0.5%) to themselves<br>
</div>
<div>* Contains a nonce for PoW of a predetermined currently ASIC
resistant hash function behind a OP_RETURN.<br>
</div>
<div><br>
</div>
<div>The template with the highest PoW since the last block would
be leading. A miner/pool can then choose to use this instead of
their own, adding the rest of the reward and the SHA nonce
themselves. That way they would set up a competition among full
nodes.<br>
</div>
<div><br>
</div>
<div>This would of course be voluntary but provable, so maybe in a
pool's interest to do this via naming and shaming.<br>
</div>
<div><br>
</div>
<div>Tomas<br>
</div>
<div>bitcrust<br>
</div>
<div><br>
</div>
<div>On Wed, May 3, 2017, at 23:43, Ben Thompson via bitcoin-dev
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I feel like this would be pointless as the vast
majority of users would likely download the blockchain from a
node that was not enforcing a tip requirement as it would seem
like unnecessary cost as in protocols such as BitTorrent there
is no such tips in sharing files and the blockchain
distribution is in eccense the same thing. However perhaps I
am underestimating the generosity of node operators but I feel
that adding a cost to the blockchain (assuming that all users
add a tip requirement) would lead to centralisation.<br>
</div>
<div><span></span><br>
</div>
<div>
<div dir="ltr">On Wed, 3 May 2017, 22:21 Erik Aronesty via
bitcoin-dev, <<a moz-do-not-send="true"
href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>>
wrote:<br>
</div>
<blockquote
style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,
204, 204);padding-left:1ex;">
<div dir="ltr">
<div>
<div>
<div>
<div>IDEA:<br>
</div>
</div>
<div>- Full nodes advertise a bitcoin address. Users
that need to download the block chain from that node
can be encouraged to send a tip to the peers that
served them (by % served). Recommended tip of
10mbit should be fine.<br>
</div>
<div><br>
</div>
</div>
<div>- A full nodes can *require* a tip to download the
blockchain. If they do, users that don't specify a
tip cannot use them.<br>
</div>
<div><br>
</div>
</div>
<div>
<div>CONS:<br>
</div>
<div><br>
</div>
<div>For some people, this may represent a barrier to
hosting their own full node. After all, if you have
to pay $15 just to get a copy of the blockchain, that
just adds to the already expensive prospect of hosting
a full node. <br>
</div>
</div>
<div>PROS: <br>
</div>
<div>
<div><br>
</div>
<div>As long as you manage to stay online, you should
get your money back and more. This is the an
incentive for quality, long term hosting.<br>
</div>
</div>
<div>
<div>In the long term, this should cause stable nodes to
stick around longer. It also discourages
"installation spam" attacks on the network.<br>
</div>
</div>
<div>Fees for other node operations can be considered if
this is successful.<br>
</div>
<div>
<div><br>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
<div><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
bitcoin-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Zcash wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/zcash-wallets">https://github.com/Ayms/zcash-wallets</a>
Bitcoin wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-wallets">https://github.com/Ayms/bitcoin-wallets</a>
Get the torrent dynamic blocklist: <a class="moz-txt-link-freetext" href="http://peersm.com/getblocklist">http://peersm.com/getblocklist</a>
Check the 10 M passwords list: <a class="moz-txt-link-freetext" href="http://peersm.com/findmyass">http://peersm.com/findmyass</a>
Anti-spies and private torrents, dynamic blocklist: <a class="moz-txt-link-freetext" href="http://torrent-live.org">http://torrent-live.org</a>
Peersm : <a class="moz-txt-link-freetext" href="http://www.peersm.com">http://www.peersm.com</a>
torrent-live: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/torrent-live">https://github.com/Ayms/torrent-live</a>
node-Tor : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms/node-Tor">https://www.github.com/Ayms/node-Tor</a>
GitHub : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms">https://www.github.com/Ayms</a></pre>
</body>
</html>
--------------812ABCBB7415E348EBCE50D8--
|
