Persisting a unique DHT for different lookup and updating the routing table

[Ayms]

Am I reading the code wrongly or it is not possible right now to create once a dht and persist it for different lookup, as well as updating the routing table continuously (and testing the nodes)? (as far as I see the routing table is supposed to be recreated for each lookup)

I saw #16 but apparently the fix is to bootstrap the dht at creation.

Is it on purpose, or in the TODO list?

[feross]

The routing table is persisted between lookups. As new nodes are discovered, they are added to the routing table.

However, to do a lookup an additional, temporary routing table is created and nodes are added to it until no closer nodes can be found. This is just an implementation detail though.

I believe this issue can be closed because the module is already working as you want it to.