The Presence Layer of the Internet

It is well understood that the internet’s original purpose was to allow different computers to communicate and share data. For decades, this exchange of information formed the bedrock of digital life.

What is less often noticed is that, over time, the internet also acquired a series of shared mechanisms that solved deeper coordination problems. Some made it possible for machines to communicate across heterogeneous networks. Others made that communication legible, secure, or economically consequential. Each extended the internet’s practical reach by allowing digital systems to coordinate around a new class of shared problem.

These are not “layers” in the narrow sense of the OSI model. They are better understood as shared coordination layers: reusable infrastructural capabilities that many different systems can rely upon. Routing, naming, secure communication, and decentralized settlement do not belong to one neat technical stack in the classical networking sense. But they do belong to a broader historical pattern in which the internet became more useful by acquiring new forms of coordination capacity.

The pattern can be sketched simply:

Coordination layer	Coordination problem addressed	What it made possible
Routing	How can data move across heterogeneous networks?	General inter-network communication
Naming	How can people and institutions refer to network destinations legibly?	Stable service discovery and human-scale navigation
Secure communication	How can parties communicate safely over untrusted networks?	Confidential, authenticated, integrity-protected exchange
Settlement	How can multiple parties coordinate around shared state or value transfer?	Durable ledgers, programmable assets, decentralized markets

Yet one major capability has remained underdeveloped: verifiable physical presence.

Digital systems can transmit messages, settle payments, authenticate users, and store records with extraordinary sophistication. What they still struggle to do, in a neutral and privacy-respecting way, is establish whether a person, device, or asset was within a defined physical region during a defined interval of time.

This page explores the idea of a Presence Layer of the Internet: a shared coordination layer that allows systems to express, verify, and adjudicate bounded claims about physical presence.

The claim is not that the internet lacks location data. Quite the opposite. Modern systems collect enormous volumes of it. The problem is that they are generally designed for tracking, analytics, administration, or platform control, not for privacy-preserving, independently verifiable adjudication of presence claims.

The Historical Evolution of Internet Layers

From a coordination perspective, the internet did not emerge fully formed. It developed through successive layers of shared capability, each addressing a problem that earlier systems could not solve well enough at scale. Looking back at these layers helps clarify why the idea of a presence layer is not arbitrary. It belongs to a broader historical pattern in which the internet became more useful by acquiring the capacity to coordinate around new categories of fact.

Packet Routing — The IP Layer

The Internet Protocol made it possible for machines to exchange packets across heterogeneous networks. This was a foundational step because it separated the problem of communication from the specifics of any one physical network. Systems no longer needed to share the same hardware assumptions, direct links, or local topology in order to communicate.

This gave the internet its basic connective tissue. Before higher-order forms of coordination were possible, there first had to be a way for packets to move between endpoints that did not already belong to one unified system. IP solved that problem well enough that the internet could begin to scale beyond isolated local arrangements and become something broader.

Naming — The DNS Layer

Once routing existed, another problem became obvious: numerical addresses may be workable for machines, but they are poor tools for human coordination. People and institutions need stable, legible ways to refer to destinations, services, and systems.

DNS provided that legibility. By mapping human-readable names to network locations, it made the internet easier to navigate, easier to organize, and easier to inhabit at social and institutional scale. It allowed services to be named, remembered, cited, and revisited without requiring users to think in terms of raw network coordinates.

DNS therefore did more than simplify access. It helped transform the internet from a transport substrate for machines into an environment in which humans and institutions could coordinate more effectively.

Secure Communication — TLS

As the internet expanded, communication needed not only to flow, but to be protected. It was no longer enough for packets to arrive. Parties increasingly needed confidence that they were communicating with the intended counterparty, that the contents of the exchange had not been altered, and that sensitive information was not exposed in transit.

TLS introduced a widely deployable basis for this kind of trust. It made confidentiality, authentication, and integrity available as general-purpose properties of digital exchange rather than exceptional features implemented separately by each application. Without it, the internet could still have carried information, but it would have remained far weaker as a substrate for commerce, private communication, account access, and other forms of consequential interaction.

TLS did not eliminate trust from the system altogether, nor did it solve every problem of security. But it made protected exchange far more standard, portable, and scalable than before. It turned secure communication into infrastructure.

Decentralized Settlement — Blockchain

More recently, blockchain systems introduced another kind of coordination capability: the ability, in certain contexts, to maintain agreement about state change without relying on a single central operator to keep the authoritative ledger.

This extended the internet’s practical scope again. It became possible for multiple parties to coordinate around shared records of value transfer, asset ownership, and programmable state transitions even when they did not fully trust one another or share the same institutional home.

Whatever one thinks of particular blockchain applications, the broader architectural contribution is clear: a reusable mechanism emerged for durable, replayable settlement across distributed participants. The important point is not that blockchains replaced prior systems, but that they expanded the internet’s coordination repertoire. They made a new class of shared problem tractable.

Taken together, these examples illustrate the larger pattern. The internet became more capable not only by becoming faster or larger, but by acquiring reusable coordination layers that allowed many different systems to rely on common solutions to recurring problems.

The Missing Layer: Physical Reality

Despite these advances, the internet still lacks a robust and widely accepted way to deal with claims about physical events.

This gap becomes visible whenever digital processes depend on facts about what happened in the world: whether a delivery occurred at a location, whether a worker visited a site, whether a vehicle entered a restricted area, whether a participant attended an event, or whether an inspection took place under the required conditions. These are not unusual edge cases. They are ordinary problems of coordination, and they often carry legal, economic, and operational consequences.

What makes them difficult is not simply that they involve geography. It is that they sit at the boundary between digital systems and physical reality. Software can transmit, authenticate, and settle information with extraordinary precision. But when a workflow depends on where something happened, when it happened, and under what conditions, the internet has historically had no shared, reusable way to handle that fact as a first-class problem.

Instead, such questions are usually managed through a patchwork of substitutes: centralized databases, trusted authorities, manual reporting, and opaque platform logs. These mechanisms may be operationally adequate, but they are weak foundations for general presence infrastructure. They are often hard for outside parties to verify, invasive in the amount of data they collect, and structurally dependent on institutions whose internal records must simply be trusted.

The problem, then, is not a lack of location data. Modern systems already collect enormous volumes of it. The problem is architectural. Most current approaches begin by gathering broad streams of data and only later asking institutions to interpret what those data mean. A presence layer would begin from a different premise: define the relevant claim first, then support a way of proving or adjudicating that claim under explicit rules.

Seen in this light, the missing layer is not “location.” It is a more principled way of handling certain bounded facts about physical reality.

Presence as a Coordination Primitive

A remarkable share of human and institutional life depends on who or what was where, and when. Meetings depend on attendance. Deliveries depend on arrival. Inspections depend on site visitation. Access decisions depend on proximity or entry. Logistics workflows depend on assets crossing thresholds. Jurisdictional obligations depend on whether a person, device, or object was within a given region during a relevant interval.

For much of history, these questions were handled informally or locally. People saw one another. They signed forms, stamped papers, inspected sites, or relied on witnesses and institutions embedded in a particular place. Those mechanisms were often imperfect, but they were socially legible. They belonged to a world in which physical presence was adjudicated through direct observation, local record-keeping, or trusted intermediaries.

As more of these processes become digitally mediated, however, that informal settlement becomes less sufficient. The systems now making decisions about payment, access, compliance, liability, and recognition increasingly operate at a distance. They require information about physical reality, but they do not inhabit physical reality themselves. They need some way to refer to presence without collapsing back into broad surveillance or blind platform trust.

This is why the question becomes infrastructural.

Digital systems increasingly need to answer propositions such as:

Was entity X within region R during time interval T?

At first glance, that can sound like a narrow technical query. In reality, it is a compact expression of a much larger design problem. What counts as evidence for such a claim? How precise must the claim be? How much information should be disclosed in order to support it? Who decides whether it is valid? Can that decision be challenged? Can it be audited later? Can multiple parties rely on it without all deferring to the same private intermediary?

When questions like these recur across many different domains, presence begins to look less like an application-specific feature and more like a candidate for infrastructure.

A feature belongs inside a particular product or workflow. A coordination primitive appears across many products and workflows because it expresses a condition other systems repeatedly need to reference. Presence increasingly has that character. It is becoming one of the recurring predicates on which digital processes depend.

That is what makes the idea of a presence layer worthy of the name.

Requirements for a Presence Layer

A viable presence layer must balance several design requirements.

Privacy

Raw location data should not be unnecessarily exposed. In many cases, the important fact is not a full movement history, but a much narrower claim: that a person, device, or asset was within a defined region during a relevant time window.

Verifiability

Independent parties must be able to verify claims. A presence system should not reduce to “trust the platform.”

Bounded Authority

No single authority should control the truth of presence. This does not require maximal decentralization everywhere, but it does require resistance to unilateral adjudicative control.

Economic Security

Participants should have incentives to behave honestly. If a system relies on adjudicators, verifiers, publishers, or dispute actors, their incentives matter.

Auditability

Historical decisions should be inspectable and replayable. Presence claims often matter later, under dispute, and across institutional boundaries.

Architecture of the Presence Layer

A presence layer can be conceptualized as four interacting components.

Measurement Layer

This concerns the sources of physical signals or observations from which a presence claim may be derived: GNSS signals, radio environments, sensor readings, or related data sources.

Proof Construction Layer

This transforms measurements into evidence that a claim satisfies defined spatial or temporal constraints. Depending on the system, this may involve commitments, constraint systems, or privacy-preserving proofs.

Verification Layer

At this stage, independent actors evaluate the claim and the evidence presented for it. This may involve committees, challenge models, economic incentives, or other adjudicative mechanisms.

Finalization Layer

Finally, adjudicated results are published into some durable coordination system so that they can be referenced, relied upon, and, where necessary, audited later.

What matters here is not the precise implementation boundary. It is the broader point: a presence layer is not merely a sensory feed or a location API. It is an adjudication-capable coordination layer.

Potential Applications

A presence layer enables new classes of digital coordination by making physical presence a more legible and verifiable input to digital systems.

Examples include:

• Logistics, where delivery and transfer events may need neutral evidentiary support
• Inspections, where the fact of site visitation matters independently of the quality of the inspection itself
• Events, where attendance may need to be verified without broad behavioral surveillance
• Asset Tracking, where rights and liabilities may depend on presence within zones or thresholds
• Decentralized Work, where geographically conditioned tasks require more than check-ins
• Jurisdiction and Compliance, where bounded facts of presence may affect legal or regulatory treatment

The broader point is not any one application. It is that digital systems increasingly need reliable ways to refer to bounded facts about the physical world.

The Future Internet Stack

If presence verification becomes more standardized, the future internet may come to include a presence layer alongside other established coordination layers.

One possible conceptual stack is:

• Application Layer
• Presence Layer
• Settlement Layer
• Security Layer
• Naming Layer
• Routing Layer

This should not be read too literally. The presence layer need not appear as a single protocol sitting neatly between fixed technical layers in the way classic network diagrams suggest.

Rather, the claim is historical and functional: just as the internet acquired shared mechanisms for routing, naming, securing, and settling, it may also require shared mechanisms for dealing with claims of physical presence.

That would allow digital systems to interact with certain classes of physical event more reliably, with greater privacy discipline, and with less dependence on opaque intermediaries.

Conclusion

The internet transformed communication, naming, security, and economic coordination, but it has historically lacked robust mechanisms for addressing the question of physical presence.

A Presence Layer of the Internet names one possible response to that gap.

It describes a shared coordination capability by which systems could express, verify, and adjudicate claims about physical presence in a way that is more structured, more privacy-respecting, and more open to independent verification than many current systems allow.

This is not a universal tracking layer, nor a claim that physical reality can be reduced to pure cryptographic certainty. It is a narrower and more important proposition: that bounded facts of physical presence are becoming important enough, recurrent enough, and consequential enough to deserve treatment as infrastructure.

If that capability matures, it may become one of the missing infrastructural pieces required for a world in which digital systems coordinate not only around information and value, but around bounded facts of physical reality.