summaryrefslogtreecommitdiff
path: root/98/47485b95f7be10a2dd0653e29844d3e9047d6b
blob: 27cfabc27c38e5198c5b398b0b5df7c7742012db (plain)
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
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <165318903@qq.com>) id 1Z4jhJ-0007pY-CO
	for bitcoin-development@lists.sourceforge.net;
	Tue, 16 Jun 2015 05:46:09 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of qq.com
	designates 14.17.43.214 as permitted sender)
	client-ip=14.17.43.214; envelope-from=165318903@qq.com;
	helo=smtpbg329.qq.com; 
Received: from smtpbg329.qq.com ([14.17.43.214])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1Z4jhC-0008MY-Mv
	for bitcoin-development@lists.sourceforge.net;
	Tue, 16 Jun 2015 05:46:09 +0000
X-QQ-mid: esmtp27t1434432597t592t11389
Received: from [10.24.75.53] (unknown [113.200.205.208])
	by esmtp4.qq.com (ESMTP) with 
	id ; Tue, 16 Jun 2015 13:29:56 +0800 (CST)
X-QQ-SSF: 0000000000000060FG101F00000000Z
X-QQ-FEAT: tZ7SKDDlSpG7Xk5XuK7+6OEQEuZaSuy2EvX+R4mpZ/a7OcP/+wb9OB9gKsLlw
	AARWy+lpJFgM85Ssy0Cs2hT32nyUez35Fp126ckYRva8J2M7pulbdd2Srikc/rWAuiGoBDb
	gpyCBNXHY9zTEr/+9oHwI7JuME/nDwnrDRQLX4AtwlagX1TV0HcsPTpFdnGUemO1ET61Tfm
	QMmAvyjEDiBYCuIf7Z+dV1DlUGBrdqr7lz0SVfTs3bFAsKKJg2JmM
X-QQ-GoodBg: 0
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
From: Potter QQ <165318903@qq.com>
X-Mailer: iPhone Mail (12B436)
In-Reply-To: <a9e2e033c786fb7f99bcf7505ad45f21@riseup.net>
Date: Tue, 16 Jun 2015 13:30:05 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <93C95467-E3A6-4247-9284-699A99B34904@qq.com>
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>
To: "justusranvier@riseup.net" <justusranvier@riseup.net>
X-QQ-SENDSIZE: 520
X-Spam-Score: -1.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
	(165318903[at]qq.com)
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [14.17.43.214 listed in list.dnswl.org]
	-0.0 SPF_HELO_PASS          SPF: HELO matches SPF record
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
	0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
	digit (165318903[at]qq.com)
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid
X-Headers-End: 1Z4jhC-0008MY-Mv
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 05:46:09 -0000

No,Bitcoin=20


=E5=8F=91=E8=87=AA=E6=88=91=E7=9A=84 iPhone

> =E5=9C=A8 2015=E5=B9=B46=E6=9C=8816=E6=97=A5=EF=BC=8C13:28=EF=BC=8Cjustusr=
anvier@riseup.net =E5=86=99=E9=81=93=EF=BC=9A
>=20
>> On 2015-06-16 03:49, Kevin Greene wrote:
>> =E2=80=8BHah, fair enough, there is no such thing as the "right" way to d=
o
>> 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=20
>> SPV is
>> the best way that exists for mobile phones to participate in the=20
>> network in
>> a decentralized way. This proposal makes the user experience for mobile
>> wallets a little more confusing and annoying.
>=20
> Suppose a billion mobile phones wanted to run SPV wallets tomorrow. Who=20=

> would provide the nodes they would need connect to? The decentralization=20=

> fairy?
>=20
> There's absolutely no reason that paying for connectivity would be any=20
> more confusing or annoying than transaction fees are.
>=20
> If some full nodes in the network started offering paid connection=20
> slots, that would just mean that users who checked the "pay subscription=20=

> fee" box in their wallet configuration would have an easier time=20
> connecting than the users who did't, just like how your transaction=20
> might eventually get mined without a fee but paying one makes it faster=20=

> and more probable.
>=20
> --------------------------------------------------------------------------=
----
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinf