Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WiCUf-0007rK-9y for bitcoin-development@lists.sourceforge.net; Thu, 08 May 2014 00:47:25 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.173 as permitted sender) client-ip=209.85.217.173; envelope-from=gmaxwell@gmail.com; helo=mail-lb0-f173.google.com; Received: from mail-lb0-f173.google.com ([209.85.217.173]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WiCUe-0004sb-28 for bitcoin-development@lists.sourceforge.net; Thu, 08 May 2014 00:47:25 +0000 Received: by mail-lb0-f173.google.com with SMTP id 10so2480944lbg.4 for ; Wed, 07 May 2014 17:47:17 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.61.199 with SMTP id s7mr271073lbr.25.1399510037185; Wed, 07 May 2014 17:47:17 -0700 (PDT) Received: by 10.112.89.68 with HTTP; Wed, 7 May 2014 17:47:17 -0700 (PDT) In-Reply-To: References: <536A8592.8010009@gmail.com> <536A902C.6080602@gmail.com> Date: Wed, 7 May 2014 17:47:17 -0700 Message-ID: From: Gregory Maxwell To: Wladimir Content-Type: text/plain; charset=UTF-8 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 (gmaxwell[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: 1WiCUe-0004sb-28 Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] Announcing the Statoshi fork 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, 08 May 2014 00:47:25 -0000 On Wed, May 7, 2014 at 2:07 PM, Wladimir wrote: > On Wed, May 7, 2014 at 10:25 PM, Mike Hearn wrote: >> Another is to export stats over regular TCP and make them public so >> literally anyone can listen to the stats feed for any node. > > TOR does this as well: http://torstatus.blutmagie.de/ > > No idea what they use to submit/gather the statistics. The tor network works based on a centralized (well, in theory, federated) trusted directory service. (More info in https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=dir-spec.txt). Much of data that is not related to relay related is just generated by probes, e.g. semi-trusted bandwidth authorities that measure node performance back to the directory authorities. More info on their monitoring work is available here: https://metrics.torproject.org/tools.html