VzxPLnHqr on Nostr: Duly noted regarding the links. Apparently I need nostr training wheels :-P I rule ...
Duly noted regarding the links. Apparently I need nostr training wheels :-P
I rule out cjdns for the same reason you do. Regarding yggdrasil, supposedly they are doing some sort of routing magic per https://yggdrasil-network.github.io/implementation.html#what-does-yggdrasil-do-differently the most succinct description I could find was:
"... A spanning tree is used to provide synchronisation and to allow nodes to allocate themselves a set of tree coordinates, which are used to exchange and establish bootstrap and path setup messages. Nodes then exchange bloom filters which contain information about which keyspace neighbours are reachable through each node. Intermediate nodes then populate their routing tables with these paths, enabling nodes to forward packets closer to their destination public key."
It feels somewhat similar to your design, but yours seems simpler.
I rule out cjdns for the same reason you do. Regarding yggdrasil, supposedly they are doing some sort of routing magic per https://yggdrasil-network.github.io/implementation.html#what-does-yggdrasil-do-differently the most succinct description I could find was:
"... A spanning tree is used to provide synchronisation and to allow nodes to allocate themselves a set of tree coordinates, which are used to exchange and establish bootstrap and path setup messages. Nodes then exchange bloom filters which contain information about which keyspace neighbours are reachable through each node. Intermediate nodes then populate their routing tables with these paths, enabling nodes to forward packets closer to their destination public key."
It feels somewhat similar to your design, but yours seems simpler.