A name is an address is an identity
Before the internet, a name meant a place. A postal address told you exactly where to find someone: street, city, country, a physical location that mail could reach and a person could stand in. A phone number did the same thing electronically — a fixed point that routed a call to one specific line, one specific household.
Domain names inherited that same job. A name typed into a browser had to resolve to one specific place: a server, an IP address, a physical machine sitting in a data center somewhere. The naming layer of the internet was never just cosmetic — it has always been the address system underneath everything people do online, the same way a street address is the address system underneath everything people do in a city.
What's changed is what a name is expected to carry. A postal address only ever pointed to a building. A modern domain name points to a business, a reputation, an entire identity built up over years — and increasingly, to a person's actual digital self, not just a website they run.
What "handshake" meant before computers
Long before it was a protocol, a handshake was a specific kind of ritual: two people agreeing to something directly, with no institution standing between them to notarize it. A handshake deal didn't need a court, a bank, or a government registry to be real. It was binding because both parties showed up and agreed, in person, without an intermediary.
That's not an accidental name for a naming protocol. Every domain name issued through ICANN passes through an intermediary — a registrar, a registry, a central authority that has to approve the transaction before it's considered valid. Handshake borrows its name from the older, simpler model: two parties reaching agreement directly, verified by nothing but the agreement itself. The protocol's entire design goal is to make that old kind of trust — peer to peer, no middleman required — work at internet scale.
The internet's missing deed registry
Real estate has had land registries for centuries. When someone buys a house, a deed gets recorded in a public registry that establishes, permanently and independent of any single company, who owns what. That registry doesn't belong to the buyer's bank or the seller's lawyer. It's a shared record that outlives any single transaction or institution involved in it.
The internet never built an equivalent system for names. Domain ownership records live inside private registrar databases and a root zone controlled by a single nonprofit operating under U.S. jurisdiction. There's no public deed, no independent registry a person can point to and say "this is mine, permanently, regardless of what happens to the company that sold it to me." A registrar can go out of business, get acquired, or get compelled by a court, and the record of who owns what changes at their discretion, not at the owner's.
A blockchain-based root does what a land registry does for houses: it makes ownership a public, permanent fact instead of a private company's internal record. Handshake names are recorded the same way a Bitcoin balance is recorded — verifiable by anyone, controlled by no single party, unable to be quietly altered by whichever company happens to be holding the database this year.
Where this connects to citizenship
This is the same structural gap explored in Digital Citizenship Without a Digital Government: identity that depends on an issuing authority can be revoked by that authority. A missing deed registry and a revocable passport are the same problem wearing different clothes — ownership that was never actually ownership, just permission that hadn't been withdrawn yet.
Resolving it in practice
None of this is theoretical to use. SkyInclude Browser handles name resolution for Handshake TLDs natively today, giving names the same everyday usability as a .com while keeping the ownership record itself outside any single company's control.
Written by NIHON — Handshake Infrastructure & Web3 Identity.