LNS as the registry for Web4 domains, and why BRIDGE comes first
LINKSPREED intends to open the Linkspreed Name Service as the registry for Web4 domains before the end of this year. Here is the dependency on BRIDGE that decides the order.
LINKSPREED intends to open LNS — the Linkspreed Name Service — as the registry for Web4 domains before the end of this year. LNS is Web4’s own naming system: a name is owned outright and secured through identity credentials, rather than rented from a registrar on an annual subscription. It is not shipping yet, and the reason is a dependency we would rather explain than hide.
LNS only makes sense once BRIDGE is ready. BRIDGE is the Web4 browser, and further out the operating-system layer, that understands the web4:// protocol natively, resolves LNS-based names natively, and treats self-created top-level domains as normal rather than as an add-on bolted onto a browser designed for something else.
Issuing names that most software cannot open would not be a launch. It would be a promise with a waiting list attached.
Naming is the most quietly rented layer of the internet
The traditional Domain Name System has one structural property that rarely gets attention: a domain is never owned. It is leased. A registrar holds the entry, renewal is annual, prices can change, and the name can be suspended or transferred by a party that is not the holder. For most of the internet’s history that trade-off was invisible, because there was no alternative.
Almost nobody notices, because the invoice is small and arrives once a year. But a name that cannot be kept without paying an intermediary indefinitely is not a name anyone owns. Every identity, brand, and community built on top of it inherits that fragility.
What LNS changes
LNS removes the landlord. Four differences matter.
| Traditional DNS | LNS | |
|---|---|---|
| Tenure | Leased, renewed annually | Owned outright |
| Security anchor | Payment relationship with a registrar | UIID identity credentials |
| Available endings | Fixed list, such as .com or .org | Self-created top-level domains |
| Protocol | https://, resolved against DNS | web4://, resolved against LNS |
The protocol difference is not cosmetic. The traditional address system was never designed to express the statement “this name is anchored in an identity that a person controls,” so we needed an addressing format that can.
Resolution is identity-anchored as a result. Because the name traces back to a verified, self-owned identity, the naming layer inherits the properties of the identity layer beneath it — including the resistance to mass-registered throwaway identities that comes from UIID’s device-bound, biometric credential model.
This sits inside HELION, Web4’s Layer 4, which covers browsing, routing, and naming. HELION does not add a feature to the existing web. It replaces how addresses are resolved. That is precisely why it cannot ship halfway.
Why the registry waits on BRIDGE
The dependency chain is short and hard to argue with.
A registry issues names. Names are only useful if something can open them. Ordinary browsers do not resolve web4://. They resolve https://, and they resolve it against DNS. Handing someone a name their browser cannot reach is handing them a certificate, not an address.
BRIDGE is the browser built to open web4:// addresses. It is the piece that turns an LNS entry from a record into a destination. Three things have to be true in BRIDGE before a registry launch is responsible rather than merely exciting.
- Native protocol support.
web4://handled as a first-class scheme, not proxied through a gateway or a translation service that reintroduces the middleman LNS exists to remove. - Native LNS resolution, including custom top-level domains. If a name holder can create an arbitrary ending, the resolver has to treat that ending as normal. A resolver that only knows a fixed list would quietly recreate the constraint LNS exists to abolish.
- Identity-aware addressing. Because LNS names are tied to a Web4 identity rather than rented from a registrar, the browser has to understand that relationship in order to verify what it is opening.
Beyond the browser, the same requirement extends downward to the operating system. W4OS, the custom software layer developed for WYNIX devices, is where native web4:// handling belongs at the OS level, so that a Web4 address opened from any application on the device resolves correctly rather than only inside one browser window.
We would rather hold the registry for a browser and an operating system that resolve these names properly than launch into an ecosystem where every LNS domain needs an asterisk.
What we are not claiming
A naming layer is exactly the sort of thing people build a business on, so two limitations belong here plainly.
LNS is in closed beta and domains are not generally available today. HELION remains in development, and features and timelines may continue to change ahead of full public availability. Anything commercial should treat LNS and HELION as not yet ready to commit to.
Support in other browsers is a hope, not a roadmap item. We would like to see additional browsers add web4:// support over time. Nothing is confirmed. Until then, a Web4-capable browser such as BRIDGE is required.
The rest of the stack is unaffected. UIID, TRIVE with GLACIER, ATRIUM, and Web4 @home are available today and do not depend on the naming layer. Our recommendation to businesses is unchanged: start with the layers that are ready, and revisit HELION and LNS when they reach general availability.
The bigger point
Web4’s guiding principle is the Ownership Thesis: every layer of the internet should trace back to something a person or organization directly controls, rather than something merely rented on their behalf. Identity, connectivity, compute, naming, software, applications, hardware — all seven layers, not one narrow slice.
LNS is our answer for the naming layer. BRIDGE is what makes the answer usable. Shipping them in the wrong order would hand people a deed to a house with no road leading to it.
We intend to open the registry before the end of the year. When we do, the names will resolve natively, because that is the only version of this worth launching.
Follow the work
- Progress on HELION, LNS, and BRIDGE: help.linkspreed.com and the LINKSPREED YouTube channel
- Early access to the LNS beta: write to [email protected] and mention LNS
- The unit: helion.linkspreed.com
- The research: the Web4 Paper and the Stack Reference Implementation at web4.one