investigate possible infinite recursion in requestQueryId
I just got hit by this by running against a buggy version that never states its own responsibility but always sends a FORWARD.
Maybe not important for simulation scenarios, where no node is buggy or evil, but should be pretty easy to fix.
periodic checking and maintenance of cache invariance
schmittlauch
deleted branch refactorSuccessorsPredecessors from schmittlauch/Hash2Pub
2020-06-27 15:22:54 +02:00
make sure only verified nodes are used as neighbours
Evaluate dynamic vs. static cache invariant node number
improve termination of lookup
periodic cache maintenance
edge case: responsibility for slices > 1/2 key space