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
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <rme@i-rme.es>) id 1Wm7UM-0005ih-SP
for bitcoin-development@lists.sourceforge.net;
Sun, 18 May 2014 20:15:18 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of i-rme.es
designates 209.85.215.54 as permitted sender)
client-ip=209.85.215.54; envelope-from=rme@i-rme.es;
helo=mail-la0-f54.google.com;
Received: from mail-la0-f54.google.com ([209.85.215.54])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wm7UL-00042F-GF
for bitcoin-development@lists.sourceforge.net;
Sun, 18 May 2014 20:15:18 +0000
Received: by mail-la0-f54.google.com with SMTP id pv20so3463047lab.13
for <bitcoin-development@lists.sourceforge.net>;
Sun, 18 May 2014 13:15:10 -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:date
:message-id:subject:from:cc:content-type;
bh=VxYfjcuWhsyO009nUZs3QA6P7wCt4DuQwh8IYQWUE8o=;
b=L7UcS6dRMi5Bj6PU4fpNPVpgyb0/o72VnPRbpHvBQkq6uBuSsJhQG4D/xDuhSX7/va
FsSZIf/GxpM8vT3U+bLM6kC7Pk4L4f6wEcipoY1jEJ/7NeAw66xq9Wu0FUc8CuysLsfQ
k1FyzDR6jkgD5p9izeiWH/vO0no9QwApwSb4BUe2spcW1xIA2gKMyFFPLFrhWKZ7xsRh
pyTPpbc1zelG1LdyqAnO1cKwqABecqUfdx8KrdCzFslc8v7nIk2WbSTsmxwSkPSxwzOp
mkPaY+CGJf7xJ7W08M8KE6j1wMmRYgOvc4O1l+HrhqFN5JILS9jRenj4eDRvvqHlOIhb
i2Hg==
X-Gm-Message-State: ALoCoQngTQm0ETJVNTICy9f4E58QQcs4NEdsqGQj61UPSTuyuoEeO5ub8J+BcG4NhpgG4JX5UyZw
MIME-Version: 1.0
X-Received: by 10.152.43.135 with SMTP id w7mr22911426lal.32.1400444110663;
Sun, 18 May 2014 13:15:10 -0700 (PDT)
Received: by 10.152.199.8 with HTTP; Sun, 18 May 2014 13:15:10 -0700 (PDT)
X-Originating-IP: [85.251.84.81]
Received: by 10.152.199.8 with HTTP; Sun, 18 May 2014 13:15:10 -0700 (PDT)
In-Reply-To: <CA+8=xu+GPykmKdAjxLdRA3QoCPR8azervT9uO-GVraNowAb49g@mail.gmail.com>
References: <CA+8=xu+GPykmKdAjxLdRA3QoCPR8azervT9uO-GVraNowAb49g@mail.gmail.com>
Date: Sun, 18 May 2014 22:15:10 +0200
Message-ID: <CA+8=xuLLmqMivUeCWVNVCLRbUk4J-3ddmcOwHXsw55A3P8UOTw@mail.gmail.com>
From: =?UTF-8?B?UmHDumwgTWFydMOtbmV6?= <rme@i-rme.es>
Cc: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=001a11c22568be85ee04f9b24d5e
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 SPF_PASS SPF: sender matches SPF record
1.2 MISSING_HEADERS Missing To: header
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: 1Wm7UL-00042F-GF
Subject: [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: Sun, 18 May 2014 20:15:19 -0000
--001a11c22568be85ee04f9b24d5e
Content-Type: text/plain; charset=UTF-8
About the small number of bitcoin nodes:
Hi, I read the message that Mike Hearn sent to this mailing list some days
ago (2014-04-07 11:34:43) related to the number of bitcoin full nodes.
As an owner of two Bitcoin Nodes, one in my home computer and one in a
dedicated server, I believe I can contribute with some of my thoughts and
ideas:
- Allow users to view the bandwith used by Bitcoin Core:
This is available in the Bitcoin Core GUI (btw, when the computer is
restarted the data gets reseted) but I cant find it in the bitcoind
commandline, people that run nodes want to see the amount of GB that they
have "donated" to the network.
- Educate users about the correct setup of a bitcoin node:
Add a page in the bitcoin.org website with a tutorial about running Bitcoin
Core with the ports opened, about runing bitcoind, etc. This guide shoud
not be for regular users but for advanced ones.
- bitcoind and Bitcoin Core should create a bitcoin.conf file on the first
start:
The first time the software should create a default config file with a
random RCP password and username (user can change it later) and the config
file should be commented so the user can know how to change configurations.
This is very useful in setups without GUI, for example in Ubuntu Server.
- bitcoind and Bitcoin Core should be in Linux repos:
People want to type "yum install bitcoind" or "apt-get install bitcoind"
and install bitcoin. No one wants to follow a tutorial made by somewho
saying that you have to add external repos to install bitcoin in your
server.
For example Electrum has been added to Ubuntu software center recently.
Bitcoin Core an bitcoind should be on CentOS, Debian, Ubuntu and Ubuntu
Server repos.
- Create a "grafical interface" for bitcoind on Linux servers:
Create a command, for example "bitcoind show" that shows a nice summary in
your Terminal (Console) with all the data that a node administrator wants
to know.
When I say "grafical interface" I mean like "top" command, an interface
made out of characters in ASCII.
- Split Bitcoin Wallet from Bitcoin Node:
I believe that this is planned, some people want to help the network and
others want to keep a wallet, someones want both.
With bitcoind you can use the option "disablewallet=1" that allows to save
some memory.
- Inform users if 8333 port is closed:
That should be more visible, I dont mean an alert or warning but some icon.
- 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.
Thanks for reading
--001a11c22568be85ee04f9b24d5e
Content-Type: text/html; charset=UTF-8
<p dir="ltr">About the small number of bitcoin nodes:<br>
Hi, I read the message that Mike Hearn sent to this mailing list some days ago (2014-04-07 11:34:43) related to the number of bitcoin full nodes.</p>
<p dir="ltr">As an owner of two Bitcoin Nodes, one in my home computer and one in a dedicated server, I believe I can contribute with some of my thoughts and ideas:</p>
<p dir="ltr"> - Allow users to view the bandwith used by Bitcoin Core:<br>
This is available in the Bitcoin Core GUI (btw, when the computer is restarted the data gets reseted) but I cant find it in the bitcoind commandline, people that run nodes want to see the amount of GB that they have "donated" to the network.</p>
<p dir="ltr"> - Educate users about the correct setup of a bitcoin node:<br>
Add a page in the <a href="http://bitcoin.org">bitcoin.org</a> website with a tutorial about running Bitcoin Core with the ports opened, about runing bitcoind, etc. This guide shoud not be for regular users but for advanced ones.</p>
<p dir="ltr"> - bitcoind and Bitcoin Core should create a bitcoin.conf file on the first start:<br>
The first time the software should create a default config file with a random RCP password and username (user can change it later) and the config file should be commented so the user can know how to change configurations.<br>
This is very useful in setups without GUI, for example in Ubuntu Server.</p>
<p dir="ltr">- bitcoind and Bitcoin Core should be in Linux repos:<br>
People want to type "yum install bitcoind" or "apt-get install bitcoind" and install bitcoin. No one wants to follow a tutorial made by somewho saying that you have to add external repos to install bitcoin in your server.<br>
For example Electrum has been added to Ubuntu software center recently.<br>
Bitcoin Core an bitcoind should be on CentOS, Debian, Ubuntu and Ubuntu Server repos.</p>
<p dir="ltr"> - Create a "grafical interface" for bitcoind on Linux servers:<br>
Create a command, for example "bitcoind show" that shows a nice summary in your Terminal (Console) with all the data that a node administrator wants to know.<br>
When I say "grafical interface" I mean like "top" command, an interface made out of characters in ASCII.</p>
<p dir="ltr"> - Split Bitcoin Wallet from Bitcoin Node:<br>
I believe that this is planned, some people want to help the network and others want to keep a wallet, someones want both.<br>
With bitcoind you can use the option "disablewallet=1" that allows to save some memory.</p>
<p dir="ltr">- Inform users if 8333 port is closed:<br>
That should be more visible, I dont mean an alert or warning but some icon.</p>
<p dir="ltr"> - Keep connections if bitcoind is restarted:<br>
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.<br>
</p>
<p dir="ltr">Thanks for reading</p>
--001a11c22568be85ee04f9b24d5e--
|
