Lithosphere’s decentralized naming and routing system resolves identity and location inside the same architecture agents already operate in, removing the external lookup step most discovery systems require.
LONDON, UK — June 29, 2026 — Lithosphere today outlined the function of DNNS, its decentralized naming and routing system, in enabling agents, services, and applications across the network to locate one another reliably as part of the broader Lithosphere stack. DNNS is designed to resolve naming and routing requests inside the same architecture used for identity, execution, and settlement, rather than depending on a separate, externally hosted lookup service.
Discovery is an easy layer to underestimate until it fails. An agent that needs to complete a multi-step task, verifying a counterparty, locating a service, executing against it, settling the result, depends on every one of those steps resolving correctly and quickly. If the naming layer responsible for locating a service sits outside the rest of the system, every lookup becomes an external call: its own request, its own response time, and its own chance of returning a stale or incorrect result.
DNNS avoids that structure by operating as a native part of Lithosphere’s architecture rather than a bolted-on directory service. When an agent operating on Lithosphere needs to resolve a name or locate a service, that resolution happens within the same environment already handling its identity through PPAL and its execution through Lithic, rather than reaching outside the stack to ask a separate system for an answer.
This becomes especially relevant as the number of autonomous agents operating across Lithosphere increases. A small network can tolerate a slow or occasionally inconsistent naming layer because the volume of lookups stays manageable. A larger one cannot. DNNS is built with that scaling pressure in mind, treating naming and routing as core infrastructure rather than a convenience layer added after the fact.
“An agent that can prove who it is but cannot reliably find the service it needs is still stuck,” said J. King Kasr, Chief Scientist at KaJ Labs. “DNNS exists so that resolving a name or locating a service is as native to Lithosphere as verifying identity or executing a task. It is not a separate system agents have to reach outside the architecture for.”
DNNS’s role also extends to how services register themselves within the network in the first place. Because naming and routing are handled inside the same architecture as identity and execution, a service registered on Lithosphere becomes discoverable to any agent operating with the appropriate permissions, without requiring a separate registration process for each system that might need to find it.
As agent-driven activity continues to expand across the Lithosphere ecosystem, DNNS is positioned to remain the layer responsible for keeping that activity navigable, ensuring that growth in the number of agents and services does not translate into growth in the friction required to find and reach them.
About Lithosphere
Lithosphere develops Web4 blockchain infrastructure for programmable digital assets, cross-chain interoperability, and AI-native decentralized execution. Its integrated stack, comprising Lithic, PPAL, DNNS, and MultX, provides autonomous agents, developers, and applications with a single coordinated environment for identity, execution, discovery, and cross-chain settlement.
Media Contact
Dorothy Marley
KaJ Labs
+1 707-622-6168
[email protected]