-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client version number #2
Comments
bitnodes.py has been storing the protocol version and user agent in nodes_version table. I will look into publishing this on the webpage for each run. |
Thank you very much! |
+1 was just looking for this. Long term graphs of version adoption would be excellent. |
I have pushed a major update to the staging site that features a set of new charts including the distribution of user agents: http://crawl-88-198-62-174.bitnodes.io/ (staging URL). The charts are using new crawl data captured using the 2nd generation crawler capable of crawling the entire network under 5 minutes. The major update will be available on getaddr.bitnodes.io once I get to put up a new map on the new site. |
That look AMAZING 👍 |
Sexy! It's interesting that we have a diurnal cycle. The size of the cycle implies something about how many people are running Bitcoin-Qt behind UPNP capable routers (or direct connect). |
Would it also be possible to collect client version number stats? I think that could be very useful metric to know how up to date the network is.
The text was updated successfully, but these errors were encountered: