As a result, the node map on DigiStats indicates that there are 14 active nodes. But, it's not accurate. It's not fully implemented. There are way more than 14 active nodes. It's hard to say exactly how many nodes there are right now ... but the number was right around 3000, or slightly higher.
screenshot, tcp-connection-list, ip-list ... something which confirms this.
A node is someone with an open wallet that has the full blockchain downloaded, which can communicate with other wallets.
Here's one way to get a list (it won't be a complete list of all nodes).
Open the core wallet. Leave it open for awhile. The longer you do, the more nodes you will get.
I opened mine for an hour and got 51 nodes. (Not everyone keeps their wallet open all the time, and you aren't going to communicate with all of them that are currently open).
When you have waited as long as you want, go to your digibyte data directory. It should be c:/users//appdata/roaming/digibyte
There will be a file called debug.log
In that file will be a bunch of data about blocks and such, several lines will look like this:
2015-07-03 11:55:46 receive version message: /DigiByte:3.0.3/: version 70002, blocks=987677, us=(your IP), them=73.198.40.189:12024, peer=73.198.40.189:12024
All you need to do is sort out these lines and count how many "them" IP addresses are unique.
Typically you would still only be able to reach a fraction of the network using the above method. You also should be forwarding port 14022 through your router and adding the line "maxconnections=100" to your digibyte.conf
The idea behind the map on digistats is similar to that of
https://getaddr.bitnodes.io The reason its taken me so long is that there is no existing implementation of the getaddr protocol message for javascript (atleast that I know of) so that means I've had to implement much of the code myself. I also need to filter out nodes that are of no use to the network but are still able to join it which for instance are android nodes, bitcore nodes and nodes running an incompatible protocol version.
The earlier version of digimap did include these nodes so the actual count is more than likely going to be lower than was advertised.
Currently the map does not search out any extra nodes but you can actually search for a specific node and it will then be added to the database by using the following API call
"
http://digistats.info/api/nodes/search/" if digistats can connect to that node you will then be presented information about that node (version, subversion, height, geoip data). As an example I just manually added the node "111.107.49.171" so the map now displays 16 nodes.
Like I said its a fairly ambitious project and it will take some time for me to perfect all the different parts and my current focus is improving the explorer and API.