Ipfs

Services Without DNS

Many networked systems assume that services must be named in order to be reachable. That assumption quietly binds identity, trust, and location together, making services brittle when they move, change networks, or need to limit who can find them. An alternative approach is to treat services as identities first and locations as optional, temporary attributes. From this framing, services can publish signed statements describing how they may be reached, while clients resolve those statements as data rather than through a naming hierarchy. Identity remains stable even as endpoints change or disappear. The result is infrastructure that tolerates mobility, partial availability, and privacy requirements without relying on DNS or other centralised resolution systems.