###### tags: `DAO` # MetaPod Sustainability Model MetaPod should remain bottom up and a public good. There shouldn't be a business model, but instead a Sustainability Model. Sustainability should come from grants, sponsorships, treasury diversification and DeFi activity. ### Two main branches of MetaPod: 1. Events - top of funnel for program - onboards both web2 & web3 projects - bottom up contributor model - collects sponsorship funding 2. Program - accelerate DAO launches - resource hub & connectors - fuels partner pipelines & continued funding - collects sponsorship funding - collects and distributes grant funding Both the event and accelerator models should be fully automated with little labor overhead for MP DAO members. ## Events Events are the life blood of MetaPod and the main bottom up driver for the ecosystem. A templatized 'micro-event' package model should be provided to the public that enables anyone to start a local event as a 'MetaPod Host'. Event process doc outline (WIP) https://hackmd.io/@MetaPod/SkhEuQqEY Leverage ticketbot to process incoming event host application requests. Event packages include: - grant funding for venue/expenses/labor - Pizza DAO pizza party - sponsorship banners - MetaGuide ops support for planning/running - promotion/networking for event/speakers Sponsorship packages can be offered based on event quantity, location and type. There can be separate packages for program sponsorships and/or combined packages. |Tier|Cost |Micro-Events | Location(s) | Type | |----|--------|-------------|-------------|----------| |1 | $5,000 | 5 |NY, CA, CO |pitch | |2 |$10,000 | 10 | any |fireside | |3 |$15,000 | 15 | any |workshop | |4 |$20,000 | 20 | any | any | Sponsorships can be paid in stables, ETH, or native tokens. Larger events can be handled separately As the top of the vetting layer, events help identify projects that can be a good fit for the program. ### To-do - start a pilot program for the micro-events - micro-event templatized process - vetting process for projects coming through event funnel - recruit initial hosts (we have some on backburner) ## Program MP DAO members should utltimately act as creators/curators of and connectors to resources (i.e. systems/processes, contributors, funding and advisory). **Use MP s0 for resource creation/curation and then dog food it for s1. Then a clearer decision on verticals and stages can emerge.** Projects brought in through the events funnel gain FREE access to the MetaPod resource hub and can schedule weekly calls. *The accelerator program should remain open year around.* - have a public calendar (calendly) for the MP DAO members to automate call scheduling for the participants. - 1-week bootcamp - quarterly seasons (intensive) - non-bootcamp week = 1 fireside per week - workshops based on scheduled calls by participants Defining specific verticals and the different stage projects that should participate in the MP program can be decided in a more emergent way as the MetaPod program continues to take shape (like recognizing POAPathon as a good fit), but ultimately the program should remain more open and MP DAO members should focus on leveraging the resource hub and feeding the pipelines. Keep automation/efficiency/scalability in mind while designing the program structure. ### To-do - define success metrics - decide on qualitative vs quantitative results - where does MetaPod (want to) fall on the spectrum? - build and maintain a robust resource hub ## Tokenomics Introduce POD Tokens (index type token) Don't take a % of the network of a MP project, but instead offer the OPTION to trade POD for the MP projects' tokens/DAO shares Have sponsors/pipeline partners add liquidity for POD token. Interact with DeFi activities involving sponsors' & MP projects' tokens. Stake portion of stables & ETH in secure, slow(er) grow DeFi protocols. ## DAO structure Event hosts, alumni and advisors should have the opportunity to join the DAO and contribute as a connector/curator/creator. DAO structure Doc (WIP) https://hackmd.io/@MetaPod/HyHAKQG0t