Buying a TLD without revealing the buyer
How an organization acquires an onchain TLD through a mandate: what the holder learns and when, which wallet receives the token, and what the record shows.
An organization that wants an onchain top-level domain usually has two reasons to keep its name out of the conversation. The first is price: a holder who learns that a large company is asking will think about what that company can pay and stop thinking about what the TLD is worth. The second is the project behind the purchase. A request for .yoursector from a company that has never operated in that sector tells a careful observer something the company has not announced.
Both problems have the same remedy, which is old and ordinary: someone else asks. Property, patents and DNS domains have been bought through intermediaries for a long time, and nothing about an onchain TLD changes the principle. What changes is the ending. An onchain TLD is a token held in a wallet, and the registry record that says which wallet holds it is public. The negotiation can be private from the first note to the last. The transfer cannot.
This article is written for the buying side only. It covers what a mandate hides and what it does not, what the holder is told at each stage, the points at which your name may have to come out, how to choose the wallet that receives the token, and what anyone will be able to read on the record afterwards. It ends with the document to write before you mandate anyone.
Why the buyer’s name moves the price and exposes the project
A TLD has no comparable sales to anchor a negotiation, so a holder builds a price from whatever information is available. The identity of the party asking is the richest piece of information there is. It tells the holder how large the budget might be, how much the string matters to the buyer, and whether there is an alternative. A company whose trademark is the string has no alternative, and the holder knows it the moment the company signs its own name.
That does not make the holder unreasonable. Any seller would do the same. It simply means that a buyer who opens under its own name negotiates against its own balance sheet, and a buyer who opens through a mandate negotiates about the asset.
The second effect is quieter. A holder who receives a note from a known organization is under no duty of silence until an NDA is in place. The holder may mention the approach to a friend, an adviser or another party who once asked about the same TLD. None of this is malicious, and none of it is controllable once your name is in the note. For a company preparing a product, a new line of business or an entry into a sector, the approach itself is the leak.
What an undisclosed buyer is, and what it is not
Buying through a mandate means that an intermediary approaches the holder, negotiates and conducts the process on your instructions, and says openly that it acts for a client it is not naming. The holder knows there is a principal. The holder does not know who.
That openness is the whole difference between discretion and deception, and it is worth being exact about it.
- The intermediary says it acts for a client. It does not pretend to buy for itself.
- It does not invent a buyer, a purpose or a budget. A false statement about who is buying or why can undo a contract in many legal systems, and rules on this vary by country. Your own counsel decides what may be said and what may simply be left unsaid.
- It answers a direct question honestly. If the holder asks whether the client is a company whose trademark matches the string, the honest answers are “yes”, “no” or “I am not permitted to say”. A false “no” is not available.
- The holder remains free to refuse to deal with an unnamed party. Some will. That is their right and it ends the anonymous route, not necessarily the acquisition.
A mandate also hides nothing from your board, your auditors, your tax adviser or any authority with a legal right to ask: the transaction sits in your own books. Anonymity here is toward the counterparty and the public during a negotiation.
One more boundary: an unnamed approach must never be used to make a holder believe that a legal threat is behind it, or that the offer will be withdrawn at an artificial deadline. A buyer that hides its name in order to apply pressure it could not apply openly has left discretion behind.
What the holder is told at each stage of an anonymous approach
The amount of information a holder has grows as the file advances. Planning the anonymous purchase means deciding, in advance, what is released at each stage and what stays back until the end or forever. The table gives a workable pattern for a file run through a buy-side mandate.
| Stage | The holder is told | The holder is not told |
|---|---|---|
| First note | An intermediary acts for a client interested in the TLD | Who the client is, why, the budget |
| After the NDA | Type of buyer in broad terms, seriousness, process | The name, unless you decide otherwise |
| Offer and terms | Price, structure, timetable, what is included | The project behind the purchase |
| Closing | The receiving wallet address | Who controls that wallet, unless agreed |
Three remarks on this pattern.
The first note is the least informative document in the file. It identifies the TLD, says that a client has an interest, and offers a confidential conversation. A holder who wants to understand what such a note means before answering can read the page for people who have received a note. The note does not carry a price. A figure in a first message tells the holder the budget before any conversation has taken place.
The NDA comes before anything descriptive. Once a mutual NDA covers the exchange, the holder can be given a broad description of the buyer: an operating company and not a reseller, for example, or a buyer with the means to close. The description is chosen so that it is true and useful to the holder without narrowing the field to one name. “An organization in the sector the string describes” may already be too much if the sector has few players.
The receiving address is the one thing the holder must learn. A token cannot be sent to an unnamed destination. At closing the holder, or the escrow acting for both sides, sees the address the TLD goes to. What that address reveals depends entirely on the wallet you chose, which is why that choice is made early and not on the day of closing.
The moments when your name may have to come out
An anonymous acquisition can stay anonymous to the end. Some do not, and the points at which the name comes out are predictable. Deciding in advance how you will respond at each of them is better than deciding under time pressure.
The holder makes it a condition
Some holders care who takes over a TLD, particularly if they have issued names under it to people who rely on them. A holder may ask who the buyer is before agreeing to sell, or may ask for assurances about what will happen to names already issued. You can often answer the second question without answering the first, by giving a commitment about those names in the contract. If the holder insists on the first, you choose between disclosure under the NDA and walking away.
The contract needs a party
A sale agreement has a buyer. That buyer can be you, a subsidiary, a company created for the purpose, or an agent contracting for an undisclosed principal where the law that governs the contract allows it. Each choice has consequences for warranties, for who can sue whom if something goes wrong, and for tax and accounting. These are questions for your counsel in the relevant jurisdictions, and they should be asked before the offer goes out. A structure invented in the last week of a negotiation tends to delay closing and to reveal more than it was meant to hide.
A compliance check requires it
Depending on the countries and the parties involved, someone in the chain may need to know who the buyer really is: an escrow provider, a marketplace, a bank that funds the purchase, or the seller’s own counsel carrying out checks the seller is obliged to make. Disclosure to a party with a duty of confidentiality and a legal reason to ask is not a leak. Plan for it, and make sure the disclosure goes to that party only and not into the general correspondence.
Choosing the wallet that receives the TLD
The wallet that receives the token is the most consequential decision in an anonymous purchase, because it is the only decision whose result is published. Everything said in the negotiation stays between the parties. The destination address goes on the public record and stays there.
A wallet address is a string of characters, not a name. On its own it identifies no one. It becomes identifiable through its history: where its funds came from, what else it holds, what it has paid for, and whether anyone has ever published it next to your organization’s name. The four realistic options differ on exactly that point.
| Receiving wallet | What an observer can infer | Main drawback |
|---|---|---|
| Your known corporate wallet | The buyer, at once | No anonymity after closing |
| A new wallet, no history | A transfer to an unknown party | Needs custody rules from day one |
| A new wallet of a subsidiary | Same as above, until the link is found | Corporate link may be traceable |
| An interim wallet held by an adviser | A transfer to an unknown party | Second transfer and trust in the adviser |
A wallet the organization already uses
This is the simplest option and it ends the anonymity on the day of closing. It suits a buyer who only wanted to protect the negotiation.
A new wallet with no history
A wallet created for this purchase, which has never transacted, tells an observer nothing except that the TLD moved. It is the standard choice for a buyer who wants the record to stay uninformative for a while.
Its weakness is everything that happens next. A new wallet needs funds to pay network fees for later operations, and the source of those funds is visible. If you top it up from your known corporate wallet, or from an account at an exchange that can be linked to you in ways you do not control, the two are connected for anyone who looks. The wallet also needs proper custody from its first minute: who holds the keys, how many people must approve a transaction, where the recovery material is kept. A multisignature wallet, which requires several keys to approve a transaction, is the usual corporate answer. An anonymous wallet with weak custody trades a confidentiality risk for a much worse one, which is losing the TLD.
A wallet held by a subsidiary or a purpose-made company
The token is the same; the difference is in the contract and the books. An entity whose name says nothing about the group can sign the sale agreement and hold the TLD. Whether that entity can be traced to you depends on what company registers disclose in the country where it is formed, and that varies widely. Do not assume that a company with a neutral name is a closed box. Ask counsel what a member of the public can find out about it.
An interim wallet held by an adviser
A law firm or another adviser receives the TLD and transfers it to you later. This separates the purchase from your wallet in time, at the cost of a second transfer that is just as public as the first. Anyone who follows the token sees it arrive in one wallet and then move to another. It also places the asset, for a period, in the hands of a third party, which must be covered by a written agreement and by that adviser’s own custody arrangements. It is rarely worth the added complexity unless the contract structure already requires it.
What the public record shows after the transfer
Before closing, the registry record of an onchain TLD shows that the token sits in the holder’s wallet. After closing, it shows that the token sits in yours. Any member of the public can read that record on a block explorer, a website that displays the contents of a blockchain. No request, account or justification is needed to look.
An observer who looks at the TLD after your purchase can see the following.
- That the token changed wallets, and when.
- The address it left and the address it arrived at.
- Possibly the amount and the asset paid, depending on how the closing was structured.
- Every later action taken from the receiving wallet: names issued under the TLD, records set on those names, further transfers.
- Everything else the receiving wallet holds or has ever done.
The same observer cannot see who controls the receiving wallet, why the TLD was bought, what was said during the negotiation, or the terms of the sale agreement beyond what the transaction itself discloses.
The price deserves a moment of attention. A buyer that hides its identity often also wants the price to stay private, and these are separate problems. Where closing runs through an onchain escrow, whether the consideration can be read on the record is a point to confirm with the venue. If the confidentiality of the amount matters to you, raise it when the closing mechanics are designed, not after. There may be no way to keep it off the record that is consistent with a safe exchange, in which case you accept it knowingly.
Here the traditional domain name system is simply better for a buyer who wants quiet. A DNS domain can change hands between two accounts at a registrar with registration data masked by a privacy service, and an outside observer may learn nothing of the change, let alone the price. An onchain transfer has no equivalent of that silence. What it offers in exchange is certainty: the token is in the wallet or it is not, with no account access to dispute and, on a Freename TLD, no annual renewal to miss. A buyer who needs the transfer itself to be invisible should understand that an onchain TLD cannot give that.
How a buyer’s identity leaks without anyone reading the record
In practice, an unknown wallet address is rarely what gives a buyer away. The buyer does. The record is a small part of the exposure, and the rest is behavior.
Use. Only the holder of a TLD can issue names under it. The day you issue pay.yourbrand and point it at a wallet that customers already know, the question of who holds .yourbrand is answered. The same is true of a website published under the TLD with your name on it. Activation and anonymity pull in opposite directions, and for most buyers activation is the point of the purchase. Plan the order: what you will do with the TLD while it is still unattributed, and what waits until you are ready to be identified.
Funding. As noted above, the source of the funds that pay for the TLD, or that pay network fees afterwards, links wallets together. This is the most common unintended connection.
People. An acquisition involves legal, finance, security and whoever sponsors the project. Each added person is a possible conversation at a conference. Keep the circle small and give the project an internal name that does not contain the string.
The seller. After closing, the former holder knows the price and the receiving address, and may know more. The NDA and the confidentiality terms of the sale agreement govern what the seller may say, and for how long. Check that the confidentiality clause survives closing and covers the existence of the sale, not only its terms.
A sequence for the anonymous purchase, from mandate to transfer
The order of the work matters more than any single measure. Decisions about the wallet and the contracting party are cheap at the start and expensive at the end.
- Define what you are protectingWrite down whether the aim is to keep your name out of the negotiation, out of the public record afterwards, or both, and for how long. Each answer leads to a different wallet and a different contract.
- Fix the internal circleName the people who know the string. Give the project a neutral name and use it in every document that does not need the string.
- Settle the contracting party with counselDecide which entity signs the sale agreement and holds the asset, and what a member of the public can learn about that entity. Take tax and accounting advice at this point.
- Create and secure the receiving walletSet up the wallet, its approval rules and its recovery material before any approach is made. Decide how it will be funded without linking it to a known wallet, if that matters to you.
- Mandate the intermediary in writingThe mandate states what may be said about you at each stage, what may never be said, and who authorizes any disclosure of your name.
- Agree the closing mechanics earlyBefore price is final, establish how the exchange will run, what the transaction will show on the record, and which party to the escrow needs to know who you are.
- Plan the first useDecide what happens to the TLD in the weeks after transfer, and at what point you issue a name or publish anything that identifies you.
When staying unnamed is not worth the effort
Anonymity has costs. It adds a structure to maintain, it slows the first conversations, and it removes a card you might have wanted to play. There are situations where the plain approach is better.
If your organization’s trademark is the string, the holder will guess. An unnamed note about .yourbrand from an intermediary who says it acts for a client leaves few candidates. The mandate still has value, since it keeps the conversation professional, keeps your staff out of direct contact, and preserves your ability to say that you have not confirmed anything. But the price effect of anonymity is weaker, and a negotiation built on the holder not working out the obvious is fragile. In that case the better approach is often to be candid under the NDA at an early stage and to negotiate on the merits. The page on brand namespace recovery describes that kind of file.
If you intend to use the TLD publicly within days of closing, protecting the record is pointless. Protect the negotiation, receive the token in the corporate wallet, and spend the saved effort on custody.
If the holder is known to sell only to parties it can identify, an unnamed approach wastes a first impression. Where that is known, open with a disclosure under the NDA.
Write the disclosure plan before you mandate anyone
The practical next step is a single page, written by the sponsor of the acquisition with counsel, before any intermediary is instructed. It answers five questions: what you are protecting and until when; which entity buys; which wallet receives the token and who controls it; what may be said about you at each stage and who can authorize more; and what you will do with the TLD after transfer, in which order. An intermediary who receives that page can run the approach without coming back to you at each turn. One who does not will be asking these questions in the middle of a negotiation, when the answers are worth less.
This is work Hush Partners does on the buying side: an organization mandates the desk to find and approach a holder. The exchanges are covered by a mutual NDA, a single named partner stays with the file from the first note until the token has moved, and closing runs through onchain escrow on an aftermarket. The fee is a fixed amount, not a percentage, charged to the organization that gives the mandate. The rules of engagement are the rules the desk works by, and the page on how a file works shows the stages in order. If you have the one-page plan, or want help writing it, the contact form is the way in. Once the token is in your wallet, the question changes from who knows to what you do with it, which is the subject of post-transfer activation.
Questions people ask
Can a holder find out who the buyer is by tracing the receiving wallet?
A holder has the same view of the record as anyone else, plus the knowledge that this address belongs to the buyer. If the wallet is new and funded without a link to a known wallet, the address alone identifies no one. If it has a history that connects it to your organization, the holder can read that history like any other observer.
Can the buyer move the TLD to another wallet later to break the trail?
It can move the TLD, but the move is recorded like the first one. Anyone following the token sees each wallet it passes through, so a later transfer adds a step to the trail without erasing it. Later transfers are useful for custody reasons, such as moving to a wallet with stronger approval rules, not for confidentiality.
Is it lawful to buy an asset without telling the seller who you are?
Acting through an agent for a principal who is not named is a long-established practice in many legal systems, provided nothing false is said. The details, including what must be disclosed to whom and what an agent may sign, vary by country and by the law chosen for the contract. This is information in general terms; your own counsel decides for your case.
