# Running a market TLD for wine and spirits
> For operators considering a TLD that names wine and spirits: who would hold a name under it, what they would use it for, and what running it involves.
Source: https://hush.partners/running-a-market-tld-for-wine-and-spirits
Category: Acquiring
Published by Hush Partners.
---
Wine and spirits is a trade built on names. The name on a label carries a reputation built over generations, a precise geographic origin, a vintage year, and in many cases a legal designation enforced by national law or international agreement. That weight makes a sector TLD plausible here in a way it is not in every industry. There are real actors who might want a name under `.yoursector`, and real things they would do with it. There are also real traps: protected origin names that must never be issued as ordinary names, and a secondary market in which doubts about provenance are a familiar concern.
This article works through all of it. By the end you should be able to judge whether a namespace in this sector has enough genuine users to justify acquiring and running a TLD, what policy choices the operator must make before the first name is issued, and what the first twelve months look like in practice.
## Who in wine and spirits would hold a name
The realistic population of name holders is narrower than it first appears. The trade produces a vast number of labels, but a TLD is not a label database. It is a namespace for actors who want a persistent onchain identifier they can use in several contexts: payments, a wallet address, a web presence, a reference in a record of custody. That population breaks into four groups.
| Holder type | Primary use | Depth of demand |
|---|---|---|
| Estate or domaine | Provenance anchor, payment address, collector contact point | Strong for engaged producers |
| Merchant or négociant | Payment routing, trade identity, invoicing between businesses | Moderate |
| Importer or distributor | Market-specific identity, payment settlement | Moderate to weak |
| Collector | Cellar identity, peer-to-peer secondary sales | Weak unless collectors are already organized |
Estates and domaines are the strongest candidates. A producer who already invests in traceability, who sells direct or through a mailing list, and who wants buyers to be sure that a payment address is really the estate's has a concrete reason to register `estate.yoursector`. The demand is real but selective. Not every producer needs this, and a producer inside a tightly regulated appellation may worry about how the name sits beside its protected designation.
Merchants and négociants buy, blend or age wine before selling it on. Their identity is commercial where the estate's is geographic. Demand here is tied to whether the merchant already settles any part of its trade onchain. A merchant who does not has little reason to start because a name exists.
Importers and distributors work under national licensing regimes that vary considerably from one country to the next. Their need for a sector name is weaker: they usually trade under one name in one market, and their payments to suppliers are covered by established banking arrangements. Some will register. Most will not unless the operator gives them a specific reason, such as a group of estates that asks its importers to be identifiable in the same namespace.
Collectors are the most uncertain segment. An individual collector has little practical need for a named onchain identity unless they trade bottles with other collectors or want to be recognized when buying direct from estates. A circle of collectors that already settles its trades onchain is a different matter, but that circle has to exist already or be patiently built by the operator.
## What a name does for each part of the trade
For an estate, the most immediate value is replacing a raw wallet address with a readable name wherever it receives payment. A buyer settling an allocation of a wine still in barrel, or a restaurant paying a direct invoice, can send to `estate.yoursector` and not to a long string of characters that nobody can check by eye. The estate can change the wallet behind the name without sending a new address to every counterparty. The name can also carry a short web record that points to the estate's own provenance documentation.
A sale in this trade rarely has only two parties. A broker introduced the buyer, a bonded warehouse holds the cases, a carrier moves them. [Payments to a name](/onchain-tld-payments) can reflect that. One example is [shaka](https://shaka.deal), an onchain payment router that lets a payment link pay out to a name where a raw address would otherwise be needed, with the division between the parties agreed and signed onchain before any money moves; it routes the funds and never holds them. For an estate that pays a broker's commission on each allocation, that is a practical convenience and not a novelty.
For a merchant, a name is a persistent trade identity that survives a change of wallet or of banking partner. A merchant with several lines of business may want more than one name under the TLD: one for its fine wine desk, one for its spirits bottlings. That is a legitimate request, and your policy should say in advance how many names one business may hold and on what grounds, because a merchant who collects names it does not use takes them away from the trade.
For a collector active in secondary sales, a name under the TLD is a modest credibility signal when approaching an estate for an allocation or another collector for a trade. On its own it is weak evidence of who someone is. Combined with a wallet that shows a visible history of settled purchases, it means more. The operator can strengthen it by setting conditions for collector names, such as an introduction by an estate or merchant that already holds a name.
For importers, the use is mostly payment settlement, and showing counterparties who care that the importer takes part in the onchain side of the trade. That is a thin case, and it is better to say so than to count importers in a forecast.
## Provenance and authenticity: what the namespace can and cannot address
Counterfeit labels, refilled bottles and false vintage claims are long-standing problems in this trade, and the incentive grows with the value of the bottle. A persistent onchain name does not solve this by itself: it cannot show that the liquid in a bottle matches the label. What it provides is a stable point of reference in a record of custody.
Consider what a credible provenance record requires. It needs to show that a specific lot left the producer's cellar, passed through identifiable intermediaries, and reached the current holder without unexplained gaps. An estate with a name under `.yoursector` can record the dispatch of a lot onchain from the wallet its name points to. A merchant who receives and resells can add a further recorded step. A collector who later sells can point to the same sequence. None of this strictly requires the TLD, but the TLD makes the identities in the sequence readable by people: the registry record is public, and anyone can look up on a block explorer which wallet `estate.yoursector` is attached to.
The limits deserve the same clarity. The record describes transfers between wallets, not the storage conditions of a case, and not whether a bottle was opened and refilled between two entries. It complements the paper trail, the condition report and the physical inspection that the fine wine trade already relies on. An operator who presents the namespace as proof of authenticity will be corrected by the first serious merchant in the room. An operator who presents it as a way to make one part of the trail harder to forge will be listened to.
The operator's contribution is the namespace and, if it chooses, a standard for what a provenance record made under that namespace should contain: which events are recorded, by whom, and with what reference to the physical lot. That is editorial work more than technical work, and it is where your knowledge of the sector matters most.
## Estates, vintages and merchants as distinct classes of name
A practical naming policy has to distinguish these three classes, because they carry different rights and different risks of abuse.
### Estate names
Estate names are the most valuable and the most contested. An estate name is typically also a trademark, sometimes registered, always in use. The trade adds a complication of its own: many estates share a family name, a village name or a common descriptive word, and several unrelated producers may have an honest claim to the same string. Before issuing an estate name, you need to know whether the applicant is the producer it says it is, and what you will do when a second producer with a similar name applies later. A name issued to the wrong party is a dispute waiting to happen, and in the wine trade it can also be a real commercial injury.
Two mechanisms are common in naming systems generally and fit this sector well. The first is a priority period before general opening, in which producers who can document their rights apply first. The second is a challenge process that lets a producer recover a name issued to someone else in error. Most operators will want both.
### Vintage and lot names
Vintage or lot names are more transactional. A name that designates one release of one wine is a record more than an identity. Such names are less contested, but they are also of little use to anyone other than the estate or merchant that asked for them, and they multiply quickly: a producer with several wines and a new vintage each year would need a new set of names every harvest. You may decide to support them, to limit them, or to leave lots and vintages to be described in the records attached to the estate's single name. The last option keeps the namespace small and legible, which is usually what a trade audience prefers.
### Merchant names
Merchant names cover a range from small négociants to large wholesale houses. The specific risk is a merchant, or anyone else, applying for a name that reads as an estate it merely distributes. A merchant who sells a producer's wine has no claim to the producer's name, however long the relationship. Your policy should say so in plain words and give the estate the priority and challenge routes described above.
## Protected origin names and the hard limits on registration
In wine and spirits, the name of a place is often a legal right in itself. Many countries protect designations of origin and geographical indications by law, and international trade agreements give the geographical indications of wines and spirits a particularly strong level of protection. These rights usually belong to no single producer. They are collective, they are defended by producer bodies and public authorities, and they often carry more legal weight than an ordinary trademark. The rules differ by country, and in many systems a protected origin name cannot be appropriated by one business as its own mark.
The same logic applies to a namespace. An operator who issues the name of a protected region as an ordinary name under `.yoursector`, to whoever applies first, is not only creating a collision. It is potentially enabling the commercial misuse of a protected designation. The legal exposure varies by jurisdiction. The damage to your standing with the producers you hope to serve does not vary: it is immediate.
The practical rule is this. Any term that is a protected geographical indication, a protected designation of origin or a controlled appellation in a jurisdiction that matters to your holders goes on a reserved list before the first name is issued. The list will not be complete on the first day, because the protected designations of the producing countries are very numerous and are recorded in separate national and regional registers. It must nonetheless be started, maintained and enforced. Near matches belong on it too: translations, common abbreviations, and a protected name combined with a generic word.
Reserving a name is not the only possible treatment. Some operators will want to keep origin names permanently unissued. Others may consider entrusting one to the body that legally represents the designation, on that body's request and never on the operator's initiative. Either choice is defensible. Issuing the name to a private applicant is not. This is the area where an operator who knows the sector has a real advantage over a generalist, and where a mistake creates the most serious problems later.
## Collectors, secondary sales and what the namespace provides there
In secondary sales, the price of a bottle depends heavily on the credibility of its ownership history, and that is where questions of provenance are sharpest. An onchain name does not replace the paper trail, but it can run alongside it and give each transfer a record that cannot be quietly rewritten afterward.
A collector who holds a name under `.yoursector` and settles secondary trades through it builds a public onchain record: transfers received, transfers made, the counterparties by name or by wallet, and the time of each. A later buyer can read that record directly.
That openness is also the main objection. Many collectors value discretion, and a public record of what passed through a wallet is not something every cellar owner wants attached to a readable name. Some will prefer a name that says nothing about who they are. Others will decline altogether. Your policy should allow the first and respect the second, and your forecast should not assume that serious collectors will welcome visibility.
The operator's role here is partly practical and partly curatorial. On the practical side, names must resolve where holders actually use them, and payment to a name must work when a sale involves a storage provider, an insurer or an intermediary who takes a commission. The curatorial side is a pair of decisions: whether collector names carry any verification requirement, and how you will treat a provenance claim made through a name under the TLD when someone contests it.
Demand from collectors stays uncertain unless you can point to an existing group that already settles trades onchain. Without that, collector registrations will be few in the first year, and an honest plan says so.
## The operator's role: rules, issuance, support and disputes
Running a TLD in this sector is a continuing commitment, not a single setup. The page for [operators](/operators) describes the role in general terms; what follows is specific to wine and spirits.
### Rules
The registration policy is the foundation. It must say who can register: any legal entity, only licensed producers and merchants, or only applicants who can document a trademark or a regulatory approval. It must say which names are reserved, how a challenge works, and what happens when a name changes hands or its holder ceases to trade. Estates are sold, merged and inherited, so the policy needs a rule for succession: whether the name follows the property, the company or the family. Publish the policy and keep its versions, so that a holder who registered under an earlier text knows how a change affects them.
### Issuance
Because you hold the TLD, you are on Freename the only party who can issue a name under it. In practice you either issue each name yourself after reviewing the application or arrange a process that lets applicants apply without you handling every case. For a curated holder base, reviewing each application by hand is reasonable in the first year. It lets you confirm that an applicant is the estate or merchant it claims to be, for instance by checking its licence or its entry in a producer register where one is public. The cost is speed: if demand exceeds expectations, manual review becomes a bottleneck.
### Support
Holders will ask questions that belong to this sector: how the name relates to their appellation status, whether using the name on a back label or a case stencil raises a labeling question, how to change the wallet the name points to. Labeling is regulated in most markets, so the honest answer to the second question is that their own counsel or their producer body decides. You need to be able to answer the rest, or know whom to send them to.
### Disputes
The UDRP, the Uniform Domain-Name Dispute-Resolution Policy, is the standard procedure for trademark complaints about domain names in the ICANN DNS. It binds registrants through the contracts of that system and does not extend to names issued under an onchain TLD. You therefore need your own dispute process, written into the registration policy. Before you promise any remedy, check what the registry's terms and tooling actually allow a TLD holder to do with a name that has already been issued. A policy that promises to withdraw a name is worth only as much as your ability to carry it out. In a sector where estate and merchant names are also trademarks, disputes will occur.
## Revenue from names: a worked example
The [Subname Revenue Calculator](/subname-revenue-calculator) builds a projection from your own assumptions. What follows is a separate worked example that shows the structure of the income and nothing more.
The assumptions are these. The TLD is a sector word in wine and spirits, held on Freename, where the holder of a TLD pays no annual renewal fee for it. The target holders are estates and merchants in one or two producing regions. The registration fee for a name, a price the holder of the TLD sets and may vary from one name to another, is assumed to be USD 120. Freename runs a royalty program that passes part of every registration fee for a name under a TLD to that TLD's holder; the program advertises a share of up to half, and the registry's current terms and activation conditions govern what is actually paid. The example takes the advertised maximum, half. It assumes 200 names registered in the first year, 80 in the second and 80 in the third. The royalty is counted on registrations only; the example assumes no income from renewals.
In year one, 200 registrations at USD 120 produce USD 24,000 in registration fees, of which the operator receives at most USD 12,000. In year two, 80 new registrations produce USD 9,600 in fees and at most USD 4,800 for the operator. Year three repeats year two. Over three years, 360 names have been registered, fees total USD 43,200, and the operator's share is at most USD 21,600.
Worked example: operator royalty by yearAssumes 200 registrations in year 1, 80 in each of years 2 and 3, a USD 120 registration fee and a royalty share of half, the advertised maximum
Year 1 (200 registrations)USD 12,000
Year 2 (80 registrations)USD 4,800
Year 3 (80 registrations)USD 4,800
Royalty counted on new registrations only. Operating costs, the annual cost of the royalty program and the price of the TLD are not included.
These are not forecasts. They are the arithmetic of stated assumptions, and the shape matters more than the amounts. Income follows new registrations, so it is highest when the pilot group and the first wave of estates arrive, and it falls once the natural holders in your regions have their names. Wine has a bounded population of producers in any given region. Growth after the first wave has to come from a new region, a new class of holder such as spirits bottlers, or a use that brings merchants in.
The example also leaves out every cost: verifying applicants, legal work on the reserved list and the dispute policy, support, and the price of the TLD itself. One of those costs comes from the registry: the TLD has no renewal fee, but taking part in the royalty program carries an annual cost that the registry sets, and it has to be deducted from each year's figure above. Some TLDs were registered under earlier terms that include the program for life, so if the one you are acquiring is among them, confirm with the registry before closing whether those terms pass to you. A realistic case sets those costs against the royalty, and in this sector the verification and legal work are heavier than in most. The page on [how a TLD valuation is built](/valuation) is the place to start for the acquisition price, which is the first figure to enter in that calculation. If the result only works with a registration count you cannot tie to named estates and merchants, treat that as the answer.
## What to check before acquiring the TLD
Acquiring a TLD comes before any income. The checks below are specific to wine and spirits; the service for [putting a TLD to work after the transfer](/post-transfer-activation) covers the general sequence.
### Does the word carry any protected status?
A sector word that is itself a geographical indication, a controlled appellation or a term reserved by a regulator in a market that matters may create legal exposure from the moment you operate it commercially. Traditional terms for styles, aging categories and production methods can be protected too, and a word that is generic in one country may be reserved in another. Have counsel who knows the sector's intellectual property rules check this before you proceed.
### Who are the natural registrants, and can you reach them?
An estate that has never heard of onchain TLDs will not register without a conversation. Before acquiring, identify a pilot group of potential holders, say twenty estates or merchants, and ask them plainly whether they would take a name and what they would use it for. If you cannot find that many who would consider it, the demand case is weak, and it is far cheaper to learn that before the acquisition than after.
### What does resolution look like for this holder base?
Onchain names live outside the DNS root that ICANN coordinates, which means a standard browser will not open one unless support has been added. Where a Freename name does work for a merchant or an estate's client is in Bitcoin.com Wallet, in MetaMask through Freename's resolver, and in desktop browsers once the Freename Web3 extension is installed. That coverage is partial and it changes. For estates and merchants who are not already at ease with wallets, this is real friction, and a restaurant buyer or a private client will usually reach the estate through its ordinary website. Be candid with holders about what works. For the detail, send them to the page on [what is live](/whats-live), where each working capability is listed with its source.
### Do you have the capacity to handle disputes?
With trademarks, shared family names and protected origin names all in play, disputes are not hypothetical. Confirm before acquiring that you have the legal resource and the time to handle them.
### Is the TLD available, and from whom?
You may not know who holds the TLD you want. An organization can mandate Hush Partners to find and approach the holder through [buy-side acquisition](/buy-side-acquisition).
## A realistic first year
The first year is mostly preparation and seeding. Income will sit below any optimistic projection, and the plan should assume so.
First-year operating sequence for a sector TLD in wine and spirits
Build the reserved listCompile the protected geographical indications, designations of origin, controlled appellations and regulated terms relevant to your target regions, with translations and near matches. Have specialist counsel review it. This work is complete before any registration opens.
Draft and publish the registration policySet out who can register, which names are available, how a challenge works, how succession is handled and what the operator will and will not do. Keep versions. Publish it before the first name is issued.
Onboard a pilot groupApproach the estates and merchants you identified before acquiring. Help each one set up a wallet if needed, explain what the name does, and issue the name yourself. This group makes the namespace credible to later applicants.
Open a priority period for producersBefore general opening, let producers who can document their rights apply for the names that match them. Time it away from harvest, when no estate has attention to spare.
Put payments to work for active holdersWork with the holders who want to be paid at their name. A settled allocation or a paid invoice is the clearest demonstration the namespace can offer to the rest of the trade.
Handle the first disputes carefullyThe first dispute, whether a trademark challenge or an error in issuance, sets how the operator is perceived. Resolve it by the published policy, document the outcome, and publish an anonymized summary so holders can see the process work.
Review the list and the policyAt the end of the year, review the challenges received and the near misses. Update the reserved list, issue a new version of the policy and tell existing holders what changed.
The calendar of the trade shapes all of this. Producers are unreachable during harvest and absorbed by the release of a new vintage. Trade tastings and fairs are where merchants and importers can be met in number. Plan outreach around those moments and expect whole months in which nothing moves.
The concrete next step comes before any acquisition: write the first version of your reserved list and hold the pilot conversations. Those two pieces of work cost little and tell you most of what you need to know. If they hold up, the [Launch Roadmap](/activation-roadmap) turns them into a dated plan. Where the TLD has to be acquired from a holder you cannot identify or would rather not approach yourself, Hush Partners acts under mandate for the organization that wants it: a standard mutual NDA covers each exchange from that first approach, and the closing is done on an aftermarket through onchain escrow.
## Questions people ask
### Can the TLD word itself be a geographic wine term?
It should not be a protected geographical indication or designation of origin. A generic sector word, such as a trade category or a production term that is not itself protected, is safer ground. Even then, ask counsel: some terms that look generic, including certain grape and style names, are protected in particular jurisdictions.
### How does a name interact with an estate's existing web presence?
A name under `.yoursector` does not replace a conventional domain name in the ICANN DNS, which remains simply better for a public website that any visitor must be able to open. The two coexist. The onchain name serves payment, wallet resolution and provenance records; the conventional domain serves the estate's public site. Holders who want to publish pages through their onchain name can read about [websites on an onchain TLD](/onchain-tld-websites) first, and should understand that visitors need a browser or wallet that supports it.
### What happens to a name when its holder stops trading?
This is a policy question before it is a technical one. Your policy should state what you intend: whether the name is kept out of circulation for a period, offered first to a successor of the estate, or opened to new applicants. For estate names that are also trademarks, opening them at once to any applicant invites confusion, so a holding period is a sensible default. Check what the registry's terms allow before you commit to any of these.