From: Felipe Micaroni Lalli <micaroni@walltime•info>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] About the small number of bitcoin nodes
Date: Mon, 19 May 2014 07:47:47 -0300 [thread overview]
Message-ID: <F8750E85-68EA-48DD-82F1-AD84BEFF568C@walltime.info> (raw)
In-Reply-To: <CA+s+GJD0VE7O4_BLO+RmS5veYcTisBvdbRfnorZdMtZuhOzu7g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]
Is the small number of bitcoin nodes a concern? If yes, why? What kind of attack can the network suffer? And where can we find statistical information about the full nodes running?
I guess the only effective incentive to keep a node running would be financial. A kind of proof of stake would be nice on bitcoin. But I have no idea how to begin with.
Felipe Micaroni Lalli
Walltime: https://walltime.info
Bitcoin Paranoid Android developer
PGP ID: 0x4c0afccfed5cde14
BTC: 1LipeR1AjHL6gwE7WQECW4a2H4tuqm768N
On 19/05/2014, at 07:39, Wladimir <laanwj@gmail•com> wrote:
> On Mon, May 19, 2014 at 10:48 AM, Wladimir <laanwj@gmail•com> wrote:
>>
>> Some hacking with ncurses could quickly make a decent tool here. It
>> could be packaged with bitcoin itself but that's not necessary. For
>> example Tor has the tool 'arm' which is a separate package.
>
> Regarding tor-arm, here are some screenshots:
> https://www.atagar.com/arm/screenshots.php
>
> It shows, among other things:
> - bandwidth up/down graphs
> - CPU usage
> - debug logging (in real time)
> - connected peers+statistics
> - currently active configuration
>
> Would be nice to have a similar tool for bitcoind.
>
> Wladimir
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
next prev parent reply other threads:[~2014-05-19 11: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
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 [this message]
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=F8750E85-68EA-48DD-82F1-AD84BEFF568C@walltime.info \
--to=micaroni@walltime$(echo .)info \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@gmail$(echo .)com \
/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