Announcing your onchain TLD, or not

You have acquired an onchain top-level domain. The registry record is public: anyone who checks a block explorer can see the wallet that holds the token. That transparency is structural. You did not choose it and you cannot reverse it. What you do choose is whether to speak about it, when, to whom, and in what terms.

That choice matters more than it appears. The wrong kind of announcement creates questions you cannot yet answer. Silence held too long can create the impression of something to hide. Most organizations land somewhere between the two, and the middle ground has its own discipline.

This article sets out the three postures, the conditions under which each makes sense, and the practical requirements attached to each. By the end, you will be able to pick a posture, plan its execution, and avoid the mistakes that damage credibility in each case.

Nothing in the registry requires you to announce

The starting point is easy to miss: the acquisition of an onchain TLD does not, by itself, trigger a public statement. The transfer happens onchain, the registry record updates, and the new holder controls the namespace from that moment forward. Nothing in that process calls for a press release, a social post, or a notice to anyone outside the small team that managed the transaction.

One qualification belongs here. Some organizations carry disclosure duties of their own, because they are publicly traded, regulated, or bound by commitments to investors or lenders. Whether an acquisition of this kind falls within such a duty depends on the organization, the size of the transaction and the country. That is a question for your own counsel, and it is settled before the communications plan, not after.

The record itself says less than people assume. An onchain TLD is held in a wallet, which is the software or device that controls the keys to an onchain address. The address is public, but the connection between that address and a named organization becomes public only if you make it so, or if someone else who knows it does. A holder can operate under a wallet address for a long time without that connection appearing in any public record.

That is not a loophole. It is simply how the system is built. A holder who understands it can plan communications with real latitude. A holder who does not understand it sometimes announces before being ready, and an early announcement is harder to undo than silence.

The case for staying quiet

Silence has advantages that are easy to underweight in the first weeks after an acquisition. Consider each one before deciding to speak.

Readiness

An onchain TLD becomes useful only when names issued under it resolve and reach the audience you intend. Onchain names resolve outside the ICANN DNS root, which means an ordinary browser does not open them without support. Resolution depends on compatible wallets and browser extensions, and that coverage is partial and changes over time.

If you announce before your intended uses are live and reachable by your audience, you will receive the same question repeatedly: where does it work? If you cannot give a complete answer, the announcement costs credibility instead of earning it. A plan that puts the uses in order, such as the one the Launch Roadmap tool builds for a newly acquired TLD, lets you see how far you are from that answer.

Competitive position

As the holder, you are the only one who can issue names under your TLD. That gives you a namespace no third party can populate, and time to shape it without an audience. The moment you announce, competitors know what you are building and can prepare their own position or their own account of yours. A holder who has put pay.yourbrand and id.yourbrand to work before any public statement arrives at the announcement with working infrastructure, not a promise.

Legal caution

If the purchase terms contain confidentiality clauses, or the exchanges that led to them were covered by an NDA, speaking about the deal before you have confirmed what you may say risks a breach of those obligations. More broadly, an announcement can affect open trademark matters, licensing negotiations or regulatory processes in ways that are hard to predict. Your counsel decides what is safe to say, not the communications team.

Optionality

Silence also keeps your options open. If circumstances change (a better use emerges, a partnership alters the plan, a wallet or browser adds support) you can build that into your first public statement instead of correcting an earlier one. A first statement is made once. Everything said after it is read against it.

Silence is not free of cost, however. It asks for discipline from everyone who knows, and it leaves you exposed if the acquisition is noticed before you have an answer prepared. Staying quiet is a posture you plan, with a reactive statement ready, not a decision to do nothing.

The case for announcing

Silence is not always the right answer. There are conditions under which speaking early serves the organization better.

The clearest case is legitimacy inside the organization. Large organizations sometimes acquire digital assets that stay invisible to most of the people who will eventually work with them. An onchain TLD that no one inside the company knows about tends to stall. Budget goes elsewhere. The IT, legal and marketing teams whose cooperation you need for putting the TLD to work after the transfer are harder to mobilize for a project they have never heard of. An internal announcement, discussed below, can unlock that cooperation even when external communication is premature.

The second case is the signal to the market. Some organizations acquire an onchain TLD because holding it says something about their technology posture or their relationship with a particular community of users. Consider a financial services firm that has acquired .yourbrand and intends to use it for payments to a name. It has a coherent story for trade journalists, partners and customers, but only once pay.yourbrand receives a payment. If the story is ready, the announcement creates the signal. If it is not, the announcement creates noise.

The third case is preemptive. You may have reason to believe the acquisition has already been noticed: by a journalist who follows onchain activity, by a partner who was involved in the work, or by a community that watches the registry. In that situation, waiting to be asked is weaker than a planned statement. A first statement on your own terms is easier to stand behind than a reply drafted in an afternoon.

The middle path: use first, explain when asked

Most organizations that handle this well follow a pattern that is neither full announcement nor strict silence: they activate first and explain when asked. This is not a compromise. It is a specific posture with its own logic.

Under this approach, you begin issuing and using names under your TLD without making any external statement about the TLD itself. You might point pay.yourbrand at a payment flow, issue names to the members of a partner program, or publish a website on the TLD at docs.yourbrand. The names do work. The TLD is live. You have not issued a press release.

When a journalist, a customer or a partner asks about the .yourbrand names they come across, you have a working answer: here is what the TLD is, here is what we use it for, here is how to reach it. The technology is explained by demonstration, not by anticipation. That is a much stronger position than announcing a capability and then being asked whether it is live yet.

Before you adopt this posture, check that what you intend to show can be shown. The page that lists what works on onchain TLDs, with sources is a useful reference for that check. A name that resolves in a supported wallet can be shown. A name that receives a payment can be shown. A planned capability that is not yet working cannot, and meeting a press inquiry with a demonstration that fails is worse than having said nothing.

The posture has one weakness. Because there is no announcement, there is no single text that everyone has read. Different people answer the same question in different words, and the differences are noticed. The remedy is a short approved set of answers, written before the first name is used in public, and held by the people most likely to be asked: the spokesperson, the support team, and the account managers of the partners who receive names.

Three postures compared

The differences between the three postures are practical. The table sets them side by side.

No posture is permanent. Many organizations move through them in sequence: silence during the acquisition and early activation, use first once something is live, a public announcement once the story is coherent and the uses are stable.

Internal communication comes first

Whatever external posture you choose, the internal one must be settled before anyone speaks outside. This is a practical constraint, not a courtesy.

An onchain TLD touches more functions than it first appears to. Legal needs to know because there may be trademark implications, confidentiality obligations and questions from counterparties. IT and security need to know because someone must control the wallet that holds the TLD, and because any use involving resolution, payments or websites requires technical work. Marketing needs to know because the names will appear in materials, and someone will have to answer questions about them. Finance may need to know because the asset has value and may call for an accounting treatment, which your own advisers determine. The list of people who need a briefing before any public statement is longer than most communications teams expect.

One account, approved before it circulates

The discipline is to brief those functions with a single, consistent account of what the TLD is, what you intend to use it for, and what people should say if asked. That account must be accurate. It cannot promise capabilities that do not exist, and it must be approved by legal before it circulates. A briefing document that moves through an organization before legal has reviewed it is a liability, because anything in it can eventually reach a journalist or a counterparty.

The briefing should separate two circles. The first is the small group that took part in the transaction and knows its terms. The second is everyone else who needs to know that the organization holds the TLD and what it is for. The second circle does not need the terms, and should not receive them. An internal memo that mentions the price is the most common route by which a price becomes public.

One spokesperson

The briefing should also name the single person who answers external questions. Organizations that let several people speak about a new acquisition tend to produce inconsistent answers, inconsistent answers produce corrections, and corrections produce more questions. One person and one approved set of answers are enough until the story is mature.

Internal communication also has a question of its own that external audiences rarely ask: who controls the wallet. Employees who understand that the TLD is a token will want to know what happens if the person holding the keys leaves. A multisignature wallet, which requires several keys to approve an action, is a common answer. The briefing should say that the question has been dealt with, without describing the arrangement in detail.

What an announcement must be able to demonstrate

If you decide to announce, the announcement makes commitments, and the audience will hold you to them. Every claim in a public statement about an onchain TLD should be supported by something the reader can verify when the statement is made, not at some later point.

The minimum for a credible announcement is at least one named use that is live and reachable by the audience you are addressing. Not planned, not in development, not available under conditions that most of your audience cannot meet.

Test from outside

That means testing before announcing. If you announce that pay.yourbrand receives payments, someone outside your organization must be able to make a payment to that name. If you announce that docs.yourbrand holds your developer documentation, a test in a clean browser with the appropriate extension must open the documentation. Have the test run by someone who was not involved in the setup, on a device that has never been used for it.

State how the name is reached

If the use requires a specific wallet or extension, say so. For a Freename name, your announcement can list the three places where it is supported: Bitcoin.com Wallet, MetaMask through Freename’s resolver, and desktop browsers through the Freename Web3 extension. That coverage is partial and it changes. Stating it honestly, and explaining what your audience needs in order to reach your names, is not a weakness in an announcement. It is the kind of precision that establishes credibility.

For the same reason, publish the announcement itself where everyone can read it: on your ordinary website, under your DNS domain. The DNS is simply better at universal reach, and an announcement that most readers cannot open defeats its purpose. The onchain names are what the announcement describes. They do not need to be the place where it lives.

Say why you hold it

An announcement should also explain why the organization holds this TLD. The explanation does not need to be elaborate, but it must be coherent. “We hold .yourbrand as a dedicated namespace for our payment and partner names” is coherent. A statement that hedges on the purpose, or lists hoped-for uses with no working example, invites the question that is hardest to answer: what does it do now?

Leave superlatives out. A statement that the TLD makes you first, or unique, or ahead of your sector is a claim you would have to prove, and it turns a factual notice into an argument. A plain description of what the names do ages better.

What the press and customers will ask

Preparing a spokesperson means preparing for specific questions. The ones raised about an onchain TLD fall into predictable groups.

Does it work in a normal browser?

This is usually the first question, and the honest answer is: not without an extension or a compatible wallet. Prepare your spokesperson to say this directly and to name the tools that work. Claiming compatibility you do not have destroys credibility with any technically informed journalist. Describing the coverage as it is, and noting that it changes, is a position you can stand behind.

Why not just use an ordinary domain?

The honest answer lies in the properties that differ. Only the holder can issue names under the TLD. If yours is a Freename TLD, you pay no annual renewal fee to keep it. The TLD is recorded onchain as a token held in your wallet. Say just as plainly that your ordinary domains are not going anywhere: onchain TLDs and DNS domains serve different purposes, and both will coexist in your infrastructure. For a journalist who wants a structured view, the side-by-side comparison of an ICANN dotBrand and an onchain TLD is a reference you can point to.

Who sold it, and for how much?

The terms are confidential and the seller is not identified. That is the complete answer to both questions, and the spokesperson is briefed to give it without elaboration.

Who else has names under your TLD?

Only you can issue names under your TLD. No one holds a name under it unless you issued it. This is worth explaining, because it is not intuitive to audiences used to shared TLDs, where anyone can register a name through a registrar. Here the exclusivity is structural, not a matter of policy.

What is its legal status?

Onchain TLDs exist outside the ICANN DNS root and are not delegated by ICANN. An onchain TLD is a registry record held as a token in a wallet. The record is public and anyone can check it on a block explorer. What that record means in a particular legal context, and how it relates to trademark rights, varies by country and is a question for your counsel, not for a press release. A spokesperson who is asked can say exactly that.

What does this change for customers?

Customers ask this more often than journalists do, and the answer should be short. If nothing changes for them unless they choose to use a name, say so. If a name replaces something they already use, say what stays available alongside it. A customer should never learn from an announcement that a familiar route has been closed.

What must never be said about the seller or the terms

The rule is simple: nothing.

The seller is not named. The price is not stated or implied. The terms of the transfer are not characterized as favorable, standard, or anything else. Hush Partners never names the seller of a given TLD, and the standard mutual NDA covers every exchange with the desk. Your purchase terms may contain their own confidentiality clauses. Review both with counsel if there is any doubt about scope. A breach exposes your organization to legal risk and harms the other party. It also tells every future counterparty how you treat a confidence.

“The terms are confidential” covers every question about the seller and the price. It covers questions from journalists, investors, partners, and colleagues who were not part of the transaction team. It covers friendly curiosity as much as hostile inquiry. There is no version of the answer to “who sold it to you” or “what did you pay” that carries any content, and it is the same for every audience.

Inference counts as disclosure

The harder failure is an announcement that does not state the seller’s name but lets it be worked out. Describing the acquisition as “bought from a long-standing holder in our sector” or “a transaction with a well-known portfolio” is not confidentiality. Neither is an adjective about the price, or a remark about how long the negotiation took. Counsel reviews the text for what it lets a reader conclude, not only for what it says.

The same care applies to the public record. The transfer between wallets is visible onchain, and someone may ask you to comment on the address the token came from. Do not. You can confirm what is yours: that your organization holds the TLD. You add nothing about any other address.

Choosing a posture and planning the next one

When to move from one posture to the next

The posture you adopt at the transfer is not necessarily the one you will hold later. Planning the transitions is part of the communications work.

The move from silence to use first is triggered by one live use that can be shown. It requires the internal briefing described above, the approved set of answers and a designated spokesperson. It does not require a press release.

The move from use first to a public announcement is triggered by a coherent story that the uses can support: several of them live, internal alignment, legal clearance, and a clear answer to “why now”. Some organizations never make this move. They run their TLD as infrastructure, explain it when asked, and find that level of communication sufficient. Others want the signal that a formal announcement produces. Both are legitimate.

Outside pressure alone should prompt neither move. A journalist asking questions is not a reason to issue a press release before the story is ready. It is a reason for your spokesperson to give the approved answer for the posture you are in. “We use .yourbrand for specific partner applications and will say more when there is more to show” is a complete answer at the use-first stage. It commits to nothing it cannot deliver.

The decision and the first three documents

Start with a decision, in writing, signed off by the person who owns the acquisition: silence, use first, or announcement. Add the condition that would move you to the next posture, so that the move is a planned step and not a reaction.

Then prepare three documents, whatever the posture. The first is the internal account: what the TLD is, what it is for, who speaks. The second is the set of approved answers to the questions above, including the two that have only one answer. The third is a reactive statement of a few lines, cleared by legal, for the day someone asks before you intended to speak. With these three in hand, each posture is safe to hold.

If your first use is not yet live, that is the work that comes before any of this. Hush Partners describes how it conducts a file, including confidentiality, in its rules of engagement. For anything those pages do not answer, the desk is reached through the contact form.

Questions people ask

Can a competitor find out about the acquisition even if we say nothing?

A competitor can see that a TLD token moved to a new wallet. What the record alone does not show is which organization controls that wallet, unless you have associated your organization with the address elsewhere. During the silence phase, avoid using that wallet for anything that carries your name.

Do we need a registered trademark before we announce?

Nothing in the registry requires one. Holding trademark rights in the name and holding the matching onchain TLD are separate facts, and an announcement can state both. Whether to file or extend a registration first depends on your countries and classes, and your IP counsel decides the sequence.

What if a journalist publishes before we are ready?

Use the reactive statement. Confirm only what you choose to confirm, decline to comment on the terms, and offer to speak about the intended uses if any are live. Do not correct details about the seller or the price, even wrong ones: a correction is information.

Can announcing create a legal exposure that silence would not?

It can, depending on the country and the name. An announcement that describes the TLD in ways that conflict with existing trademark rights, yours or a third party’s, can create problems that silence would have avoided. This is one more reason legal review covers which names you show and how you describe them. This article is information, not advice.

Should the announcement mention the registry?

If the way the TLD works matters to your audience, naming the registry is accurate and adds context: on Freename, a TLD is recorded onchain as a token held in a wallet. A developer audience may want that detail. A general audience may not. The test is whether the detail makes the announcement clearer or more cluttered.