2 ms·
We did spend a little bit of time documenting the earlier v0.3 protocol, as you have linked, but the protocol has changed significantly in design twice since th
by neilalexander 2y ago
We did spend a little bit of time documenting the earlier v0.3 protocol, as you have linked, but the protocol has changed significantly in design twice since then. v0.4 changed the DHT quite a bit and v0.5 removed the DHT altogether. As a research project it likely will continue to change until we settle on a design we are happier with, at which point we will definitely spend more time documenting it.
The need for ordered/reliable links is mostly for convenience of development at this stage, but that can be fixed for sure.
- Rhapso 2y agoLook at https://arxiv.org/pdf/1502.06461 https://arxiv.org/pdf/1502.06461 if you want to try a chord dht again. Kademlia is a lot less intuitive, but by not ever assuming it's tables are correct, it handles and corrects inconsistency (and malicious nodes) better. Chapter 6 of this pile of (my) crap https://scholarworks.gsu.edu/cs_diss/106/ https://scholarworks.gsu.edu/cs_diss/106/ talks about doing latency optimization on dht routing. Basically just embedding then network graph into a metric space.
- godelski 2y agoSome documentation can help with those issues though. I find it helps more because you’re writing to yourself why you’re making certain decisions and it helps when you decide to make others. It just so happens that it’s also a great way to onboard people.