A first-principles derivation of Society Protocol, and how it differs from Network States, Network Nations, and everything else it gets compared to.
There’s a recurring problem when people first encounter Society Protocol. They ask “what is it like?” and every answer fails. “It’s a blockchain” — no, blockchains store assets. “It’s a DAO” — no, DAOs vote with tokens. “It’s a Network State” — no, but this one gets closer, and it’s worth understanding why it still fails.
The problem isn’t that SP is complicated. The problem is that the available words are Trojan horses. Each one comes loaded with assumptions baked in. The listener fills the gaps with what they already know, thinks they’ve understood, and then says something that reveals they haven’t.
This post is an attempt to fix that. Not by comparing SP to things it isn’t, but by deriving it from what any collective actually needs.
The Derivation
Start from a single question: what does any collective need in order to act together durably?
Not “what does a state need.” Not “what does a DAO need.” Just: any group of entities that wants to do something together, over time, without dissolving.
The list is short and non-negotiable:
- A way to know who is in the group
- A way to know what is true about the group’s state
- A way to know what the group wants
- A way to make decisions
- A way to enforce those decisions
- A way to remember what happened
- A way to change without collapsing
- A way to exit without losing everything
None of these are design choices. Each is forced by the premise. A group that lacks any one of them either can’t act, can’t act durably, or dissolves under pressure.
Now check the existing forms against this list.
Online community — has exit, has a weak kind of memory. Lacks enforcement, lacks real governance, lacks accountability. Dissolves when the pressure is real.
Corporation — has enforcement, memory, governance, membership. But it’s narrow: only economic function. Cannot be a society.
Nation-State — has all eight, but pays for them with territory, coercion, slow coordination, and elite capture. Can’t serve translocal communities. Can’t update at modern speed.
DAO — has enforcement (code) and memory (chain). Lacks sybil-resistant membership, persistent identity, accountability over time. Every metric is fakeable.
Network State (Balaji) — has a mission, a founder, an aspiration to territory and recognition. Defers membership, identity, and accountability to the future. The substrate doesn’t exist yet.
Network Nation (De Filippi et al.) — has belonging, commons, entanglement. Lacks enforcement, lacks persistent identity, lacks a mechanism to hold commitments over time. Names the problem beautifully. Can’t build the answer.
Each of these fails on at least one item on the list. The failure modes cluster around the same few primitives: persistent identity, sybil-resistant membership, enforcement over time, and cheap exit.
Society Protocol is what you get when you require all eight simultaneously. Not because it’s ambitious, but because each is forced by the premise that a collective should be able to act together durably. Once you stop inheriting assumptions from existing forms and derive from requirements, you arrive at:
- a Timeline (memory)
- Actors (persistent identity)
- Energy (money that reflects contribution)
- Value Functions (explicit value system)
- modular governance (decisions)
- automated enforcement (code, not police)
- Portal (exit without loss)
- privacy tiers (not everything belongs in the public record)
That’s SP. It’s not a type of organization. It’s the substrate any organization needs in order to become self-governing at scale. It sits below Network State and Network Nation the way TCP/IP sits below the web — not a competitor to them, the layer they’d have to run on.
Why This Is Ontologically Hard
Because people compare instead of derive.
Comparison asks: “what is this like?” Derivation asks: “what is required?” Comparison tells you what’s similar. Derivation tells you what’s necessary. SP is only visible if you derive. If you compare, you’ll always land on the nearest available category and assume you understand it.
Worse: every available word is a Trojan horse.
- “Network” → implies the network is the unit. SP’s unit is the Actor.
- “State” → implies territory, sovereignty, monopoly on force.
- “DAO” → implies tokens, proposals, periodic votes.
- “Blockchain” → implies assets, blocks, mining or staking.
- “Identity” → implies verification, credential, proof at a point in time.
- “Money” → implies stock, supply, inflation.
- “Community” → implies shared interest, low commitment.
- “Governance” → implies representatives, elections, cycles.
Each word is mostly right for the thing it names and specifically wrong for SP. The listener fills the gaps with pre-loaded assumptions, thinks they’ve understood, and then says something that reveals they haven’t.
This is what happens when someone matches SP to “Network State.” The word “State” smuggles in territory and recognition. The listener thinks they’ve found the category. They haven’t.
The only way out is to either forbid comparison and force derivation, or let the listener run their assumption, watch it fail, and then ask what doesn’t fail. The second is better. It’s Socratic. It makes them do the work.
The Table
| Attribute | Society Protocol | Network Nation | Network State | (Digitally extended) Nation-State | Online Community |
|---|---|---|---|---|---|
| Sovereignty model | Full-stack internal sovereignty over the shared state. No territorial claim required — but diplomatic recognition is welcome. States can adopt SP instances directly. | Functional, domain-specific, no territorial claims | Aspires to territorial sovereignty and diplomatic recognition | Territorial sovereignty, extended digitally (e.g., e-residency) | None |
| Membership | Permissioned entry via Parents, then self-sovereign. Earned through time and Energy. Multiple memberships possible. | Voluntary, overlapping, values-aligned | Voluntary, often founder-led | Citizenship tied to territory or legal status | Open or interest-based |
| Relationship to existing states | Parallel and compatible. Substitutes functions without contesting territory. Can be adopted by states, communities, or anyone. States that adopt it gain superior coordination. | Complementary — coexists with existing systems | Competitive — seeks to replicate and rival the state form | Is the state, extending digitally | Operates within platform rules, largely apolitical |
| Core logic | Align individual interest with collective interest through Energy flows and Value Functions | Entanglement and collaboration across communities | Exit and competition among states | Territorial control and legal enforcement | Affinity and shared interest |
| Governance depth | Full stack, modular. Constitution, Parameters, Laws, Courts, Disputes. Anywhere from autocracy to futarchy. Forkable. | Self-governing institutions, commons stewardship, mutual aid | Governance modelled on startups/states | Full state apparatus | Moderation rules, community guidelines |
| What holds it together | Accumulated stake — every Actor’s Energy, history, and relationships are embedded and inseparable | Shared identity, mutual commitment, collective practices | A shared mission defined by a founder; land as end goal | Legal obligation, national identity, monopoly on force | Shared hobby, platform, or topic |
| Unit of coordination | The Actor | The community (network of communities) | The founder’s mission | The citizen | The conversation |
| Implementation layer | A protocol: identity, Energy, Value Functions, Synchronized Social Contract, Portal | Web3 tooling, popup cities, commons stewardship | Founder’s vision + land + diplomatic recognition | Law, bureaucracy, force | Platform (Discord, Reddit, etc.) |
SP is on a different axis than the other four. They’re positions on a sovereignty spectrum. SP is the substrate any position on that spectrum would have to run on.
The Network State Comparison, Sharpened
The word “Network State” does a lot of work for people who haven’t examined it. It sounds like it captures everything: a network that becomes a state. But the two halves of that phrase are pulling in different directions.
Balaji’s Network State is a political ambition: gather a community, acquire territory, negotiate recognition. It assumes sovereignty is something you claim and then negotiate. The substrate is secondary. In this reading, Balaji may never need SP, because Balaji is playing a diplomatic game, not a protocol game. He wants a seat at the table.
SP treats sovereignty as something you exercise. Build the substrate first. Identity, Energy, governance, records, exit. Let the community become self-governing. Territory becomes optional. Recognition becomes available but not required.
So: Balaji negotiates sovereignty. SP exercises it. One is a claim. The other is a capability.
This means Network State isn’t a competitor to SP. It’s one thing you could build on SP. Or not build on SP — in which case it degrades into a founder-led community with a flag and a plan. The ambition is fine. Without a substrate, it’s just ambition.
The same is true of Network Nation. De Filippi et al. built the best political framework available. But their own primer names the gap: “a decentralized protocol can distribute technical functions while effective influence remains concentrated among founders, developers, or token holders.” They know. They just don’t have the primitive. SP is the primitive.
For States
There’s an implication here that deserves its own note.
If a Nation-State wanted to upgrade its coordination capacity — and every Nation-State currently does, which is why CBDCs are being built — it has two paths. The first is CBDCs. The second is to build or adopt a Society Protocol instance as the national coordination layer.
SP is not reluctant about this. It doesn’t require states to give up territory or sovereignty. It gives them better coordination. And states that adopt it early would gain a competitive advantage over those that don’t, because their coordination capacity would be higher.
The advice to world leaders, then, isn’t “abandon your state.” It’s: stop building CBDCs. Build an SP instance instead. You keep everything you have. You gain coordination you don’t have. You stop trying to build the thing from scratch when someone has already derived the requirements.
Network Nations, Network States, corporations, families, DAOs, and Nation-States are all welcome. Not because SP is neutral in the sense of having no opinion, but because SP is the substrate, not the position. The substrate serves whoever builds on it.
- Credits to the Network Nation alliance for the table.
- Written with help of Deepseek AI.