Running a market TLD for online communities

A sector TLD for online communities is a namespace built around a word that the sector already uses: a string like .yoursector under which a forum, a membership club, a decentralized organization or a niche guild can hold name.yoursector as its persistent onchain identity. The operator of that TLD decides who may register and on what terms, and may receive a share of each registration fee under the registry’s royalty program. The community that registers a name gets something more durable than a username on a platform someone else controls.

Whether this makes sense for you as an operator depends on what the sector actually needs, what you can deliver without a dedicated engineering team, and how the economics work at realistic registration volumes. This article takes those questions in turn, with enough detail to let you form a view before you go further. It does not assume you have already acquired a TLD; if you are still at the assessment stage, it covers that too.

Who would hold a name, and what it does for them

Three groups account for almost all plausible registrations, and they have different motivations worth separating.

Forums and long-running discussion spaces. These are communities that have existed for years, often around a craft, a hobby, a professional practice or a shared interest. They have administrators, recurring members and a reputation built up over time. A name under .yoursector gives the forum a stable, portable identifier that is not tied to a hosting provider or platform operator. When the forum migrates from one hosting stack to another, the name can follow. The name can also point to a wallet address, so that members can send contributions directly without going through a payment processor whose policies may change.

Membership groups and subscriber collectives. Paid or gated communities (subscription newsletters with comment sections, private groups organized around professional development, fan communities with tiered access) benefit from a name that doubles as a credential. circle.yoursector or guild.yoursector signals belonging and can be configured to point to a wallet, to a website published to IPFS (a decentralized file-storage network), or to a governance tool. The name becomes part of the group’s identity instead of a backend detail.

Decentralized organizations (DAOs). A DAO, a decentralized autonomous organization, is a group that coordinates through smart contracts (self-executing code on a blockchain) and votes recorded onchain, with or without a traditional legal entity around it. DAOs need a human-readable identifier for their treasury address, their governance portal and their public communications. A name under a well-chosen sector TLD can serve all three from a single registration, and it is more legible than a raw wallet address to members who are new to onchain tools.

The table below maps each group to its primary use for a name.

Individual members can also register names, such as a pseudonym or a role under .yoursector, and in communities where onchain identity already matters, some will. But the anchor demand comes from the organizations, not the individuals, and it is thinner than it might appear. Many communities are small, and many will register one name and stop. Model for that from the start.

What the name does in practice

For a forum, the practical effect of forum.yoursector resolving to a wallet address is that any member can send a contribution to a readable string instead of copying a long hexadecimal address. With an onchain payment router such as shaka, the forum can go one step further and publish a payment link that pays out to names, with the division between, say, a moderators’ wallet and a shared treasury agreed and signed onchain before any funds move. The router passes the funds through and never holds them. For a community that runs on trust between volunteers, a split that everyone can see in advance removes one of the oldest sources of suspicion: who handled the money.

For a membership group, a name pointing to content published to IPFS means the group’s archive and onboarding materials do not depend on a single platform. The platform may change its terms or close; the name stays with the group’s wallet, and the content stays reachable for as long as someone keeps it stored on the network. That is a real advantage for groups with years of accumulated material and no legal entity to protect it. Whether members can actually open that content depends on which wallets and browsers support resolution, which the callout below sets out. The what’s live page keeps a sourced account of which capabilities work and where.

For a DAO, the name addresses a concrete embarrassment: governance proposals, treasury movements and public announcements tend to reference wallet addresses that are opaque to anyone outside the founding group. A readable name such as dao.yoursector that points to the treasury address and the governance portal makes the organization legible to new contributors and to outside observers who want to verify they are dealing with the real entity and not an imitation.

Names as membership and governance rights

On Freename, a TLD is recorded onchain as a token that sits in a wallet, and nobody but its holder can issue names under it. A name issued to a community is likewise controlled from a wallet. That makes it usable as a condition of access to a gated space, as a marker of who may take part in a community poll, or as a record of contribution. None of this requires you as the operator to build it: the holder of name.yoursector can connect that name to whatever tooling they use for governance and access control. What you provide is the underlying identity layer.

The governance angle is worth taking seriously because it is where names become sticky instead of decorative. If a DAO uses names under .yoursector to recognize members in its governance tool, each name has operational value that persists regardless of what the registration cost. A member who loses the name loses their voice in the vote. That is a strong reason to keep the wallet secure, and a strong reason for the community to care about how your namespace is run.

The same dynamic applies to multisignature wallets, which require agreement from more than one key-holder before a transaction executes. A DAO that links treasury.yoursector to a multisignature wallet has an address that is both readable and verifiable. The registry record is public, and anyone can look it up on a block explorer (a public viewer of onchain records) to see which wallet the name is attached to.

The operator’s role here is to set clear rules about which names may carry governance claims. A registration policy that allows anyone to take admin.yoursector or council.yoursector without review will produce disputes, because in a community those words are titles, not just strings. Reserve them, or create a separate tier for names that carry governance weight, and document the distinction before you open registrations.

Volunteer moderation and what running the namespace costs

Most online communities are run by volunteers. The administrators who approve new members, resolve disputes and keep discussions on topic are not paid. When you issue names to these communities, you are selling into a context where operational bandwidth is already stretched and where the people responsible for the community may change without notice.

This has a direct effect on what you need to provide as an operator. Support requests will come from people who are technically comfortable (DAOs, developer-adjacent groups) and from people who are not (hobbyist forums, professional guilds run by practitioners and not technologists). You need to be prepared for both. A forum moderator who registered forum.yoursector some years back and has since handed administration to someone else may not know where the wallet is, who controls the recovery phrase, or how to update the record the name points to. That is your support ticket.

The cost of running the namespace is therefore not purely technical. It includes the time spent on support, the time spent reviewing registrations against your policy, and the time spent on disputes that arise when a name is used in a way that conflicts with your rules. None of this is free, and the revenue model worked out below needs to carry it. A namespace with a handful of registrations and a heavy flow of support tickets does not pay for itself at any price point.

Volunteer turnover also shapes what you should ask for at registration. Encourage a community to hold its name in a wallet that more than one trusted person can operate, and to write down who those people are. A name held in the personal wallet of one moderator works until that moderator leaves, and then it becomes a problem for the community and a recurring request in your inbox.

Good documentation reduces the cost per name but does not eliminate it. The Launch Roadmap tool builds a launch roadmap for a newly acquired TLD; when you use it, add the support workflow to the plan, because it is the item most often overlooked at the planning stage.

Treasuries, contributions and payment flows

Communities that hold a treasury, whether a DAO with a formal multisignature wallet or a forum that collects voluntary contributions from members, have a recurring need that a name under your TLD can address directly. The name points to an address; the address receives funds; the community decides how to spend them. The chain is short and the logic is clear. The page on payments to a name explains how this works.

What is less clear, and what you should think through before issuing names for this purpose, is the legal context. A community that holds funds onchain may be operating as an unincorporated association, a partnership, or something a court in its country would classify differently, and the rules vary from one country to another. Your registration terms cannot resolve that question, but they should be explicit that you provide a naming service and not a financial or legal structure. How the funds are managed, and whether the structure is appropriate where the community operates, is for the community and its own counsel.

A readable treasury name also raises the stakes of imitation. If members learn to send contributions to club.yoursector, a near-identical name issued to someone else under the same TLD is a route to misdirected funds. This is a reason to review registrations that closely resemble an existing community’s name, and to tell communities to publish their exact name in the places their members already trust.

The contribution model also affects what a name can cost. A forum that lives on small voluntary contributions cannot absorb a high registration fee without deciding that the name is not worth it. The worked example in the revenue section uses a modest fee for that reason: community demand is sensitive to price in a way that commercial domain demand is not.

What happens when a community splits

Communities divide. A forum forks when moderators disagree about rules. A DAO splits when a governance vote goes badly and a minority leaves to form a competing organization. A membership group loses its founding organizer and the community fragments.

When that happens, the name under your TLD becomes contested. Two factions will each claim to be the legitimate continuation of the original community. Only one of them controls the wallet the name sits in, and under the onchain model that wallet is the holder of record. That is the correct technical answer, but it is not necessarily the answer that satisfies either faction.

As an operator, you need a disputes policy that addresses this scenario before it occurs. The policy should state three things. You do not adjudicate internal community disputes. You recognize the wallet that holds the name as the holder of record. And you act on a binding decision from a competent court or arbitral tribunal, to the extent the registry’s mechanics allow you to act at all. That is the full extent of your role. Anything beyond it, such as mediating between factions or determining which group is the “real” community, is a commitment you cannot sustain and should not make.

A split is a foreseeable event in this sector, not an edge case, so the policy belongs in your registration terms from the first name issued. Make it public and point to it whenever a dispute reaches you. You can also reduce the damage in advance: when a community registers, suggest that it decide in its own rules who controls the name if the group divides. A community that has answered that question itself rarely needs to ask you. The operators page is written for those who run a market TLD as a namespace; read it alongside your counsel’s advice before you finalize your terms.

The operator’s role: rules, issuance, support and disputes

The operator is not a passive royalty recipient. You set the rules under which names are issued, you apply those rules, and you handle the consequences when they are broken.

Rules. At minimum: which names are reserved (your own terms, terms that would mislead users about affiliation with you, role words such as those discussed above); what uses are prohibited (impersonation of a person or community, illegal activity, use that infringes the intellectual property of third parties); and what the holder’s obligations are. The rules need to be specific enough to give you a clear basis for action, and simple enough that a volunteer forum moderator can understand them.

Issuance. Because issuing names is reserved to the holder of the TLD, nothing appears under .yoursector without you. How much of the flow can be automated, and how a review step fits into it, depends on the registry’s tooling; confirm it before you promise a turnaround time. A reasonable design is to let ordinary registrations through quickly and to look by hand at requests for reserved strings and at names that resemble an existing community. The post-transfer activation service is concerned with putting a TLD to work once the transfer is done.

Support. Budget for it. Most questions will be about wallet access, pointing the name at the right address, and payment routing. A small namespace can be supported by one person part-time if the documentation is good. A larger one, or one serving less technical communities, needs more.

Disputes. Third parties, such as trademark owners or people who believe a name infringes their rights, will contact you. You need a process for receiving, logging and answering those contacts. You are not bound by the UDRP (the Uniform Domain-Name Dispute-Resolution Policy, the administrative procedure that applies to names registered under ICANN’s generic TLDs), but you should have a documented procedure that a complainant can follow.

Revenue from names: a worked example

The following is a worked example. Every assumption is stated. Do not treat the numbers as a forecast.

Assumptions. The registration fee is USD 40 per name. Freename’s royalty program gives the holder of a TLD a share of every registration fee paid for a name under it; that share is advertised at up to half and depends on the registry’s current terms and activation conditions. This example uses half, the advertised ceiling. Only first registrations are counted: no income from later years of the same names is assumed. The operator issues 120 names in year one to forums, membership groups and DAOs. Support takes two hours per registrant over the year, an assumption suited to a largely non-technical audience.

Revenue at the ceiling. 120 registrations at USD 40 each come to USD 4,800 in registration fees. Half of that is USD 2,400 for the TLD holder, or USD 20 per name. If the share that applies to you is lower than the ceiling, the figure falls in proportion. The Subname Revenue Calculator lets you run your own assumptions.

Time. Two hours of support for each of 120 registrants is 240 hours. USD 2,400 spread over 240 hours is USD 10 per hour of support, before any time spent drafting the policy, reviewing registrations or handling disputes, and before the price paid for the TLD. On the holding side, Freename charges no annual renewal fee on a TLD, but membership of the royalty program does carry an annual cost, set by the registry, which is not in these figures and comes off the USD 2,400. Certain TLDs date from earlier terms that include the program for life, and whether a buyer inherits those terms is to be confirmed with the registry before closing.

What the arithmetic shows. The return per hour does not improve with volume in this model: each name brings USD 20 and costs two hours, whether you issue 50 or 200. What changes the result is support time per name. If good documentation and a more technical audience bring it down to half an hour per registrant, the same USD 20 corresponds to USD 40 per hour. The lever you control is therefore not the number of names but how much help each community needs, which is why a DAO-heavy namespace and a hobbyist-heavy namespace have very different economics at the same fee.

The chart below shows the holder’s share at three registration volumes, holding the other assumptions constant.

50 registrationsUSD 1,000

120 registrationsUSD 2,400

200 registrationsUSD 4,000

The TLD holder's share only, at the advertised ceiling. The actual share depends on Freename's current terms and activation conditions. Operating time, the annual cost of the royalty program and the cost of acquiring the TLD are not deducted.

Be honest with yourself about whether the sector holds 120 communities that will pay USD 40 for a name. It is not a large number in absolute terms, but it requires active outreach by someone the communities already know. A namespace that simply waits to be found will not reach it.

What to check before acquiring the TLD

If you do not yet hold .yoursector, the assessment before acquisition is the most consequential step. Five things to verify:

Does the word belong to anyone? A sector word that is also a registered trademark in relevant classes creates risk. A trademark owner has legal tools that do not depend on the DNS, including, depending on the country, a claim that names issued under the word infringe its rights. Check the trademark registers that matter for your audience before proceeding. The free Trademark Name Check on this site is a starting point; your counsel decides whether a particular word is safe to use.

Is the word specific enough? A very generic word, one that describes something nearly everyone does online, will attract speculative registrations and abuse alongside real community uses. A more specific word, one that names a particular kind of community or practice, produces a smaller but more committed base of registrants. Specificity is generally preferable for a market TLD built on community trust.

What does the public record show? The registry record of a TLD is public and can be read on a block explorer. If the TLD you want is already held, acquiring it means approaching its holder. That is what buy-side acquisition covers: you give Hush Partners a mandate, and the desk locates the holder and makes the approach for you. If the string has not been registered, the registry is where you would register it.

What is it worth to you? For an operator, the defensible way to think about price is the revenue the namespace can realistically produce, set against the work it demands. The worked example above gives you a method for the first half. The page on how a TLD valuation is built describes the approach on the desk’s side.

Do you have standing in the sector? A namespace launched by an operator who is known and trusted in these communities will reach registrations faster than one launched by a stranger. Communities check who is behind a new structure before they adopt it. If you do not have those relationships, factor in the cost and time of building them.

A realistic first year

The first year of running a community TLD is mostly groundwork. The registrations will not arrive without it.

1. Secure and set up the TLDComplete the acquisition and confirm the token is in a wallet you control, ideally one that more than one person can operate. Read the activation conditions of the registry's royalty program and complete them before any name is issued.
2. Draft and publish the registration policyWrite the rules: reserved names, prohibited uses, the complaints procedure and your position on split communities. Publish them at a stable address you can reference in every registration. Have counsel review them before launch.
3. Identify anchor registrantsBefore opening to the public, approach a few forums, DAOs or membership groups whose presence would give the namespace credibility. Their names, once in use, become the demonstration case for every later registrant.
4. Open registrations with active outreachPresent the namespace where your target communities gather. Write plainly about what the name does and what it does not do, including the limits of resolution. Answer questions in public so the answers are visible to everyone considering a registration.
5. Build a support baselineDocument the most common support questions and publish the answers before they are asked. Set a response time you can keep. A slow answer to a volunteer moderator travels through a community faster than any praise.
6. Review the mix of registrantsAfter the first cohort, look at who registered. If speculators outnumber real communities, add a light review step or adjust the terms the registry lets you set. If real communities decline because of the fee, remember that the price of names under your TLD is yours to set, and that it need not be the same for every name: a lower one for non-commercial groups is open to you.
7. Assess the second yearBefore the year ends, count the names that are in use (pointing to a wallet or a site, not just registered) and the support time per registration. Use those two numbers to decide whether to grow the namespace or hold it at its current size.

Where a well-run namespace stands after twelve months

After twelve months, a well-run community TLD in a reasonably active sector should have a working registration flow, a published policy that has been tested against at least one hard case, a small cohort of anchor registrants who actively use their names, and a revenue figure that is honest about what the royalty covers and what it does not.

What it probably will not have: large registration volumes, income that replaces other revenue, or a community that promotes the namespace without being asked. Online communities are self-organizing and skeptical of external structures. They will adopt a name if it solves a real problem, and they will ignore it if it solves a problem they do not have.

A community TLD is a medium-effort, medium-return asset if the sector is right and the operator has standing in it. It is a low-return asset if the operator is starting cold.

Your next step before the TLD changes hands

Do the assessment work first, in this order. Write down the ten communities you would approach as anchor registrants and ask two or three of them, in confidence, whether a name under the word would be useful to them. Run the worked example with your own fee, your own share and your own estimate of support time per name. Have counsel look at the word against the trademark registers that matter. If any of the three answers is weak, you have learned it before paying for the TLD.

If the answers hold and the TLD is already in someone’s wallet, Hush Partners can act for you under a mandate to find and approach the holder, with every exchange covered by a standard mutual NDA and closing through onchain escrow on an aftermarket. The desk is reached through the contact form and nowhere else.

Questions people ask

Can a name under .yoursector be used to control access to a gated community?

In principle, yes. The name is controlled from a wallet, and granting access according to what a wallet holds is an established pattern in onchain tooling. Whether a specific community platform supports it depends on that platform. The operator does not build this integration; the community does, using the tools available for its own setup.

What if the holder loses access to the wallet holding the name?

Under the onchain model, the wallet controls the name. If the wallet’s private key is lost and there is no recovery mechanism, such as a multisignature arrangement, the name is out of reach. The operator cannot solve this after the fact. Include wallet security guidance in your onboarding documentation and recommend that communities holding operationally important names use a multisignature wallet from the start.

Is there a UDRP equivalent for onchain TLDs?

No single one. The UDRP belongs to the ICANN system, and onchain TLDs sit outside it. A trademark owner who believes a name infringes its rights relies on the operator’s own published procedure and on the law of the relevant country, which may mean the courts. What applies to you as an operator is a question for your counsel.

Do communities in this sector already use onchain tools?

It varies sharply. DAOs and developer-adjacent communities are already onchain and will understand registration without explanation. Hobbyist forums and professional guilds may never have used a wallet. You either provide clear, jargon-free onboarding for the second group, or accept that your addressable market is limited to the first.

Can the operator give names to anchor communities without charge?

Issuance is in the operator’s hands, and so is pricing: as holder of the TLD you set what a name costs and can price an anchor community’s name differently from the rest. What remains practical is whether the registry’s flow lets you waive or cover the fee altogether for selected names, and what that does to the royalty. A fee that is not paid produces no share. Confirm those mechanics with the registry before you promise a free name to an anchor community.