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
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
|
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 1VjoOZ-0000wE-Tz
for bitcoin-development@lists.sourceforge.net;
Fri, 22 Nov 2013 10:55:32 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.51 as permitted sender)
client-ip=209.85.214.51; envelope-from=ayeowch@gmail.com;
helo=mail-bk0-f51.google.com;
Received: from mail-bk0-f51.google.com ([209.85.214.51])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VjoOW-0005vO-Ao
for bitcoin-development@lists.sourceforge.net;
Fri, 22 Nov 2013 10:55:31 +0000
Received: by mail-bk0-f51.google.com with SMTP id 6so718609bkj.24
for <bitcoin-development@lists.sourceforge.net>;
Fri, 22 Nov 2013 02:55:21 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.205.14.197 with SMTP id pr5mr1448203bkb.33.1385117721581;
Fri, 22 Nov 2013 02:55:21 -0800 (PST)
Received: by 10.204.111.131 with HTTP; Fri, 22 Nov 2013 02:55:21 -0800 (PST)
In-Reply-To: <CANEZrP1ZoU5DXf=4arxcy++3P1z2jHFZWCn1R=JuYxQDEX4W1Q@mail.gmail.com>
References: <CANEZrP3Amb+vBDR-JyVLDmDy9ewF8DQFVDJgOEg4izhTaR7hVw@mail.gmail.com>
<CAA3bHny27fRZNNYMtqa85wrr7e3_EUgxsDFba6+E=QOW1o+mqw@mail.gmail.com>
<CANEZrP1ZoU5DXf=4arxcy++3P1z2jHFZWCn1R=JuYxQDEX4W1Q@mail.gmail.com>
Date: Fri, 22 Nov 2013 21:55:21 +1100
Message-ID: <CAA3bHnyq2AAZ-WAb-PE1UEyCP+Mz84ao=eJMdRjvPEa+P=EB7w@mail.gmail.com>
From: Addy Yeow <ayeowch@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=20cf301cc42cc485ef04ebc1d963
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: bitcointalk.org]
-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.0 NORMAL_HTTP_TO_IP URI: Uses a dotted-decimal IP address in URL
0.0 WEIRD_PORT URI: Uses non-standard port number for HTTP
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: 1VjoOW-0005vO-Ao
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Who or what is /Satoshi:0.8.99/Gangnam
Style:2.1/ ?
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: Fri, 22 Nov 2013 10:55:32 -0000
--20cf301cc42cc485ef04ebc1d963
Content-Type: text/plain; charset=ISO-8859-1
Hi Mike,
I am glad you are still following up with Bitnodes. The recent spike in
nodes count should probably be taken with a grain of salt; run #231 (
http://getaddr.bitnodes.io/231/) does appear artificial to me, i.e.
potentially bogus nodes being added. I am still working on a more in depth
analysis on the data.
There are quite some TODOs for the project at the moment for the next
couple of months. I have included propagation data as well into the list.
Cheers,
Addy
On Fri, Nov 22, 2013 at 1:47 AM, Mike Hearn <mike@plan99.net> wrote:
> Thanks. By the way, your bitnodes site is excellent. Thanks for doing
> that. If you're in the mood for extending it, it'd be great to gather and
> chart data on block and tx propagation times.
>
> Do you think the recent explosion in running nodes is real, or due to some
> kind of custom experimental thing?
>
>
> On Thu, Nov 21, 2013 at 2:55 PM, Addy Yeow <ayeowch@gmail.com> wrote:
>
>> Try https://bitcointalk.org/index.php?action=profile;u=19897?
>>
>>
>>
>>
>> On Fri, Nov 22, 2013 at 12:48 AM, Mike Hearn <mike@plan99.net> wrote:
>>
>>> I added some additional logging to my node and ran it for a few days.
>>> There's a pull req open for my extra logging, it is quite trivial. Here's
>>> what it looks like:
>>>
>>> 2013-11-21 13:41:04 AcceptToMemoryPool: 5.9.24.81:7834/Satoshi:0.8.99/Gangnam Style:2.1/ : accepted
>>> 2d1bbcc2bf64dfcb57a2f0180b2607a48a34de4422c446929b26b190083bbfe7 (poolsz
>>> 2087)
>>> 2013-11-21 13:41:05 AcceptToMemoryPool: 198.12.127.2:29057/Satoshi:0.8.99/Gangnam Style:2.1/ : accepted
>>> 28bb94978bdaa224faeafa95d03a0c4f5743396d6f592469c5ac2b64184ac716 (poolsz
>>> 2088)
>>> 2013-11-21 13:41:06 ERROR: AcceptToMemoryPool : nonstandard transaction:
>>> dust
>>> 2013-11-21 13:41:06
>>> 42323d9553e4c592d27765dc3ef9152c186cb7d67b08d783d72974a56085032d from
>>> 82.68.68.254:39232 /Satoshi:0.8.1/ was not accepted into the memory
>>> pool: dust
>>> 2013-11-21 13:41:06 AcceptToMemoryPool: 198.12.127.2:29057/Satoshi:0.8.99/Gangnam Style:2.1/ : accepted
>>> 2fdb19e5e87d518b7b6bb7371d547a5f60c2bb056ba4522190460f0bc41b51fb (poolsz
>>> 2089)
>>> 2013-11-21 13:41:08 AcceptToMemoryPool: 5.9.24.81:7834/Satoshi:0.8.99/Gangnam Style:2.1/ : accepted
>>> 52c8ed6a48f89d48b1152b67ac0b718a7aadb5f9a0c70c18b9b2fed058ca3323 (poolsz
>>> 2090)
>>> 2013-11-21 13:41:08 AcceptToMemoryPool: 198.12.127.2:29057/Satoshi:0.8.99/Gangnam Style:2.1/ : accepted
>>> 980bbdbd4a6b365fa6f13fb5247eb6cb1e54847e490c3b7c3026d1548fb9efc6 (poolsz
>>> 2091)
>>> 2013-11-21 13:41:08 AcceptToMemoryPool: 64.120.253.194:60896/Satoshi:0.8.99/Gangnam Style:2.0/ : accepted
>>> 03f79c611bbdc1afa7afa67eb0bbd4d8bc86a730a7066622e2709ae506e61e0f (poolsz
>>> 2092)
>>> 2013-11-21 13:41:10 AcceptToMemoryPool: 5.9.24.81:7834/Satoshi:0.8.99/Gangnam Style:2.1/ : accepted
>>> af8096ad637af1ca022a5146e07cf1fc6bfbec877935f9e114b279fcfe26c06d (poolsz
>>> 2093)
>>> 2013-11-21 13:41:10 AcceptToMemoryPool: 5.9.24.81:7834/Satoshi:0.8.99/Gangnam Style:2.1/ : accepted
>>> 751c2415d058d45ca602fdf1b6490edb6e57fc718e914d628c11b17e25aac834 (poolsz
>>> 2094)
>>>
>>>
>>>
>>> Despite that I have 87 connections from regular nodes, virtually all
>>> transactions seen by my node are being announced by this modified software,
>>> which appears to run on several different machines.
>>>
>>> I am wondering if anyone out there knows/owns these nodes and if they
>>> are relaying transactions without checking their validity. That seems the
>>> most likely reason for how they are always able to win the race to be the
>>> first to announce to my node.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Shape the Mobile Experience: Free Subscription
>>> Software experts and developers: Be at the forefront of tech innovation.
>>> Intel(R) Software Adrenaline delivers strategic insight and game-changing
>>> conversations that shape the rapidly evolving mobile landscape. Sign up
>>> now.
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Bitcoin-development mailing list
>>> Bitcoin-development@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>
>>>
>>
>
--20cf301cc42cc485ef04ebc1d963
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi Mike,<div><br><div>I am glad you are still following up=
with Bitnodes. The recent spike in nodes count should probably be taken wi=
th a grain of salt; run #231 (<a href=3D"http://getaddr.bitnodes.io/231/">h=
ttp://getaddr.bitnodes.io/231/</a>) does appear artificial to me, i.e. pote=
ntially bogus nodes being added. I am still working on a more in depth anal=
ysis on the data.</div>
<div><br></div><div>There are quite some TODOs for the project at the momen=
t for the next couple of months. I have included propagation data as well i=
nto the list.</div></div><div><br></div><div>Cheers,</div><div>Addy</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri,=
Nov 22, 2013 at 1:47 AM, Mike Hearn <span dir=3D"ltr"><<a href=3D"mailt=
o:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>></span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">Thanks. By the way, your bitnodes site is excellent. Thank=
s for doing that. If you're in the mood for extending it, it'd be g=
reat to gather and chart data on block and tx propagation times.<div><br>
</div>
<div>Do you think the recent explosion in running nodes is real, or due to =
some kind of custom experimental thing?</div></div><div class=3D"HOEnZb"><d=
iv class=3D"h5"><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quot=
e">
On Thu, Nov 21, 2013 at 2:55 PM, Addy Yeow <span dir=3D"ltr"><<a href=3D=
"mailto:ayeowch@gmail.com" target=3D"_blank">ayeowch@gmail.com</a>></spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Try=A0<a href=3D"https://bi=
tcointalk.org/index.php?action=3Dprofile;u=3D19897" target=3D"_blank">https=
://bitcointalk.org/index.php?action=3Dprofile;u=3D19897</a>?<div>
<br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div clas=
s=3D"gmail_quote"><div><div>
On Fri, Nov 22, 2013 at 12:48 AM, Mike Hearn <span dir=3D"ltr"><<a href=
=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>></span=
> wrote:<br></div></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>
<div dir=3D"ltr">I added some additional logging to my node and ran it for =
a few days. There's a pull req open for my extra logging, it is quite t=
rivial. Here's what it looks like:<div><br></div><div><div>2013-11-21 1=
3:41:04 AcceptToMemoryPool: <a href=3D"http://5.9.24.81:7834" target=3D"_bl=
ank">5.9.24.81:7834</a> /Satoshi:0.8.99/Gangnam Style:2.1/ : accepted 2d1bb=
cc2bf64dfcb57a2f0180b2607a48a34de4422c446929b26b190083bbfe7 (poolsz 2087)</=
div>
<div>2013-11-21 13:41:05 AcceptToMemoryPool: <a href=3D"http://198.12.127.2=
:29057" target=3D"_blank">198.12.127.2:29057</a> /Satoshi:0.8.99/Gangnam St=
yle:2.1/ : accepted 28bb94978bdaa224faeafa95d03a0c4f5743396d6f592469c5ac2b6=
4184ac716 (poolsz 2088)</div>
<div>2013-11-21 13:41:06 ERROR: AcceptToMemoryPool : nonstandard transactio=
n: dust</div><div>2013-11-21 13:41:06 42323d9553e4c592d27765dc3ef9152c186cb=
7d67b08d783d72974a56085032d from <a href=3D"http://82.68.68.254:39232" targ=
et=3D"_blank">82.68.68.254:39232</a> /Satoshi:0.8.1/ was not accepted into =
the memory pool: dust</div>
<div>2013-11-21 13:41:06 AcceptToMemoryPool: <a href=3D"http://198.12.127.2=
:29057" target=3D"_blank">198.12.127.2:29057</a> /Satoshi:0.8.99/Gangnam St=
yle:2.1/ : accepted 2fdb19e5e87d518b7b6bb7371d547a5f60c2bb056ba4522190460f0=
bc41b51fb (poolsz 2089)</div>
<div>2013-11-21 13:41:08 AcceptToMemoryPool: <a href=3D"http://5.9.24.81:78=
34" target=3D"_blank">5.9.24.81:7834</a> /Satoshi:0.8.99/Gangnam Style:2.1/=
: accepted 52c8ed6a48f89d48b1152b67ac0b718a7aadb5f9a0c70c18b9b2fed058ca332=
3 (poolsz 2090)</div>
<div>2013-11-21 13:41:08 AcceptToMemoryPool: <a href=3D"http://198.12.127.2=
:29057" target=3D"_blank">198.12.127.2:29057</a> /Satoshi:0.8.99/Gangnam St=
yle:2.1/ : accepted 980bbdbd4a6b365fa6f13fb5247eb6cb1e54847e490c3b7c3026d15=
48fb9efc6 (poolsz 2091)</div>
<div>2013-11-21 13:41:08 AcceptToMemoryPool: <a href=3D"http://64.120.253.1=
94:60896" target=3D"_blank">64.120.253.194:60896</a> /Satoshi:0.8.99/Gangna=
m Style:2.0/ : accepted 03f79c611bbdc1afa7afa67eb0bbd4d8bc86a730a7066622e27=
09ae506e61e0f (poolsz 2092)</div>
<div>2013-11-21 13:41:10 AcceptToMemoryPool: <a href=3D"http://5.9.24.81:78=
34" target=3D"_blank">5.9.24.81:7834</a> /Satoshi:0.8.99/Gangnam Style:2.1/=
: accepted af8096ad637af1ca022a5146e07cf1fc6bfbec877935f9e114b279fcfe26c06=
d (poolsz 2093)</div>
<div>2013-11-21 13:41:10 AcceptToMemoryPool: <a href=3D"http://5.9.24.81:78=
34" target=3D"_blank">5.9.24.81:7834</a> /Satoshi:0.8.99/Gangnam Style:2.1/=
: accepted 751c2415d058d45ca602fdf1b6490edb6e57fc718e914d628c11b17e25aac83=
4 (poolsz 2094)</div>
</div><div><br></div><div><br></div><div><br></div><div>Despite that I have=
87 connections from regular nodes, virtually all transactions seen by my n=
ode are being announced by this modified software, which appears to run on =
several different machines.</div>
<div><br></div><div>I am wondering if anyone out there knows/owns these nod=
es and if they are relaying transactions without checking their validity. T=
hat seems the most likely reason for how they are always able to win the ra=
ce to be the first to announce to my node.</div>
</div>
<br></div></div>-----------------------------------------------------------=
-------------------<br>
Shape the Mobile Experience: Free Subscription<br>
Software experts and developers: Be at the forefront of tech innovation.<br=
>
Intel(R) Software Adrenaline delivers strategic insight and game-changing<b=
r>
conversations that shape the rapidly evolving mobile landscape. Sign up now=
.<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D63431311&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D63431311&iu=3D/4140/ostg.clktrk</a><br>___________________=
____________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
--20cf301cc42cc485ef04ebc1d963--
|