title: What are the most recent bittorrent DHT implementation recommendations?
body: <p>I'm working on implementing yet another bittorrent client and at this time struggling with DHT. It is implemented accordingly to this specification <a href="http://www.bittorrent.org/beps/bep_0005.html" rel="nofollow">http://www.bittorrent.org/beps/bep_0005.html</a> but starting debugging it I noticed that other nodes' responses on the network vary.</p>
  
  <p>For example, find_node is supposed to return either target node info or 8 closest nodes. Most of the nodes reply with 34 closest nodes and usually only 1 - 3 nodes from those 34 successfully reply to the consequent ping request.</p>
  
  <p>Is there another document with better implementation recommendation? May be it is already proved that using 15 minutes interval to change the nodes state to questionable is not efficient and I have to use 10 or other number? Where can I find the best up to date suggestions?</p>
  
  <p>There is another strange thing. Bootstrap nodes like router.bittorrent.com reply with even more closest nodes and usually the "nodes" BDictionary property  buffer length is not divisible to 6 (compact node info: 4 for IP and 2 for port). For now, I simply cut off the buffer at the closest divisible to 6 length but all that is strange. Does anybody know why that might happen?</p>