Onchain TLDs and game publishers: what to check

A game publisher’s brand does not sit in one place. It lives in a studio name, a roster of franchise titles, a set of in-game economies, and a network of community spaces that the publisher did not build and does not fully control. When the studio name or a franchise title exists as an onchain top-level domain (a TLD recorded as a token on a blockchain, outside the ICANN DNS root), each of those layers acquires a distinct exposure that a standard domain audit will not catch.

This guide is written for the head of legal or of community at a game publisher. It covers why the sector sits in a position of its own, where the exposure lies by function, and what to check first. By the end you will have enough to brief a working group and delegate most of the checklist the same day.

How an onchain TLD works in general is dealt with once, briefly, in the section that follows. Everything after it is about games: if your organization already understands the technology, start at the section on why gaming differs.

What an onchain TLD is, and what it is not

An onchain TLD is a top-level domain, the segment after the final dot in a name, whose record lives on a blockchain and not in the ICANN DNS root. On the Freename registry, the TLD exists as a token that sits in a wallet, so control of the wallet is control of the TLD. Issuing names under it, such as pay.yourbrand or vault.yourbrand, is reserved to that holder. A Freename TLD carries no yearly renewal charge, which means a TLD does not lapse because someone forgot to pay.

Because these names are resolved away from the DNS that ICANN coordinates, a standard browser needs added support before it can open one. A compatible wallet, a browser extension or a supporting application does that work. Coverage is partial and it changes; the page on what is live keeps the picture, with sources. Partial coverage does not remove the question for a publisher, because the uses that matter most in games (names shown in wallets, names that receive payments, names used as identity) sit exactly where resolution already works.

The registry record is public. Anyone can look it up on a block explorer and see which wallet holds a TLD. That tells your team that a TLD exists and where it sits. It does not tell you who is behind the wallet.

One limit to keep in view: the UDRP, the dispute procedure that ICANN-accredited registrars are bound to follow for DNS domain names, was built for the DNS and does not extend to names recorded on a blockchain.

Why gaming sits in a different position from most sectors

Most reviews of onchain TLDs treat the matter as a variant of a domain name dispute: a name that looks like your brand exists somewhere, and you would like to hold it. That framing misses what is specific to gaming.

The first difference is the audience. Part of a game publisher’s audience is comfortable with wallets, keys and digital items in a way that the customers of a bank, a luxury house or a drug maker generally are not. A player who has held a tokenized item, received a token reward or traded on a secondary market already understands that an onchain name is an asset with a holder. When a name under .yourbrand appears in a wallet or in a community space, that audience does not need the system explained before taking the name seriously.

The second difference follows from the first. In many sectors, the exposure created by a matching TLD in other hands is mainly one of confusion about who is speaking. In gaming it reaches into money. A TLD that matches a franchise title can carry a whole family of payment names, and those names can appear in wallet interfaces as destinations. If a player sends funds to store.yourbrand expecting to pay for an in-game item, and that name points to a wallet the publisher does not control, the harm is financial for the player and a support and trust problem for the publisher.

The third difference is how communities form. Fan projects, modding groups and unofficial guilds organize quickly around a franchise name, and they stay. A community project that obtains names under .yourbrand is not necessarily acting in bad faith. The publisher, however, cannot correct or withdraw those names, because whoever holds the TLD decides which names exist under it.

The fourth difference is the number of names. A game organization tends to run several brands at once: a studio identity, a catalog of franchise titles, and often a launcher or platform name. Each is a candidate TLD. A review that checks only the corporate name will miss the titles, and in this sector the titles are usually what players care about.

The franchise and title layer

A publisher’s intellectual property typically spans a catalog of active titles and a back catalog of dormant franchises whose names keep their community long after the last release. Each title is a possible TLD, and each has a community that would read a name under that TLD as meaningful.

The practical consequence is that the scope of a review is not one name. It is a map of the whole catalog, sorted by three things: the size of the community, how likely that community is to use wallets, and whether items from the title change hands outside the game. A franchise with an active trading economy sits higher on the map than one whose players never touch an onchain asset. A franchise whose fans run their own chat servers, wikis and tournaments has already shown that it can organize a namespace without the publisher.

Dormant titles deserve a line of their own. A publisher may not have shipped anything under a name for a long time, yet the name still gathers players, speedrunners, collectors and modders. If a remake, a remaster or a licensing deal is on the internal roadmap, the name is commercially alive even though the storefront page is quiet. Product and business development know which dormant names are in that position; legal often does not, which is why the scope map needs their input.

Sequels and sub-brands raise a narrower question. A TLD is a single word after the dot, so the exposure usually attaches to the franchise word itself and not to each numbered entry. Abbreviations are the exception. Many communities refer to a title by a short form that the publisher never registered as a trademark and never used in marketing. If players type the abbreviation more often than the full title, the abbreviation belongs on the map.

When a franchise title exists as a TLD and the publisher does not hold it, two things are true at once. First, the holder can issue names that the publisher cannot withdraw. Second, the publisher cannot build anything of its own under that TLD (no official payment name, no player identity, no licensed storefront name) until the question of who holds it is settled.

A publisher can measure how exposed each of its brands is onchain with the Namespace Exposure Score, a tool that costs nothing to use. For a publisher with several titles, running it on each franchise name separately, and not only on the studio name, gives a more accurate view of where the exposure is concentrated.

Players already used to wallets: adoption is not hypothetical

The usual objection to any onchain brand question is that few people use the technology. In gaming that objection is weaker than elsewhere. Some of the audience, by no means all of it, already holds wallets, trades onchain assets and uses wallet-linked names as handles in community spaces. No figure is needed to make the point: your community team can tell you from its own channels whether wallet addresses and onchain names circulate among your players.

This matters for a specific reason. A name under an onchain TLD carries the most weight in the places that this wallet-holding audience already trusts, and far less on a website that an ordinary browser cannot open. Those places are wallet interfaces, onchain payment links, token-gated community spaces (spaces that admit a member on the strength of a token held in the member’s wallet) and peer-to-peer marketplaces. They are the same places where part of a gaming audience spends its time.

Support is concrete, if incomplete. Freename names can be used in Bitcoin.com Wallet, in MetaMask by way of Freename’s resolver, and in desktop browsers that have the Freename Web3 extension installed. That list is partial and it moves, so nobody should assume a name resolves everywhere. For a publisher the relevant fact is narrower: a player who already uses a supporting wallet can see and use a name under a franchise TLD without installing anything new.

Consider a name such as drops.yourbrand displayed in a wallet that resolves it. A player used to reward drops will read it as the publisher’s channel for those rewards. That player does not have to be careless to be mistaken. The name looks right, and the software confirms that it resolves.

The page on payments to a name explains how names work as payment destinations. For gaming, the scenarios to keep in mind are the ones in which players send funds: purchases, entry fees, tips to creators, paid access to events. In each of them, a name under the franchise TLD would be read as the publisher’s own.

It is worth being equally clear about where the DNS remains the better tool. The official store, the account system, customer support and the launcher’s update servers run on DNS domain names, open in every browser, and are covered by dispute procedures your counsel already knows. Nothing about an onchain TLD replaces them. The question in this guide concerns the wallet-facing edge of the audience, not the core of the publisher’s web presence.

In-game purchases, secondary markets and payment names

Games that sell cosmetics, season passes or tradeable items run a small economy that players treat as real. Secondary markets for those items, where they exist, extend that economy beyond the publisher’s platform. Both layers are touched when the franchise name exists as an onchain TLD.

The purchase side

A name under .yourbrand can serve as a payment destination in wallets that resolve onchain names. If the TLD is in other hands, a name such as shop.yourbrand or pass.yourbrand becomes a destination that a player could mistake for the publisher’s. The publisher cannot remove the name or point it elsewhere.

The publisher’s own checkout does not need to accept onchain payments for this to matter. What matters is whether players believe the publisher might. A publisher that has announced, tested or merely discussed in public any tokenized item or onchain reward has made that belief more plausible. One that has stated clearly that it takes payment only through its own store has a simpler message for its support and community teams to repeat.

The secondary market side

Where items are traded peer to peer outside the publisher’s control, participants rely on signals to tell official from unofficial: account names, wallet handles and names that look like the franchise. A TLD that matches the franchise, held outside the publisher, can lend an appearance of authenticity in the very market where buyers most want to know that what they are buying is genuine.

Creator and revenue-share arrangements add a further case. Publishers pay creators, tournament partners and licensed sellers, and split revenue with them. Tooling exists that makes names part of that flow. shaka, for example, is an onchain payment router whose payment links can send the payout to a name where a raw address would otherwise go; the parties agree the split and sign it onchain before any funds move, and the router passes funds along without holding them. The point for a publisher is neutral: names are already usable as payment destinations, so the question of who can issue partners.yourbrand is a practical one. If the publisher holds the TLD, it decides. If it does not, someone else does.

Community-run projects that use the franchise name

Fan communities in gaming build things that last. A modding group, a guild network, a fan tournament organizer or an unofficial wiki may take names under a franchise TLD out of affection for the game and with no intention to deceive. That good faith does not change the structure of the problem.

When a community project obtains names under .yourbrand, onchain records are created that can outlive the project. A fan site may close while the names it used go on resolving to whatever they were last pointed at. A guild that organized around guild.yourbrand and then disbanded leaves that name in existence. The UDRP does not apply to these names, since no ICANN-accredited registrar is involved. Whether trademark law or another body of law offers a remedy depends on the facts and on the country, and your own counsel decides that question.

Most publishers already have a position on fan works: what a mod may do, whether a fan tournament may charge entry, how the franchise name may appear on fan sites. That position was written for websites, videos and events. It probably says nothing about names issued under a TLD that matches the title. Reading the fan content policy with that gap in mind is one of the cheapest checks in this guide, and it belongs to the community function, not to legal alone.

There is also a relationship to protect. The community lead knows which fan projects are long-standing partners in all but name and which are unknown. A legal letter sent to a well-liked modding group over a name can cost more goodwill than the name is worth. Before any contact with a community project, legal and community should agree on who speaks, in what tone, and with what offer.

If the publisher later acquires the TLD, it takes on a namespace that may already hold names, the people who use them, and their expectations. The fewer names exist at that point, the simpler the decisions. That is a reason to learn the state of each TLD early. It is not a reason to rush an approach.

Exposure by function, and the ten checks each one owns

Different parts of a publisher meet the same TLD in different ways. The table maps the main functions to the kind of exposure each carries and to the first thing each would notice if a matching TLD were active in other hands.

The table is not exhaustive. A publisher with a merchandise arm, an esports program or a creator fund will find further rows of its own. All of them come back to one fact: the names under the franchise TLD are decided by whoever holds it.

A first-review checklist of ten checks, with owners

The checklist covers the minimum scope of a first review. Each check names the function best placed to own it, so that the list can be handed out as it stands.

1. Map every name in scopeList the studio name, every active franchise title, every dormant title with a living community, the abbreviations players use, and every platform or launcher name. Owner: IP counsel, with brand and product.
2. Check each name on the registryFor each name, confirm whether a matching TLD exists on Freename. The registry record is public and the holding wallet can be seen on a block explorer. Owner: brand protection.
3. Look for names issued under each TLDWhere a TLD exists, look in the community spaces, fan marketplaces and secondary markets your players use for names under it. Owner: community management, reporting to legal.
4. Identify payment usesCheck whether any name under a franchise TLD is presented to players as a place to send funds. A name used for payments ranks above one used only as a display handle. Owner: store and payments, reporting to legal.
5. Review trademark coverageConfirm which names in scope are covered by registered marks, in which classes and countries, and where the gaps are. Owner: IP counsel.
6. Read the fan content policyCheck whether the policy on mods, fan sites and fan events says anything about names under a TLD matching a title, and note the gap if it does not. Owner: community lead, with legal.
7. Rank the names in tiersOrder the names by community activity, payment use and trademark strength. The first tier is the short list on which a decision is needed. Owner: IP counsel, with brand protection.
8. Decide the route for each first-tier nameFor each first-tier name, choose between watching, a documented decision to leave it, and an approach to the holder. No approach is made before the organization has settled its position. Owner: general counsel.
9. Set up monitoringNames can be issued under a TLD at any time, so a single review is a snapshot. Put the names in scope on a standing watch. Owner: brand protection.
10. Plan custody before any acquisitionIf a TLD may be acquired, decide in advance which entity holds the token, in what kind of wallet, who can act on it, and what the naming policy will be. Owner: general counsel, with platform and security.

Two remarks on running the list. Checks one to six can run in parallel, and most need no outside help. Whether the review’s working papers can be kept under legal privilege depends on the country and on who prepares them, so ask your counsel before drafts circulate beyond the legal team.

The options, and who should own the file

Once the scope is mapped and the tiers are set, the organization has a decision to make for each name. The options are not exclusive, and the right one differs from name to name.

Watch. For a name with little community activity, no payment use and a sound trademark position, monitoring without further action can be proportionate. The limit of this option is that it gives the publisher information and no control: names issued in the meantime stay issued. The service that keeps a publisher’s brand names under onchain monitoring is Namespace Watch.

Leave it, on the record. Some names in the catalog will not justify any effort: a title with no community left, or a word so generic that the publisher has no particular claim to it. A short written decision, with the reasons, is better than silence. It shows that the name was considered, and it gives the next reviewer a starting point.

Acquire the TLD by negotiation. Where a TLD matches a core franchise or the studio name, a quiet approach through an intermediary is often the most direct route. Hush Partners acts for organizations that mandate it to find and approach a holder, and the page on brand namespace recovery describes that service. The fee is a fixed amount, charged only to the organization that gives the mandate; a party that answers a note pays the price of the TLD and no fee. Closing runs through onchain escrow on an aftermarket.

Form a view of value before deciding. A publisher will rarely approve an approach without a budget. That view is an internal exercise first: what the title earns, how wallet-active its community is, what the publisher would build under the TLD, and what a continuing absence of control would cost in support and community work. Finance and the franchise lead can supply most of this.

Acquire and build. Acquisition does not have to be purely defensive. What becomes possible once the publisher holds the TLD is the subject of the next section.

Who owns the file

The file should sit with general counsel, or with the head of IP where that role has budget authority. Community, brand protection and the store and payments function all contribute, and each sees the issue first in its own way. The decision to approach a holder, though, combines trademark strategy, budget and confidentiality, and those meet at the level of general counsel.

Two failure modes are specific to this sector. The first is ownership by the community team alone: it sees the issue earliest and knows the fan projects best, but it cannot commit budget or decide a trademark position. The second is ownership by a web3 or innovation team, where one exists: it understands the technology, but its mandate usually covers new products, not the protection of the back catalog. Either team is a valuable contributor. Neither should hold the file.

A practical arrangement is a working group of four: IP counsel in the chair, the community lead, someone from store and payments, and someone from platform or security for custody questions. The page for brands and legal teams sets out how the desk works with this kind of reader.

What holding the TLD would let the publisher do, beyond defense

Acquisition is presented above as a protective step, and for most publishers that is the first reason. It is not the only one. Holding the TLD turns a question about someone else’s names into a decision about your own.

Official payment names. A publisher that holds .yourbrand can issue shop.yourbrand or drops.yourbrand as its own destinations, readable in wallets that resolve them. A name is easier to check by eye than a long address, and the publisher can state in its official channels which names are its own. This helps only the players whose wallets resolve the name; everyone else continues to use the store as before.

Player and creator identity. The publisher can issue names to players, partners and licensed creators inside the franchise namespace. A name such as pro.yourbrand, handed out by the publisher, signals a status that came from the publisher and from nobody else. Tournament winners, long-standing community moderators and partnered creators are the obvious first recipients. How much control the issuer keeps over a name after issuing it depends on the registry’s terms, so settle the naming policy before the first name goes out.

A share of registration fees. Freename operates a royalty program under which a TLD’s holder is paid part of the fee each time a name is registered under that TLD. The share is advertised at up to half, and it depends on the registry’s terms in force and on its activation conditions. Taking part in the program is not free for the publisher: although the TLD itself has no renewal fee, the registry sets an annual cost for the program. Some TLDs were registered under earlier terms that include the program for life, and whether those terms carry over to a buyer should be confirmed with the registry before closing. For a franchise whose fans would want names of their own, that is a modest income line and, more usefully, a view of who is registering what. The free Subname Revenue Calculator on the Hush Partners site estimates revenue from names issued under a TLD, from assumptions you enter.

Licensed and partner names. Since the holder alone can issue names, a publisher that holds the TLD can give a name to each licensed merchandise partner, official tournament organizer and platform integration. A partner’s name then shows at a glance, to anyone who can resolve it, that the partner sits inside the official namespace. Licensing teams can write the grant and the withdrawal of a name into the license itself.

Identities for game agents. ERC-8004, known as “Trustless Agents”, is a draft Ethereum standard, and as a draft it may change. It sets out three registries: one for identity, in which every agent is an ERC-721 token that points to the agent’s card, one for reputation, built from feedback by those the agent worked with, and one for validation, meaning independent checks of its work. The way naming registries connect to it is still being worked out. A publisher experimenting with AI-driven characters, support agents or creator tools may one day want those agents named under the franchise. That is a possibility to note, not a plan to budget for.

None of this is automatic after a transfer. Custody, naming policy and the first names all need decisions, and the service for putting a TLD to work after the transfer is where that begins.

Where to start

Start with the scope map: every name your organization owns that could exist as a TLD, ordered by community size and onchain activity. It takes one meeting between IP counsel, the franchise leads and the community lead. That list is the document you hand to brand protection for the registry check, and to community for the search of fan spaces.

For a first look at a single name, the page on trademark TLDs holds the free Trademark Name Check form. Run the studio name and the two or three titles with the most wallet-active communities, and you will know within the week whether there is a file to open at all.

If the tiers show a name on which your organization wants to act, Hush Partners is reached through the contact form, and by no other channel. From the first note to closing, the publisher’s file stays with a single named partner.

Questions people ask

Does holding a trademark give the publisher a claim over a matching TLD?

A trademark gives rights that are recognized in the countries where it is registered or otherwise protected. The procedures built for the DNS, the UDRP among them, do not apply to onchain names. Whether a trademark supports an enforceable claim against the holder of an onchain TLD, or against the user of a name under it, depends on the facts and on the country. Your own counsel decides. In practice, negotiation is often the more direct path.

What if a large fan community already uses the TLD that matches our franchise?

Then an acquisition is more involved, not impossible. The publisher will have to decide what happens to the names already in use: whether they stay, whether their users receive names under a new policy, and how the change is explained. Those are community decisions as much as legal ones, and they are best settled before closing so that the first public message is the right one.

Is this only relevant for publishers with blockchain games?

No. The exposure depends on the audience’s habits, not on the publisher’s roadmap. A franchise whose players use wallets, even if only for other games or for unrelated purposes, is a franchise whose name can carry meaning in a wallet. A publisher with no onchain product at all can still find its title in use there.

Should a publisher check names for titles that have not been announced?

Checking the public registry record for a name reveals nothing about who is looking, so the check itself is safe. Anything beyond the check is different. An inquiry about an unannounced title, made in the publisher’s own name, discloses the title. For those names, keep the work within the legal team and let any outside contact go through an intermediary bound by confidentiality.