From: Addy Yeow <ayeowch@gmail•com>
To: bitcoingrant@gmx•com
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Modularizing Bitcoin
Date: Thu, 16 May 2013 20:55:44 +1000 [thread overview]
Message-ID: <CAA3bHnzge4qB2a4D9FCwoAY0t9jBB0kMTB932-DcjyMOfjrgdQ@mail.gmail.com> (raw)
In-Reply-To: <20130516104809.82690@gmx.com>
Is the number representing the count for the client nodes?
I was curious of the count myself earlier this week and started to
traverse down the network using getaddr message starting from seed
nodes and found upward to 57k nodes running protocol >= 70001 with
timestamp no older than 24 hours.
On Thu, May 16, 2013 at 8:48 PM, <bitcoingrant@gmx•com> wrote:
> our estimates: ~8000
>
>
>
> ----- Original Message -----
>
> From: Addy Yeow
>
> Sent: 05/16/13 06:27 AM
>
> To: bitcoingrant@gmx•com
>
> Subject: Re: [Bitcoin-development] Modularizing Bitcoin
>
>
>
>> Such developments would significantly strengthen the system.
>> Modularization would make cancer attacks less likely and increase the node
>> count, which, currently, is fairly low.
>
> Do we know for certain or at least a rough figure of the node count in
> the network?
>
next prev parent reply other threads:[~2013-05-16 10:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 10:48 bitcoingrant
2013-05-16 10:55 ` Addy Yeow [this message]
2013-05-26 23:57 ` Luke-Jr
-- strict thread matches above, loose matches on Subject: below --
2013-05-27 2:57 Tamas Blummer
2013-05-26 21:46 Ron
2013-05-16 10:02 bitcoingrant
2013-05-16 10:27 ` Addy Yeow
2013-05-16 16:43 ` Brenton Camac
2013-05-16 19:35 ` Mike Hearn
2013-05-20 5:16 ` Quinn Harris
2013-05-26 23:53 ` Luke-Jr
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=CAA3bHnzge4qB2a4D9FCwoAY0t9jBB0kMTB932-DcjyMOfjrgdQ@mail.gmail.com \
--to=ayeowch@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoingrant@gmx$(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