Crowdsourced CDN: bad idea?

Tl:dr: have a WAF/reverse proxy with caching for edge and a mesh linking component. Worth it to build out for a full P2P CDN, or pass?

Hey y’all, so for the past couple months to learn rust I tried writing a web application firewall and reverse proxy. I’m happy with the WAF now, does the normal stuff and bites back a little. poisons AI bots if detected in a tarpit, follows malicious IP blocklists, stealth by default (leaves socket to hang from some attacks, opinionated to reveal little info to attackers like erros or server info). Considered also scanning a couple ports of connecting clients during the bot challenge to look for common command and control protocols to detect botnets, although could be invasive or resource intensive. But, only so much you can do against ddos with a single point of presence anyway.

So I’ve moved to building a mesh network into it with WireGuard/QUIC. The idea is to have a crowd sourced CDN and to share threat intelligence to react to attacks quickly. There’s still work to get it to this point, P2P is hard and widens the attack surface. The pure mesh networking part is almost functional on a small test network but i still need to stress test and optimize. True P2P gets more complicated though. So that’s why I’m asking - I could release it as is and build out the mesh part as a private mini CDN for myself.

My proposition is this: we share ownership of the infrastructure. You run a node, you get to run your stuff through the network as a first class citizen. If it gets to a stable point where there’s enough capacity, we let people without servers host stuff through it too. Anyone interested in running this? Love to know, I’ll keep hacking.

Or if I’m an idiot let me know too. DNS is the other side to this and will be simpler without P2P the way I’m envisioning it.