3 ms·
Asymmetric keys as the only addresses, and an authenticated version of Virtual Ring Routing as the routing protocol. That guarantees you're talking to the corre
by JoshTriplett 5y ago
Asymmetric keys as the only addresses, and an authenticated version of Virtual Ring Routing as the routing protocol. That guarantees you're talking to the correct server for an address, that addresses never need to change, and that a server can have as many different addresses as it needs to.
Build in a layer for onion routing as well, so that all the servers in the middle don't automatically know who you're trying to reach.
- neilalexander 5y agoYou have very closely described Yggdrasil, which is a proof-of-concept for these sorts of ideas: https://yggdrasil-network.github.io/ https://yggdrasil-network.github.io/
- JoshTriplett 5y agoAs far as I can tell, though, it sounds like Yggdrasil is still an overlay network, designed to bridge nodes running Yggdrasil across a network that isn't. I'd want to see that as part of the base network rather than as an overlay.
- neilalexander 5y agoIndeed, because it’s pretty much the only way to feasibly scale-test something like this without asking people to replace their hardware or breaking them in other ways. Maybe one day we will see protocols like this at lower layers.
- native_samples 5y agoTry looking at cjdns, it provides what you want but also at a base layer.