Onchain today
What an onchain TLD can be used for is a question of fact, and the facts change. These articles describe what works now and where the limits are: how a name resolves and in which software, websites published to IPFS, payments to a name, names for staff, teams and AI agents, and the records a name can carry. Each one says plainly where the DNS remains the better tool.
Pricing the names under your TLD
A price list decides who registers under your TLD long before it decides what you earn. Here is how to build one you can explain to any registrant.
Terms of use for names issued under your TLD
The document a registrant accepts is the only place where your rules for a name become a commitment. Here is what belongs in it, clause by clause, and what to leave out.
The reserved list: names to hold back before launch
Four families of names should not be available on opening day. Here is how to find them, who approves the list, and the routes by which a name leaves it.
Email and onchain names: what does not work yet
Internet mail looks for its destination in the DNS, and an onchain name is not there. A plain account of the limit, and of the division of work that holds up.
Onchain names on a phone: what resolves
Most of your customers will meet your onchain name on a phone. Here is what that screen can do with it, what it cannot, and how to check before you print the name anywhere.
Measuring the use of a TLD from its public record
A count of names issued says little by itself. Here is how to measure issuance, spread across wallets and records set, and where the record stops.
What no renewal fee changes for a TLD holder
The renewal date was a cost, a risk and a reminder at once. Take it away and a holder has to decide what replaces each of the three.
Forget Jerseys: Claim Your Esports Name for Digital Identity and Brand Power
In esports the name is the asset: the tag on the scoreboard, the handle on the stream. A name under .esports puts that asset in your own wallet.
How an onchain name resolves, and where it does not
Resolution is the difference between a name that exists and a name that works. Where things stand, without overstatement.
Paying to a name instead of an address
A forty-character address invites mistakes. A name removes one class of error and introduces a question: who controls the name.
Naming AI agents under your own TLD
An agent that negotiates, orders or pays on your behalf needs an identity others can check. Where naming fits.
Onchain top-level domains: the complete guide
What a TLD is, who holds it, what it is for, where its limits are, and how it changes hands.
A website on an onchain TLD: how publishing to IPFS works
A site on an onchain name is not a replacement for your main website. It is a different kind of presence, with different strengths.
Managing a TLD from an AI assistant: what to delegate
Convenience is not the question. The question is which actions on your namespace should ever happen without a second pair of eyes.
Onchain TLD and DNS domain: twelve practical differences
They look alike on a screen and behave differently in almost every respect that matters to an owner.
What a resolver is, and why it decides where a name works
A name works exactly where a resolver answers for it. Understanding that one component explains most of the limits.
Tokens, wallets and keys: what a lawyer needs to know
Who owns it, who controls it and who can prove it are three different questions. The vocabulary that separates them.
How to read the public record of an onchain TLD
The record does not lie, but it does not explain itself either. A guide to what you are looking at.