From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1VjUcE-0000tn-G7 for bitcoin-development@lists.sourceforge.net; Thu, 21 Nov 2013 13:48:18 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.47 as permitted sender) client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f47.google.com; Received: from mail-oa0-f47.google.com ([209.85.219.47]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VjUcC-0000ps-0l for bitcoin-development@lists.sourceforge.net; Thu, 21 Nov 2013 13:48:17 +0000 Received: by mail-oa0-f47.google.com with SMTP id k1so6945727oag.6 for ; Thu, 21 Nov 2013 05:48:10 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.182.229.34 with SMTP id sn2mr177098obc.86.1385041690627; Thu, 21 Nov 2013 05:48:10 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.76.85.4 with HTTP; Thu, 21 Nov 2013 05:48:10 -0800 (PST) Date: Thu, 21 Nov 2013 14:48:10 +0100 X-Google-Sender-Auth: hO48Sb7Z6i01uJGeh9bw1I9Jn6k Message-ID: From: Mike Hearn To: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a11349750f8150b04ebb02557 X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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: 64.120.253.194] 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_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: 1VjUcC-0000ps-0l Subject: [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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Nov 2013 13:48:18 -0000 --001a11349750f8150b04ebb02557 Content-Type: text/plain; charset=UTF-8 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. --001a11349750f8150b04ebb02557 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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:

2013-11-21 1= 3:41:04 AcceptToMemoryPool: 5.9.24.81:783= 4 /Satoshi:0.8.99/Gangnam Style:2.1/ : accepted 2d1bbcc2bf64dfcb57a2f01= 80b2607a48a34de4422c446929b26b190083bbfe7 (poolsz 2087)
2013-11-21 13:41:05 AcceptToMemoryPool: 198.12.127.2:29057 /Satoshi:0.8.99/Gangnam Style:2.1/ : accepte= d 28bb94978bdaa224faeafa95d03a0c4f5743396d6f592469c5ac2b64184ac716 (poolsz = 2088)
2013-11-21 13:41:06 ERROR: AcceptToMemoryPool : nonstandard transactio= n: dust
2013-11-21 13:41:06 42323d9553e4c592d27765dc3ef9152c186cb= 7d67b08d783d72974a56085032d from 82.6= 8.68.254:39232 /Satoshi:0.8.1/ was not accepted into the memory pool: d= ust
2013-11-21 13:41:06 AcceptToMemoryPool: 198.12.127.2:29057 /Satoshi:0.8.99/Gangnam Style:2.1/ : accepte= d 2fdb19e5e87d518b7b6bb7371d547a5f60c2bb056ba4522190460f0bc41b51fb (poolsz = 2089)
2013-11-21 13:41:08 AcceptToMemoryPool: 5.9.24.81:7834 /Satoshi:0.8.99/Gangnam Style:2.1/ : accepted 52c8ed= 6a48f89d48b1152b67ac0b718a7aadb5f9a0c70c18b9b2fed058ca3323 (poolsz 2090)
2013-11-21 13:41:08 AcceptToMemoryPool: 198.12.127.2:29057 /Satoshi:0.8.99/Gangnam Style:2.1/ : accepte= d 980bbdbd4a6b365fa6f13fb5247eb6cb1e54847e490c3b7c3026d1548fb9efc6 (poolsz = 2091)
2013-11-21 13:41:08 AcceptToMemoryPool: 64.120.253.194:60896 /Satoshi:0.8.99/Gangnam Style:2.0/ : acc= epted 03f79c611bbdc1afa7afa67eb0bbd4d8bc86a730a7066622e2709ae506e61e0f (poo= lsz 2092)
2013-11-21 13:41:10 AcceptToMemoryPool: 5.9.24.81:7834 /Satoshi:0.8.99/Gangnam Style:2.1/ : accepted af8096= ad637af1ca022a5146e07cf1fc6bfbec877935f9e114b279fcfe26c06d (poolsz 2093)
2013-11-21 13:41:10 AcceptToMemoryPool: 5.9.24.81:7834 /Satoshi:0.8.99/Gangnam Style:2.1/ : accepted 751c24= 15d058d45ca602fdf1b6490edb6e57fc718e914d628c11b17e25aac834 (poolsz 2094)



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.

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.
--001a11349750f8150b04ebb02557--