Can JAM Have Sovereign Domains?
I’ve been thinking about JAM and Kusama primarily as a question of political philosophy: what kinds of authority, rights, and boundaries emerge when a shared technical substrate supports multiple persistent communities?
But this question should not remain purely philosophical. Polkadot 1.0 already gives us a concrete failure experience, and the BitTensor example—where the project ultimately moved away from the parachain model—offers another useful comparison. These cases suggest that the question of sovereignty is not an abstract preference. It is closely connected to whether a community can actually control its own development, economic rules, resources, and future.
I’m not sure I have the right answer yet, so I’m posting this mainly because I’d like to hear where this line of thinking is wrong.
One thing that keeps coming back to me is that Polkadot has already gone through something similar with compute.
Coretime is not just a technical concept anymore. Once computation becomes scarce, there has to be some way to decide who gets it, for how long, under what conditions, and what happens when those conditions change.
So computation gradually becomes a resource, and resource allocation becomes an economic and eventually a governance question.
Polkadot 1.0 showed what can happen when the architecture, economics, and governance of that resource do not align with the needs of the communities using it. Parachains were given a formal place within the system, but their practical independence remained constrained by shared security, slot allocation, governance processes, technical dependencies, and the cost of maintaining a position in the overall structure.
The result was not necessarily that parachains lacked value. Rather, the model made their autonomy conditional. A community could build its own economy and identity, but its access to the underlying system remained dependent on arrangements it did not fully control.
That experience matters because it shows that technical inclusion is not the same thing as political independence.
The BitTensor case raises a related question from another direction. If a project eventually decides that the parachain model does not provide the flexibility, control, or economic alignment it needs, then leaving the model may become more rational than continuing to negotiate within it.
This does not mean that every project should abandon shared infrastructure. It does suggest, however, that a system must explain why an independent community should remain inside it.
Shared security, interoperability, and common infrastructure are powerful benefits. But they are not sufficient by themselves. A community also needs to know what it controls, what it can change, what it can refuse, and what happens to its state and assets if the relationship breaks down.
This is where the question of sovereignty becomes necessary.
I wonder if state is going to follow a similar path.
There is an important difference, though. Compute is mostly a flow. State is persistent.
If I get some compute today, I use it and it is gone. But if a domain gets a piece of state space, that state represents something that continues to exist. It can contain an economy, assets, applications, organizations, and eventually perhaps autonomous agents.
At that point, I don’t think the question is simply “who gets how much state?”
It becomes something more like:
Who controls it?
For how long?
Can it be taken away?
Who can change the rules governing it?
What happens to the state and assets if the domain wants to leave?
And perhaps most importantly, can the higher layer change the political boundaries of the lower layer whenever it wants?
These are not merely technical questions. They are the practical form of the sovereignty question.
This is where the question of a JAM constitution becomes important to me.
The distinction between owning the underlying resource and controlling everything that happens on top of it seems quite important.
For example, imagine that the common governance layer retains ownership of the scarce resource, while a domain gets a long-term right to use part of it. The domain could then have its own economy and governance without necessarily owning the underlying substrate itself.
At first this sounds like a simple resource-allocation arrangement.
But if the rights become sufficiently durable, something more interesting starts to happen.
The domain is no longer simply using a resource because someone currently allows it to.
It starts to have its own political boundary.
This is where the recent Kusama discussion becomes interesting to me.
A lot of the questions being raised there are not really about whether Kusama should have “more freedom” in an abstract sense. They are very concrete questions about who can control what, what happens when different communities disagree, whether certain changes can be rejected, whether state and assets remain intact, and what happens if a community eventually wants to leave.
Those sound a lot like constitutional questions.
But Kusama also shows that constitutional questions cannot be separated from actual institutional action. The issue is not only what rights should exist in theory, but whether those rights are encoded in governance, reflected in economic incentives, protected by technical mechanisms, and respected when conflicts arise.
In that sense, thought should provide the principles, while concrete governance experiments provide the test.
And this makes me wonder whether Kusama is actually revealing a problem that any successful JAM domain will eventually have.
Suppose JAM eventually contains not just Polkadot and Kusama, but many different domains, organizations, DAOs, perhaps eventually autonomous agents and economic systems that we haven’t really seen yet.
If all of these subjects become economically important, can the upper layer realistically govern their internal affairs forever?
Maybe it can. I’m not sure.
But it seems to me that there will eventually be a point where the question changes from:
“Who owns the underlying resource?”
to:
“What rights does a subject have while using that resource?”
And those are not the same question.
In fact, I think separating them may be one of the most important design decisions JAM eventually has to make.
The common governance layer could remain the owner of the common substrate.
JAM could remain the common security and infrastructure layer.
But the domains using it could have their own protected sphere of decision-making.
That would be quite different from simply giving them permission to govern themselves.
If the higher layer can revoke everything whenever it wants, then I would call that autonomy or delegated authority.
If some rights cannot be unilaterally revoked, then we’re getting closer to something I’d call sovereignty.
If those rights are defined by rules that constrain both the upper and lower layers, then we are probably talking about a constitutional relationship.
This is also why I don’t think the word “sovereignty” itself is particularly important.
Anyone can call something sovereign.
The interesting question is what the actual rights are.
Can the domain say no?
Can it control its own internal economic rules?
Can the upper layer intervene?
Can the domain leave?
If it leaves, what happens to its state and assets?
And can another domain obtain the same rights, or is this just a special arrangement negotiated with one particular community?
That last question may actually be the most important one.
If one community gets a special arrangement, that doesn’t necessarily mean much.
But if the same basic rights eventually become available to multiple independent JAM domains, then I think we’d be looking at something much more significant.
At that point, “Nested Sovereignty” wouldn’t just be a philosophical description. It would be an actual property of the system.
Maybe this is also why I find the lease versus freehold discussion interesting.
At first glance, giving domains permanent ownership of their state footprint seems like the stronger form of independence.
But I’m no longer sure that’s necessarily true.
If the underlying JAM resource remains common property while domains receive durable rights over its use, you can potentially have both things at the same time:
a common substrate, and genuinely independent political subjects living on top of it.
That seems to me like a potentially very powerful combination.
It also avoids one possible problem with permanent ownership: whoever gets the scarce resource first could eventually become a kind of resource landlord to everyone who comes later.
Maybe keeping the underlying resource at the higher layer while protecting the rights of the lower layer is actually a better foundation for a multi-domain system.
But this only works if the protected rights are real. A lease that can be cancelled arbitrarily is not a constitutional settlement. It is simply a revocable permission.
So the practical question is how JAM, Kusama, and related governance systems can turn these principles into enforceable arrangements: clear allocation rules, predictable renewal or exit mechanisms, limits on unilateral intervention, protection of state and assets, and procedures for resolving disputes between the common layer and individual domains.
I don’t know if JAM will go in this direction.
It could instead become a much more centralized hierarchy where the common governance layer ultimately retains the ability to redefine everything underneath it.
That would be a completely different political structure.
What I’m interested in is whether the architecture and economics of JAM will gradually make one of these arrangements more natural than the other.
My current suspicion is that once you have scarce compute, persistent state, many independent economic subjects, and a shared substrate, some kind of constitutional boundary becomes difficult to avoid.
Not necessarily because people want a constitution.
Simply because eventually somebody will ask:
“What exactly can you decide about me, and what can you not decide about me?”
That seems like a very old political question appearing in a very new technical environment.
The experience of Polkadot 1.0, the decision of projects such as BitTensor to move away from the parachain model, and the current Kusama and JAM discussions all point toward the same practical issue: a shared system must offer more than technical connectivity. It must provide a credible answer to why independent communities should participate, what they receive in return, and what they are allowed to preserve.
So I’m curious what people who are much closer to the JAM implementation and governance discussions think.
Am I making a category mistake by treating persistent state as something that will naturally create stronger rights?
Or is this actually a problem JAM will eventually have to solve?
And perhaps the biggest question:
Can JAM remain one common substrate while allowing the things built on top of it to become genuine political subjects in their own right?
I’m not claiming that Nested Sovereignty is where JAM is going.
I’m wondering whether the structure of JAM might make it increasingly difficult to avoid—and whether the lessons of Polkadot 1.0, BitTensor, and Kusama can help turn that question from a philosophical concern into a concrete design and governance agenda.