Week 11 of 12 · Intermediate

Communities And Institutions

You study decentralized communities as human institutions: network states and pop-up cities, cooperatives, and the commons governance work of Elinor Ostrom. You finish with a practical guide to running a decentralized community responsibly.

3 hours18 slides7 min read
Open slidesRead study notes

You Will Be Able To

  • Describe the network state idea and the pop-up city format as experiments.
  • Explain how a cooperative is owned and governed.
  • List Ostrom's design principles for governing a commons.
  • Apply those principles to a digital or local community.
  • Write a short charter with roles, rules, conflict steps, and exit rights.

From Protocols To People

Ten weeks of technical tools lead to one question. Who are they for? Protocols, contracts, and proofs help only when a group of people uses them to cooperate. Week 8 showed that DAO failures are often social: unclear roles, burnout, and unresolved disputes. This week studies the human side directly.

A community is a group with shared purpose, shared resources, and shared habits. An institution is a set of lasting rules that shapes how the group acts. Decentralized communities replace a single owner with distributed decision making, but they still need institutions. Without clear rules, informal power appears anyway, and it is harder to see and question.

We study three bodies of experience. Network states and pop-up cities are recent experiments that bring online groups into physical places. Cooperatives are a long-standing model of shared ownership. Commons governance, from the work of Elinor Ostrom, gives evidence about what makes shared resources last.

Network States

The term network state comes from the 2022 book The Network State by Balaji Srinivasan. He describes a path that starts with an online community built around a shared purpose and moral vision. The community organizes, builds a cooperative economy, buys land in places around the world, and seeks recognition from existing governments. A network state, in this vision, is a highly aligned online community with a capacity for collective action that crowdfunds territory.

Treat this as an idea under test, not an established institution. Supporters see a way for people to form communities by choice instead of by birthplace. Critics raise questions about legal status, about who is excluded, about whether shared online values hold up when people live together, and about how a founder-led group handles dissent. Both views are useful to a student. Your task is to learn which questions the experiments answer.

A helpful habit is to list the specific, checkable claims of any project: how many residents, which legal structure, how decisions are made, what happens to a member who disagrees. Claims that can be checked tell you more than slogans.

Pop-Up Cities

A pop-up city is a temporary gathering where a community lives and works together for a few weeks, usually in a rented venue or a small town. It is a small-scale test of the network state idea. Participants experience shared housing, shared meals, talks, and projects in a place that was not built for them.

Zuzalu, held in Montenegro in 2023, was an early example. It gathered several hundred residents for about two months, with a program built by participants around topics such as longevity, public goods, and cryptography. It inspired later events such as Vitalia, Edge City, Zuconnect, and other gatherings, each trying its own format. Organizers learned about practical questions: visas, venues, safety, costs, and how a program emerges from participant proposals.

Pop-up cities teach useful lessons for builders. Short events allow fast learning at low risk. Residents form real relationships, which strengthen online groups afterward. The hard problems are follow-through and continuity. A beautiful month can fade if no institution carries the work to the next one. Good organizers therefore define what lasting outputs they want, such as a shared tool, a published report, or a local partnership.

Cooperatives

A cooperative is an organization owned and governed by its members, who may be workers, customers, producers, or residents. The International Cooperative Alliance lists shared principles, including voluntary and open membership, democratic member control, member economic participation, autonomy, education, cooperation among cooperatives, and concern for community.

The central rule is one member, one vote, regardless of how much money a member invests. Profits, called surplus, are shared according to use or work rather than only capital. Credit unions, farm cooperatives, housing cooperatives, and worker-owned shops follow this pattern. The Mondragon group in the Basque Country of Spain is a well known federation of worker cooperatives that has operated for decades.

Cooperatives matter to a decentralized builder because they solve a problem DAOs struggle with: aligning ownership with participation. Platform cooperatives apply the model to digital services, where the people who use or work on the platform own it. A DAO can borrow the structure, such as one member one vote with identity checks, member-set budgets, and surplus sharing. A cooperative can borrow the tools, such as transparent ledgers and programmable payments. Legal form varies by country, so local advice is essential.

Commons Governance After Elinor Ostrom

A commons is a resource shared by a group, such as a fishery, a forest, an irrigation system, or an open-source codebase. Garrett Hardin's 1968 essay The Tragedy of the Commons argued that shared resources get overused because each person gains from taking more while the cost is spread over everyone. His conclusion was that only private ownership or state control could prevent ruin.

Elinor Ostrom examined real cases and found a third path. She studied communities in Switzerland, Japan, Spain, the Philippines, and elsewhere that managed shared resources successfully for centuries without privatization or central control. For this work she won the Nobel Prize in Economic Sciences in 2009, the first woman to do so. Her book Governing the Commons describes the common features of these successful cases as design principles.

Applying Ostrom To Digital Communities

Ostrom's principles translate into questions a community builder can ask. Who counts as a member, and how does a newcomer join? Are the rules written in simple language, and do members help change them? Who watches for misuse, and how are they chosen? What happens after a first mistake, and after a fifth? Where does a dispute go, and how long does it take?

Take an open-source project as an example. Boundaries come from contributor and maintainer roles. Rules appear in a contribution guide and a code of conduct. Monitoring comes through code review. Sanctions escalate from a reminder to a temporary ban. Conflict resolution may use a small committee. Nesting appears when subprojects have their own maintainers under the main project.

Apply it to a local community too, such as a neighborhood tool library or a shared garden. The same questions guide a fair schedule, a repair fund, and a fair way to handle someone who never returns borrowed tools. Ostrom's lesson is that people can govern shared resources well when the design gives them voice, visibility, and fair consequences.

Ostrom's Design Principles For A Commons
PrincipleIn an open source project
Clear boundariesWho is a maintainer, who is a user
Local rulesContribution guide fits this project
Collective choiceContributors can propose rule changes
MonitoringPublic logs and reviews
Graduated sanctionsWarning before ban
Conflict resolutionKnown mediators

The first six of eight, each with a digital counterpart. The last two are outside recognition and nesting. Source: Ostrom, Governing the Commons, 1990; course synthesis

Running A Decentralized Community Responsibly

Responsible practice begins before launch. Write a charter that states purpose, membership, roles, decision rules, and how the charter can change. Publish who holds admin keys and what each key can do. Name a small group that handles safety reports, and give members a way to reach them privately.

Plan for conflict and for exit. Choose a dispute process with clear steps: talk, mediate, decide, appeal. Make leaving easy by letting members export their data and take their contributions. Protect minority voices with meeting norms, written summaries, and tools such as Pol.is that surface views across groups. Protect people's privacy, as week 7 showed, and collect only the data that you need.

Handle money and legal duties in the open. Choose a legal wrapper that fits the country, such as an association, foundation, or cooperative, and ask a qualified adviser. Keep accounts public to the extent the law allows. Share decision authority with newcomers gradually, so power does not stay with founders by default. Review the charter regularly and record each change with its reason.

Handling A Conflict
  1. Someone reports a problem
  2. A neutral member reviews it
  3. Both sides respond
  4. A decision is posted with reasons
  5. An appeal path exists

Cheap and quick resolution keeps small disputes from becoming splits.

Key Terms

Network state
A proposed model where an online community with shared values gains physical territory and recognition.
Pop-up city
A temporary gathering where a community lives and works together for a few weeks.
Cooperative
An organization owned and governed by its members, usually with one member one vote.
Surplus
Money left after costs in a cooperative, shared by member use or work.
Commons
A resource shared and managed by a group.
Tragedy of the commons
The idea that shared resources are overused when users gain individually and share the costs.
Design principles
Ostrom's list of features found in long-lasting commons governance.
Graduated sanctions
Penalties that grow with the seriousness and repetition of a rule break.
Charter
A written statement of a community's purpose, roles, rules, and how they change.

Exercise: Write A Community Charter And Test It Against Ostrom

  1. Choose a real or imagined community of 20 to 200 people, such as a neighborhood group, a study circle, or an open-source project.
  2. Write a one page charter covering purpose, who can join, roles, how decisions are made, and how the charter changes.
  3. Add a conflict section with four steps, and a leaving section describing data export and what members keep.
  4. List Ostrom's eight principles in a table and mark where your charter satisfies each one.
  5. Find the two weakest principles and rewrite the charter text to strengthen them.
  6. Swap charters with a partner and give two written suggestions each.

Further Reading