Running a market TLD for gaming communities
For operators considering a TLD that names gaming communities: who would hold a name under it, what they would use it for, and what running it involves.
Gaming communities have a naming problem that is much older than any blockchain. Players carry tags, guilds carry names, teams carry abbreviations, and none of those identifiers belong to the people who built them. They live inside platforms that can rename, ban or delete an account. A tournament organizer has no portable record of the events they have run. A creator’s handle is a lease, not an asset.
A sector TLD, one whose string is a word the gaming world already uses for itself, offers a different model. The operator holds the TLD as an onchain token and issues names under it, and those names can point to a wallet or to content and stay with their holders. This article is for someone considering whether to acquire and run such a TLD: a platform, an association, a publisher, or a founding team that comes out of competitive play. It covers who would register a name, what they would do with it, and what you take on when you run the namespace.
Demand in this sector is real but uneven. Guilds and competitive teams are the strongest case. Casual players are a much weaker one. That distinction matters for your revenue model and for how you present registration to communities.
Who would hold a name and what for
Four groups have a coherent reason to register under a gaming sector TLD. Their needs are different enough that treating them as one audience will produce the wrong product.
| Holder type | Primary use | Secondary use | Demand strength |
|---|---|---|---|
| Guild or clan | Shared wallet address for treasury | Public identity of the group | Strong |
| Competitive team | Portable team identity across tournaments | Payout destination | Strong |
| Content creator | Readable address for contributions | Profile pointer | Moderate |
| Tournament organizer | Stable identity for the event series | Address for the prize fund | Moderate |
Guilds and clans are the anchor case. A guild that manages a shared treasury (collecting entry fees, distributing earnings, holding digital items collectively) needs a human-readable address that every member can check and share. A name in the form name.yoursector is easier to communicate than a long string of letters and digits, and unlike a username on a platform it does not live inside that platform’s account system. The name sits with whoever holds it in their wallet.
Competitive teams operate at higher stakes. They enter tournaments under a tag, receive prize payouts to a wallet, and need both to be consistent over time. A team name under a sector TLD can serve as the standing payout address for the roster. That lowers the risk of an organizer sending funds to a stale address because a player left and took a personal wallet with them.
Content creators in gaming communities (streamers, coaches, match analysts) have a lighter but genuine use. Fans who want to send a contribution can use a name rather than a raw address. The name also works as a profile pointer: one string the creator keeps while the wallet behind it changes, wherever the name is supported.
Tournament organizers are a smaller segment with larger sums passing through it. An organizer who runs regular events wants an identity that outlasts any one platform and a public address for prize funds that participants can recognize from one event to the next. Do not expect many names from this group. Expect a few that matter, because each organizer brings teams with it.
The weak case deserves a plain statement. A casual player who never receives a payout, never joins a structured guild and never sends funds to anyone has little to do with a name. If your plan depends on that player registering in large numbers, the plan is fragile.
What a name actually does for each of them
A name under a sector TLD is an onchain record that can carry data: a wallet address, a pointer to a website. What matters for this sector is which of those capabilities work in practice, and where the limits are.
Wallet resolution is the most immediately useful function. A name resolves to a wallet address in software that supports it. For a guild or team name issued on Freename, that software is Bitcoin.com Wallet, MetaMask through Freename’s resolver, and desktop browsers through the Freename Web3 extension. Coverage is partial and it changes: a name does not resolve in every wallet or every browser. Tell your registrants this plainly, and point them to the list of capabilities that are live rather than promising universal resolution that does not exist.
Payment routing is where the practical value concentrates. With shaka, an onchain payment router, a payment link can pay out to a name instead of a raw address, and the split between the parties is agreed and signed onchain before any funds move. For a tournament organizer who has to divide a prize among the members of a roster in agreed proportions, that replaces a spreadsheet of addresses collected by chat. The router routes funds and does not hold them. The page on payments to a name covers this capability in more detail.
Web publishing under a name is possible. Freename’s website builder lets a holder build pages and publish them to IPFS, a peer-to-peer network for storing files, and the site is then reached through the holder’s name in browsers that support it. For most guilds this is a secondary concern. A roster page or a rules page under the guild’s name is pleasant to have, but the audience that can open it is limited to people whose browser resolves the name. The wallet use is the one a guild feels first.
Automated accounts are a further use for a technically minded guild. A bot that collects entry fees or handles routine treasury tasks can operate under its own name rather than a raw address, which makes its role legible to members. Treat this as an optional extra, not a reason to acquire the TLD.
Tags, status and membership: players who already carry a name
The tag convention players already follow
Every player who has competed in an organized event already has an identity structure: a personal handle, and a team tag worn as a short prefix or suffix to show affiliation. The two are read together. Anyone in a structured guild understands at a glance that the tag says who you play for and the handle says who you are.
This matters for how you present registration. You are not teaching a new convention. You are giving an existing one an onchain form. In a sector namespace the guild holds one name and each player holds another, both in the form name.yoursector. A player who registers the handle the community already knows them by now has a wallet identity that anyone can type, without asking which wallet the player uses.
The tag itself needs a decision from you. A namespace offers two levels, the TLD and a name under it, so a player’s name cannot sit beneath the guild’s name. You can let players fold the tag into the name they register, or keep player names free of tags and let each guild publish its roster on its own page. The first option mirrors what players see on a scoreboard but breaks every time a player changes team. The second keeps a player’s name stable across a whole career. For most operators the second is easier to run, because transfers between teams are frequent in this sector and a name that must change at every transfer is a name nobody trusts as a payout address.
The limitation is that a game client does not resolve your TLD. The name lives outside the ICANN DNS root and outside the game’s own identity system. It is a parallel identity layer, not a replacement for the in-game handle. Operators who oversell integration will create support work for themselves. Operators who present the name as a portable wallet identity that matches an existing handle will find the idea is accepted more easily.
Names as status and as membership
In competitive gaming, the team you play for is more than an affiliation. It is a credential. A sector namespace can carry part of that credential if you design issuance for it.
The simplest version is at the guild level. If you issue guild names only after checking that the applicant speaks for the guild, then holding a guild name in your namespace says something: this group exists, someone accountable registered it, and the operator looked before issuing. A tournament organizer can then use the namespace as a first filter for a guild category, by asking each entrant for its name under .yoursector and looking it up.
Player membership is harder to express, because a name issued to a player sits with the player. A guild’s own roster, published under the guild’s name and kept current by its leaders, is a more honest membership record than a name that outlives the membership. Design for that: the guild’s name is the anchor, and the roster is what the guild says it is.
The status dimension is real but easy to overstate. Names carry social weight when the community assigns weight to them. If serious guilds register in your namespace, a name there signals seriousness. If the namespace fills with low-effort registrations, it loses that signal, and the guilds you most wanted will not bother. Deciding who gets a guild name, and under which rules, is part of what you are managing. It is also the one lever in this sector that no pricing decision can replace.
Tournaments, prizes and payouts
Tournament operations are a high-friction setting for onchain payments. Prize pools are split across several recipients, addresses change as rosters change, and a misdirected transfer is hard to reverse. A sector namespace can reduce that friction at two points.
First, the team’s name becomes the payout destination, in place of an individual wallet. The organizer sends to the team’s name under .yoursector, not to a raw address supplied by whoever answered the last message. The team controls the wallet the name points to and can update it without the organizer needing to know.
Second, a payment router lets the prize split be defined and signed before funds move. A split agreed before the final is then an onchain record and no longer a verbal arrangement. This does not remove disputes. It does remove the kind of dispute that begins with one player remembering a different share than another.
There is a governance question inside the first point. A name that receives prize money should not point to a wallet that one person can empty. Encourage teams to place the name on a multisignature wallet, a wallet that needs several holders to approve a transfer, so that the payout destination survives the departure of any one member. You cannot impose this, but you can make it the documented practice for team names and say so in your onboarding material.
You may be tempted to issue a separate name for each event or each season. Resist it. Event names multiply quickly, go stale after the final, and leave you with a namespace full of dead entries. A cleaner structure is one name per team and one per organizer, with each managing its own payout arrangements. You run the namespace. You are not the tournament software.
Be honest with organizers about what the namespace does not solve. It does not confirm that a team is eligible, that a result is valid, or that the prize fund exists. It gives the payout a stable, readable destination and gives the split a record. Those are narrow gains, and they are the ones you can deliver.
Moderation: what happens when a name is abused
Moderation in a gaming namespace has a different character from a corporate one. The disputes you are most likely to face are: a former member who keeps a name tied to a guild after leaving; two guilds that share a name or an abbreviation; a name registered to pass as a well-known team; and a name used to collect funds in a scam.
Roster disputes will be the most frequent. On Freename, only the holder of a TLD can issue names under it, so issuance is yours to control. What happens to a name after it has been issued is a different matter: confirm with the registry what an operator can and cannot do to an issued name before you write your rules, and do not promise a remedy you cannot carry out. Your registration terms should say from the outset which names are tied to a role (a guild name is held for the guild, not for the person who registered it) and what the process is when that role ends.
Shared names are the gaming-specific problem. Guild names repeat across games and regions, and abbreviations repeat even more. Two groups can each have an honest claim to the same string. Decide in advance how you settle that: first to register, longest documented use, or a split by game or region written into the name. Whichever rule you pick, publish it. A rule that players can read before they apply produces fewer disputes than a wise decision made case by case.
Impersonation is harder. If someone registers the name of a known guild to pass as it, you need a process that moves quickly. The UDRP (the Uniform Domain-Name Dispute-Resolution Policy) binds registrants of domains in the ICANN system and does not apply to your namespace. You make the policy for your own TLD. Build a fast track for clear impersonation and fraud cases, with response times you can keep, before you open registration.
Trademark claims will arrive. A team name used in commerce over a long period may have trademark rights behind it, and those rights vary by country. Your terms should require registrants to state that they have the right to use the name they register, and your dispute process should let a rights holder file a complaint with supporting evidence. This is information, not legal advice: your own counsel decides how the terms are drafted.
The operator’s role: rules, issuance, support, disputes
Running a namespace is not passive. Freename runs a royalty program that gives the holder of a TLD a share of each registration fee for names registered under it, advertised at up to half and subject to the registry’s current terms and activation conditions. That is the financial return. The operational work is what determines whether the namespace keeps its value.
Rules means registration terms that every registrant accepts, covering acceptable use, what the operator may do when a name is abused, the dispute process, and the limits of your liability for what holders do with their names. This is a legal document. It should be drafted by counsel who understands both your jurisdiction and the onchain mechanics.
Issuance means deciding whether registration is open (anyone can register any available name) or curated (you approve each registration). For a gaming namespace a hybrid often works better: open registration for individual player handles, curated registration for guild, team and organizer names. Curated issuance takes more time but reduces the moderation load later. It also requires you to hold back the names of well-known groups until the right applicant appears, which means saying no to early money.
Support means a channel where registrants ask questions and report problems. Expect modest volume in the first year. Expect two recurring cases: a name that does not resolve in a particular wallet, and a name still held by someone who has left a guild. Both need a human answer, and the first needs an answer that does not blame the registrant.
Disputes means the process described in the previous section. Write it down before the first dispute arrives. The page for operators who run a market TLD sets out what running a namespace involves.
One point is specific to this sector. Gaming communities are vocal and well connected, and a moderation decision will be discussed in public within hours. Decide in advance who speaks for the namespace, publish your decisions in a consistent form, and never argue a case in a community channel.
Revenue from names, modelled honestly
The share an operator receives and the conditions for receiving it are set by Freename’s current terms. Verify them before you model revenue.
Consider a worked example. Every figure in it is an assumption, not a forecast. The registration fee for a name is USD 20. The royalty share is at the advertised maximum, half of the fee, so USD 10 per registration reaches the operator. The TLD records 400 registrations in its first year: 180 from guilds and clans, 120 from competitive teams, 60 from content creators and 40 from tournament organizers. Renewals and resale are left out.
On those assumptions, first-year royalty revenue is 400 registrations multiplied by USD 10, which is USD 4,000. That is a modest number. It does not pay for a full-time operator. It does not cover the legal work on the registration terms. It does not cover the price of the TLD. It is also stated before the royalty program’s own annual cost, which the registry sets and which has to be deducted from the USD 4,000, even though the TLD itself has no annual renewal fee. Some TLDs were registered under earlier terms that include the program for life, and whether a buyer inherits those terms is a question to confirm with the registry before closing.
Worked example only. Assumes a USD 20 registration fee, a royalty share of half and 400 registrations in the first year. No renewal or resale revenue included.
At this scale, royalties are a secondary return. The primary one is what the namespace does for an organization that already operates in the sector: the ability to give your community names, a public view of which groups register, and whatever the TLD itself is worth if the namespace grows. An operator with no existing community has only the royalty line, and on these assumptions that line does not carry the project.
The split in the example follows the demand assessment at the start of this article. Guilds and teams bring the volume. Creators and organizers add names at lower density. If you have a relationship with a league or an association that encourages its member guilds to register, the guild line could be much higher. If your access is mainly to individual players, lower every line. Use the subname revenue calculator to test your own assumptions, and do not present its output as a forecast.
What to check before acquiring the TLD
Before you commit to acquiring a sector TLD, six questions need clear answers.
Does the string conflict with a trademark? A word the gaming world uses generically can still be a registered mark for games or entertainment services in some countries. Have a trademark search run across the jurisdictions where you operate before you proceed. The page on trademark TLDs holds a free name check.
Who holds the string? A TLD that exists onchain is a token held in a wallet. The registry record is public, and you can look it up on a block explorer. If the holder has to be found and approached, buy-side acquisition is the service in which an organization mandates the desk to do that.
Which registry does it sit on? Freename is the reference case in this article, but other registries exist. Resolution support, royalty arrangements and transfer mechanics differ between them. Confirm the technical basis before you put a value on the asset.
What is the TLD worth to you? For a gaming sector word, the answer depends less on the string than on the community you can bring to it. The same TLD is worth more to a league with member guilds than to a newcomer. Read how a TLD valuation is built and do not negotiate from a seller’s number alone.
Is the word the one players use? Gaming vocabulary shifts by genre and by generation. A word that competitive players use for themselves is worth more than a word outsiders use for them. Ask the guild leaders you know which word they would be glad to carry after their name. Their answer is better evidence than any keyword list.
Do you have the moderation capacity? If you are a small team, curated issuance with a slow rollout is safer than open registration with a fast launch. A small namespace of well-managed names is a better asset than a large one with an unresolved impersonation dispute being discussed on every community forum.
A realistic first year
- Checks and acquisitionComplete the trademark search, the valuation and the review of the registry record. Mandate an adviser if the holder needs to be approached. Closing runs through onchain escrow and transfer.
- Legal and policy foundationDraft the registration terms, the acceptable use policy and the dispute process with counsel. These documents govern every name you issue, so do not open registration without them. This work can run alongside the acquisition.
- Technical setup and testingActivate the TLD under the registry's terms, including the royalty program. Test resolution in each supported wallet and browser before you announce anything, and write down what does not work.
- Quiet start with anchor registrantsInvite a handful of guilds or teams you know directly to register first. Use their experience to find friction in registration and resolution. Do not publicize the namespace until this group is satisfied.
- Public registration with a curated guild trackOpen registration for individual player handles. Run an application track for guild, team and organizer names. Announce through the communities where your anchor registrants are active, not through general press.
- Moderation and support routineReview reported disputes and support requests at a fixed interval. In the first year this is likely a part-time task for one person. Document every decision so that your policies develop consistently.
- Year-end reviewCount the names in use, the disputes and the support load. Redo the revenue model with real figures. Decide whether to widen curation, change the rollout or seek integrations with tournament tools.
The first year will not look exactly like this. The acquisition may take longer. A dispute may arrive before you expected it. A league you had not contacted may ask to register its members in bulk. The steps are a planning frame, not a guarantee.
The most important thing in the first year is not the number of registrations. It is the reputation of the namespace. A gaming community adopts a naming convention when credible, respected participants already use it. If the first names go to guilds the community recognizes, later registrations follow from that credibility. If the first names go to anyone who pays, you are competing on price with every other namespace, and that is a poor position to hold.
Plan the first tournament season as the real test. A namespace proves itself the first time an organizer pays a prize to a team’s name and the split reaches every player without a correction. Arrange that event deliberately with an organizer among your anchor registrants, and write up what happened, including what went wrong. One documented payout is worth more to the next guild leader than any description of what a name could do.
Starting the process
Start with the community, not the TLD. List the guilds, teams and organizers you could invite in the first quarter and ask a few of them whether they would use a name as a payout address. If the answers are lukewarm, you have learned what you needed before spending anything.
If the answers are good and you have identified a sector TLD that fits, two pieces of work come next: establishing what the TLD is worth and, where needed, approaching its holder. Hush Partners is a private desk for onchain TLDs that acts for organizations on exactly that kind of file. A mutual NDA in standard form applies to every exchange, a single named partner stays with the file from the first note until closing, and closing takes place through onchain escrow on an aftermarket. The desk’s fee is a fixed amount, not a percentage, and only the client who mandates the desk pays it.
Once the TLD is yours, the activation roadmap tool builds a launch plan you can adapt to the first-year steps above, and post-transfer activation is the service for putting a TLD to work after the transfer. A guild, league or platform reaches the desk through the contact form on the site.
Questions people ask
Can the operator take back a name after it has been issued?
That depends on your registration terms and on the mechanics of the registry, and you need both. The terms should state the conditions under which a name can be withdrawn (a finding of abuse, or the end of the role the name was issued for) and the process you follow. The registry determines what you can actually do to an issued name. Confirm that with the registry first, then have counsel draft terms that promise no more than the mechanics allow.
Do onchain names resolve in game clients?
No. Onchain names resolve outside the ICANN DNS root and are not visible in a game’s own naming system. They work as wallet identities and, where a browser supports them, as addresses for a site. They do not replace in-game usernames or appear on in-game leaderboards unless a game publisher builds that integration. Describe this accurately to registrants.
What should registrants be told about resolution?
That it is partial and that it changes. A name works in the wallets and browsers that support the registry, and nowhere else. A registrant who expects to type a name into any browser will be disappointed, and the disappointment lands on you. Publish a short, current list of where names under your TLD resolve, and update it when support changes.
Is a sector TLD or a brand TLD the better fit for a gaming organization?
It depends on what you want. A TLD that matches your organization’s name, such as .yourbrand, is mainly for your own use: your teams, your events, your payment names. A sector TLD such as .yoursector exists to issue names to third parties, which brings royalty income and also the duties of running a public namespace. An organization with one strong team may want the first. A league or a platform that serves many groups is the natural operator of the second.
