Closed zllovesuki closed 2 years ago
2030fedea419590fc1b2611176f1cd73fdc83f3a partially unblocks this issue by providing key consistency during join/leave + concurrent kv operations
supposedly implemented in c31106400fcf812b1423d0ee862c7b9ccaec55de, however more testing is required
in concurrent kv operations while nodes are joining and leaving, it is possible that keys are transferred, but the network does not know about the new/old node yet. therefore, a concurrent kv could still be serviced by the old successor, causing lookup to fail.
possible solution: https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.71.6111&rep=rep1&type=pdf
this must be resolved before we can put certmagic.Storage on DHT