0x9e0e9d25…57b1sent to0xf790a5f5…1365·#23,726,674·view on Etherscan
Just trying to understand better, what problem in Nouns DAO are you guys actually trying to solve with this? From what I read, it sounds like Moosh is getting its infra tested while Nouns gets a decentralized hosting setup, but the main issue we’ve faced with frontends isn’t really AWS going down. The problem has always been that when funding stops, the infrastructure behind those sites goes dark.
A Nouns frontend doesn’t just run on a web server. It depends on a bunch of external services like RPC endpoints to read and write to the blockchain, subgraphs to fetch indexed proposal and auction data, APIs for Farcaster or Discord integration, and sometimes even image or metadata hosting. Each of these services has its own cost, and when the DAO stops paying the bills or the developer maintaining it disappears, everything breaks. That’s why we’ve seen frontends vanish overnight before, not because AWS failed, but because the payments or maintenance stopped.
So I’m wondering, how does Moosh actually solve that? Does it decentralize the full stack, including RPCs and subgraphs, or only handle the hosting layer? Because even if we self-host the frontend, it still relies on paid endpoints for data. If those go unpaid, we end up in the same situation again.
Basically, if the goal is to make Nouns infra censorship resistant, that’s great, but it also needs to be financially sustainable. Otherwise, decentralizing the hosting is like putting a backup generator in a house that still depends on someone else’s water and gas lines, it might keep the lights on, but the rest still shuts down when the bills aren’t paid.