daos

Really enjoyed this conversation with @bpetes.eth. I especially appreciated the insights into the emerging readiness of onchain tooling/execution layer (Hats, Farcaster etc) to actually (finally) implement some of the interoperable goodness we have been dreaming about for DAOs. 

Great conversation @thethriller

፨ Legal Entities for Web3 & DAOs 🎙️Host of Just DAO It! Podcast & /daos Channel 💼 Founder of MIDAO 🟪 Purple 🏴 bDAO nf.td/thethriller

@teamSobol
DAOin’ w/ @dimoDAO, @hatsprotocol
Alum: @banklesssDAO, CityDAO, PolygonDAO

Really enjoyed this conversation with @bpetes.eth. I especially appreciated the insights into the emerging readiness of onchain tooling/execution layer (Hats, Farcaster etc) to actually (finally) implement some of the interoperable goodness we have been dreaming about for DAOs. 

Great conversation @thethriller

https://podcasts.apple.com/us/podcast/just-dao-it-dao-news-interview-with-bryan-petes-from-sobol/id1630815761?i=1000659322808

yeoro.eth → db.team → /slc → SuperBenefitDAO, All in For Sport → "purpose aligned networks of small autonomous teams”

I'm still bullish Sobol

I think starting with experiments in structuring small team projects that can scale into DAO type networks. For structure (speculatively):
- ENS (sub domains) as a project anchor/wrappers
- FC channels and DCs (when ready) as colab/coordination primitives
- FC login/Privy/something else for identity
- EAS for agreements
- Hats for roles
- Something to hold group state at different scales, globally addressable
- And Sobol to surface the network and make the above visible and accessible

Thanks 🙏. What’s the first thing to build given where we find ourselves in this moment?