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
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WmHjx-0006qA-7v
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 07:12:05 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.176 as permitted sender)
client-ip=74.125.82.176; envelope-from=jgarzik@bitpay.com;
helo=mail-we0-f176.google.com;
Received: from mail-we0-f176.google.com ([74.125.82.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WmHjw-0006Rp-5r
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 07:12:05 +0000
Received: by mail-we0-f176.google.com with SMTP id q59so4933903wes.7
for <bitcoin-development@lists.sourceforge.net>;
Mon, 19 May 2014 00:11:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type:content-transfer-encoding;
bh=/P/kJliiUxYTtUoam3YUO2CxlI9emePtgAX7m1g4GIQ=;
b=kYuGRv0ieWdbuEjQsSKXHmg/gCo0hR01jPBXFzT2EEckY2cVOjLvtDGFvEZSli1liZ
UP6bTA+zkQ4co9eJ3NX26syFpXKH+mEHrozCV43FAAiRMHCFrzPs0Qau8cxoAvuwOGhx
H+uANSnskIfSYcYmWN1UaIjhn//d/qt0nEB+SLdIkSv/qz5oTDtwvjn/SidieRB68Yap
+gaitzczSd2yKDxNuIOOSgRpPfegciRYQv1sVKw1DnYlcaYXOLqaXHWL0IhJbk56oAT1
r2YTGr+w3RwU5VygSLJTTb8OgnAQrF1BI2d3xI1tH0Z9RN9+Nx5I3Ou3bX9pWqIDLcvj
ghXA==
X-Gm-Message-State: ALoCoQmJHPEGIQUsOma3CvQchFqiL3VgJytl5oW94Brg1QRCaNVeV5QB/zBkiXEo6vcTBnU9Wpxy
X-Received: by 10.180.72.136 with SMTP id d8mr11057907wiv.36.1400483517907;
Mon, 19 May 2014 00:11:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.240.166 with HTTP; Mon, 19 May 2014 00:11:37 -0700 (PDT)
In-Reply-To: <CA+8=xu+GPykmKdAjxLdRA3QoCPR8azervT9uO-GVraNowAb49g@mail.gmail.com>
References: <CA+8=xu+GPykmKdAjxLdRA3QoCPR8azervT9uO-GVraNowAb49g@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Mon, 19 May 2014 03:11:37 -0400
Message-ID: <CAJHLa0ODAUCpG8D7AMpsmi5bL9r_7KS711OC7HSzeeyTKoheXg@mail.gmail.com>
To: =?UTF-8?B?UmHDumwgTWFydMOtbmV6?= <rme@i-rme.es>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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 SPF_PASS SPF: sender matches SPF record
-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: 1WmHjw-0006Rp-5r
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] About the small number of bitcoin nodes
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: Mon, 19 May 2014 07:12:05 -0000
On Sun, May 18, 2014 at 1:43 PM, Ra=C3=BAl Mart=C3=ADnez <rme@i-rme.es> wro=
te:
> - Allow users to view the bandwith used by Bitcoin Core:
+1 for the sake of transparency
HOWEVER, the impact on this feature RE user population is
unpredictable. Users may see bigger than expected numbers, and switch
off their node.
> - Educate users about the correct setup of a bitcoin node:
+1
> - bitcoind and Bitcoin Core should create a bitcoin.conf file on the firs=
t
Meh. I like example configs, perhaps tuned by the distro. If the
distro (_not_ Bitcoin Core upstream) chooses to install a bitcoin.conf
in the proper location, that's up to them.
> - bitcoind and Bitcoin Core should be in Linux repos:
Agreed with conditions:
1) The distro MUST let bitcoin devs dictate which dependent libs are
shipped with / built statically into the bitcoin binaries/libs.
2) The distro MUST permit fresh updates even to older stable distros.
2) The maintainer(s) MUST be active, and follow bitcoin development,
release status, etc. on a near-daily basis, be able to respond quickly
if security issues arise, etc.
Matt C seems to do a good job of this in Ubuntu PPA, I'm told.
> - Create a "grafical interface" for bitcoind on Linux servers:
> When I say "grafical interface" I mean like "top" command, an interface m=
ade
> out of characters in ASCII.
The best path for this is figure out what statistics you want to see,
and have bitcoind export those raw numbers to any willing consumer.
Then write your bitcoind-top on top of that.
> - Split Bitcoin Wallet from Bitcoin Node:
+1
In progress. Disable-wallet support, at compile time or runtime, was
the first step.
> - Inform users if 8333 port is closed:
+1
> - Keep connections if bitcoind is restarted:
> I noticed that if I restart bitcoind (to apply new config) my reset to 0 =
and
> take some hours to rise up to ~40. I believe that my peers should notice
> that I am down for less than ~15 minutes and try to connect again faster.
No, you don't want this (and it's not possible in many cases anyway).
--=20
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
