Digital Sovereignty and the Access Layer

Sovereignty is no longer a question of control over the system itself, but of position within it.

Digital sovereignty is usually discussed as control: where systems run, who operates them, and under which jurisdiction they exist. But in globally distributed systems, control is not the only question. The system can be independent, yet access to it can still depend on infrastructure that is not.

Blockchains Solved Trust, Not Access

In Down the Rabbit Hole series, I discussed the fact that blockchains were designed to solve a specific problem: coordination across participants that do not trust each other. However, this coordination property applies only to the internal mechanics of the network. The layer in between the users and blockchain, the interaction, requires a different kind of coordination.

RPC operations such as submitting a transaction or querying state are not directly part of consensus. In principle, any participant can connect to any node and engage with the network directly: the network does not impose any restrictions on how it is accessed. So, applications and users rely on interfaces that expose the network in a structured way, abstracting away the underlying nodes and standardizing how requests are handled. These interfaces do not alter the protocol but define how the protocol is reached. As a result, the system removes trust from verification while leaving access dependent on the infrastructure that mediates interaction.

The Hidden Centralization: RPC Layer

In practice, this access layer does not remain distributed in the same way as the underlying network. That is, while the protocol allows any participant to connect to any node, most interactions are routed through a limited set of RPC providers. These providers operate large-scale infrastructure, maintain highly available nodes, and expose standardized endpoints that applications can easily integrate with.

However, in time, they became the default interface to the network because of the operational-level decisions. Running and maintaining nodes at scale requires resources, coordination, and reliability guarantees that individual participants often choose not to manage themselves. From the perspective of applications, this abstraction simplifies interaction: instead of managing connectivity, synchronization, and performance, they rely on a stable interface that behaves predictably.

Yet this is another structural asymmetry. The network itself remains distributed but the paths through which this network is reached become increasingly concentrated. Requests are served, transactions are propagated, and the system appears to function as expected. But the distribution of responsibility is no longer aligned between the protocol and its access layer.

A system that is decentralized in its core can still exhibit centralization at its edges. And since interaction depends entirely on these edges, their structure begins to define how the network is experienced in practice.

Why It Matters Now

This structure does not immediately create visible problems. RPC providers operate close to the core network, maintain synchronized nodes, and optimize for availability. Applications, without needing to manage underlying complexity., send the requests with low latency, their transactions get propagated efficiently. This model prioritizes performance by concentrating infrastructure where it can be maintained most effectively. These providers deploy the nodes in regions with strong connectivity to the peer-to-peer network, often within large cloud environments that provide predictable uptime and scalability.

However, access paths to the blockchain networks begin to overlap especially under stress. Since infrastructure is deployed in similar environments, relies on similar providers, and operates under similar constraints; though the protocol distributes responsibility across independent participants, the access layer tends to align around a narrower set of dependencies.

Under normal circumstances, this alignment is invisible. But as the world becomes on-chain over time as we see today, the architecture and its flaws become visible. Latency increases when requests travel across longer distances, rate limits appear when demand concentrates on shared endpoints, and hence failures do not remain isolated when infrastructure dependencies overlap; they propagate across providers that rely on the same underlying systems. At that point, the distinction between a protocol issue and an access issue becomes less clear from the outside.

The network has evolved, but the way it is reached has not. As Maxim Gorky once wrote, “In the carriages of the past you can’t go anywhere.” The protocol moved toward decentralization, and yet the access layer remained aligned with earlier models.

Sovereignty as Presence

At this point, sovereignty is no longer a question of control over the system itself, but of position within it.

Blockchains do not require local ownership to function, their state is maintained globally and operation does not depend on any single region. Their conditions under which they are accessed change over regions. When access depends entirely on external infrastructure, the interaction becomes indirect. Requests are routed through distant systems, shaped by their latency, limited by their capacity, and exposed to their failure modes. These constraints are not part of the protocol at all, yet they have the power to define how the protocol is experienced.

Introducing local infrastructure does not change the protocol but changes this vicious relationship. Running nodes within a region alters how that region connects to the network. Requests no longer need to traverse the same paths, depend on the same providers, or align with the same infrastructure assumptions. The interaction layer begins to reflect the environment in which it is used, rather than an external one.

At the same time, this is not only an access-level change. Additional nodes contribute to the peer-to-peer layer, introduce new propagation paths, and reduce the concentration of network activity around specific regions. The topology shifts slightly because participation changes, leading to a less uniform system.

In this sense, sovereignty is not defined by ownership of the system but by whether participation introduces new structure or remains dependent on an existing one.

A region that relies entirely on external access does not shape the network; it follows it. A region that introduces its own infrastructure does not control the network, but by changing how it connects and participates, it becomes part of how that structure is formed.