From: Jeff Garzik <jgarzik@bitpay•com>
To: "Raúl Martínez" <rme@i-rme•es>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] About the small number of bitcoin nodes
Date: Mon, 19 May 2014 03:11:37 -0400 [thread overview]
Message-ID: <CAJHLa0ODAUCpG8D7AMpsmi5bL9r_7KS711OC7HSzeeyTKoheXg@mail.gmail.com> (raw)
In-Reply-To: <CA+8=xu+GPykmKdAjxLdRA3QoCPR8azervT9uO-GVraNowAb49g@mail.gmail.com>
On Sun, May 18, 2014 at 1:43 PM, Raúl Martínez <rme@i-rme•es> wrote:
> - 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 first
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 made
> 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).
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-05-19 7:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 17:43 Raúl Martínez
2014-05-18 20:15 ` Raúl Martínez
2014-05-19 7:11 ` Jeff Garzik [this message]
2014-05-19 7:25 ` Justus Ranvier
2014-05-19 14:02 ` Scott Howard
2014-05-19 8:48 ` Wladimir
2014-05-19 10:39 ` Wladimir
2014-05-19 10:47 ` Felipe Micaroni Lalli
2014-05-19 9:26 ` Bjørn Øivind Bjørnsen
2014-05-19 12:15 ` Mike Hearn
2014-05-19 12:24 ` Bjørn Øivind Bjørnsen
2014-05-19 12:28 ` Mike Hearn
2014-05-19 12:44 ` Wladimir
2014-05-19 12:53 ` Mike Hearn
2014-06-30 10:16 ` Wladimir
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=CAJHLa0ODAUCpG8D7AMpsmi5bL9r_7KS711OC7HSzeeyTKoheXg@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=rme@i-rme$(echo .)es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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