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 1YyLB8-0005yM-Ek for bitcoin-development@lists.sourceforge.net; Fri, 29 May 2015 14:22:30 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.178 as permitted sender) client-ip=209.85.212.178; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f178.google.com; Received: from mail-wi0-f178.google.com ([209.85.212.178]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YyLB7-00043Q-Bw for bitcoin-development@lists.sourceforge.net; Fri, 29 May 2015 14:22:30 +0000 Received: by wivl4 with SMTP id l4so19089277wiv.1 for ; Fri, 29 May 2015 07:22:23 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.9.161 with SMTP id a1mr823975wjb.39.1432909343326; Fri, 29 May 2015 07:22:23 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.194.143.9 with HTTP; Fri, 29 May 2015 07:22:22 -0700 (PDT) In-Reply-To: References: <16096345.A1MpJQQkRW@crushinator> Date: Fri, 29 May 2015 16:22:22 +0200 X-Google-Sender-Auth: huw9PJ6-PhktfUUPxwTZB6uM_aE Message-ID: From: Mike Hearn To: Gavin Andresen Content-Type: multipart/alternative; boundary=047d7b5d34fa6788b805173934a5 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 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: 1YyLB7-00043Q-Bw Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Proposed alternatives to the 20MB step function 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: Fri, 29 May 2015 14:22:30 -0000 --047d7b5d34fa6788b805173934a5 Content-Type: text/plain; charset=UTF-8 > > And looking at the version (aka user-agent) strings of publicly reachable > nodes on the network. > (e.g. see the count at https://getaddr.bitnodes.io/nodes/ ) > Yeah, though FYI Luke informed me last week that I somehow managed to take out the change to the user-agent string in Bitcoin XT, presumably I made a mistake during a rebase of the rebranding change. So the actual number of XT nodes is a bit higher than counting user-agent strings would suggest. I sort of neglected XT lately. If we go ahead with this then I'll fix things like this. --047d7b5d34fa6788b805173934a5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
And looking at the version (aka user-agent) str= ings of publicly reachable nodes on the network.
(e.g. see the co= unt at =C2=A0https://getaddr.bitnodes.io/nodes/ )

Yeah, though FYI Luke informed me last week that I= somehow managed to take out the change to the user-agent string in Bitcoin= XT, presumably I made a mistake during a rebase of the rebranding change. = So the actual number of XT nodes is a bit higher than counting user-agent s= trings would suggest.

I sort of neglected XT latel= y. If we go ahead with this then I'll fix things like this.
=
--047d7b5d34fa6788b805173934a5--