Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <voisine@gmail.com>) id 1Z4lif-0005wZ-Le for bitcoin-development@lists.sourceforge.net; Tue, 16 Jun 2015 07:55:41 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.176 as permitted sender) client-ip=209.85.220.176; envelope-from=voisine@gmail.com; helo=mail-qk0-f176.google.com; Received: from mail-qk0-f176.google.com ([209.85.220.176]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z4lie-0002k0-Jt for bitcoin-development@lists.sourceforge.net; Tue, 16 Jun 2015 07:55:41 +0000 Received: by qkbp125 with SMTP id p125so587694qkb.2 for <bitcoin-development@lists.sourceforge.net>; Tue, 16 Jun 2015 00:55:35 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.140.97.136 with SMTP id m8mr41116282qge.32.1434441335206; Tue, 16 Jun 2015 00:55:35 -0700 (PDT) Received: by 10.140.91.37 with HTTP; Tue, 16 Jun 2015 00:55:35 -0700 (PDT) In-Reply-To: <a9e2e033c786fb7f99bcf7505ad45f21@riseup.net> References: <CALqxMTHrnSS9MGgKO-5+=fVhiOOvk12Recs11S0PcSUxQT1wdQ@mail.gmail.com> <CA+c4Zoy6U9RXH3Qw15sXXnaeYL-9PFbnTp=VLAJsvpC_zoAK_A@mail.gmail.com> <CAEY8wq41ftFA1ObyUWiRGOgebwqDCAw_j+hU6_wfcXv5GSZaJw@mail.gmail.com> <201506160341.10994.luke@dashjr.org> <CAEY8wq4SOddGUJNqkrdhhfQEn4tXehCWiifk-P=PYUdfFcXFTQ@mail.gmail.com> <a9e2e033c786fb7f99bcf7505ad45f21@riseup.net> Date: Tue, 16 Jun 2015 00:55:35 -0700 Message-ID: <CACq0ZD5uYikAfVuep8XCgEs-53NbF-SYhvm4qneZsEQdgd=6rw@mail.gmail.com> From: Aaron Voisine <voisine@gmail.com> To: Justus Ranvier <justusranvier@riseup.net> Content-Type: multipart/alternative; boundary=001a113a5d523c780d05189de6c0 X-Spam-Score: -0.6 (/) 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 (voisine[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 X-Headers-End: 1Z4lie-0002k0-Jt 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 07:55:41 -0000 --001a113a5d523c780d05189de6c0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Suppose a billion mobile phones wanted to run SPV wallets tomorrow. Who > would provide the nodes they would need connect to? The SPV wallet author would if they wanted their wallet to function. Aaron Voisine co-founder and CEO breadwallet.com On Mon, Jun 15, 2015 at 10:28 PM, <justusranvier@riseup.net> wrote: > On 2015-06-16 03:49, Kevin Greene wrote: > > =E2=80=8BHah, fair enough, there is no such thing as the "right" way to= do > > anything. But I still think punishing users who use SPV wallets is =E2= =80=8Ba > > less-than-ideal way to incentive people to run full nodes. Right now > > SPV is > > the best way that exists for mobile phones to participate in the > > network in > > a decentralized way. This proposal makes the user experience for mobile > > wallets a little more confusing and annoying. > > Suppose a billion mobile phones wanted to run SPV wallets tomorrow. Who > would provide the nodes they would need connect to? The decentralization > fairy? > > There's absolutely no reason that paying for connectivity would be any > more confusing or annoying than transaction fees are. > > If some full nodes in the network started offering paid connection > slots, that would just mean that users who checked the "pay subscription > fee" box in their wallet configuration would have an easier time > connecting than the users who did't, just like how your transaction > might eventually get mined without a fee but paying one makes it faster > and more probable. > > > -------------------------------------------------------------------------= ----- > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --001a113a5d523c780d05189de6c0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">>=C2=A0<span style=3D"font-size:13px">Suppose a billion= mobile phones wanted to run SPV wallets tomorrow. Who</span><br style=3D"f= ont-size:13px"><span style=3D"font-size:13px">> w</span><span class=3D""= tabindex=3D"0" style=3D"font-size:13px"><span class=3D"">ould pro</span></= span><span style=3D"font-size:13px">vide the nodes they would need connect = to?=C2=A0</span><div><span style=3D"font-size:13px"><br></span></div><div><= span style=3D"font-size:13px">The SPV wallet author would if they wanted th= eir wallet to function.</span></div></div><div class=3D"gmail_extra"><br cl= ear=3D"all"><div><div class=3D"gmail_signature"><div dir=3D"ltr"><div><div = dir=3D"ltr"><div><br>Aaron Voisine</div><div>co-founder and CEO<br><a href= =3D"http://breadwallet.com" target=3D"_blank">breadwallet.com</a></div></di= v></div></div></div></div> <br><div class=3D"gmail_quote">On Mon, Jun 15, 2015 at 10:28 PM, <span dir= =3D"ltr"><<a href=3D"mailto:justusranvier@riseup.net" target=3D"_blank">= justusranvier@riseup.net</a>></span> wrote:<br><blockquote class=3D"gmai= l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left= :1ex"><span class=3D"">On 2015-06-16 03:49, Kevin Greene wrote:<br> > =E2=80=8BHah, fair enough, there is no such thing as the "right&q= uot; way to do<br> > anything. But I still think punishing users who use SPV wallets is =E2= =80=8Ba<br> > less-than-ideal way to incentive people to run full nodes. Right now<b= r> > SPV is<br> > the best way that exists for mobile phones to participate in the<br> > network in<br> > a decentralized way. This proposal makes the user experience for mobil= e<br> > wallets a little more confusing and annoying.<br> <br> </span>Suppose a billion mobile phones wanted to run SPV wallets tomorrow. = Who<br> would provide the nodes they would need connect to? The decentralization<br= > fairy?<br> <br> There's absolutely no reason that paying for connectivity would be any<= br> more confusing or annoying than transaction fees are.<br> <br> If some full nodes in the network started offering paid connection<br> slots, that would just mean that users who checked the "pay subscripti= on<br> fee" box in their wallet configuration would have an easier time<br> connecting than the users who did't, just like how your transaction<br> might eventually get mined without a fee but paying one makes it faster<br> and more probable.<br> <div class=3D"HOEnZb"><div class=3D"h5"><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> --001a113a5d523c780d05189de6c0--