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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <raystonn@hotmail.com>) id 1Z4ZZO-0001Jp-2E
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 18:57:18 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of hotmail.com
designates 65.55.34.211 as permitted sender)
client-ip=65.55.34.211; envelope-from=raystonn@hotmail.com;
helo=COL004-OMC4S9.hotmail.com;
Received: from col004-omc4s9.hotmail.com ([65.55.34.211])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1Z4ZZN-0006uM-Ad
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 18:57:18 +0000
Received: from COL131-DS1 ([65.55.34.201]) by COL004-OMC4S9.hotmail.com over
TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751);
Mon, 15 Jun 2015 11:57:11 -0700
X-TMN: [OmDuCXaciNI3Wd7hucm7Vi11Hfs1u0Yk]
X-Originating-Email: [raystonn@hotmail.com]
Message-ID: <COL131-DS1BD3015F98131D224B0D6CDB80@phx.gbl>
From: "Raystonn ." <raystonn@hotmail.com>
To: "Bitcoin Dev" <bitcoin-development@lists.sourceforge.net>
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>
In-Reply-To: <CALqxMTF2T0Wgt15bmjkpMK199vhwH+ufYw+LJU7AEzx4X7dykQ@mail.gmail.com>
Date: Mon, 15 Jun 2015 11:57:02 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original
Content-Transfer-Encoding: 7bit
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 18:57:11.0736 (UTC)
FILETIME=[162AEB80:01D0A79D]
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.2 STOX_REPLY_TYPE STOX_REPLY_TYPE
-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 SPF_PASS SPF: sender matches SPF record
-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [65.55.34.211 listed in list.dnswl.org]
1.9 STOX_REPLY_TYPE_WITHOUT_QUOTES STOX_REPLY_TYPE_WITHOUT_QUOTES
-0.1 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1Z4ZZN-0006uM-Ad
Subject: [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 18:57:18 -0000
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
|
