Running a market TLD for the art market
For operators considering a TLD that names the art market: who would hold a name under it, what they would use it for, and what running it involves.
The art market runs on identity. A gallery’s name is its reputation. An artist’s name is their work. An adviser’s name is their relationships. Yet onchain, those same actors are a long wallet address, a string of characters that tells a collector nothing and tells anyone who looks it up more than its owner would choose to share. A sector TLD, a short sector word recorded onchain as a top-level domain, lets an operator issue names that carry meaning inside the market and give each participant an address a counterparty can read.
This article is for someone considering whether to acquire such a TLD and run it as a namespace for artists, galleries, art advisers and collectors. It covers who would actually register a name and why, what the operator has to build and maintain, how revenue works, and what to verify before committing. It spends most of its space on what is particular to art: the provenance problem, the relationship between a gallery and the artists it represents, the discretion collectors require, and the commission structures with several parties that sit behind a sale.
Who in the art market would hold a name
Four groups have a plausible reason to register. They are not equally strong, and being honest about that is the starting point for any realistic plan.
| Holder type | Primary use | Demand strength |
|---|---|---|
| Artists | Stable identity for payment and portfolio links | Strong for digitally active artists |
| Galleries | Institutional address for invoices and collector contact | Moderate; varies with gallery size |
| Art advisers | Clean payment address for shared commissions | Strong once payment routing is in place |
| Collectors | Pseudonymous receiving address; discretion first | Weak to moderate; opt-in audience only |
Artists who sell work onchain, issue certificates of authenticity digitally, or work with several galleries are the most natural registrants. They already operate with a wallet; a name that resolves to that wallet is a direct improvement. An adviser who shares commissions with other parties has a concrete operational reason: a name is an address every party to a deal can read and check, where a raw address invites copying errors and a bank transfer leaves the split to whoever receives the money first. Galleries and collectors follow with more conditional demand.
The table also shows who is missing. An artist who sells only through one gallery, is paid by bank transfer and has no wallet has no use for a name until something else changes. That describes a large part of the market, and no registration rule or launch campaign alters it. A plan that counts every working artist as a prospect is counting people who have no reason to register.
What a name does for artists, galleries, advisers and collectors
Artists. The most immediate function is a payment address a person can read. When a collector or a gallery sends proceeds, typing name.yoursector is less error-prone than copying a raw address. Beyond payments, a name functions as a stable pointer: it can resolve to a portfolio page published under the same namespace, or to a certificate of authenticity stored on IPFS (a decentralized file-storage network). The name itself does not move when the artist changes wallets; the record can be updated to point to a new address while the name stays constant.
Emerging artists gain something a mid-career artist may not need as much: a namespace that signals they belong to a sector with entry rules, where a bare wallet address signals nothing. If registration requires a basic credential check by the operator, the name carries implicit vetting.
Galleries. A gallery uses its name as a clean endpoint for invoices to collectors, for settlement with other trade counterparties, and for incoming consignment payments. Publishing one name also lets the gallery keep its operational wallets apart from its public address, which matters for internal accounting. For a gallery that sells nothing onchain, the name is a reservation of its own identity in the namespace and little more, and you should expect such galleries to register late or not at all.
Art advisers. An adviser typically sits between a collector, a selling gallery, and sometimes a second adviser or finder. A single sale can involve three or four parties who each expect a share. The conventional route is a sequence of bank transfers with the lead party redistributing by hand, which is slow, open to dispute and opaque to everyone downstream. A payment that goes out to names under a split fixed in advance removes the redistribution step. shaka is an onchain payment router built on that idea: its payment links can pay out to names where a raw address would otherwise be needed, the parties agree and sign their split onchain before any funds move, and the router passes funds along without holding them. For an adviser whose income arrives through this kind of structure, the name is the settlement address, not a badge.
Collectors. Demand here is the weakest and the most driven by privacy. A collector who buys work onchain may want a name that receives payment for a consignment or a resale without handing every counterparty a raw address to copy. The operational case is narrower than for the other three groups, and some collectors will see no need for a name at all. Plan for collector registrations as a secondary flow, not a primary one.
Attribution and provenance: the art market’s specific case
Every sector has identity needs. The art market has them in a particular form because the chain of custody for a physical or digital work is itself a commercial and legal asset. A work with clear provenance sells more easily, insures more cleanly, and travels across borders with fewer complications. A work whose chain of ownership is ambiguous loses value.
An onchain name can sit inside that provenance record without replacing it. When an artist issues a certificate, an onchain record stating that a specific work was made by them, the wallet it comes from is the identity anchor, and the name that resolves to that wallet is what a reader of the certificate actually recognizes. A name held under a namespace whose operator has done a basic identity check on registrants carries more evidentiary weight than a raw address that anyone could have generated. The registry record is public and can be looked up on a block explorer; the operator, for its part, can say who applied for the name.
This is not a legal authentication system and the operator should not represent it as one. Attribution in the art market rests on expert opinion, documentary history, catalogues of an artist’s work and, at times, technical examination. A name adds none of those. What it provides is a persistent, machine-readable link between a name and a wallet that can be referenced in provenance documentation alongside other evidence. Your own counsel should advise on how much weight that carries in a given jurisdiction.
The same limit shapes your rules. If a name under .yoursector is going to appear in provenance files, the cost of issuing an artist’s name to the wrong person is much higher than in a namespace where names are only labels. A wrongly issued name can end up attached to certificates that circulate long after the name is canceled. This is the strongest argument for checking identity before issuance for artist names, even if you apply a lighter process to other registrants.
Resale royalties are a further point specific to art. In a number of jurisdictions, artists have a statutory right to a share of the proceeds when their work is resold; the rules vary by country and your counsel decides what applies. Where no such right exists, some sellers and galleries agree a share voluntarily. In both cases the practical obstacle is the same: someone has to know where to pay the artist, often years after the first sale. A stable name such as name.yoursector, which the artist can repoint when they change wallets, gives the parties to a later sale an address that stays valid.
The gallery and the artists it represents
A gallery represents artists under exclusive or non-exclusive arrangements. A namespace for the sector has to take a position on that relationship, and a general-purpose TLD never faces the question.
The cleanest model is the one where the gallery holds its own name and the operator issues artist names directly to individual artists. The gallery and the artist each hold their own records; neither controls the other’s name. This keeps the namespace clean if the representation ends: the artist’s name stays with the artist, the gallery’s with the gallery.
A more complex model has the gallery apply for names on behalf of its artists and keep them in the gallery’s wallet. It is convenient at the start, because one application covers a whole roster and artists who have no wallet are not left out. It also concentrates control with the gallery. If the representation ends, the question of who holds the artist’s name becomes your problem as operator. Your rules must say whether a gallery may hold a name for an artist, under what conditions, and how the name passes to the artist when the relationship ends or the artist asks for it.
The practical recommendation: issue each name to the person or legal entity it identifies, not to an intermediary. Keep the terms of representation in the representation contract, not in who holds which name. Where a gallery wants to present its artists together for marketing purposes, that is a legitimate use of a portfolio or landing page under the gallery’s own name, and no reason to put artists’ names in the gallery’s wallet.
Two cases need a rule of their own. An artist represented by several galleries in different territories should still hold one name; the galleries refer to it and none of them owns it. An artist’s estate, or the foundation that manages a deceased artist’s work, is the natural holder of that artist’s name, and the application should come with evidence of that standing. Homonyms are common enough among artists that the rules should also state how two applicants with the same name are told apart, for example by a qualifier agreed with the later applicant.
Discretion of collectors, and what the operator can and cannot offer
Collectors are the most privacy-sensitive group in the market. Their buying patterns, the artists they follow, the prices they pay and the scale of their collection are commercially sensitive, and occasionally a matter of personal security.
An onchain name does not provide more privacy than a raw address. The name resolves to a wallet, and the wallet’s history is public on the chain. If anything, a name is easier to remember and to repeat than an address, so a collector who registers under their own name makes their wallet easier to find, not harder. What a namespace can offer is a label that is not the collector’s legal name: you can decide in your rules to accept a pseudonym or the name of a holding vehicle. You can permit this without endorsing opacity, provided you have done basic identity checks at registration and keep them where a lawful request can reach them.
What the operator cannot offer is anonymity. Records in the registry are open to anyone with a block explorer, and you hold the mapping between the registered name and the applicant’s identity. That mapping is the most sensitive thing you will keep: it deserves restricted access, a retention policy and a clear statement to registrants of when it can be disclosed. Data protection rules differ by country, and counsel should review how you store it. Collectors who need strong anonymity should take their own legal and operational advice. Your responsibility is to be clear about what the namespace does and does not provide, and not to oversell it.
This is also where weak demand should be admitted. Many collectors transact through advisers, galleries and holding structures precisely so that their own identity stays out of the paperwork. For them a name adds a record without adding a benefit, and the adviser’s name is the one that matters in the transaction.
Payments and commissions among several parties
An art sale of any significance typically involves more than two parties. Consider an invented case: a collector buys from a gallery; the gallery represents an artist who is owed a share of the primary sale; an adviser introduced the collector and is owed a fee; a second adviser co-brokered and is owed part of that fee. Four parties are waiting on one payment.
Under a conventional bank transfer, the gallery receives the full amount and redistributes. The redistribution depends on the gallery’s willingness and speed. The downstream recipients are paid when the gallery pays them, and what they hold is a contract or an exchange of messages, not a record that sits with the payment itself.
Where the parties hold names under the namespace and use a router for payments to a name, the payment goes out to names, and the split is agreed and signed onchain before funds move. The agreement is on record before the buyer pays, and it is the same record for everyone.
This does not eliminate disputes about whether the underlying commercial terms were correctly stated, or about whether a fee was owed at all. It narrows the kind of dispute where one party says the split was never agreed, or that the shares were changed after the fact. For an adviser whose practice depends on commission income from transactions they do not control, that is a material change.
Be realistic about scope. This applies to sales settled onchain, and most art sales are not. A gallery that invoices in its own currency and is paid through a bank gains nothing here. The payment case is real for the part of the market that already settles in digital assets and it is hypothetical for the rest, so measure that part among your own contacts before you build a plan on it.
You do not need to build the payment infrastructure. You need names that resolve correctly to wallets and documentation that tells registrants which tools support resolution.
The operator’s role: rules, issuance, support, and disputes
Running a namespace is not the same as holding a TLD. A holder who takes no action keeps the token in a wallet and does nothing else. An operator who issues names to third parties has taken on a set of responsibilities that grow with each name issued.
The operator sets the registration rules: who may register, what identity verification is required, what names are reserved (names of well-known artists and galleries, and common words that could be used deceptively, such as terms suggesting authentication or appraisal), and what conduct leads to suspension or cancellation. These rules need to be written, published, and applied consistently.
Issuance is the registry function: checking applications against the rules, issuing the name to the correct wallet, and keeping a record of the application. A Freename TLD lets nobody but its holder issue names under it, so the operator and the TLD holder must be the same entity or be bound by a clear contract.
Support means answering registrants who cannot resolve their name, who need to update their wallet address, or who want to transfer their name to a new owner. In this sector, expect many of those questions to come from gallery staff and studio assistants acting for the registrant, which means your procedures must say who is allowed to ask for a change.
Disputes are the most demanding part. A name that conflicts with a trademark, a gallery name that was issued to the wrong applicant, or a name used in a fraud attempt all require a documented process and a decision-maker. Have a dispute procedure in place before the first name is issued, not after the first complaint arrives.
The page for operators is written for organizations that run a market TLD as a namespace. The Launch Roadmap tool builds a launch plan for a newly acquired TLD, which is a useful frame for putting these duties in order.
Revenue from names: a worked example
On Freename, the registry runs a royalty program: when a name is registered under a TLD, part of the registration fee goes to that TLD’s holder. For an operator in the art market, the advertised figure is a share of up to half, and what a given TLD receives depends on the registry’s current terms and activation conditions. The royalty applies to registrations, so the example below counts registrations only and assumes no income from renewals. The TLD itself carries no yearly renewal fee, which keeps the cost of holding it low while the namespace grows slowly. The royalty program is a separate matter: taking part in it carries an annual cost set by the registry, which the figures below leave out and which has to be deducted from them. A gallery group or art-market operator acquiring a TLD that was registered under earlier terms may find the program included for life in those terms, as it is for some TLDs; whether they pass to the buyer has to be confirmed with the registry before closing.
The following is a worked example. Every assumption is stated and the figures are illustrative, not a forecast. Use the Subname Revenue Calculator to run numbers against your own assumptions.
Assumptions. The registration fee is USD 60 per name. The holder’s share is half of each registration fee, the upper end of what is advertised; actual terms may be lower. In year one, 200 names are registered. In year two, 150 new names are registered.
Year one. 200 registrations at USD 60 come to USD 12,000 in fees. The holder’s share, at half, is USD 6,000.
Year two. 150 new registrations at USD 60 come to USD 9,000 in fees. The holder’s share, at half, is USD 4,500.
Worked example only. Registrations only; no renewal income is counted. The actual share depends on the registry's current terms and activation conditions.
These are small numbers, and the second year is smaller than the first because the anchor registrants have already registered. Over two years the example yields USD 10,500 for the holder, before the program’s annual cost and the cost of identity checks, support and counsel. On these assumptions the namespace is not a revenue business; it is a credibility and utility asset for the operator. Do not acquire a TLD on the expectation that income from names will cover the acquisition cost. For an operator already active in the sector, such as a gallery group, an art fair organizer or an advisory firm, the value comes from the utility and affiliation the namespace creates, and the registration fees are a contribution to running costs.
What to check before acquiring the TLD
The decision to acquire a sector TLD is not only a question of whether demand exists. It is a question of whether the specific word you are acquiring is the right one, whether it is clean to hold, and whether you are the right operator.
The word itself. A sector TLD should be a word that the art community recognizes and uses without explanation. A word that names one medium or one segment excludes potential registrants: a term that suits painters may mean nothing to a dealer in photography or design. A word in a single language limits international uptake in a market that is international by habit. Generic words may also conflict with trademarks in one or more jurisdictions. Have the word checked against trademark registers in the countries where your intended registrants operate; your counsel advises on the risk.
Existing conflicting uses. If the word is already in use as a brand, a domain name or the name of an organization in the sector, acquisition creates a conflict that will surface in disputes. Find these before you commit. They also bear on price, and the page on how a TLD valuation is built explains what goes into one.
The TLD’s current state. Find out whether names have already been issued under the TLD, to whom, and under what conditions. A TLD with existing names has existing obligations, and in a namespace meant to carry artists’ identities, a handful of names issued without checks is a liability you inherit. The page on what works with onchain TLDs lists the capabilities you can rely on, with sources.
Your own position. Ask whether you have the relationships to seed registrations in the first months, the staff time to run support and disputes, and the legal support to publish and enforce registration rules. An operator who cannot answer yes to all three should consider whether to proceed alone or with a partner. Neutrality matters too: a namespace run by one gallery group will be read by competing galleries as that group’s project, and an association or a fair may find it easier to be accepted as a neutral issuer.
The acquisition path. A TLD that is already held changes hands by agreement with its holder, and a holder who has not offered it has to be found and approached. The buy-side acquisition service is for organizations that mandate a desk to do that on their behalf. A plan for putting the TLD to work after the transfer should be in place before closing, not drafted afterwards.
A realistic first year
The first year of running a market TLD is operational, not commercial. The revenue is small. The work is significant. The value is in establishing that the namespace means something to the people whose names are in it.
- Close and transferAcquire the TLD through onchain escrow on an aftermarket. Confirm on a block explorer that the registry record shows the TLD in your wallet. Check that resolution is working before announcing anything.
- Draft and publish the registration rulesDefine who may register, what identity verification is required, which names are reserved, and what the dispute procedure is. Have counsel review the rules before publication, and refer to them in every registration confirmation.
- Reserve the key namesIssue reserved names to their rightful holders or hold them under a documented reservation policy. Names of well-known artists, estates and galleries, and sector words that could be used deceptively, should be settled before open registration begins.
- Seed with anchor registrantsApproach a small group of artists, galleries and advisers whose presence shows that the namespace is in use. Document the identity checks you have done for each. These names are your proof of concept.
- Open registration with a managed queueDo not open to all comers at once. A managed queue lets you catch conflicts and identity issues before they become disputes. Process applications in batches and respond within a defined window.
- Make names usable for paymentCheck that names resolve to wallet addresses in the environments where your registrants transact, and document the wallets and tools that support them. This is the point at which the namespace moves from identity to utility.
- Establish support and dispute channelsOne responsible contact, a defined response time and a written procedure for disputes. These do not need to be elaborate in year one. They need to exist and to be applied consistently.
- Review the rules at mid-yearBy then you will have seen the edge cases the rules did not anticipate. Revise with counsel, notify existing registrants of changes, and keep a public record of what changed.
The step to take first
Before any of this, test demand by hand. Write down the names of the artists, galleries and advisers you could ask in person, and ask them two questions: whether they receive or send payments onchain, and whether they would use a name under .yoursector if it existed. If fewer of them say yes than your plan needs as anchor registrants, the plan is not ready, whatever the TLD costs.
If the answers hold up and the TLD you want is held by someone else, that is where Hush Partners comes in. The desk acts for organizations that mandate it to find and approach a holder; one named partner follows the file from the first note to closing, and a standard mutual NDA covers every exchange. The desk is reached through the contact form.
Questions people ask
Does an onchain name replace a conventional website domain?
No. Onchain names are resolved outside the ICANN DNS root, which means an ordinary browser will not open them unless support has been added. For Freename names, that support exists in Bitcoin.com Wallet, in MetaMask through Freename’s resolver, and in desktop browsers through the Freename Web3 extension. Coverage is partial and changes. For a public website that collectors or the press will visit, a conventional domain in the DNS remains the right choice, and here the DNS is simply better. The onchain name adds a payment address and a wallet-linked identity alongside it.
Can the operator prevent a gallery from registering an artist’s name without their consent?
The rules can and should require that an application for a name corresponding to an identifiable living artist be made by that artist or with their consent. Enforcing this requires a process: a declaration at registration, a period in which the named artist can object, and a clear cancellation procedure if consent cannot be verified. Without these, the namespace will face disputes it could have avoided.
Is the TLD useful if only some wallets resolve its names?
Partly. A name is useful for payment wherever the payer’s wallet or tool supports it, and that is the function advisers and galleries value most. A name cited in provenance documentation can be checked on a block explorer whether or not a browser opens it. Be honest with registrants about what works and what does not; overstating resolution coverage damages trust in the namespace more than the technical limits do.
What happens to names if the operator stops running the registry?
The TLD is a token in a wallet and does not disappear if the operator becomes inactive. Names already issued remain on record. What stops is new issuance, support, and the handling of disputes, and the identity records you kept still need a responsible custodian. An operator considering winding down should plan a transfer of the TLD to a successor willing to honor the published rules, give registrants notice, and take advice on whether and how registration records can pass to that successor.
