While the design of this is purely DNS; it's only giving a few IP addresses for the network to chose from. Since these nodes will really have a complete picture of all the nodes on the network, it may be useful for them to be able to respond to getaddr queries with their list of addresses.

• Need to figure out why the .dat file sometimes writes the data, sometimes writes nothing. I suspect db is getting cleaned out. It should leave you off where you were when you shut down; then when you start up, validate the saved ones.
• - The current queue of found addresses should be stored when it dumps the database; so it can start up with those queued again.
• - Code needs some massive cleaning up
• - could use a log file for network failures; a lot are in threads and can't be printed easily.
• - needs a quiet mode
• - should have a way to point the output files to a folder and not the current directory
• - The protocol needs to be cleaned up. Needs a much cleaner state machine for version send, version response, verack send, verack receive, then getaddr send with re-attempts if you don't get a response right away.
• - When receiving addresses; they should be checked against the current ones in the queue. I don't think they are, there are likely a lot of duplicates.
• - There should be some sort of statistical determination of proper block height to accept; so we don't report out stuck nodes. something that uses the timestamp and the protocol timing to determine if it appears to be moving... rather than basing on a fixed hardcoded block height that's acceptable.