devp2p VS Nebula

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

Nebula - Peer-to-peer overlay network. Developed and used internally by Slack. Similar to Tailscale but completely open source. Doesn't use WireGuard. Written in Go.

(I am a Nebula maintainer.) We recently merged support for gVisor-based services, although it's very new, and I don't know of much experimentation that's been done with it yet: https://github.com/slackhq/nebula/pull/965

Nebula, originally from Slack[0].

Wireguard rightly gets a lot of attention, but Nebula is a really simple and easy to deploy mesh network that is often overlooked.

It does lack a management GUI and that stuff is very much DIY.

[0] https://github.com/slackhq/nebula

Fair enough about the android mobile client... My use case only involves meshing linux appliances across various networks so we only need the nebula core binaries which are under MIT license

https://github.com/slackhq/nebula/blob/master/LICENSE

That's not at all confusing with Slack's Nebula. https://github.com/slackhq/nebula

Sounds like a bunch of your pain points are just related to needing an online CA or ICA. But, looking through the Nebula docs I don't know that it supports things like CRL addresses where you could host the CRL, or OCSP responders. Someone got support for an OCSP responder but never submitted a PR with completed code: https://github.com/slackhq/nebula/issues/72

Nebula is a scalable, cross-platform overlay networking tool focused on performance, simplicity, and security. This portable tool is equally adapted for linking a small number of computers or scaling to connect tens of thousands. It integrates encryption, security groups, certificates, and tunneling into a powerful, cohesive connectivity solution. Thanks for the recommendation go to jmeador42.

Replying to my own comment as I can no longer edit it:

The folks over at Slack had an interesting discussion regarding the the "battle of the VPNs" article published by Netmaker I sourced in my parent comment:

https://github.com/slackhq/nebula/discussions/911

Interesting. I thought recognized the logo, apparently seems to be a commercial support offering of https://github.com/slackhq/nebula and they support the "nebula" iOS app. I had been using for nebula/defined in the past.

Nebula: Is super easy to get running. It uses an interesting angle, working on the service and not just the device level. Unfortunately their NAT support seems to be still quite problematic and I am not going to maintain all those forwarded ports manually. There is a PR to support PCP but even if that ever gets applied I am not sure how well that will play with older routers. While it should be battle proven at slack, the community seems to be not that active. It still has the in-house tool that just got released.