The Journal
When not to sell a TLD
A desk that sells TLDs should say when not to. Here are the cases.
What happens to the names under a TLD when it changes hands
A buyer of a TLD inherits whatever was issued under it. Why that matters to all three parties.
A shared suffix or a TLD of your own: two naming models
Under a shared suffix you are a tenant of the namespace. With your own TLD you write the rules.
What the domain aftermarket learned in thirty years
The resale of names is not new. Most of what goes wrong today went wrong before.
The case against onchain TLDs, taken seriously
A desk that sells these assets should be able to state the case against them. Here it is, without softening.
Selling a TLD that already has names issued under it
An occupied namespace is not unsellable. It is a different asset and should be presented as one.
Browser extensions that resolve onchain names: what to ask
The bridge between an onchain name and a browser is usually an extension. A plain look at what that means.
Losing access to a TLD: prevention and real recovery
Most losses are organisational before they are technical: a departure, a device, a note nobody kept.
What the list of applied-for strings tells a brand owner
The list answers one question publicly: who applied for which string. What a brand team should do with it.
What makes a naming system last
Durability is not a promise a system makes. It is a set of conditions you can examine.
Succession planning for holders of onchain TLDs
The asset has no registrar to call and no account to recover. Planning is the only route.
IPFS and content addressing, explained without the mythology
Permanent, uncensorable, free: three things people say about IPFS that need qualifying.
How a new gTLD application is evaluated, in outline
Evaluation asks whether the applicant can run a registry and whether the string raises problems. An outline for non-specialists.
What the applied-for strings list tells a TLD holder
A match raises interest in your TLD. It does not entitle you to pressure anyone.
How wallets and browsers decide which names to support
No rule obliges a wallet to understand a name. Support is a product decision, made for product reasons.
Selling a TLD held by several people
A buyer wants one counterpart who can commit. Getting there is work to do before the first approach.
What an onchain name proves, next to a certificate
A name proves who controls a namespace. It does not prove who that is. The difference matters.
Objections and rights protection in an ICANN round
The DNS gives third parties a moment to object. Onchain, that moment does not exist.