Acquiring

Running a market TLD for the legal profession

For operators considering a TLD that names the legal profession: who would hold a name under it, what they would use it for, and what running it involves.

Running a market TLD for the legal profession

The legal profession has attributes that few other sectors share: its practitioners are admitted by a licensing authority, their standing can usually be checked by the public, and their clients hand over some of the most sensitive facts in their lives. Those attributes create both a genuine case for a sector namespace and a set of constraints that any operator must take seriously before issuing a single name.

This article is for anyone considering acquiring a TLD whose string is a word or phrase associated with the legal profession and running it as a market namespace: issuing names to firms, individual lawyers and professional bodies. It works through who would register, what they would do with a name, what the profession’s regulated character means for issuance rules, and what the operator takes on financially and operationally. It ends with a realistic view of the first year.

A sector namespace lives or dies on whether there is a genuine population of holders who want a name, a credible reason for the operator to exist, and enough revenue to sustain operations. All three are worth examining honestly here before a TLD changes hands.

The natural registrant population has three distinct tiers, each with different motivations.

Holder type Primary use Weight for the operator
Law firm Onchain identity, payments, a published profile High: firms are the economic core
Individual lawyer Personal professional identity that moves with them Medium: the largest possible volume
Bar or professional body Namespace governance, member services Low count, high importance

Law firms are the most commercially significant tier. A firm that holds name.yoursector gains an onchain name that can receive payments without the firm circulating a raw wallet address, and that can lead to a page the firm publishes about itself. The name does not depend on the firm’s hosting provider or banking relationship. For a firm with a practice in digital assets or cross-border transactions, an onchain name also shows technically minded clients that the firm works with the same infrastructure they do. Read what works on onchain TLDs, with sources before drawing up any technical promises.

Individual lawyers represent the largest potential volume. A sole practitioner, an advocate who moves between sets of colleagues, or an in-house counsel has a specific problem: when they change firms or set up independently, their email address and website change, but their professional record and client relationships do not. A name under .yoursector that the lawyer keeps in their own wallet goes with them in a way that a firm-issued address does not. The use case is real. Whether lawyers adopt it in numbers depends heavily on how easy the operator makes registration and how consistently the namespace is associated with verified standing.

Bar associations and professional bodies are a small group by count but disproportionately important. If a regional bar or a specialist association holds a name, it lends legitimacy to the namespace itself. A body might use its name for member communications or for a page of official documents. It might also vouch for member registrations. An operator who secures one or two institutional bodies in the first year has a credential that no volume of individual registrations can replace.

Where demand is weak

Be honest with yourself about the limits. Most law firms acquire clients through referrals, reputation and a conventional website, and none of that needs an onchain name. Most clients pay by bank transfer and will go on doing so. A firm with no digital-asset practice and no clients who hold wallets has little practical use for a name beyond reserving it. The realistic early population is narrow: firms that advise on digital assets, lawyers who are paid by clients in that field, and bodies willing to experiment on behalf of their members. Plan around that population, and treat anything beyond it as a later possibility, not a forecast.

What a name concretely does for each holder

The functions that work on Freename names are a short list: a name that wallets can read and that payments to a name can target, a website published on IPFS (a network that stores files by their content) and reached through the name, and resolution in Bitcoin.com Wallet and in MetaMask by way of Freename’s resolver. These names are not part of the ICANN DNS root, so an ordinary browser opens one only with help, which on a desktop means the Freename Web3 extension. Coverage is partial and it changes. Tell holders this plainly.

For a law firm, the practical value sits in two places. The first is payment: pay.yoursector or name.yoursector can receive funds without a raw wallet address appearing on an engagement letter or an invoice. With a payment router such as shaka, a payment link pays out to a name, and the parties fix and sign the split onchain ahead of any movement of funds, for example between a firm and an outside advocate instructed on a matter. The router passes funds on and does not keep them. The second is a published profile: the firm can put behind its name a page that states where it is admitted to practice, who its partners are, and where its entry on the regulator’s register can be found. The page does not replace the register. It points to it.

For an individual lawyer, the value is portability and professional signal. A name in their own wallet stays with them whatever their employment. It can receive payments and carry a professional profile. The operator’s responsibility is to make sure the name was issued to a verified, licensed practitioner, which is where the logic of a regulated profession applies.

For a professional body, the value is collective control. A multisignature wallet, one that needs several approvals before it acts, means no single officer can act alone on the body’s behalf. The member directory, published standards and committee notices can all sit on a site reached through a name that the body controls as an institution.

Regulated standing and why it changes the issuance problem

In most consumer namespaces, the question of who may register a name is answered by who pays first. In a legal-profession namespace, that logic fails. A name under .yoursector carries an implicit representation: the holder is a lawyer or a law firm in good standing. That representation has value precisely because the profession is regulated. If it is wrong, the namespace can mislead the public, and the operator may have to answer for it.

Lawyers are admitted to practice by a licensing authority (a bar association, a law society or another regulator), and that admission is typically public. In many jurisdictions the regulator publishes a roll or a register that anyone can consult. An operator who ties issuance to that register does something that operators in unregulated sectors cannot do: it grounds a name in an external fact about the holder’s standing that others can check, not in the holder’s self-description.

The consequence is that eligibility rules for this namespace must be more demanding than for a sector with no license. The operator needs a clear answer to three questions before issuing any name. Is this person or entity licensed now? In which jurisdiction or jurisdictions? What happens to the name if the license is suspended or revoked?

These are operational questions with legal implications, and the rules differ from one country to the next. The operator’s own counsel should draft the eligibility policy before the namespace opens, because writing it after contested issuances costs far more. The policy, once set, shapes the operator’s exposure if a name is abused.

Deciding who is entitled to a name, and who decides

There are two structural models. In the first, the TLD operator acts as sole issuer: it checks credentials, issues names, and handles disputes. In the second, the operator works with one or more professional bodies who vouch for their members, and the operator issues names on the body’s recommendation. The second model is easier to defend and scales better, but it requires that at least one body be willing to take part formally.

Neither model is cheap to run. Credential verification takes staff time or a dependable connection to a public register. The operator cannot hand these responsibilities away entirely. It can only share them with an institution that has comparable accountability.

For the co-issuer model to work, the body needs a reason to participate. The most persuasive reason is member benefit: members get a name that signals regulated status and that goes with them through a career, and the body has a say when a member is disciplined. That alignment of incentives is the argument the operator makes to a bar or law society when seeking a partnership.

The page on how operators run a market TLD gives a fuller view of the responsibilities involved before those conversations begin.

The operator’s daily work: rules, issuance, support, disputes

Rules come first and are written down: who qualifies, what evidence is accepted, how a firm name differs from a personal name, and what is reserved for professional bodies.

Issuance is the visible part. Each request is checked against the rules, the check is recorded, and the name is issued to the wallet the applicant supplies. A record of who verified what, and when, is what lets the operator explain a decision later.

Support in this sector is unusual. Many applicants will be setting up a wallet for the first time, and a lawyer who loses access to a wallet loses control of the name. The operator should expect to explain custody in plain terms and to say clearly what it cannot recover.

Disputes will be specific to the profession. Two lawyers share a surname and both want the same string. A firm dissolves and two successor practices claim its name. A partner leaves and the firm name still contains theirs. Each case needs a defined process and someone with authority to decide. An operator inside the profession can borrow conventions that already exist for firm names. An operator outside it has to write them.

Confidentiality and what a client expects

Legal clients have confidentiality expectations that go further than in most professions. A client who pays a law firm at an onchain name leaves a public, lasting record that a payment was made. Depending on jurisdiction and the nature of the matter, that record might be neutral. In other cases (a regulatory investigation, a family dispute, a transaction covered by professional secrecy) it is not. The operator cannot resolve this tension, but it must acknowledge it.

The practical implication is that the operator should not present public payment records as a benefit of the namespace. The proposition to lawyers is professional identity and a way to be paid. How a lawyer uses those tools with any given client is a matter of professional judgment and of the conduct rules that bind that lawyer, not of namespace governance. A firm may reasonably decide that an onchain name is suitable for some matters and unsuitable for others. The operator’s documentation should be written on that basis and should say so.

There is a second confidentiality dimension: the operator’s own records. The operator knows which practitioners hold names and holds the evidence they supplied to qualify. Depending on jurisdiction, those records may fall under data protection law. The operator’s privacy policy and data practices need to be designed by counsel from the start, not added after the first inquiry.

Why a professional body is a more natural operator than a technology company

A technology company that acquires a legal-profession TLD faces a legitimacy problem. The namespace claims to represent a regulated profession, but the operator has no part in its governance. Practitioners who are cautious about onchain technology, as members of a profession built on care with client matters can be expected to be, will be harder to reach if the namespace is run from outside the profession’s institutions.

A bar association, a law society, or a specialist association that operates the namespace sits inside the trust the profession already has. Its decision to issue a name to a practitioner carries weight that a third-party company’s decision does not. Its decision to withdraw a name for disciplinary reasons is consistent with authority it already exercises. Its messages to members about the namespace travel through channels that are already believed.

A body also has a different relationship to revenue. A company needs the namespace to pay for itself and then to return something. A body can treat it as a member service, fund verification from existing staff, and accept slow growth. That patience matters in a sector where adoption will be gradual.

If the operator is a technology company or a platform, the most important single step it can take is to establish a formal advisory or governance relationship with one or more professional bodies before issuance begins. That relationship does not have to involve handing over control of the TLD. It requires a clear, written understanding of who vouches for eligibility and who can trigger a review of a name.

A professional body that wants the relevant string and does not hold it can mandate a desk to find and approach the holder, which is what a buy-side acquisition is.

Revenue from names: a worked example

Freename runs a royalty program for TLD holders. For each name registered under the TLD, the holder is paid a share of the registration fee. That share is advertised at up to half, and it depends on the registry’s terms in force and on the program’s activation conditions. The TLD itself carries no yearly renewal charge. Taking part in the royalty program is another matter: the registry sets an annual cost for it, which the figures below do not include and which you must deduct from them. Some TLDs were registered under earlier terms that include the program for life, and whether those terms pass to a buyer is a point to settle with the registry before closing. The Subname Revenue Calculator lets you model your own scenario. The example below is an illustration, not a forecast, and states every assumption.

Worked example, assumptions. The registration fee is USD 120 for a firm name and USD 60 for an individual lawyer’s name. The holder’s share of each registration fee is half, the advertised maximum, which actual terms may not match. In year one, 200 firm names and 400 lawyer names are registered. In year two, 100 new firm names and 200 new lawyer names are registered. No name is issued free. The royalty is counted on registrations only: nothing is counted for renewals of names issued earlier.

Year one:

  • 200 firm names at USD 120: USD 24,000 in registration fees, of which half is USD 12,000
  • 400 lawyer names at USD 60: USD 24,000 in registration fees, of which half is USD 12,000
  • Total year one royalty: USD 24,000

Year two, new registrations only:

  • 100 firm names at USD 120: USD 12,000 in registration fees, of which half is USD 6,000
  • 200 lawyer names at USD 60: USD 12,000 in registration fees, of which half is USD 6,000
  • Total year two royalty: USD 12,000
Worked example: royalty to the TLD holderUSD; holder's share assumed at half of each registration fee; firm names at USD 120, lawyer names at USD 60
Year one, 200 firm namesUSD 12,000
Year one, 400 lawyer namesUSD 12,000
Year one, totalUSD 24,000
Year two, 300 new namesUSD 12,000

Assumptions as stated in the text. The actual share depends on the registry's terms. Registrations only. Verification and support costs, which the operator bears, are not deducted, nor is the annual cost of the royalty program.

Two things stand out. The first is that income follows new registrations, so it falls when the first wave of interested holders has been served, as year two of the example shows. A namespace for a profession has a finite population, and an operator who budgets on year one repeating itself will be short.

The second is that the registration counts in the example are assumptions, and demanding ones. Every name in this sector has to be verified, adoption depends on active outreach, and volume usually needs an institutional channel. A new namespace without a professional body behind it should expect a far smaller first year than the example shows. Set the cost of verification, support and counsel against whatever figure your own assumptions produce. In this sector the namespace is more plausibly a service that covers part of its costs than a business in its own right.

The Launch Roadmap tool helps order the steps from the transfer of the TLD to the first issuance targets.

What to check before acquiring the TLD

Before any transfer, the operator should satisfy itself on five points.

First, the string. Does the word or phrase in the TLD actually signal the legal profession in the jurisdictions where you plan to operate? Some strings are clear. Others are ambiguous or carry different connotations across languages, and the profession’s own vocabulary changes from one legal tradition to another. A string that practitioners in the target jurisdiction would use to describe themselves is worth more than a generic one that needs explaining.

Second, trademark exposure. A string that matches a registered trademark for legal services is a problem to settle before closing, not after. A trademark protects a sign for particular goods and services in particular countries, so the answer depends on where you will operate. Your counsel should run a clearance search.

Third, the registry record. On Freename, a TLD exists as a token recorded onchain and sitting in a wallet. That record is open to the public, and a block explorer lets anyone look it up. Closing runs through onchain escrow on an aftermarket.

Fourth, resolution, seen from a client’s desk. Lawyers and their clients mostly use conventional browsers on managed office machines, where installing an extension may need approval from an IT department. An operator who presents the onchain name as a complement to a firm’s ordinary website, never a replacement for it, will have more credible conversations than one who overstates where names open.

Fifth, the operator’s own regulatory position. Running a namespace for a regulated profession may draw the attention of professional regulators in some jurisdictions, particularly where the use of professional titles is restricted. Take advice from your own counsel on whether operating the namespace creates any obligation where you are based or where you market.

Understanding how a TLD valuation is built before any price is agreed helps you test the price against realistic issuance, not against the most optimistic scenario.

A realistic first year

The first year of a legal-profession namespace is almost entirely about institutional groundwork, not volume. The revenue from names is secondary to building the conditions under which names mean something.

First-year operating sequence for a legal-profession TLD
  1. Complete the acquisition and settle custodyTake the transfer of the TLD through onchain escrow. Decide which wallet holds it and whether a multisignature wallet suits an institutional operator. Check what the royalty program requires before it is active.
  2. Draft and review the eligibility policyHave counsel draft the eligibility rules, the review procedure for a holder who loses the license, and the process for disputes. Do not open registrations without it.
  3. Approach one or two professional bodiesIdentify the bar association, law society or specialist body whose membership best matches the holders you want. Present the namespace as member infrastructure, not a technology product. Seek a formal endorsement or a co-issuer arrangement, and allow for the pace at which such bodies decide.
  4. Build the verification workflowConnect registration to a check of the public register or to a manual review. It need not be automated in the first year, but it must be consistent and documented.
  5. Run a closed pilot with a defined groupIssue names to a small group of firms and lawyers who understand the limits of resolution and will use the name to be paid and to publish a profile. Collect structured feedback before opening more widely.
  6. Open registration with clear documentationPublish the eligibility rules, the limits of resolution and the fees. Issue names to verified holders. Begin regular checks for holders who lose the license or leave the profession.
  7. Review at twelve monthsLook at the number of names, how the pilot group used theirs, how many disputes arose, and where the institutional partnerships stand. A small set of verified names and one endorsement is a stronger position than a large set of unverified names.

The technical side of putting a TLD to work after the transfer is the subject of post-transfer activation. The policy and partnership work in the steps above runs alongside it, and it stays with the operator: no registry does it for you.

Getting the TLD to the right operator

If you are a professional body or a platform that serves the legal profession and you do not hold the TLD you have in mind, the first step is to find out whether it can be acquired and on what terms. That conversation goes better through a structured process than through an unannounced approach, with confidentiality in place from the first exchange and the economics understood before any negotiation begins.

Hush Partners is a private desk for onchain TLDs. An organization can mandate it to find a holder and approach that holder on its behalf. A standard mutual NDA applies to all exchanges, one named partner stays with the file from the first note until closing, and closing takes place through onchain escrow on an aftermarket. The desk is reached through the contact form.

Before you write, settle two things internally: which body will vouch for eligibility, and who will carry the cost of verification in the first year. An operator who can answer both has a namespace worth acquiring a TLD for. The operators most likely to make this work are those who treat the profession’s regulated character as a design constraint, not an obstacle.

Questions people ask

That is a question for the practitioner’s own counsel and the relevant professional regulator, not for the namespace operator. Rules on where client funds may be held and how they must be identified vary by jurisdiction and are set by professional conduct rules. The operator should not represent that a name meets any requirement for client accounts. It issues an onchain name, not a regulated financial account.

What happens to issued names if the operator stops running the namespace?

The TLD is a token in a wallet, and only the wallet that holds it can issue names beneath it. If the operating organization dissolves or transfers the TLD, issuance and the rules pass to whoever holds the token next, or stop. What happens to names already issued depends on the registry’s terms, which you should read before you launch. An operator of a professional namespace should write down a succession plan, and a professional body is well placed to be named in it. Holders who have printed a name on their letterhead have a reasonable expectation that continuity is planned for.

Does running this namespace create a lawyer-client relationship between the operator and holders?

Issuing a name is not a legal service, and the eligibility check is an administrative step, not an opinion on the holder’s standing. Whether any duty arises is for the operator’s counsel to confirm under the law that applies. The operator’s terms should make the position explicit, and its communications should never imply that it vouches for a practitioner’s competence or conduct beyond the narrow question of whether the license was in force when checked.

Should a holder be able to pass a name to someone else?

In a namespace that signals professional standing, a name that moves to a person who was never verified breaks the representation the name makes. Decide before launch how your rules treat a transfer between holders, for example when a practice is sold or a lawyer retires, and require the new holder to pass the same check. Whether the registry lets an operator restrict transfers technically is a point to confirm in its terms. Where it does not, the rule lives in your policy and in your review process.

The Hush Partners desk

Notes from the desk. Written by the people who run the files.

Tell us what you hold. Quietly.

One named partner reads every request. Holders start with a private valuation. Organizations start with a confidential brief.