Protocolizing Tokenized Communities
summary
Argues that tokenized communities must be engineered as repeatable social protocols rather than vague culture, proposing four concrete steps: a handbook in source control, a defined cycle time, phased onboarding/leveling/building, and componentized modules that are modular and self‑sustaining. Implements examples: auction onboarding (nouns style), prediction‑market grants, and Machinations models; experiments with Polygon Labs aim to make grants self‑funding. Flags three real risks: burnout, internal capture, and litigation, and shows how incentives and mechanism design mitigate them.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:05Community vs protocol first
- 3:32Tokenized communities
- 5:21Social protocols
- 7:30Transforming to social protocol
- 10:39Defining cycle phases
- 12:06Componentizing mechanisms
- 15:34Unbundling rebundling
- 17:00Risks of not evolving tokenized communities
- 19:07Beyond DeFi nation-states
- 20:58Closing remarks
related talks
23mTech Beyond the Algorithm: Building for Communities (and Profit)
29mOnboarding Diversity: Exploring community challenges and unique solutions
31mToken Engineering Panel
15mToken Engineering Commons
21mThe best strategies for decentralized platforms and social media
27mToken Engineering Toolkit: Practical Insight
37mMy Little Token (Part 2)
30mCommunity Building in the Web3 Era Panel