yggdrasil-go VS devp2p

> The next version will make it much simpler to deploy isolated networks by using TLS roots to prevent accidental peerings.

Is that PR #1038 [1]? Any info on how to use that feature and whether it works over multicast as well?

I noticed this PR uses SHA-1 for matching fingerprints. SHA-1 has been broken for 13 years now. Is it possible to use something more secure?

> It's also worth noting that Yggdrasil doesn't have the equivalent of "peer exchange" — only directly connected peers would ever find out your public IP address. Yggdrasil will not form new peerings automatically, with the single exception being multicast-discovered nodes on the same LAN.

Right, my worry is that by having a server with a public IPv4 address and Yggdrasil running on an open port (so that my other nodes can connect to it) will allow someone to connect to it (either on purpose or accidentally) and cause my traffic to route over their node(s) and/or the public mesh.

Thanks!

[1] https://github.com/yggdrasil-network/yggdrasil-go/pull/1038

From a purely networking perspective, there are far better solutions than tailscale.

Have a look at full mesh VPNs like:

https://github.com/cjdelisle/cjdns

https://github.com/yggdrasil-network/yggdrasil-go

https://github.com/gsliepen/tinc

https://github.com/costela/wesher

These build actual mesh networks where every node is equal and can serve as a router for other nodes to resolve difficult network topologies (where some nodes might not be connected to the internet, but do have connections to other nodes with an internet connection).

Sending data through multiple routers is also possible. They also deal with nodes disappearing and change routes accordingly.

tailscale (and similar solutions like netbird) still use a bunch of "proxy servers" for that. You can set them up on intermediate nodes, but that have to be dealt with manually (and you get two kinds of nodes).

The only real solution long-term is completely peer-to-peer ad-hoc networking that doesn't depend on BGP.

A few projects are in similar territory but none I've seen are working at the layer of bypassing BGP. Many are just acting as an overlay; which works to an extent. https://github.com/yggdrasil-network/yggdrasil-go

It's probably begging for a different model of the "internet" and where data lives.

My requirements:

1. Offline-first applications that sync via a pub/sub DHT of trusted peers. More details here but basically allows bypassing BGP.

It seems like you can limit connections to your node with AllowedPublicKeys (ref).

at least on the official discord the recommended way if you don’t want to play on a public server is using yggdrasil

For example the latest addition to devp2p was snap sync: https://github.com/ethereum/devp2p

So your proposed blocks wouldn't be broadcast to all nodes, you can read more about how that works here but essentially it's a p2p network so you'll only be connected to some nodes and bad blocks won't propagate across it.

https://spec.filecoin.io/systems/filecoin_nodes/network/ https://iohk.io/en/blog/posts/2021/04/06/boosting-network-decentralization-with-p2p/ https://github.com/ethereum/devp2p

For example Ethereum is a P2P protocol (https://github.com/ethereum/devp2p), most newer coins have extensive and complicated network requirements. Without unrestricted network access in your CI it's going to be difficult to get an implementation like this that actually works in practice (someone said commits as input data but I can't see this working either, it's just going to be a non-starter based on complexity). At this point the person trying to do this is most likely going to say fuck it, it's not worth the effort and go find another tool they can exploit. That is the reality.

See here: https://github.com/ethereum/devp2p/blob/master/caps/les.md