Onchain today
What an onchain TLD does today: websites, wallets, payments, agents.
ERC-8004 explained: the draft standard for trustless agents
Three registries, one question: can you trust an agent you have never met. A plain reading of the draft.
Names for staff and teams under your own TLD
A name that says who someone is in the organization is useful only if it can be withdrawn the day they leave.
Verifying a counterparty by its onchain name
A name narrows the question from which address to whose name. The second question still needs an answer.
The records an onchain name can carry
A name does nothing until records are set. The kinds of record, and the discipline they need.
Privacy on a public record: what others see about your TLD
Nothing on the record says who you are. A good deal can still be learned from what you do.
One name, several blockchains: how a name maps to addresses
The same name can lead to different places depending on the network. Useful, and a source of costly confusion.
AI agents that pay and get paid under a name
An agent with a budget is a new kind of counterparty. Identity and payment have to be thought about together.
Lookalike characters in onchain names: the homoglyph problem
A name can look exactly like yours on a screen and be a different string. An old problem in a new setting.
Testing an onchain name before you publish it
A name that fails in the one wallet your largest customer uses is worse than no name. Test first.
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.
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.
IPFS and content addressing, explained without the mythology
Permanent, uncensorable, free: three things people say about IPFS that need qualifying.
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.