summaryrefslogtreecommitdiff
path: root/8f/1e6f66ac5d6e8f8a5e0d6a9b2f6eb9636ef9c7
blob: f8d737c4ef11855937c477d2f00c9bf4a00cff2f (plain)
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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1WkB7C-0000Zs-34
	for bitcoin-development@lists.sourceforge.net;
	Tue, 13 May 2014 11:43:22 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.171 as permitted sender)
	client-ip=209.85.223.171; envelope-from=laanwj@gmail.com;
	helo=mail-ie0-f171.google.com; 
Received: from mail-ie0-f171.google.com ([209.85.223.171])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WkB7A-0007N9-Vs
	for bitcoin-development@lists.sourceforge.net;
	Tue, 13 May 2014 11:43:22 +0000
Received: by mail-ie0-f171.google.com with SMTP id rl12so172346iec.16
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 13 May 2014 04:43:15 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.92.42 with SMTP id cj10mr55964232igb.34.1399981394932;
	Tue, 13 May 2014 04:43:14 -0700 (PDT)
Received: by 10.64.22.168 with HTTP; Tue, 13 May 2014 04:43:14 -0700 (PDT)
In-Reply-To: <536FAFEA.5050404@gmail.com>
References: <536FAFEA.5050404@gmail.com>
Date: Tue, 13 May 2014 13:43:14 +0200
Message-ID: <CA+s+GJAoLTrujeHVEUZYDR1mNUFHVsLhH9BYPntrxLKzMm_AEw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Jameson Lopp <jameson.lopp@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.3 (-)
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
	(laanwj[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	0.3 URIBL_RHS_DOB Contains an URI of a new domain (Day Old Bread)
	[URIs: statoshi.info]
	-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: 1WkB7A-0007N9-Vs
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] statoshi.info is now live
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: Tue, 13 May 2014 11:43:22 -0000

Hello Jameson,

On Sun, May 11, 2014 at 7:14 PM, Jameson Lopp <jameson.lopp@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Since it seems unlikely that we'll be able to ship an integrated stats / monitoring feature in the short term, I went ahead and set up a public Statoshi instance and threw a nicer interface on top of it.
>
> http://statoshi.info

Must say it looks very nice.

One comment about the graphs: in the 'connected peers' chart you
visualize some larger quantities (especially knownAddresses) and some
very small ones (peer.(dis)connect). This makes the latter invisible
due to scale.

Some random stats may be useful as well:

- Number of connected peers that are SPV clients or full nodes (NODE_NETWORK)
- Current block height (so that it's possible to detect stuck nodes)
- Number of transactions in mempool
- Number of transactions in UTXO set
- Maybe some fee statistics,
https://github.com/bitcoin/bitcoin/pull/3959 would be useful here
- Number of orphan blocks/orphan transactions

Wladimir