DNNS Lets Services Control Who Can Find Them, Not Just Whether They Can Be Found

Discovery on Lithosphere is permissioned by design, letting a service stay resolvable to authorized agents while remaining invisible to everyone else.

LONDON, UK – July 14, 2026 – Lithosphere today detailed a distinction in how DNNS, its decentralized naming and routing system, handles discovery: resolving a name is not the same as making a service visible to everyone. Most naming systems treat discoverability as binary — a service is either publicly resolvable or it isn’t listed at all. DNNS is built to support a middle setting, where a service is resolvable to specific agents and closed to everyone else.

That distinction depends on discovery being tied to identity rather than handled as a separate, anonymous lookup step. Because DNNS operates inside the same architecture as PPAL, a resolution request already carries the requesting agent’s verified identity with it. A service can be configured to resolve only for agents holding a particular credential or relationship, without needing to build and maintain its own separate permission layer on top of a public directory.

“Most naming systems assume discovery has to be all-or-nothing — public or unlisted,” said J. King Kasr, Chief Scientist at KaJ Labs. “Because DNNS resolves identity and discovery together, a service can stay findable to exactly the agents it wants to work with, and effectively invisible to everyone else, without extra infrastructure to enforce that.”

This matters for services handling sensitive workflows or restricted counterparties, where broad discoverability is a liability rather than a convenience. It also reduces the surface available to unwanted probing, since a service that hasn’t granted resolution rights to a given agent simply doesn’t resolve for it, rather than resolving and then rejecting the request after the fact. The same permissioned model extends downstream: execution through Lithic and settlement through MultX only ever engage with counterparties DNNS has already resolved, so an unauthorized agent is filtered out at the discovery step rather than later in the workflow.

As more services on Lithosphere handle restricted or higher-value workflows, permissioned discovery through DNNS is positioned as a default capability of the stack rather than something each service has to build for itself.

About Lithosphere

Lithosphere develops Web4 blockchain infrastructure for programmable digital assets, cross-chain interoperability, and AI-native decentralized execution. Its integrated stack — Lithic, PPAL, DNNS, and MultX — gives autonomous agents, developers, and applications a single coordinated environment for identity, execution, discovery, and cross-chain settlement.