Bitcoin Forum
November 17, 2024, 09:40:01 AM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: The Bitcoin network  (Read 1791 times)
MagicalTux (OP)
VIP
Hero Member
*
expert
Offline Offline

Activity: 608
Merit: 501


-


View Profile
February 22, 2012, 11:15:54 AM
Last edit: February 22, 2012, 12:01:30 PM by MagicalTux
 #1

Some time ago, I created a bitcoin network analyzer that would collect information on all the available bitcoin nodes.

The system hasn't been updated for a long time, however it was recently updated to process connection attempts much faster, while giving nodes more time to accept the connection attempts.

The database was erased and re-created today, and the next dump will include a new info, "Last_Error", which is a small string giving details on the last error we had ("timeout", "connection_refused", etc).

The main interest of these database dumps is of course historical, as it shows the progression of the bitcoin network over time. It is free to download to anyone, directly from http://dump.bitcoin.it/misc/

The next file (20120223) will restart from an empty database, with the new field, and the new scanning method. It is possible to have a realtime overview of the database from this API: https://mtgox.com/api/stats/accepting (and people writing bitcoin clients can use the bootstrap api to collect initial bitcoin addresses to connect to: https://mtgox.com/api/stats/bootstrap )


Anyway, this thread has two goals:

  • If you have any suggestion regarding this system (extra data we could collect), let me know. I'm planning on adding a passive node too that would collect data from nodes which are not available from outside (firewalled).
  • If you make anything out of the historical data available, post it here Wink
And a last nifty thing that can be done with this: http://maps.google.com/?q=https://mtgox.com/api/stats/bitcoin.kml

UPDATE: The next database version will also include a User_Agent field containing the user agent transmitted by the bitcoin client (see BIP#0014 for details).
Wordlet
Newbie
*
Offline Offline

Activity: 26
Merit: 0



View Profile
February 22, 2012, 01:38:38 PM
 #2

That google maps link throws an error for me:
"https://mtgox.com/api/stats... could not be displayed because it is too large."
finway
Hero Member
*****
Offline Offline

Activity: 714
Merit: 500


View Profile
February 22, 2012, 03:46:34 PM
 #3

Interesting,  If there are more than 10 guys trying to connect to every bitcoin node, will the network be broken?

MagicalTux (OP)
VIP
Hero Member
*
expert
Offline Offline

Activity: 608
Merit: 501


-


View Profile
February 22, 2012, 11:10:09 PM
 #4

Interesting,  If there are more than 10 guys trying to connect to every bitcoin node, will the network be broken?

Actually... no.

That google maps link throws an error for me:
"https://mtgox.com/api/stats... could not be displayed because it is too large."

I guess then the only option is to download the kml and load it in google earth. It used to work when the db was not that big (currently over 100k known bitcoin nodes).

finway
Hero Member
*****
Offline Offline

Activity: 714
Merit: 500


View Profile
February 23, 2012, 07:03:28 AM
 #5


are these online nodes ?   What's the timeline ?

kuzetsa
Sr. Member
****
Offline Offline

Activity: 369
Merit: 250


View Profile
November 10, 2012, 02:46:15 PM
 #6

This information is great. Thanks so much, I'm cooking portions of the historical data now, trying to troubleshoot some stuff that I otherwise would have had trouble with due to lack of data.

There are a couple broken links by the way (the API ones) in this thread.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!