One .esports Name, One Payment, Every Party Paid

A sponsorship clears. Prize money lands. A tournament pays out. And then the least glamorous part of competitive gaming begins: working out who gets what, moving it between accounts, and hoping every wallet string survived the copy and paste. For a sector that settles everything else in milliseconds — a clutch, a flick, a round — the money still moves like it is 2009.

It does not have to. When an identity and a payment address are the same thing, the money can arrive already knowing how to divide itself. That is what a .esports name does when it is resolved by an onchain payment router. One name in the payer's hands. One payment. Every party paid at the same instant, in the same transaction, at the shares agreed in advance.

This article explains how that works — what the .esports name actually is, why it is powered by Freename, how Shaka resolves it into a payment, and what it looks like in practice when a roster, an agent, and an organisation all need to be paid out of a single incoming amount.

The 42-Character Problem

For years, getting paid onchain meant handing someone a wallet address: a forty-two-character string of letters and numbers that means nothing to a human eye. You cannot read it. You cannot remember it. You cannot glance at it and know it is correct. You copy it, you paste it, and you pray that nothing went wrong in between.

That string was never the future. It was a placeholder that leaked up out of the plumbing and into the interface because there was nothing better to put there. And it carries a specific, well-documented risk: the swapped-address attack, where a lookalike string is substituted at the moment of payment and the money goes to the wrong place — final, gone, unrecoverable. The address is unreadable, so the substitution is invisible. The whole failure mode exists because humans were asked to handle machine identifiers.

In esports the problem compounds, because the people getting paid are often young, often paid across borders, and often paid in groups. A single roster might have five players in four countries. A single sponsorship might owe the player, the agent who made the introduction, and the platform that hosted the deal. Every one of those recipients is another address, another copy, another chance for a digit to go wrong. The complexity does not scale linearly. It scales with the number of parties, and esports deals almost always have several.

The answer is not a better string. It is to stop handing people strings at all.

A Name That Is Also an Account

An onchain name held properly is not a label that points at an account somewhere else. It is the account. Ownership of the name and the destination of the payment are the same fact, recorded in the same place, verifiable by anyone at any time.

This is the part that changes everything downstream. When team.esports or a player's handle.esports is itself the payment endpoint, the payer no longer touches a wallet string at all. They see a name they can read. They can confirm it is right before they send, because a name defends itself in a way an address never could: s1mple.esports is either correct or obviously wrong. You cannot subtly alter it into a lookalike that still resolves to the same person, because the resolution is bound to ownership recorded onchain. Change the name and it stops being theirs. Keep the name and it stays theirs. Your eye and the mathematics agree — and the swapped-address attack has nothing to grab onto.

So the name does two jobs at once. It is the brand — the thing that goes on a jersey, a stream overlay, a tournament bracket, a sponsorship deck. And it is the account — the thing that gets paid. In competitive gaming, where identity and brand power are the whole game, collapsing those two into one owned name is not a convenience. It is the natural shape of the thing.

Where .esports Comes From: Freename

The .esports name is a top-level domain — a root, the same class of name as .com or .xyz, but issued and owned onchain rather than leased from a traditional registry.

It is powered by Freename, an onchain domain registrar that issues sovereign top-level domains. The word that matters there is sovereign. A conventional domain is a lease: you pay a registry every year, and the registry can revoke, reclaim, or refuse to renew under terms you do not control. A Freename TLD is different in kind. Ownership is recorded on the chain, verifiable by anyone, and it is not a tenancy that sits at the mercy of a registry's goodwill. The holder of a Freename TLD holds the root itself.

Freename issues the top-level name; the names beneath it — the individual player, team, and tournament identities under .esports — inherit that same onchain, verifiable ownership. Every TLD in the Freename namespace works this way, and every one of them is integrated into the same payment layer described here. .esports is one name in that namespace, chosen for this article because competitive gaming is a sector where readable, ownable identity and cross-border group payment collide most sharply. But the mechanism is general: a Freename TLD is a name you own onchain, and a name you own onchain can be paid to directly.

That is the foundation the rest of this rests on. Freename provides the sovereign, onchain name. What turns that name into a working payment endpoint — one that can receive an amount and divide it correctly among several people — is the router that resolves it.

Where the Payment Comes From: Shaka

Shaka is an onchain payment router built on Ethereum. It resolves Freename names natively, .esports included, and it does one thing with precision: it takes the total amount of a deal and distributes it, instantly, to every party at preset shares, in a single transaction, with finality.

The word router is exact. Shaka is non-custodial — it routes funds, it never holds them. There is no account where the money sits and waits. There is no moment where one party is holding a sum that partly belongs to others. The incoming payment arrives already carrying its own instructions for how to divide, and it separates into each recipient's share in the same transaction that delivered it. No party held the whole. No one did arithmetic after the fact. No one is owed a cut to be settled later, manually, on trust.

Put those two layers together and the picture is complete. Freename gives the sector a name it owns and can read. Shaka makes that name receive money and split it correctly. The name is the identity and the account; the router is what makes the account behave the way a group of people actually needs it to.

What This Looks Like for a Roster

Put it in a room. A team wins a tournament. The prize is a single amount, and it is owed to more than one person: five players, a coach, and the organisation that fields the team. Under the old way, that amount lands in one account — usually the org's — and now the org is holding money that is not entirely theirs. It owes each player a share and the coach a share, to be paid out later, manually, once someone has done the maths and moved the funds. That gap between "the money arrived" and "everyone has been paid" is where late payments live, where disputes start, and where a young player waits weeks for money that was theirs the moment the match ended.

Now give the roster a .esports name with the split configured in advance. The tournament pays one name. The amount arrives already knowing how to divide itself: each player's share, the coach's share, the org's share, separated in the same transaction that delivered them. Nobody held the whole sum. Nobody did arithmetic. The player in another country has their share the instant the prize settles, not the following month. The org's job got simpler, not harder — it configured the shares once, and every payout after that runs on rails.

The same shape covers a sponsorship. A player closes a deal, and three parties have a claim on it: the player, the agent who made the introduction, and the platform that hosted it. The sponsor pays one .esports name. The money arrives split three ways, in one transaction, at the shares everyone agreed before the payment was ever sent. The sponsor's experience got simpler — one readable name instead of three wallet strings. Everyone else's got safer — no one is holding funds that belong to someone else, and no one is waiting on a manual transfer that might slip.

This is the pattern esports runs on constantly: money owed to a group, arriving as a single amount, needing to be divided. Prize pools split among a roster. Sponsorships split among a player and their representation. Tournament revenue split among organisers. Coaching and bootcamp fees split among staff. Every one of those is a single incoming payment that has to become several correct payouts. That is precisely the operation Shaka performs, and a .esports name is the readable endpoint that triggers it.

Why Preset Shares Matter More Than They Sound

The phrase "preset shares" carries the whole weight of the thing, so it is worth slowing down on it.

The shares are agreed before the payment exists. The parties decide who gets what — the player's percentage, the agent's percentage, the platform's percentage — and that agreement is configured into how the name pays out. When the money finally arrives, there is no negotiation left to have, no invoice to reconcile, no trust required that the party holding the funds will pass along the rest. The division already happened, structurally, before a cent moved.

This is what removes the most common source of friction in group payments: the interval between receiving and distributing. In the traditional flow, that interval can be days or weeks, and it depends entirely on the good behaviour and solvency of whoever received the lump sum. In the routed flow, that interval is zero. Receiving and distributing are the same event. A player does not have to chase their org. An agent does not have to invoice and wait. The structure pays everyone at once because the structure was set up to, in advance, by agreement.

And because the settlement is onchain, it is final. Once it clears, it is done — not pending, not reversible, not subject to a later clawback. For the recipient, finality is the point: the money that arrived is theirs, verifiably, immediately. For a sector that pays a lot of young people across a lot of borders, that certainty is worth more than almost anything else the payment rail could offer.

The Cross-Border Reality

There is one more thing esports feels more acutely than most sectors, and it deserves its own attention: almost every payment crosses a border.

A roster is rarely in one country. A tournament is hosted in one place, sponsored from another, and won by players scattered across several. An agent may sit in a different jurisdiction from the player they represent. When the money moves the traditional way, each of those borders is a point of friction — a currency conversion, a correspondent bank, a delay measured in days, a fee taken somewhere in the chain that the recipient never fully sees. A young player in one country waiting on prize money routed through banks in two others can wait a long time for money that was theirs the moment the match ended.

A name resolved onchain does not care where the parties are. The payment settles on the chain, not through a chain of correspondent banks, so the border stops being a series of gates the money has to pass through. The roster split that pays five players in four countries pays all five at the same instant, on the same rail, in the same transaction. Geography stops being a variable in how fast and how reliably people get paid. For a sector that is global by default and young by default, that is not a marginal improvement. It is the difference between getting paid and chasing payment.

Identity and Brand Power, Wired to Payment

Everything above is the payment argument. But it lands on top of an identity argument that esports feels more sharply than almost any other sector.

Competitive gaming is built on names. A player's handle is their entire public identity — often more recognisable than their legal name, and more valuable. A team's name is a brand that carries sponsorships, merchandise, and a fanbase. Tournaments are brands. Leagues are brands. The sector runs on identity and brand power in a way that traditional sport, with its clubs and its jerseys, only partly matches. In esports the name is the asset.

Which is why owning that name — really owning it, onchain, sovereign, not leasing it from a platform that can suspend it — matters. A handle on a game client can be banned. A username on a social platform can be reclaimed. A .esports name held onchain through Freename is owned in a way those are not. It is the identity that cannot be taken back by the platform it lives on, because it does not live on any platform's terms. It lives on the chain.

And when that owned identity is also the payment address, brand and bank account stop being two separate things to manage. The name a player puts on their stream is the name they get paid to. The name a team puts on a jersey is the name a sponsor sends money to. The name a tournament organiser builds a reputation on is the name that receives entry fees and pays out prizes. There is one name, and it carries everything — the identity, the brand, and the money — verifiable in the same place by anyone who cares to check.

That is what it means to claim a .esports name rather than rent a username. It is not a label. It is a durable, owned identity that also functions as an account, on rails that already work.

The Practical Path

For the parties who would use this, the shape is straightforward.

The payer's experience is the simplest it has ever been: a name instead of a string, readable and verifiable, with none of the copy-paste risk that made onchain payment feel fragile. The recipients' experience is the safest it has ever been: preset shares, instant division, no one holding anyone else's money, no manual transfer to wait on, finality the moment it clears.

The Shape of It

Esports settled everything else about itself onchain-fast a long time ago — the matchmaking, the rankings, the broadcast, the community. The money was the last thing still moving like it belonged to another era, passed around as unreadable strings and lump sums that someone had to divide by hand.

A .esports name closes that gap. Powered by Freename, it is a sovereign onchain identity the sector can own and read. Resolved by Shaka, it is a payment address that takes one incoming amount and pays every party their agreed share at the same instant, in one transaction, with finality. Identity and account, brand and bank, collapsed into a single name that a payer can actually handle.

One name. One payment. Every party paid. That is what the base layer of a sport's money should look like — and for .esports, it already does.