TL;DR

A symbiotic experiment for Nouns and Moosh. Nouns get a cloud, Moosh gets its infra battle-tested.

Requesting 60K USDC

Who are we?

We are a team of passionate Web3 natives building Moosh, a peer to peer cloud marketplace and social network. We are decentralizing Web3 from the hardware layer up.

What we want to deliver:

If centralized hosting ever went down, Nouns lives on.

• Cloud hosting desktop application R&D based on our MVP
• App templates for Nouns-specific use cases in the Moosh decentralized cloud marketplace Beta release
  • Strengthen Nouns DAO’s censorship resistance with radical decentralization
  • Proliferate Nouns by exposing it to our users in the Moosh app
• Determine resource usage for each of the Nouns frontends
  • To assess hardware requirements for the Nouns Cloud v1
  • As a guide for optimisation by the Nouns-monorepo and Nouns95/berryos developers
• Hardware distributed to Nouners to run the Nouns Cloud
  • Initially to run redundant instances of the Nouns frontends
  • Organic use-case expansion, especially to API dependencies for the Nouns frontends such as Ethereum RPC or a Farcaster Hubble node.

Why is this important?

See the previous Nouns topic discussion here for why it’s important for Nouns DAO.

It’s an immediate value add for Nouns that will go on to help many more Web3 communities through bringing uncompromised Web3 infra solutions to their ecosystems.

In return it gives Moosh a tangible use case where we can test our peer to peer provider solution in real networking scenarios that we’ve designed for.

What Moosh need to build to make this happen:

1. Nouns-specific app templates for several Nouns frontends that provide a drag and drop deployment user experience via the Moosh Desktop application, to be released in the Moosh Beta.
   • Nouns monorepo (.wtf)
     • A nouns.wtf template would make the auction dapp available via self-hosting to make auctions resilient against DOS attacks.
   • Berry OS
     • Collaborate with Wylin.eth for delivering Nouns95/BerryOS app templates
   • Request collaboration with .camp contributors
2. Moosh will secure instances by automatically providing a unique, identity-based subdomain for secure public accessibility via https.
   • Eg. A custom DNS solution requires R&D to implement a DNS-01 challenge resolver and integrate with the template system.
   • Users can also bring their own domains but this feature ensures they can always get TLS encryption regardless of whether they own a domain.
3. Self-hosting: Currently our desktop app is for VPS customers, but we will add a feature for providers to provision and manage workloads on their own hardware with all the app’s features remaining.
   • Primarily for the Nouns community, we will build out the self-hosting use-case where a provider wants to use the Moosh Desktop features to utilise their own physical hardware for deployments.
   • For those persons that aren’t hardware savvy they can choose to lease machines over the Moosh marketplace (e.g. from other Nouners) to deploy the templates from point 1.
4. Bonus Easter Egg: Nouns PFPs for Moosh social graph
5. Nouns x Moosh media/branding pack
   • Work with Nouner illustrators for visuals to help promote the Nouns Cloud and Moosh joint effort

Let’s put all those beautiful Nouns frontends to work! We can get compounding value from all of those previous/current projects.

Budget & Admin

None of this grant proposal is retroactive. It makes a considerable positive dent in the operational costs for Moosh’s Beta development and will bring Nouns Cloud V1 roadmap to fruition.

Moosh Team x 3 months	40,000USDC
5-10 ‘mini PCs," ~16 core 64 GB RAM with 2TB minimum. Plus testing hardware for Moosh.	~ 1500-2000 US each ~20,000USDC

Contacts

admin@moosh.gg x.com/mooshnet