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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ayeowch@gmail.com>) id 1Ucvqh-0008El-LB
for bitcoin-development@lists.sourceforge.net;
Thu, 16 May 2013 10:55:51 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.53 as permitted sender)
client-ip=209.85.214.53; envelope-from=ayeowch@gmail.com;
helo=mail-bk0-f53.google.com;
Received: from mail-bk0-f53.google.com ([209.85.214.53])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Ucvqg-0007Kg-UN
for bitcoin-development@lists.sourceforge.net;
Thu, 16 May 2013 10:55:51 +0000
Received: by mail-bk0-f53.google.com with SMTP id mx10so115289bkb.40
for <bitcoin-development@lists.sourceforge.net>;
Thu, 16 May 2013 03:55:44 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.205.115.11 with SMTP id fc11mr12554516bkc.72.1368701744497;
Thu, 16 May 2013 03:55:44 -0700 (PDT)
Received: by 10.204.203.15 with HTTP; Thu, 16 May 2013 03:55:44 -0700 (PDT)
In-Reply-To: <20130516104809.82690@gmx.com>
References: <20130516104809.82690@gmx.com>
Date: Thu, 16 May 2013 20:55:44 +1000
Message-ID: <CAA3bHnzge4qB2a4D9FCwoAY0t9jBB0kMTB932-DcjyMOfjrgdQ@mail.gmail.com>
From: Addy Yeow <ayeowch@gmail.com>
To: bitcoingrant@gmx.com
Content-Type: text/plain; charset=ISO-8859-1
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(ayeowch[at]gmail.com)
-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: 1Ucvqg-0007Kg-UN
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Modularizing Bitcoin
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: Thu, 16 May 2013 10:55:51 -0000
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?
>
|
