public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Potter QQ <165318903@qq.com>
To: "justusranvier@riseup.net" <justusranvier@riseup.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] The Bitcoin Node Market
Date: Tue, 16 Jun 2015 13:30:05 +0800	[thread overview]
Message-ID: <93C95467-E3A6-4247-9284-699A99B34904@qq.com> (raw)
In-Reply-To: <a9e2e033c786fb7f99bcf7505ad45f21@riseup.net>

No,Bitcoin 


发自我的 iPhone

> 在 2015年6月16日,13:28,justusranvier@riseup.net 写道:
> 
>> On 2015-06-16 03:49, Kevin Greene wrote:
>> ​Hah, 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 ​a
>> 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/listinf



  reply	other threads:[~2015-06-16  5:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 21:23 [Bitcoin-development] comments on BIP 100 Adam Back
2015-06-14 22:23 ` Mike Hearn
2015-06-14 23:58   ` Adam Back
2015-06-15  0:53     ` Eric Lombrozo
2015-06-15  0:55       ` Eric Lombrozo
2015-06-15  4:11       ` Peter Todd
2015-06-15  4:43         ` Eric Lombrozo
2015-06-15  9:27     ` Mike Hearn
2015-06-15  9:39       ` Eric Lombrozo
2015-06-15 10:24       ` Pieter Wuille
2015-06-15 10:36         ` Mike Hearn
2015-06-15 10:40           ` Pieter Wuille
2015-06-15 10:50             ` Mike Hearn
2015-06-15 11:16               ` Rebroad (sourceforge)
2015-06-15 17:53                 ` Raystonn .
2015-06-15 18:14                   ` Adam Back
2015-06-15 18:57                     ` [Bitcoin-development] The Bitcoin Node Market Raystonn .
2015-06-15 19:18                       ` sickpig
2015-06-15 19:36                         ` Raystonn .
2015-06-15 20:12                           ` sickpig
2015-06-16  3:30                             ` Kevin Greene
2015-06-16  3:41                               ` Luke Dashjr
2015-06-16  3:49                                 ` Kevin Greene
2015-06-16  4:05                                   ` Kevin Greene
2015-06-16  4:12                                   ` Aaron Voisine
2015-06-16  5:28                                   ` justusranvier
2015-06-16  5:30                                     ` Potter QQ [this message]
2015-06-16  7:55                                     ` Aaron Voisine
2015-06-16 13:32                                       ` justusranvier
2015-06-16 17:04                                         ` Aaron Voisine
2015-06-16 17:22                                         ` Aaron Voisine
2015-06-16 15:52                                       ` devrandom
2015-06-15  4:43   ` [Bitcoin-development] comments on BIP 100 Peter Todd
2015-06-15  9:06     ` Mike Hearn
2015-06-15  2:28 ` Jeff Garzik
2015-06-15  2:44   ` Jeff Garzik
2015-06-16  4:38 [Bitcoin-development] The Bitcoin Node Market Raystonn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=93C95467-E3A6-4247-9284-699A99B34904@qq.com \
    --to=165318903@qq.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=justusranvier@riseup.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox