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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <raystonn@hotmail.com>) id 1Z4aBd-0006pX-BZ
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 19:36:49 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of hotmail.com
designates 65.55.34.217 as permitted sender)
client-ip=65.55.34.217; envelope-from=raystonn@hotmail.com;
helo=COL004-OMC4S15.hotmail.com;
Received: from col004-omc4s15.hotmail.com ([65.55.34.217])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1Z4aBb-0001Uj-Ty
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 19:36:49 +0000
Received: from COL131-DS9 ([65.55.34.201]) by COL004-OMC4S15.hotmail.com over
TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751);
Mon, 15 Jun 2015 12:36:42 -0700
X-TMN: [fB2ghhDzbTG1/dXXIV+H8jC9SePCXfEZ]
X-Originating-Email: [raystonn@hotmail.com]
Message-ID: <COL131-DS97146D8FC6E7EC7D3F5D9CDB80@phx.gbl>
From: "Raystonn ." <raystonn@hotmail.com>
To: <sickpig@gmail.com>
References: <CALqxMTHrnSS9MGgKO-5+=fVhiOOvk12Recs11S0PcSUxQT1wdQ@mail.gmail.com><CANEZrP1nx9rNf1q-nubP77U8RMABuLtmEB_P7UpY2zyFf-Ns-w@mail.gmail.com><CALqxMTENbj+E7ypJASrM1r04eW3kYe+afwy+Rt3i9ubeT-=2mA@mail.gmail.com><CANEZrP0Z_EOmVgbvVmYDvegm6jfd1cKB52acXHocjRuM-qGEog@mail.gmail.com><CAPg+sBgc0i-XsN=g0V4Y0bko-Xb1AT5x=UWDa+opL3eFbBmJfA@mail.gmail.com><CANEZrP0eGDTafK+ZUBNcQBOe2JU_PqZVXMt0Ds-b8Ley7kbGrA@mail.gmail.com><CAPg+sBiPhhrBh8f3QxJLtoysfywtVFSo2RH0WXVR+vpX9z6+HQ@mail.gmail.com><CANEZrP10gn+969d-oe-8Em9ipe4DOP9q0WkNtL6u-6V5aphkPQ@mail.gmail.com><CAFBxzAAExA-aE+8o-+HGQtnuwWuWpkt8Lbgxvh7hT64XkMKOPg@mail.gmail.com><COL131-DS5331AE0C03A2BF6E0553ECDB80@phx.gbl><CALqxMTF2T0Wgt15bmjkpMK199vhwH+ufYw+LJU7AEzx4X7dykQ@mail.gmail.com><COL131-DS1BD3015F98131D224B0D6CDB80@phx.gbl>
<CA+c4ZoyjmfFO+3+Zqvjabk1KuezuV42pvPNa57JPzJCAePJ5hw@mail.gmail.com>
In-Reply-To: <CA+c4ZoyjmfFO+3+Zqvjabk1KuezuV42pvPNa57JPzJCAePJ5hw@mail.gmail.com>
Date: Mon, 15 Jun 2015 12:36:32 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0012_01D0A767.E9291C40"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3555.308
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308
X-OriginalArrivalTime: 15 Jun 2015 19:36:42.0416 (UTC)
FILETIME=[9B33FB00:01D0A7A2]
X-Spam-Score: -0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(raystonn[at]hotmail.com)
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [65.55.34.217 listed in list.dnswl.org]
-0.0 SPF_PASS SPF: sender matches SPF record
-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain 1.0 HTML_MESSAGE BODY: HTML included in message
1.0 FREEMAIL_REPLY From and body contain different freemails
-0.1 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1Z4aBb-0001Uj-Ty
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] The Bitcoin Node Market
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: Mon, 15 Jun 2015 19:36:49 -0000
------=_NextPart_000_0012_01D0A767.E9291C40
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
I am only partially through the content at the below link, and I am very =
impressed. Has Justus Ranvier began work on implementation of the ideas =
contained therein?
From: sickpig@gmail.com=20
Sent: Monday, June 15, 2015 12:18 PM
To: Raystonn .=20
Cc: Bitcoin Dev=20
Subject: Re: [Bitcoin-development] The Bitcoin Node Market
Sorry for top posting and the brevity but I'm typing from my phone
You shoud be interested in this post by Justus Ranvier then:
https://bitcoinism.liberty.me/economic-fallacies-and-the-block-size-limit=
-part-2-price-discovery/
On Jun 15, 2015 8:57 PM, "Raystonn ." <raystonn@hotmail.com> wrote:
I have been toying with an idea and figured I'd run it by everyone =
here
before investing further time in it. The goal here is to make it
sustainable, and perhaps profitable, to run full nodes on the Bitcoin
Network in the long term.
- Nodes can participate in a market wherein they are paid by nodes, =
wallets,
and other services to supply Bitcoin Network data. Payment should be =
based
on the cost imposed on the Node to do the work and send the data, but =
can be
set in any way the node operator desires. It's a free market.
- Nodes that are mostly leeching data from the Bitcoin Network, such =
as
those that do not receive inbound connections to port 8333, will send
payments to the nodes they connect to, but will likely receive no =
payments
from other nodes, wallets, and other services.
- Nodes that are providing balanced full service to the Bitcoin =
Network will
tend to have a balance of payments coming in and going out with =
regards to
other balanced full service nodes, leaving them revenue neutral there. =
But
they will receive payments from leech nodes, wallets, and other =
services.
The net effect here is that the cost to run nodes will be shared by =
those
who are using the Bitcoin network but not contributing by running a =
full
node. A market will develop for fees to connect to the Bitcoin =
Network
which should help cover the cost of running the Network. It's still
possible to continue offering access to your node for free as there is
nothing forcing you to charge a fee. But this isn't very sustainable
long-run. Market efficiencies should eventually mean nodes take in =
only
what is required to keep the Network operational.
Raystonn
=
-------------------------------------------------------------------------=
-----
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
------=_NextPart_000_0012_01D0A767.E9291C40
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<HTML><HEAD></HEAD>
<BODY dir=3Dltr>
<DIV dir=3Dltr>
<DIV style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'; COLOR: #000000">
<DIV>I am only partially through the content at the below link, and I am =
very=20
impressed. Has Justus Ranvier began work on implementation of the =
ideas=20
contained therein?</DIV>
<DIV> </DIV>
<DIV=20
style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: =
"Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; =
DISPLAY: inline'>
<DIV style=3D"FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A =
title=3Dsickpig@gmail.com=20
href=3D"mailto:sickpig@gmail.com">sickpig@gmail.com</A> </DIV>
<DIV><B>Sent:</B> Monday, June 15, 2015 12:18 PM</DIV>
<DIV><B>To:</B> <A title=3Draystonn@hotmail.com=20
href=3D"mailto:raystonn@hotmail.com">Raystonn .</A> </DIV>
<DIV><B>Cc:</B> <A title=3Dbitcoin-development@lists.sourceforge.net=20
href=3D"mailto:bitcoin-development@lists.sourceforge.net">Bitcoin =
Dev</A> </DIV>
<DIV><B>Subject:</B> Re: [Bitcoin-development] The Bitcoin Node=20
Market</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV=20
style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: =
"Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; =
DISPLAY: inline'>
<P dir=3Dltr>Sorry for top posting and the brevity but I'm typing from =
my=20
phone</P>
<P dir=3Dltr>You shoud be interested in this post by Justus Ranvier =
then:</P>
<P dir=3Dltr><A=20
href=3D"https://bitcoinism.liberty.me/economic-fallacies-and-the-block-si=
ze-limit-part-2-price-discovery/">https://bitcoinism.liberty.me/economic-=
fallacies-and-the-block-size-limit-part-2-price-discovery/</A></P>
<DIV class=3Dgmail_quote>On Jun 15, 2015 8:57 PM, "Raystonn ." <<A=20
href=3D"mailto:raystonn@hotmail.com">raystonn@hotmail.com</A>> =
wrote:<BR=20
type=3D"attribution">
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc =
1px solid">I=20
have been toying with an idea and figured I'd run it by everyone=20
here<BR>before investing further time in it. The goal here is to =
make=20
it<BR>sustainable, and perhaps profitable, to run full nodes on the=20
Bitcoin<BR>Network in the long term.<BR><BR>- Nodes can participate in =
a=20
market wherein they are paid by nodes, wallets,<BR>and other services =
to=20
supply Bitcoin Network data. Payment should be based<BR>on the =
cost=20
imposed on the Node to do the work and send the data, but can =
be<BR>set in any=20
way the node operator desires. It's a free market.<BR>- Nodes =
that are=20
mostly leeching data from the Bitcoin Network, such as<BR>those that =
do not=20
receive inbound connections to port 8333, will send<BR>payments to the =
nodes=20
they connect to, but will likely receive no payments<BR>from other =
nodes,=20
wallets, and other services.<BR>- Nodes that are providing balanced =
full=20
service to the Bitcoin Network will<BR>tend to have a balance of =
payments=20
coming in and going out with regards to<BR>other balanced full service =
nodes,=20
leaving them revenue neutral there. But<BR>they will receive =
payments=20
from leech nodes, wallets, and other services.<BR><BR>The net effect =
here is=20
that the cost to run nodes will be shared by those<BR>who are using =
the=20
Bitcoin network but not contributing by running a full<BR>node. =
A market=20
will develop for fees to connect to the Bitcoin Network<BR>which =
should help=20
cover the cost of running the Network. It's still<BR>possible to =
continue offering access to your node for free as there is<BR>nothing =
forcing=20
you to charge a fee. But this isn't very =
sustainable<BR>long-run. =20
Market efficiencies should eventually mean nodes take in only<BR>what =
is=20
required to keep the Network=20
=
operational.<BR><BR>Raystonn<BR><BR><BR>---------------------------------=
---------------------------------------------<BR>________________________=
_______________________<BR>Bitcoin-development=20
mailing list<BR><A=20
=
href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develop=
ment@lists.sourceforge.net</A><BR><A=20
=
href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development"=
=20
rel=3Dnoreferrer=20
=
target=3D_blank>https://lists.sourceforge.net/lists/listinfo/bitcoin-deve=
lopment</A><BR></BLOCKQUOTE></DIV></DIV></DIV></DIV></BODY></HTML>
------=_NextPart_000_0012_01D0A767.E9291C40--
|
