Forget Jerseys: Claim Your Esports Name for Digital Identity and Brand Power

In most sports the jersey carries the identity. In esports it never really did. A player is known by a tag, a team by a name that fits in a bracket, a tournament by a title that fans type into a search bar. The shirt is merchandise. The name is the asset.

That asset usually sits on platforms its owner does not control: a handle on a streaming service, an account on a publisher’s launcher, a username on a social network. Each can be renamed, suspended or lost with the account, and none of them moves with the player to the next team or the next game.

This article looks at a different place to keep an esports name: under .esports, an onchain top-level domain recorded on the Freename registry. It covers what such a name is, what it does in practice for players, teams and organizers, how Freename works underneath, and where the limits are, because there are several and they matter.

Why the name outweighs the jersey in esports

A traditional club owns a crest, a stadium and a century of local history. An esports organization owns far less that is physical. Its roster changes between seasons, its players compete from several countries, and the game it is known for can lose its audience in a few years. What stays is the name people recognize.

The same holds for individuals. A professional player may wear four jerseys in six years. The tag stays the same, and the audience follows the tag. For a streamer or a caster there is no jersey at all: the handle is the whole brand.

This is why disputes in esports so often concern names: who keeps the team name when founders split, whether a player can take a tag to a rival, what happens to a tournament title when the organizer changes. A name that lives only as a row in someone else’s database is a weak basis for any of those answers.

What a name under .esports is

.esports is an onchain top-level domain, or TLD: the part after the last dot, at the same level as .com in the domain name system, but recorded on a blockchain instead of in the DNS. Names are issued under it in the form yourtag.esports or yourteam.esports.

Such a name is a token held in a wallet. Whoever controls the wallet controls the name: which wallet address it points to, which website it opens, which records it carries. There is no account with a platform that can be closed, and no login to lose apart from the wallet itself.

Two levels are involved, and it helps to keep them apart. The TLD, .esports, has one holder, and on Freename only the holder of a TLD can issue names under it. The names beneath it, one per player, team or event, belong to whoever they were issued to. A player who holds yourtag.esports does not depend on a team, a league or a publisher to keep it.

A name is also short enough to say aloud on a broadcast, which a wallet address is not. That is a small point with large consequences for anything involving payments.

How Freename works underneath

Freename is the registry on which .esports is recorded. A registry is the system that says which names exist and who holds them. Freename keeps that record onchain, so the entry for a TLD or for a name can be read by anyone on a block explorer, without asking the registry for permission.

A few properties of the registry shape what a name under .esports can do.

• No renewal on the TLD. A Freename TLD carries no annual renewal fee, which removes the most common way a namespace disappears: someone forgetting to pay.
• Issuance belongs to the TLD holder. Names under a TLD come from its holder, who also sets what a name costs and may price a short or sought-after tag differently from an ordinary one.
• A royalty program. Freename shares part of each registration fee with the holder of the TLD under which a name is registered, advertised at up to half, under the registry’s current terms and activation conditions. Taking part carries an annual cost that the registry sets.
• Two worlds, one company. Freename also operates as an accredited registrar for ordinary DNS domains, so the same organization works on both sides of the line between the DNS and onchain names.

Freename also holds a United States patent, US 12,401,618 B1, filed on February 23, 2024 and granted on August 26, 2025. It describes a method for deciding which name resolves when two naming systems contain the same string, by scoring the competing names, and the earliest date of creation is one of the criteria it weighs. A patent describes a method. It is not a court ruling and it binds nobody outside the software that adopts it. It does show that the registry has thought about what happens when an onchain TLD and a DNS TLD share a string, which is a question worth asking of any namespace you build an identity on.

What a player can do with a name

For a player, the practical uses are few and concrete.

Receive money without reading out an address. Prize splits, coaching fees, sponsor payments and tips all require someone to send funds to the right place. A wallet address is forty-two characters that nobody can check by eye. A name such as yourtag.esports can be typed, read on a stream overlay and verified at a glance. Wallets that support Freename names resolve the name to the address behind it, which is the subject of the page on names that resolve in wallets.

Keep one identity across teams and games. The name does not carry a team prefix and does not belong to a publisher. When the roster changes, the player updates a page, not an identity.

Publish a page that stays put. A name can open a website. Freename’s builder lets a holder assemble pages and publish them to IPFS, a network that stores files by their content, and the site is then reached through the name in browsers that support it. A player can keep results, sponsors and contact details there, independent of any social network. The mechanics are on the page about websites on an onchain TLD.

Show a record others can check. Because the name is a public onchain record, anyone can see when it was created and which wallet holds it. That does not prove who the person is. It does prove continuity: the same wallet has held this name since a given date.

Choosing the tag you register

The name you register should be the one a caster says, not the one a platform forced on you. Years of taken usernames have left most players with a tag that carries a trailing number, an underscore or a doubled letter on at least one service. Under .esports the clean form is often still open, and the clean form is the one worth holding.

A few habits make the choice easier to live with. Register the spelling that appears on the scoreboard, because that is what a fan will type from memory. Avoid characters that look alike, such as a zero in place of the letter O, unless they are truly part of the tag, since a name that has to be spelled out loses its main advantage. Leave the team out of it: a tag with a sponsor or an organization in front of it expires with the contract. And if you compete under one tag and stream under another, decide which one receives money, and publish only that one for payments.

None of this is specific to blockchains. It is the discipline every domain owner learns, applied to a name you carry between employers.

What a team or an organization can do with one

An organization has the same needs at a larger scale, and one more: it has to manage names for people who come and go.

The team name itself is the obvious one. yourteam.esports gives the organization an address for payments, a home for its page and a public record of how long it has held the name. For sponsor invoices or prize money paid in digital assets, a readable name reduces the risk of a mistyped address, and the page on payments to a name describes what works and with which tools.

Payment routing matters more for a team than for a player, because a team’s income is usually shared. A prize is split between players, staff and the organization, a sponsorship between a team and an agency. shaka is an onchain payment router in which a payment link can pay out to a name instead of a raw address, with the split between the parties agreed and signed onchain before any funds move. It routes funds and never holds them.

Then come the names of the people. A team has to decide whether a player’s name belongs to the player or to the team. Under .esports each name is a separate token, so the honest structure is simple: the player holds the player’s tag, the organization holds the organization’s name, and neither depends on the other. An organization that wants names it can reassign, for a roster slot or a role, should hold those in a wallet it controls and say so in the player’s contract.

Tournament organizers and leagues have a third use: an event name that survives a change of sponsor, platform or even game. A circuit that has moved its broadcasts twice knows the value of an address nobody else can redirect.

Sponsors, agencies and creators

The people around a team have a use for a name too. An agency that represents several players is paid from several sources and pays out to several people, and a readable name per player makes its statements easier to check against the public record. A sponsor that funds a prize pool can publish the name the money was sent to, which lets anyone confirm that the payment reached the stated recipient, without the sponsor or the organizer having to be believed.

Content creators sit closest to the player’s case, with one difference: their income arrives in many small payments from many people. A name on an overlay is the plainest way to ask for support in digital assets without putting a long address on screen, provided the audience’s wallets support it. Where they do not, the name still works as a label that leads to a page with the alternatives.

What it costs, and what it does not

Registering a name has a price, set by the holder of the TLD and shown at registration. Beyond that, the running costs are mostly attention: keeping the wallet safe, keeping the records current, and renewing nothing by accident elsewhere because this felt like enough. The cost people forget is the one that never appears on an invoice, which is the time to decide who in the organization answers for the name. A name with no owner inside the team is the first to be pointed at an old wallet, and nobody notices until a payment goes there.

How to claim a name and set it up

The steps are short, and the order matters more than the tools.

1. Decide who holds itA personal tag belongs in the player's own wallet. A team or event name belongs in a wallet the organization controls, ideally one that needs more than one person to approve a change.
2. Check the name everywhereLook for the same tag on the main platforms and in trademark registers. A name that someone else already trades under is a dispute waiting to happen, onchain or not.
3. Register it under .esportsNames are issued by the holder of the TLD, at the price shown at registration. Register the exact spelling you use on broadcast, and the obvious misspelling if it is cheap.
4. Point it at a walletSet the address the name resolves to, then send a small test payment from a wallet that supports Freename names before you publish the name anywhere.
5. Give it a pageEven one page with your results and a contact route is enough. A name that opens nothing looks abandoned.
6. Write down the recovery planRecord who can reach the wallet, where the backup is kept and who takes over if that person leaves. Most lost names are lost here, not onchain.

The fourth step deserves the emphasis. A name printed on an overlay or in a sponsor deck will be used by people who never checked it. Testing it yourself first, from the wallet a fan is most likely to use, costs a few minutes.

Where an onchain name stops

An article that only listed the advantages would be doing you a disservice. The limits are real, and some of them are permanent.

It does not open in an ordinary browser. Onchain names resolve outside the ICANN DNS root, the list of TLDs that every browser and mail server consults by default. Without added support, typing yourteam.esports into a browser leads nowhere. Freename names are supported in Bitcoin.com Wallet, in MetaMask through Freename’s resolver, and in desktop browsers through the Freename Web3 extension. That coverage is partial and it changes. The page on what is live today keeps the current state, with sources.

It is not email, and it is not your main website. Mail still runs on the DNS. So do search engines, ticketing systems and most sponsor tooling. An onchain name sits beside a DNS domain. It does not replace one, and for reach the DNS is simply the better tool.

It is not a trademark. Holding yourteam.esports gives no legal right in the words “your team”. If another organization holds the trademark, the name does not protect you, and the rules that apply differ by country. The reverse is also true: the dispute procedure that trademark owners use for DNS domains, the UDRP, binds registrants in the ICANN system and does not extend to onchain TLDs. A team that cares about its name should register the mark and hold the name, and take advice on the first.

It does not prove who you are. The record shows a wallet, not a person. A fan who sends money to a name is trusting that the name was published by the real player. Publishing it consistently, on the stream, the team page and the event listing, is what makes it trustworthy.

A lost wallet is a lost name. There is no password reset. That is the price of having no platform in the middle, and it is why the recovery plan belongs in the setup, not after the first scare.

What to watch for as an organization

Three questions are worth settling before a team prints its onchain name on anything.

The first is who holds what. Founders’ wallets are where team names go to become disputes. If the organization is a company, the name belongs in a wallet the company controls, and the people with access should be named in a document that survives a departure.

The second is which names matter. A team has a name, an abbreviation, sometimes an academy roster and a content brand. Not all of them need to be held. Those printed on broadcasts and those that receive money do. The Namespace Exposure Score is a quick way to see where an organization stands.

The third is what the same string looks like elsewhere. .esports is one namespace on one registry. A tag can exist under other onchain TLDs and in the DNS, held by other people. That is normal, and it is the reason to publish the full name, suffix included, every time.

A fourth question arrives later, usually at a bad moment: what happens when someone leaves. A departing manager who still controls the wallet behind the team name can do nothing illegal and still cause a week of confusion. The fix is dull and effective. Review access whenever a role changes, move the name to a wallet the remaining people control, and send one small payment afterwards to confirm that it still lands where it should.

For an organization whose own name already exists as a TLD held by someone else, the question is different and belongs on the page about trademark TLDs.

Where this goes next

Two developments are worth following without betting a season on them.

One is software that acts for people. Tournament platforms, payout tools and assistants increasingly need to know which account or agent speaks for a team. ERC-8004, “Trustless Agents”, is a draft Ethereum standard that defines registries for the identity, reputation and validation of AI agents. It is a draft and may change, and how naming registries connect to it is still being worked out. The page on AI agents under a TLD follows it.

The other is the meeting of the DNS and onchain names. ICANN opened a new round of applications for top-level domains in 2026, and its window closed on August 12, 2026. When a string exists both as a DNS TLD and as an onchain TLD, the software in between has to decide which one a user reaches. Nobody can promise how each browser and wallet will answer. What a holder can do is use the name, publicly and continuously, because an identity that is visibly in use is harder to confuse with another.

What to do this week

If you are a player, check whether your tag is free under .esports, register the spelling you actually use, point it at a wallet you control and test one payment. Then put it where people already look for you.

If you run a team or an event, start with an inventory: the names you print, the names that receive money, and who holds the wallet behind each. Decide which the organization must hold itself, write down who has access, and only then publish.

If the name you need is a whole TLD and not a name under one, because you intend to run a namespace for a league, a game community or a region, that is a different undertaking, described on the page for operators. Hush Partners is a private desk for onchain TLDs: it acts for holders who want a buyer and for organizations that want a TLD found and acquired, under a standard mutual NDA, and it is reached through the contact form.

Questions people ask

Is a name under .esports the same as an esports.com address?

No. A DNS domain is rented from a registrar and listed in the system every browser uses. A name under .esports is a token in your wallet, recorded on Freename, and it opens only in software that supports Freename names. Most teams that use one keep their DNS domain too.

Can my team take my name back if I leave?

That depends on which wallet holds it. A name you registered in your own wallet stays with you. A name the organization registered and holds in its own wallet stays with the organization. Agree on this in writing before the name appears on a broadcast.

Does holding the name stop someone else from using my tag?

Not by itself. It stops anyone else from holding that exact name under .esports. It gives no right over the same tag on other platforms or under other TLDs, and it is not a trademark.

What happens to my name if I lose access to my wallet?

The name stays where it is, and nobody can move it, including you. There is no reset. Keep a tested backup of the wallet and, for a team, more than one person who can approve a change.

Do I need to understand blockchains to use one?

You need a wallet, the habit of testing before you publish, and a backup. The rest works much like pointing a domain at a website.