3
The size of the Bitcoin network is available here:
http://bitcoinstatus.rowit.co.uk/
As the page says, they do this by listening for Address messages that are broadcast over the network.
Since the Ripple server is now open-source, we can expect a number of individuals and companies to start running their own nodes. Is there a way to estimate the size of the network, either using an RPC command on the server, or by modifying the server code itself to collect some information about the peers?
I would be interested in the following numbers:
- Number of public servers
- Number of validators
I imagine the first one could be obtained by querying peers recursively. Unfortunately the RPC interface is only available to 127.0.0.1 by default. As for the second metric, I'm guessing we can get this by looking at the ledger.
So you connected to server A, which is in turn connected to servers B and C, and it gave you the unique node keys of B and C (as well as its own). How did you do this? Did you use an RPC command? What about server D, which is connected to C, but not to A? – Manish – 2013-10-02T23:12:38.120
1I used the
peerscommand. And I connected to almost half the servers in the process. Since most servers try to have at least 10 connections, that should have almost 100% coverage. – David Schwartz – 2013-10-02T23:18:36.5403
A new feature peer finder is being developed. This will allow every server to maintain a fairly complete map of the network topology (for all non-private servers).
– David Schwartz – 2013-10-03T04:48:07.087