Common questions people still get stuck on
A lot of the same conceptual questions keep coming up in the community. This post is an attempt to answer some of the most common ones clearly, using the actual framing of Society Protocol.
These are not official answers — just a careful reading of the whitepaper, handbook concepts, and core articles.
1. What’s the difference between synchronization and coordination?
Coordination is the goal.
Synchronization is the infrastructure that makes high-quality coordination possible.
Society Protocol treats synchronization as the process of creating and maintaining a shared state that everyone can see and act on at the same time. That shared state is what the project calls the state that binds.
Without a reliable shared state, coordination remains fragmented, slow, and easy to capture. With it, the system can run algorithmic coordination mechanisms (Value Functions, Energy redistribution, etc.) that would otherwise be impossible.
Clocks are the classic example used in the articles. A clock doesn’t coordinate society by itself — it gives everyone a single precise integer they can synchronize around. That shared integer then enables large-scale coordination. Society Protocol is trying to do the same thing with a much richer shared state.
2. Why is Energy not treated like a normal token?
Energy is the unit of social value and influence inside a Synchronized State.
It is zero-sum. It cannot be created or destroyed — only transferred between Actors according to the rules of the instance.
In normal crypto, a token is mostly about ownership and transfer.
In Society Protocol, Energy is about participation and social weight. It moves through Value Functions based on what the instance defines as valuable.
This is why treating it like a speculative token misses the design.
3. How do Value Functions avoid just rewarding who is most active online?
They don’t automatically.
Value Functions are configurable. If an instance leans too heavily on raw activity metrics (time spent, posts, votes), it will drift toward rewarding presence over real contribution.
The protocol gives communities the tools (Energy, Activity Scores, history, Family Trees, attestation mechanisms), but the actual design choices belong to each instance. Deliberate design is required to weight outcomes, peer recognition, or offline-attested work more heavily than pure visibility.
4. What does Portal actually protect when someone leaves?
Portal is designed so that groups who strongly disagree can exit while retaining their identities, relationships, history, and as much of their state as possible.
At the same time, the instance they leave retains the locked Energy of the exiting group instead of having it dumped on an open market. The goal is to make exit less destructive for both sides than traditional exits usually are.
5. Why does the project say crypto alone can’t fully decentralize?
The core argument (laid out in Fake Everything) is that current blockchain architectures lack robust sybil-resistant identity. Without that, the social layer remains outside the system.
As a result, ownership sets, valuations, governance participation, and real coordination stay opaque and gameable. Cabals can form and maintain influence while the system still looks decentralized on the surface.
Society Protocol’s claim is that you need to bring identity and the social layer into the synchronized state itself if you want to move past that limitation.
6. What does “shared state” actually mean in practice?
It means a single, synchronized record of the relevant public reality that all participants can read and (within the rules) act on.
In Society Protocol this includes identities, relationships, Energy flows, Events, history, and the Synchronized Social Contract. The more complete and reliable that shared state is, the higher the quality of coordination that becomes possible on top of it.