cjdns VS devp2p

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).

I'm excited about P2P/decentralized/distributed overlay networks. Still catching up so would be grateful for tips on resources.

Pinecone[0][1], newer initiative made by former Yggdrasil[2] maker(s).

CJDNS[3].

AIUI CJDNS relies on intermediary high-uptime discoverable router nodes which is what is motivating Pinecone. POKT[4][5] to CJDNS seems like what Filecoin is to IPFS.

I'm yet to get around to doing the groundwork of grokking more established solutions like B.A.T.M.A.N. and how all these pieces fit together,

[0]: https://fosdem.org/2022/schedule/event/matrix_p2p_pinecone/

[1]: https://github.com/matrix-org/pinecone

[2]: https://yggdrasil-network.github.io/

[3]: https://github.com/cjdelisle/cjdns/

[4]: https://www.pokt.network/

[5]: https://piped.kavin.rocks/watch?v=-xgRUAA_p5E

CJDNS, a further step towards automatic and cryptographically secure nodes at the protocol level#23077

yggdrasil is a cjdns clone with different routing

cjdns has a whitepaper

https://github.com/cjdelisle/cjdns/blob/master/doc/Whitepape...

I was really excited for a moment, because I thought this was cjdns https://github.com/cjdelisle/cjdns.

https://github.com/slackhq/nebula https://github.com/yggdrasil-network/yggdrasil-go https://github.com/cjdelisle/cjdns

> To be honest I kind of wish someone would build a proof-of-bandwidth crypto.

https://pkt.cash/ exists "built to incentivize the growth of infrastructure," and "PKT Network is designed to decentralize internet access around the world by enabling anyone to become an ISP." [0]

Presumably this will work with cjdns. https://github.com/cjdelisle/cjdns

[0]: https://pkt.cash/PKT_Network_v1.0_2021.02.01.pdf

cjdns

You probably already know these: https://github.com/cjdelisle/cjdns/ https://yggdrasil-network.github.io/

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.