From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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: From: "Raystonn ." To: References: In-Reply-To: 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 ." 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
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?
 
 
Sent: Monday, June 15, 2015 12:18 PM
Subject: Re: [Bitcoin-development] The Bitcoin Node=20 Market
 

Sorry for top posting and the brevity but I'm typing from = my=20 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=20 have been toying with an idea and figured I'd run it by everyone=20 here
before investing further time in it.  The goal here is to = make=20 it
sustainable, and perhaps profitable, to run full nodes on the=20 Bitcoin
Network in the long term.

- Nodes can participate in = a=20 market wherein they are paid by nodes, wallets,
and other services = to=20 supply Bitcoin Network data.  Payment should be based
on the = cost=20 imposed on the Node to do the work and send the data, but can = be
set in any=20 way the node operator desires.  It's a free market.
- Nodes = that are=20 mostly leeching data from the Bitcoin Network, such as
those that = do not=20 receive inbound connections to port 8333, will send
payments to the = nodes=20 they connect to, but will likely receive no payments
from other = nodes,=20 wallets, and other services.
- Nodes that are providing balanced = full=20 service to the Bitcoin Network will
tend to have a balance of = payments=20 coming in and going out with regards to
other balanced full service = nodes,=20 leaving them revenue neutral there.  But
they will receive = payments=20 from leech nodes, wallets, and other services.

The net effect = here is=20 that the cost to run nodes will be shared by those
who are using = the=20 Bitcoin network but not contributing by running a full
node.  = A market=20 will develop for fees to connect to the Bitcoin Network
which = should help=20 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=20 you to charge a fee.  But this isn't very = sustainable
long-run. =20 Market efficiencies should eventually mean nodes take in only
what = is=20 required to keep the Network=20 = operational.

Raystonn


---------------------------------= ---------------------------------------------
________________________= _______________________
Bitcoin-development=20 mailing list
Bitcoin-develop= ment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-deve= lopment
------=_NextPart_000_0012_01D0A767.E9291C40--