path: root/a0/f9c80a7b7b0aa5b9f30f8b323fcdc0b3a68d6e

Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <kgreenek@gmail.com>) id 1Z4hai-0000aQ-ED
	for bitcoin-development@lists.sourceforge.net;
	Tue, 16 Jun 2015 03:31:12 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.50 as permitted sender)
	client-ip=74.125.82.50; envelope-from=kgreenek@gmail.com;
	helo=mail-wg0-f50.google.com; 
Received: from mail-wg0-f50.google.com ([74.125.82.50])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Z4hag-0004wQ-G1
	for bitcoin-development@lists.sourceforge.net;
	Tue, 16 Jun 2015 03:31:12 +0000
Received: by wgbhy7 with SMTP id hy7so2753888wgb.2
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 15 Jun 2015 20:31:04 -0700 (PDT)
X-Received: by 10.180.188.109 with SMTP id fz13mr1786985wic.74.1434425464469; 
	Mon, 15 Jun 2015 20:31:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.27.20.1 with HTTP; Mon, 15 Jun 2015 20:30:44 -0700 (PDT)
In-Reply-To: <CA+c4Zoy6U9RXH3Qw15sXXnaeYL-9PFbnTp=VLAJsvpC_zoAK_A@mail.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>
	<COL131-DS97146D8FC6E7EC7D3F5D9CDB80@phx.gbl>
	<CA+c4Zoy6U9RXH3Qw15sXXnaeYL-9PFbnTp=VLAJsvpC_zoAK_A@mail.gmail.com>
From: Kevin Greene <kgreenek@gmail.com>
Date: Mon, 15 Jun 2015 20:30:44 -0700
Message-ID: <CAEY8wq41ftFA1ObyUWiRGOgebwqDCAw_j+hU6_wfcXv5GSZaJw@mail.gmail.com>
To: "sickpig@gmail.com" <sickpig@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c25f68443d4605189a34ac
X-Spam-Score: 0.4 (/)
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
	(kgreenek[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	1.0 FREEMAIL_REPLY         From and body contain different freemails
X-Headers-End: 1Z4hag-0004wQ-G1
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: Tue, 16 Jun 2015 03:31:12 -0000

--001a11c25f68443d4605189a34ac
Content-Type: text/plain; charset=UTF-8

Would SPV wallets have to pay to connect to the network too? From the
user's perspective, it would be somewhat upsetting (and confusing) to see
your balance slowly draining every time you open your wallet app. It would
also tie up outputs every time you open up your wallet. You may go to pay
for something in a coffee shop, only to find that you can't spend your
bitcoin because the wallet had to create a transaction to pay to sync with
the network.

Also, users of centralized wallet services like Coinbase would not have to
pay that fee; but users of native wallets like breadwallet would have no
such option. This incentivizes users to use centralized wallets.

So this is kind of imposing a worse user experience on users who want to
use bitcoin the "right" way. That doesn't seem like a good thing to me :/

On Mon, Jun 15, 2015 at 1:12 PM, sickpig@gmail.com <sickpig@gmail.com>
wrote:

> Hi Raystonn
>
> On Mon, Jun 15, 2015 at 9:36 PM, Raystonn . <raystonn@hotmail.com> wrote:
> >
> > 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?
>
> I don't know if he or someone else has begun writing code to implement
> what was described in the liked post, but I'm sure he will reply to
> you since he's subscribed to this mailing list.
>
>
> >
> >
> >
> > From: sickpig@gmail.com
> > Sent: Monday, June 15, 2015 12:18 PM
> > To: Raystonn .
> > Cc: Bitcoin Dev
> > 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
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--001a11c25f68443d4605189a34ac
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"color:#336666">Would=
 SPV wallets have to pay to connect to the network too? From the user&#39;s=
 perspective, it would be somewhat upsetting (and confusing) to see your ba=
lance slowly draining every time you open your wallet app. It would also ti=
e up outputs every time you open up your wallet. You may go to pay for some=
thing in a coffee shop, only to find that you can&#39;t spend your bitcoin =
because the wallet had to create a transaction to pay to sync with the netw=
ork.</div><div class=3D"gmail_default" style=3D"color:#336666"><br></div><d=
iv class=3D"gmail_default" style=3D"color:#336666">Also, users of centraliz=
ed wallet services like Coinbase would not have to pay that fee; but users =
of native wallets like breadwallet would have no such option. This incentiv=
izes users to use centralized wallets.</div><div class=3D"gmail_default" st=
yle=3D"color:#336666"><br></div><div class=3D"gmail_default" style=3D"color=
:#336666">So this is kind of imposing a worse user experience on users who =
want to use bitcoin the &quot;right&quot; way. That doesn&#39;t seem like a=
 good thing to me :/</div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Mon, Jun 15, 2015 at 1:12 PM, <a href=3D"mailto:sickpig=
@gmail.com">sickpig@gmail.com</a> <span dir=3D"ltr">&lt;<a href=3D"mailto:s=
ickpig@gmail.com" target=3D"_blank">sickpig@gmail.com</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">Hi Raystonn<br>
<span class=3D""><br>
On Mon, Jun 15, 2015 at 9:36 PM, Raystonn . &lt;<a href=3D"mailto:raystonn@=
hotmail.com">raystonn@hotmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; I am only partially through the content at the below link, and I am ve=
ry impressed.=C2=A0 Has Justus Ranvier began work on implementation of the =
ideas contained therein?<br>
<br>
</span>I don&#39;t know if he or someone else has begun writing code to imp=
lement<br>
what was described in the liked post, but I&#39;m sure he will reply to<br>
you since he&#39;s subscribed to this mailing list.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; From: <a href=3D"mailto:sickpig@gmail.com">sickpig@gmail.com</a><br>
&gt; Sent: Monday, June 15, 2015 12:18 PM<br>
&gt; To: Raystonn .<br>
&gt; Cc: Bitcoin Dev<br>
&gt; Subject: Re: [Bitcoin-development] The Bitcoin Node Market<br>
&gt;<br>
&gt;<br>
&gt; Sorry for top posting and the brevity but I&#39;m typing from my phone=
<br>
&gt;<br>
&gt; You shoud be interested in this post by Justus Ranvier then:<br>
&gt;<br>
&gt; <a href=3D"https://bitcoinism.liberty.me/economic-fallacies-and-the-bl=
ock-size-limit-part-2-price-discovery/" rel=3D"noreferrer" target=3D"_blank=
">https://bitcoinism.liberty.me/economic-fallacies-and-the-block-size-limit=
-part-2-price-discovery/</a><br>
&gt;<br>
&gt; On Jun 15, 2015 8:57 PM, &quot;Raystonn .&quot; &lt;<a href=3D"mailto:=
raystonn@hotmail.com">raystonn@hotmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; I have been toying with an idea and figured I&#39;d run it by ever=
yone here<br>
&gt;&gt; before investing further time in it.=C2=A0 The goal here is to mak=
e it<br>
&gt;&gt; sustainable, and perhaps profitable, to run full nodes on the Bitc=
oin<br>
&gt;&gt; Network in the long term.<br>
&gt;&gt;<br>
&gt;&gt; - Nodes can participate in a market wherein they are paid by nodes=
, wallets,<br>
&gt;&gt; and other services to supply Bitcoin Network data.=C2=A0 Payment s=
hould be based<br>
&gt;&gt; on the cost imposed on the Node to do the work and send the data, =
but can be<br>
&gt;&gt; set in any way the node operator desires.=C2=A0 It&#39;s a free ma=
rket.<br>
&gt;&gt; - Nodes that are mostly leeching data from the Bitcoin Network, su=
ch as<br>
&gt;&gt; those that do not receive inbound connections to port 8333, will s=
end<br>
&gt;&gt; payments to the nodes they connect to, but will likely receive no =
payments<br>
&gt;&gt; from other nodes, wallets, and other services.<br>
&gt;&gt; - Nodes that are providing balanced full service to the Bitcoin Ne=
twork will<br>
&gt;&gt; tend to have a balance of payments coming in and going out with re=
gards to<br>
&gt;&gt; other balanced full service nodes, leaving them revenue neutral th=
ere.=C2=A0 But<br>
&gt;&gt; they will receive payments from leech nodes, wallets, and other se=
rvices.<br>
&gt;&gt;<br>
&gt;&gt; The net effect here is that the cost to run nodes will be shared b=
y those<br>
&gt;&gt; who are using the Bitcoin network but not contributing by running =
a full<br>
&gt;&gt; node.=C2=A0 A market will develop for fees to connect to the Bitco=
in Network<br>
&gt;&gt; which should help cover the cost of running the Network.=C2=A0 It&=
#39;s still<br>
&gt;&gt; possible to continue offering access to your node for free as ther=
e is<br>
&gt;&gt; nothing forcing you to charge a fee.=C2=A0 But this isn&#39;t very=
 sustainable<br>
&gt;&gt; long-run.=C2=A0 Market efficiencies should eventually mean nodes t=
ake in only<br>
&gt;&gt; what is required to keep the Network operational.<br>
&gt;&gt;<br>
&gt;&gt; Raystonn<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; ------------------------------------------------------------------=
------------<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Bitcoin-development mailing list<br>
&gt;&gt; <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitco=
in-development@lists.sourceforge.net</a><br>
&gt;&gt; <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment" rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.n=
et/lists/listinfo/bitcoin-development</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/=
listinfo/bitcoin-development</a><br>
</div></div></blockquote></div><br></div>

--001a11c25f68443d4605189a34ac--