# A market TLD in operation: reading the .esports registry

> What a running market TLD publishes, read page by page on the .esports registry: rules, reserved names, proof, limits, payments and guides.

Source: https://hush.partners/a-market-tld-in-operation-reading-the-esports-registry
Category: Acquiring
Published by Hush Partners.

---
Almost everything written about market TLDs uses a placeholder. A sector word becomes `.yoursector`, a member becomes `name.yoursector`, and the reader is asked to imagine the rest. That is the right way to explain a model. It is a poor way to judge whether the model survives contact with real members, real disputes and real money.

This article does the opposite. It takes one market TLD that operates in public, .esports, and reads what its registry publishes at esports.name, page by page, the way an operator, a buyer or a general counsel should read any registry. Each section says what a published element is, what job it does for the member, and what an operator of another TLD should take from it.

One thing has to be said first. Esports Name is a registry by Hush Partners, and business, trademark and brand questions about .esports names come to this desk. That is why it can be described here in detail: it publishes itself, and nothing below reveals anything about a client, a counterparty or a file. Every statement about the registry in this article comes from its own public pages, and can be checked there.

<figure class="keyfacts">
<div class="keyfacts-grid">
<div><b>Once</b><span>a .esports name is paid for one time, with no renewal</span></div>
<div><b>7</b><span>kinds of professional names held back from sale</span></div>
<div><b>4</b><span>things the registry states it will not do</span></div>
</div>
<p class="fig-src">Counted on the public pages and the policy of the .esports registry at esports.name.</p>
</figure>

## What a member reads on the first screen

A registry has a few seconds to answer three questions: what is this, who is it for, and what does it cost me over time. The .esports registry answers all three before the reader scrolls. It presents itself as the official registry of .esports names. It says the names are for players, teams, coaches and organizers. And it states the terms of holding one in plain words: paid once, no renewal, held in your own wallet.

Notice what is missing. The first screen does not explain what a blockchain is, what a token is, or why an onchain TLD differs from a domain in the DNS. A member who plays under a handle does not need that lesson to decide whether the handle is worth holding. The registry describes the name by what it does for the person: the name you play, cast, coach or organize under.

For an operator, this is the first test of a registry page. If the opening screen needs a glossary, the sector has not been addressed yet. The technology is true and it matters, and it belongs further down, for the reader who asks. The promise at the top has to be written in the vocabulary of the sector, because that is the vocabulary in which a member decides.

The first screen also avoids a number. It does not print a price. It says that the check shows whether a name is free and what it costs. That is a deliberate choice an operator can make, because the holder of a TLD sets the price of the names under it and can price names differently. A registry that prints one figure has decided that every name is worth the same. This one has not.

## Three steps, and what each one leaves to the member

The registry reduces the whole process to three steps. They are worth reading closely, because each one hands a responsibility to the member, and says so.

<figure class="fig">
<figcaption><b>How a .esports name is taken, as the registry describes it</b></figcaption>
<ol class="fig-steps">
<li><b>Check the name</b>The member searches for the name they go by. The check answers whether it is free and what it costs. Names reserved for professionals cannot be bought this way.</li>
<li><b>Pay once, from your own wallet</b>There is one payment and no yearly fee. The name is created onchain and sent to the wallet that paid.</li>
<li><b>Use it</b>The registry names three uses: a profile, payouts and a jersey. A name can carry a wallet address, so money sent to the name reaches its holder.</li>
</ol>
</figure>

The second step carries the weight. Paying from your own wallet means the member already has one, or creates one first. The registry does not pretend otherwise, and it publishes a guide for members who are setting up a wallet for the first time. An operator who hides this step loses the member at the worst moment, in the middle of a payment.

The same step sets a boundary that returns later in the policy. Once the name sits in the member's wallet, it is the member's to keep and the member's to lose. The registry does not hold it for them. That sentence is uncomfortable to publish, and it is the most useful one on the page, because it tells the member where the registry's help ends before they need it.

The third step is the reason the first two are worth the effort. A name with nothing to do is a collectible. A name that appears on a profile, receives a payout and can be printed on a jersey has three reasons to exist, and each one is something the sector already does every week.

## The reserved list, applied in public

Every market TLD has names that should never be sold to the first person who asks. In a sector with public figures, those names are the public figures themselves. The .esports registry deals with this before the question arises. Its policy reserves the names of professional players, teams, coaches, organizations, tournaments, leagues and games. It says these names are not for sale, and that they are kept for their rightful holders.

Three things about this are worth copying.

First, the list is defined by category, in writing, where a member can read it. A reserved list that exists only in a spreadsheet protects nothing until someone tests it. A list announced in the policy tells the whole sector how the registry will behave, including the people who were hoping it would behave differently.

Second, the registry gives up revenue on purpose. The names it holds back are the ones a stranger would pay most for. Declining that money is what makes the rest of the namespace credible. A team that finds its own name already taken by someone else under a sector TLD does not register a second choice. It leaves, and it tells the other teams.

Third, the rule is the same for everyone. Nothing in the policy says that a reserved name can be had for a higher price. If it could, the list would be a price list. An operator who wants premium pricing for generic words can have it, since pricing under a TLD is the holder's to set. Names that belong to identifiable people and organizations are a different family, and this registry keeps the two apart.

This design has a cost, and the registry accepts it. A reserved list has to be kept up. New teams form, players turn professional, tournaments appear, and each one is a name that was not on the list the day before. A list that was right at launch and never revisited protects the sector as it used to be.

The page for [operators](/operators) describes what running a namespace involves, and the reserved list is the first decision on that road.

## Releasing a reserved name: what counts as proof

A reserved list needs a way out, or the names it protects never reach the people it protects them for. The .esports registry publishes that route. A professional submits a request with the name they are asking for, an optional team or organization, and a link to an official profile or website. The registry then answers by email, and the reply that counts has to come from an address tied to the holder.

| Evidence | Accepted | Why |
| --- | --- | --- |
| Reply from the team's or organization's own domain | Yes | Only the organization controls it |
| Reply from the agency that represents the person | Yes | The agency answers for its client |
| Reply from the address shown on the official profile | Yes | The profile already vouches for it |
| A screenshot or a forwarded message | No | Anyone can produce one |

The table is the policy in four lines, and its last line is the important one. A screenshot proves that someone can take a screenshot. By refusing it in writing, the registry removes the most common argument before it starts. Nobody can say they were not told.

The check itself is modest. It does not ask for an identity document and it does not claim to verify a person in any legal sense. It relies on something the sector already maintains: official domains, agencies and public profiles. A registry does not have to invent an identity system when the sector has one that people already trust.

Release terms are set case by case, and the registry says so. That honesty matters too. A fixed public tariff for reserved names would invite the very speculation the list exists to prevent. Once released, the name goes to the holder's wallet, or is kept for them until they have one.

If you run a different sector, the equivalent question is simple. Which addresses, registers or profiles does your sector already treat as official? Your proof rule should rest on those, and name what it will not accept.

## What the registry says it will not do

Most product pages list what the product does. The policy of the .esports registry also lists what the registry does not do. There are four items, and each one closes a misunderstanding that would otherwise become a support request or a dispute.

| The registry does not | What that means for a member |
| --- | --- |
| Hold a name once it is in your wallet | Custody is yours from the moment of payment |
| Recover a name if you lose access to the wallet | Keep the wallet safe and plan for loss |
| Publish esports news, results or transfers | The registry is not a media outlet |
| Accept card payments | Payment comes from a wallet, as the steps say |

The first two lines are the same fact seen from two sides. A name issued onchain is a token in a wallet, and whoever controls the wallet controls the name. That is the property that makes the name the member's own. It is also the property that makes loss permanent. A registry that advertises the first half and stays silent on the second has not been dishonest, exactly. It has left the member to discover the second half alone.

The third line protects the registry's role. A sector registry that also reports on the sector will sooner or later write about one of its own members. Staying out of news keeps the registry a neutral record of who holds which name.

The fourth line is the one a marketing team would cut. It costs conversions. It also means that no member starts a purchase expecting a card form and abandons it in confusion. Stating a limit early is cheaper than explaining it late.

An operator drafting a policy should write this list before the feature list. If you cannot name four things your registry will not do, you have not yet decided what it is.

## Impersonation and the single official channel

A name that reads like a known player is an obvious tool for someone pretending to be that player. The reserved list handles the names the registry could foresee. The policy handles the rest with a reporting route and a statement of what the registry can and cannot do about it.

The route is short. Someone who finds a name being used to pass as them writes to the registry with the name and a link to their official profile. The registry's answer is bounded by how the system works. Ownership onchain is a public record, so the registry can show which wallet holds a name. It cannot take a name out of that wallet.

<aside class="callout">
<span class="callout-label">For legal teams</span>
<h4>A registry can show who holds a name. It cannot undo the holding.</h4>
<p>Read a registry's policy for this sentence before you rely on it. What the registry can do after the fact is limited, so the protection that counts is the one applied before a name is issued: the reserved list and the proof rule.</p>
</aside>

This is the honest version of a limit that every onchain registry shares. It is also the strongest argument for a reserved list. Prevention is the only remedy that the technology fully supports, so the registry spends its effort there.

The policy adds one more protection, and it costs nothing. It states where the registry exists: one website, the addresses that website provides, and a single named social account. It says that any other account using the name is not the registry. For a sector where impersonators copy logos within hours, a written list of official channels gives members a test they can apply without asking anyone. It also tells them where policy changes will appear, which in this case is the registry's own news section.

If your organization's name is the one at risk under some other TLD, the page on [trademark TLDs](/trademark-tlds) holds a free name check, and the answer is given privately.

## Prize money paid to a name

The use the registry puts first is payment. In esports, money moves to groups: a prize goes to a roster, a sponsor fee to an organization and its players, a tournament fee to an organizer and its crew. The usual method is a list of wallet addresses collected by message, and one wrong character sends a share to nobody.

The registry points its members to [bulbea](https://bulbea.org), an onchain payment router, for exactly this case. A payment link can pay out to a name, and the split between the parties is agreed and signed onchain before any funds move. The router routes the payment and does not hold it.

A worked example shows what changes. Assume a prize of USD 100,000 won by a roster of five players, a coach and the organization behind them. Assume the parties agree that the organization receives 20 percent, each player 15 percent and the coach 5 percent. Those shares add up to 100 percent.

<figure class="fig">
<figcaption><b>One prize, seven payees</b><span>Worked example, for a prize of USD 100,000</span></figcaption>
<div class="fig-bars">
<div><span>Organization (20 percent)</span><i style="width:100%"></i><b>USD 20,000</b></div>
<div><span>Each of five players (15 percent)</span><i style="width:75%"></i><b>USD 15,000</b></div>
<div><span>Coach (5 percent)</span><i style="width:25%"></i><b>USD 5,000</b></div>
</div>
<p class="fig-src">Worked example only. The shares are assumptions, not a recommendation, and no fee of any kind is included.</p>
</figure>

With names, the organizer pays one link. The organization's share goes to the organization's name, each player's share to that player's name, and the coach's share to the coach's name. Each of the seven read and agreed their own share before the organizer paid. Nobody forwards money to anybody afterwards, and nobody waits on a treasurer.

Two limits belong next to this picture. The split is only as good as the agreement behind it, so the conversation about shares still has to happen. And a name is only as trustworthy as its issuer's rules, which is the reason the reserved list and the proof rule come first in this article. The page on [payments to a name](/onchain-tld-payments) covers the capability in detail.

## Guides written by seat, not by feature

A registry page sells nothing to a reader who cannot see themselves in it. The .esports registry carries more than sixty guides, and the way they are organized says more than their number. One set is written by seat. There is a guide for players, one for teams, one for organizations, one for coaches and staff, one for casters and talent, one for creators and streamers, one for agents and agencies, one for sponsors and brands, and one for tournament organizers. That is nine audiences, each addressed in its own terms.

A second set follows the titles people compete in, with a guide per game. A third follows situations: a player who changes team, a team that rebrands, a roster that disbands, two players who share the same handle, a name after retirement, a wallet that is lost.

The third set is the instructive one. Each of those guides answers a question a member will ask on a bad day. Who owns the name when a team disbands. What moves with a player and what stays. What happens to a name when access to the wallet is gone. A registry that publishes those answers before the bad day arrives has done part of its support in advance, and in public, where the answer binds the registry as much as it informs the member.

For an operator planning a launch, this is the part most often left for later. The policy is written, the reserved list is loaded, and the content is postponed. On this registry the content is the bulk of the site. The [launch roadmap](/activation-roadmap) tool builds a plan in which that work has a place in the first ninety days.

## Where a .esports name works, and where it does not

No description of a registry is complete without its edges. An onchain name resolves outside the ICANN DNS, so an ordinary browser does not open it without support. That is true of .esports as of any onchain TLD.

For names issued on Freename, the registry on which .esports runs, resolution works in Bitcoin.com Wallet, in MetaMask through Freename's resolver, and in desktop browsers through the Freename Web3 extension. Coverage is partial and it changes. A member who expects a .esports name to open in every browser on every phone will be disappointed, and a registry that lets them expect it will lose them.

This shapes what the registry puts forward. It leads with uses that do not depend on a browser: a handle shown on a profile, a destination for a payout, a name on a jersey. Those work wherever the name is read by a person or by a wallet that supports it. A website on the name is possible and it is not the headline, because it is the use that depends most on software the member does not control.

There is a second edge, and it concerns the sector more than the software. A name under .esports identifies whoever holds it in a wallet. It does not, by itself, tell a tournament organizer that the holder is the player they have in mind. The registry narrows that gap for professionals through the reserved list and the proof rule. For every other name, ordinary care applies: confirm a payout name with the person, through a channel you already trust, before the first payment.

An operator should make the same choice with open eyes. Lead with the uses that work for your members now, state where resolution stops, and point to [the list of capabilities that are live](/whats-live) so that nobody has to take your word for it. For ordinary web addresses and for email, the DNS remains the tool, and saying so costs a registry nothing.

## Reading any registry with the same six questions

The value of a live example is the grid it leaves behind. The six questions below can be put to any registry, whether you are thinking of acquiring the TLD behind it, running one of your own, or judging one that carries a name close to yours.

<figure class="fig">
<figcaption><b>Six questions for any registry</b></figcaption>
<ol class="fig-steps">
<li><b>What does the first screen promise</b>Who the names are for, and what holding one costs over time, in the vocabulary of the sector.</li>
<li><b>Which names are held back</b>The categories reserved, stated in a policy a member can read, and whether any of them can simply be bought.</li>
<li><b>What counts as proof</b>The evidence accepted to release a reserved name, and the evidence refused.</li>
<li><b>What will the registry not do</b>Custody, recovery and payment limits, stated before a member pays.</li>
<li><b>Where is it official</b>The channels the registry recognizes as its own, and where a change of policy is announced.</li>
<li><b>What is the name for</b>The uses that work for a member now, and the limits of resolution.</li>
</ol>
</figure>

A registry that answers all six in public is one you can assess from the outside. A registry that answers none is asking for trust it has not yet earned, and a TLD in that state is a different asset from one that has done the work. If you hold a TLD and want to see how it reads to a buyer, the [TLD Readiness Score](/tld-readiness-score) asks a related set of questions.

If you are an organization looking at a sector word, the sequence is the reverse of the one in this article. You find out who holds the TLD, you acquire it, and then you build what .esports shows. [Buy-side acquisition](/buy-side-acquisition) is the service in which an organization mandates Hush Partners to find and approach a holder, and [post-transfer activation](/post-transfer-activation) covers the policy, the reserved list and the first names after the transfer. The page on [a market TLD in operation](/esports-tld) shows the registry itself, with a link to it.

## Questions people ask

### Who runs the .esports registry?

Esports Name, at esports.name, a registry by Hush Partners. Names are checked, paid for and released on the registry, and business, trademark and brand questions about .esports names are handled by the desk.

### Can anyone buy the name of a professional team under .esports?

No. The registry's policy reserves the names of professional players, teams, coaches, organizations, tournaments, leagues and games, and states that they are not for sale. A reserved name is released to its rightful holder after a check by email.

### What happens if a member loses access to the wallet that holds a name?

The registry states that it cannot recover a name in that case. The name is a token in the member's wallet, so the safety of the wallet is the member's responsibility, and the registry publishes guidance on keeping a name safe.

### Does a market TLD need all of this before it launches?

The policy, the reserved list and the proof rule should exist before the first name is issued, because a name issued to the wrong party stays with that party. Guides can grow after launch, starting with the situations that produce disputes.
