Running a market TLD for music: who it serves and how

A namespace built around music starts with a question that is easy to skip: who, exactly, needs a name, and what do they do with it? The word “music” covers artists, their management, labels of every size, venues, session players, producers, publishers and fan communities. Each has a different relationship to identity, to payment and to the people they work with. A TLD that tries to serve all of them without distinguishing between them will serve none of them well.

This article is for anyone considering acquiring a sector TLD in music and issuing names under it. It describes who the real holders of names would be, what a name would concretely do for each of them, and what the operator must build and maintain. It also models revenue honestly, because the gap between an optimistic registration forecast and realistic take-up is where a sector namespace disappoints its owner. After reading it you should be able to judge whether there is enough genuine demand in this sector to justify the acquisition, and what running it would require.

The role in question is that of an operator who runs a market TLD as a namespace: you hold the TLD onchain, you decide who may have a name under it and on what conditions, you handle disputes, and where the registry’s royalty program applies you receive a share of each registration fee.

Who holds a name and why: four distinct holder types

Music is one of the few sectors where individual people, small collectives, large commercial entities and informal fan groups all have a plausible reason to hold a name. That variety is an asset in principle, but it creates four very different support and policy problems in practice.

The table is not meant to be discouraging. It shows that the operator’s early energy belongs in the first row. Artist adoption unlocks the other three. Starting with a fan community that has no artist anchoring it produces names that point to nothing meaningful.

Labels and distributors

A label’s interest is rarely one name. It is a consistent set: one name for the label, one for each act on the roster, perhaps one for each imprint. The benefit is administrative. A label that pays session players, producers and featured artists in digital assets can keep a list of readable names instead of a spreadsheet of addresses, and a mistyped name fails to resolve where a mistyped address may simply send funds to the wrong place.

The weakness is just as concrete. A label that does not pay anyone onchain has no use for this, and a name will not change how it pays. Independent labels that already work with onchain releases are the plausible holders. A large label will send the question to its legal team first, and that team will ask who the operator is, what the rules are and what happens in a dispute. Have the answers written before the meeting.

Venues and promoters

For a venue, a name is a payment point and a sign above the door. A promoter settling with a touring act after a show, or a venue taking deposits for private hire, could publish one name instead of a new address each time. That only matters where both sides already settle onchain, which in live music is uncommon. Treat venues as a later audience and do not count them in a first forecast.

What a name does for an artist, concretely

An artist who holds artistname.yoursector gets, in the first instance, a human-readable identifier for a wallet address. Instead of handing a counterparty a long string of letters and digits, the artist shares a name that the counterparty can use in a wallet or payment tool that supports onchain names. This matters most for direct payments from collaborators, small labels, licensees who want to place a track in a film or an advertisement, and fans who want to support an artist outside a streaming service.

A name also anchors an artist’s public onchain identity. If an artist releases recordings as tokens, issues access tokens for shows or publishes digital collectibles, all of that can be associated with one name. The name becomes the address of record for what the artist does onchain. It plays a part similar to a domain, but it sits outside the ICANN root, so an ordinary browser does not open it without support. Resolution is partial and it changes. Names on Freename can be used in Bitcoin.com Wallet, they work in MetaMask once Freename’s resolver is added, and desktop browsers reach them with the Freename Web3 extension. State this limit plainly to every prospective holder, and point them to the list of what works with onchain TLDs, which gives the sources.

A name can also serve as a lightweight website address. An artist can publish a profile, a release list and a payment link as pages stored on IPFS (a distributed file storage network) and reached through the name in browsers that support it. Whether this matters to a given artist depends on whether the audience can open it. For an artist whose fans use ordinary browsers, a DNS domain is simply better for the public site, and the onchain name is the payment and identity layer beside it. Be honest about that.

Artists and their teams: the name is rarely one person’s property

Most working artists of any scale operate through a company, a manager, a label agreement, a publishing agreement or some combination. The person who asks for artistname.yoursector may not be the one who controls that artist’s name commercially. A manager may run the artist’s online presence. A label may hold rights in the recording name. A band name may belong to a partnership of four people, one of whom is asking.

When you issue a name to “an artist”, you are in practice issuing it to whoever controls the wallet that receives it. That may be the artist personally, a manager, a company account or a label. If the artist later leaves the label, the name stays with the wallet. If the manager changes, the name stays with the wallet. You are not a party to those arrangements and should not try to referee them. What you can do is require, when a name is issued, a statement of who the holder acts for, and say in your rules that the namespace does not replace the contracts between an artist and the people around them.

Teams asking for several names at once, such as a management company that wants actone.yoursector and acttwo.yoursector, will expect a single process, not a separate application and payment for each act. Bulk issuance for rosters is worth settling in the launch plan, and the Launch Roadmap tool is a convenient place to draft that plan before the first conversation with a label.

Fans and membership: real demand, wrong timing

Fan communities generate the most enthusiasm in early planning and the least activity at launch. The reason is structural: a fan takes a name under .yoursector because it expresses membership of a community around a specific artist, genre or scene. That motivation exists only once the namespace means something in that community. At launch, it does not.

The realistic path is to treat fan names as a second-wave product. Once a meaningful group of artists holds names under the TLD, their fan communities have a reason to follow. You can help by working with artists on named memberships, where holding member.yoursector gives access to something: a presale link, a private page, a place in a group. The name becomes a credential and not just an address. That use is genuine, but it requires the artist to have built something for the name to open, and most artists will need help to do so.

Fan collectives that run a shared treasury, vote on decisions or distribute funds among members are a stronger case than individual fan names. A collective that holds collective.yoursector and uses it as the payment name for its treasury and the address of its public page has daily use for it. Collectives of this kind, including those whose rules are enforced by smart contracts (programs that run on a blockchain), need a stable shared identity that does not belong to one member. That need is concrete, which makes them one of the better near-term audiences.

Weigh one more point before promising fans anything. A fan who pays for a name expects it to keep working. If the artist it refers to walks away from the namespace, the fan holds a credential for a door that no longer exists. Your rules should say what a membership name is and is not, so that nobody mistakes it for a claim on the artist.

Royalties, splits and payments between rights holders

Music rights are almost always shared. A single recording may involve the performers, one or more songwriters, a publisher and the owner of the master recording, and a license to use the track in a film or a game is negotiated separately for each use. Each of those interests belongs to a different party, and the money usually travels through different channels on different timetables. How rights are divided and collected varies by country.

A name in a music namespace can serve as the payment name for any one of those interests. An artist holds artistname.yoursector and receives direct payments there. A songwriter holds writer.yoursector and gives that name to whoever licenses a song. A label holds label.yoursector and receives what its distribution partners agree to pay onchain.

The namespace is most useful when one payment must reach several named parties in agreed proportions. An onchain payment router such as shaka lets a payment link pay out to names instead of raw addresses, with the split between the parties agreed and signed onchain before any funds move, and it routes the funds without holding them. For a recording with a singer, a producer and a featured guest, that means the proportions are fixed by the parties themselves before the money arrives, and each of artist.yoursector and producer.yoursector receives a share. The page on payments to a name explains this in more detail.

Keep the limits in view. A split covers the payment it was set up for. It does not replace the collection of public performance or broadcast income, which runs through established channels that do not pay to onchain names. It does not settle who owns what: the proportions come from the agreements between the parties, and a wrong proportion signed onchain is still wrong. What it removes is one manual step, in the cases where the parties already agree and already accept onchain payment.

You do not administer these splits and you are not a party to the underlying rights agreements. Your job is to make sure that names keep resolving and that your rules do not cut across the rights structure, for example by letting a label take an artist’s name without the artist’s consent.

Impersonation and the operator’s duty

Impersonation is the most serious continuing risk in a music namespace. An artist’s name is often a trademark as well as a stage name, and it is the thing fans search for. A third party holding famousartist.yoursector could receive payments meant for the artist, send fans to misleading content or suggest an association that does not exist.

The UDRP binds people who register domain names through ICANN-accredited registrars, because they accept it in their registration agreement. Nobody who takes a name under .yoursector has accepted it, and no outside panel will decide the dispute for you. That is not a reason to avoid the sector. It is a reason to do the policy work before launch.

Your strongest control is at issuance. On Freename, only the holder of a TLD can issue names under it, so a name that matches a known artist does not have to be issued until you are satisfied about who is asking. Publish before launch who may hold a name that corresponds to an artist, a band or a label, what evidence of authority you ask for, and how a challenge is handled. What you can do about a name after it has been issued depends on the registry’s terms and on the controls it gives a TLD holder. Confirm that with the registry before you write a rule that promises cancellation or transfer, and never promise a remedy you cannot carry out.

Music adds complications that a general policy will not anticipate, and your rules should name them:

• Shared names. Two unrelated acts in different countries may perform under the same name, each legitimately. First to ask is one possible rule, but say so in advance.
• Tribute acts. A tribute band has a real business and a name that deliberately recalls another act. Decide whether such names are allowed and how they must differ.
• Band splits. Former members may each claim the band name. Ask for evidence of who controls it, and decline to issue while the dispute is open.
• Estates. The name of a deceased artist is usually managed by an estate or a rights company. Treat it as you would a living artist’s name.

An operator without a published dispute policy faces pressure from two sides: from artists and their counsel when a name looks abusive, and from holders who feel a decision against them was arbitrary. Before issuing any name close to a known artist, check it against registered trademarks. The free Trademark Name Check on the site is one place to start, and your own counsel decides what a conflict means in your jurisdiction.

The operator’s day-to-day role

Running a music namespace is not a passive income stream. The operator sets policy, handles onboarding, responds to disputes, watches for abuse and keeps the process of obtaining a name working. None of that requires a large team, but it requires consistent attention, and in music it requires someone who understands how artists, managers and labels relate to each other.

The core tasks are:

• Policy maintenance. The eligibility rules, the dispute procedure and the conditions for a name are documented, published and revised when they prove inadequate. The first band split or tribute act will test them.
• Onboarding support. Most artists and their teams are not fluent in onchain tools. A manager with no experience of wallets must be able to obtain a name for an act, and there must be a person to ask when that fails.
• Dispute handling. When a name is challenged, someone investigates, applies the published rules and communicates the outcome. This cannot be left to the registry.
• Abuse monitoring. Someone looks regularly at the names issued and at where they point, for names that imitate artists or mislead fans.
• Revenue tracking. Where the registry’s royalty program applies, check that the TLD meets its activation conditions and that the share of registration fees arrives as expected.

Support is the task most often underestimated here. A touring artist who cannot receive a payment the night before a show does not want a help page. Decide in advance what hours you cover and say so. For an operator who has just acquired a TLD, the post-transfer activation service addresses the stage of putting it to work.

Revenue from names: a worked example

What follows is a worked example, not a forecast. Its assumptions are these: 400 names are registered under the TLD in the first year; the average registration fee is USD 30 per name; the TLD holder receives half of each registration fee, which is the upper limit of what Freename advertises for its royalty program; nothing else is counted, neither later years nor names priced above the average. The share actually paid depends on the registry’s terms and on its activation conditions when you join, so half is the best case.

Total registration fees: 400 times USD 30 equals USD 12,000. The operator’s share at half: USD 6,000 for the year. Later years and names priced above the average are left out, and a lower share under the registry’s terms lowers the result in proportion. The USD 6,000 is also counted before the annual cost of taking part in the royalty program, which the registry sets and which has to be deducted, even though the TLD itself has no annual renewal fee. A TLD registered under earlier terms may include the program for life, so ask the registry before closing whether those terms carry over to you as the buyer.

USD 6,000 in a year is not a business by itself, and 400 names is not a modest assumption for a namespace whose main audience is artists who already work onchain. Reaching it means persuading 400 acts, labels or collectives, most of them one conversation at a time. The result improves if some names carry a higher fee because the artist behind them has commercial weight, and if the namespace keeps growing after the first year. Neither is certain. The Subname Revenue Calculator lets you test other fee levels and volumes before you commit.

The honest conclusion is that registration fees alone are unlikely to justify the price of a sector TLD in the first year, unless you already have a route to many names: a membership you run, a roster you represent, a platform with artists on it. The more realistic case is that the namespace is worth having for another reason, as a credential for the members of an association, as an identity layer for a platform, or as the naming system behind payments you already route. In that case the share of fees is a secondary benefit. Set it against the price using the same logic by which a TLD valuation is built, and treat any tax or accounting question as one for your own advisers.

What to check before acquiring the TLD

Acquiring a sector TLD means acquiring the token that records it onchain. Anyone, a label’s legal team included, can open a block explorer and read that token’s registry record, which is public. Before proceeding, verify four things that weigh heavily in music.

First, check whether the string conflicts with a registered trademark in the countries where you will operate. Genre words, instrument names and terms close to well-known acts are often registered as trademarks for music services or merchandise. A string that is free in one country may not be in another. Your counsel decides.

Second, assess whether the string means something to the people you want as holders. A word that working musicians use about themselves carries its own explanation. A word chosen because it was available will need marketing before anyone wants a name under it. Ask five artists and two managers what they would expect to find at name.yoursector. If they hesitate, so will everyone else.

Third, confirm the technical state of the TLD: which registry it is recorded on, whether names under it resolve in the wallets that support that registry, and whether it meets the conditions of the royalty program.

Fourth, find out whether names have already been issued under the TLD, and to whom. Names sold to artists, labels or anyone else remain theirs after the transfer, while names the seller itself holds under the TLD can pass to you with it if the two of you agree. If some of them correspond to real artists who never asked for them, you take over a dispute file along with the TLD, and the price should reflect it.

If the TLD you want is held by someone else, you do not have to approach the holder yourself. An organization can mandate the desk to find and approach a holder on its behalf.

A realistic first year

The first year of a music namespace is a year of policy and onboarding, not of revenue. The first names are mostly the operator’s own and those of a few early adopters. The names that give the namespace meaning, those of artists with an audience, take longer, because artists decide slowly and their teams decide more slowly still. Release schedules and touring also matter: an act in the middle of an album campaign will not add a new tool until it ends.

1. Acquire the TLD and confirm its stateComplete the transfer through onchain escrow, check the royalty program conditions, and test that names resolve in supported wallets. Write down the technical state before issuing any name.
2. Publish the rulesPublish eligibility, conditions, the dispute procedure and the rules for shared names, tribute acts, band splits and estates. Do this before any public announcement.
3. Seed with anchor namesIssue the operator's own names and a small number of names for artists or labels who have agreed in advance. Anchor names give the namespace meaning before it opens.
4. Open by applicationIssue names on application or invitation and review each request against the rules. This is slower and produces a cleaner namespace.
5. Handle the first disputesApply the published rules to the first contested name, record the outcome and clarify any rule that proved unclear. Artists and managers will judge the namespace by how this is handled.
6. Widen access and show the payment useOnce the namespace has a visible set of legitimate names, show artist teams and labels how a split payment reaches several names. This is the use most likely to convince professionals who already work onchain.
7. Review against the forecastCompare the names actually issued with your assumptions, adjust the conditions if needed, and decide whether fan and membership names are ready to follow.

If, at the end of the year, the anchor artists use their names for real payments, the namespace has a base to grow from. If they hold names they never use, more names will not fix it. Go back to the use case before spending on promotion.

Where to start if the case holds

Begin with demand, not with the TLD. Write down the names of twenty artists, labels or collectives who already take onchain payments and whom you can reach in person. If you cannot fill that list, the namespace has no first row, and the acquisition can wait.

If you can, draft the rules next, the impersonation rules above all, and run your own numbers through the worked example with your assumptions in place of ours. Only then settle on the string and find out whether it can be acquired.

That last step is where Hush Partners may be useful. It is a private desk for onchain TLDs, and an organization can mandate it to locate the holder of a TLD and make the approach. The mandating client pays a fixed amount, and each exchange falls under a standard mutual NDA. For a music TLD as for any other, the contact form on the site is how you reach the desk.

Questions people ask

Can an artist hold a name personally if their label objects?

The rules are set by the operator. You can require evidence of authority before issuing a name that corresponds to an artist under a label agreement, or you can issue to the artist and leave the contract question to the parties. Either choice should be written in the rules. If you choose not to ask for evidence, expect to hear from label legal teams.

Does an onchain name replace an artist’s DNS domain?

No, and an operator should never suggest it does. A DNS domain opens in every browser without an extension or a wallet. An onchain name works in a narrower set of environments. It adds to the artist’s identity in places where a DNS domain does not reach, such as wallet payments and access by token. The artist keeps the domain.

What happens to a name when an artist dies or a band dissolves?

The name stays with the wallet that holds it. If nobody can access that wallet, the name is stranded. Operators serving working musicians should address this in their rules, at least by recommending that a band’s name be held in a multisignature wallet (one that needs approval from more than one key before anything moves), so that the loss of one key or the departure of one member does not strand it.

Is a genre word or a functional word the better string?

A genre word attracts people with a strong sense of belonging, but that community must already be onchain for belonging to turn into names. A functional word, one that describes what a holder does in music, attracts professionals who see a practical use. Neither is better in general. Judge the string by the audience you can actually reach.