Running a market TLD for education: who it serves and how
For operators considering a TLD that names education: who would hold a name under it, what they would use it for, and what running it involves.
A sector word held as an onchain TLD can function as a shared namespace for the institutions, networks and learners that belong to that field. Education looks like a natural candidate. It is structurally diverse and full of parties with a plausible reason to hold a persistent identifier: schools, colleges, professional training providers, alumni networks, credentialing bodies and, eventually, the learners themselves.
The question for a prospective operator is not whether the sector exists. It is whether the namespace has real users, what those users would actually do with a name, and what running the TLD requires. This article works through each of those questions in the order an operator needs to answer them, from who registers down to the first year of operation.
Where resolution, payments or credentials enter the picture, the answer depends on what works now, not on what the technology may eventually support. The article keeps that distinction in view throughout, and it says where demand in education is weak.
Who would hold a name under .yoursector
Three groups account for most plausible registrations.
| Holder type | Example name | Primary reason to register |
|---|---|---|
| School or college | school.yoursector |
Readable identity for wallets and payments |
| Alumni network | classof.yoursector |
Cohort address that outlasts committee changes |
| Training provider | course.yoursector |
Named issuer for course completion records |
Schools and colleges are the anchor group. An institution that already has a conventional domain may still want an onchain name for functions the DNS does not serve natively: receiving donations in digital assets, or issuing credential tokens that point back to the institution by name instead of by a raw hexadecimal address. A readable name such as school.yoursector, in place of a long string of characters, reduces errors in payment flows. It also makes the institution’s onchain activity easier to audit for anyone who can use a block explorer, the public website that displays what a blockchain records.
Alumni networks are a distinct category because they are structurally separate from the institution they come from. A class association is usually run by volunteers, and its conventional domain often sits in the personal account of whoever set it up. When that person steps back, the address can lapse. An onchain name held in a multisignature wallet, one that requires agreement from several keyholders before anything moves, is tied to the committee and not to one member. That continuity is the specific value for a network governed by volunteers.
Training providers sit between the two. A provider that delivers continuing professional development or compliance courses has a commercial reason to make its certificates easy to tell apart from those of others. A name under .yoursector that the provider holds becomes the identity under which it issues completion records, a point developed further below.
Where demand is weak
Be honest with yourself about the parties who will not register. A primary or secondary school with no digital-asset activity has little use for an onchain name: its parents pay by bank transfer, its pupils are minors, and its website already lives in the DNS. Public institutions bound by procurement and treasury rules may be unable to accept digital assets at all, whatever the name looks like. Individual learners will not seek out a name on their own; they will hold one only if an institution they trust gives them a reason.
That leaves a narrower market than the size of the sector suggests: institutions with an endowment or fundraising office open to digital assets, alumni bodies with an active committee, and commercial training providers whose certificates carry weight with employers. An operator’s plan should be built on those three, not on every school in a country.
What a name does for each holder, concretely
The useful functions differ enough from one holder type to the next to be worth separating.
Schools and colleges. The most immediate use is receiving payments to a name instead of a raw wallet address. A sponsor funding a scholarship can pay school.yoursector through a payment router such as shaka, where the payment link points to the name. The router passes funds on and never keeps them, and the parties agree and sign the split onchain before any money moves. That suits a gift shared between a scholarship fund and a department, or a project run jointly by two institutions. The name also anchors the school’s wallet identity: when the institution issues an attendance token or a completion record, the record carries a readable origin in place of an anonymous address.
Alumni networks. The primary use is persistent group identity. A cohort name like classof.yoursector can serve as the payment destination for reunion fees and class gifts, and it gives the network one stable address even when the committee behind the wallet changes. In a wallet that supports the registry’s resolver, a member sending a contribution types a name and not a string of characters. Whether that member’s wallet is one of the supported ones is a separate matter, covered under resolution below.
Training providers. The richest use is credential issuance. A provider that holds course.yoursector can issue a completion token from the wallet that holds the name to each learner who passes. An employer who inspects the token sees which wallet issued it and can look up the name that wallet holds. Because the registry record is public, anyone can confirm on a block explorer that the name exists under the TLD and where it sits. That does not remove the need for the provider to publish, on its ordinary website, which name is its own; it does give verifiers a second, independent place to look.
Lifelong identity and credentials after graduation
A name that outlasts the student account
The strongest long-term case for education names is persistence after graduation. An institutional email address is often closed some time after a student leaves. The record of their studies sits in a database they cannot export. An onchain name held in a wallet the graduate controls stays with them for as long as they keep the wallet.
This matters most for professional credentials. A person who completed a program in healthcare, finance or engineering may need to demonstrate that credential at job applications and audits for years, sometimes decades. If the issuing institution closes or migrates its systems, a credential stored only in its database may become hard to verify. A credential held as a token in the graduate’s wallet, recording the issuer and the program, does not depend on the institution’s systems remaining online in the way a certificate lookup page does.
Under the registry rule that only the holder of a TLD can issue names under it, a graduate’s name comes from the operator, not from the school. The sensible design is that the operator issues a graduate name only on the confirmation of the institution concerned, and that the naming convention keeps institutional names and personal names visibly distinct. An institution might hold school.yoursector; a graduate holds a personal name issued at the institution’s request. The operator’s public rules should state which patterns are reserved for institutions, so a personal name can never be mistaken for an official one.
Demand here is unproven, and you should treat it that way. A graduate gains from a lifelong name only if employers and licensing bodies are willing to look at it. Until they are, the name is a convenience for alumni giving and little more. Plan for graduate names as a second phase that follows institutional adoption, not as the opening market.
Who may attest a credential
An onchain credential is a token issued to a wallet address, typically carrying a few details: the issuer, the program, and any expiry condition. The credential derives its value from the issuer’s standing, not from the technology. A name under .yoursector does not confer accreditation, and the operator should say so plainly in the registration rules.
The parties best placed to issue credentials in this namespace are those with existing authority to do so: accredited institutions, licensed training providers, and professional bodies that already issue certificates in the conventional sense. The namespace extends their reach onchain. It does not create new authority, and recognition rules differ from one country to another.
Attestation by third parties is a related question. A professional body might want to attest that the holder of a given name is licensed to practice, without having issued the original qualification. That attestation can live as a separate token sent to the holder’s wallet. The operator does not need to run this technically; the namespace only provides readable addresses. What the operator does need is a rule about who may present a name as that of a credential issuer. A fraudulent certificate issued under a name that appears to belong to a legitimate institution harms every other holder under the TLD.
The answer is institutional onboarding. Before issuing a name at the institutional level, the operator checks that the applicant claiming to be an accredited school or licensed provider is one, using the public registers that exist in the applicant’s country. That check is manual, slow and the core of the product. A namespace in education is worth exactly as much as the confidence a verifier can place in the names that claim institutional status.
Donations and fees paid to a name
Education depends on donations, alumni giving and course fees, and all three can be sent to an onchain name. For an operator, this is the main argument for adoption: a holder has a financial reason to put the name to use, because it opens a payment channel its supporters can reach.
A payment addressed to a name is less error-prone than one addressed to a copied string, and the transfer is visible onchain. An institution can print its name in fundraising materials and invite donors who already hold digital assets to send directly. The onchain record confirms the transfer, which helps a development office reconcile gifts without chasing screenshots.
For training providers, course fees are the more relevant flow. A learner pays course.yoursector and, on completion, receives a credential token from the same named party, so payment and credential share one visible origin. Providers that already collect periodic license or membership fees from practitioners will recognize this as an extension of an existing workflow, not a new one.
Three limits belong in your own planning. First, receipts: a donor who wants a tax receipt still needs one from the institution in the ordinary way, and the rules on gifts of digital assets vary by country. The institution’s own counsel and accountants decide how such gifts are recorded. Second, restricted funds: a gift earmarked for a purpose needs the same internal controls onchain as off it, and a readable name does nothing to enforce them. Third, readiness: a school whose governors have never discussed digital assets will not receive such donations in its first year under the namespace. Payment to a name is among the capabilities documented on the page that lists what works now, but adoption inside any one institution depends on that institution’s own treasury policy.
Minors and privacy: what an operator must not do
Education is the one sector where a large share of the end users are children. That changes what an operator may responsibly build.
Most countries have laws that restrict the collection of personal data from children, usually requiring the consent of a parent or guardian below a certain age. Many also have separate rules protecting student records, which limit what a school may disclose about a pupil and to whom. The details, the age thresholds and the enforcement bodies vary by country. The common principle does not: data about a child, and data about a student’s education, are treated more strictly than ordinary personal data.
The design consequence is simple. The namespace issues names to institutions and to adults, never to pupils. An operator should not accept a request, even from a school, to issue names that identify individual children, whether by full name, class or student number. A name that reads as a child’s identity and sits in a public registry cannot be made private afterwards.
Data protection law adds a second layer in many jurisdictions. An onchain name is a public record. Connecting it to a living person’s data may bring the operator within the scope of rules on personal data, including rights of erasure that a public blockchain cannot easily honor. The cautious design keeps verification documents off the blockchain entirely, stores only what the operator needs to confirm an institution’s status, and deletes it on a stated schedule.
There are four things an operator in this sector should rule out in writing. No names for anyone below the age of majority in their country. No publication of class lists, cohorts of named individuals or graduation rolls as names. No marketing directed at pupils. No use of a school’s verification file for any purpose other than verification. Each of these is easier to promise at launch than to retrofit after a complaint from a parent.
Adult graduates are a different case, since they can consent for themselves. Even so, a personal name should be opt-in, requested by the graduate, and free of any detail (a date of birth, a student number) that the graduate did not choose to make public.
The operator’s role: rules, issuance, support, disputes
Running a market TLD is not purely a technical exercise. The operator decides which names are issued, under what conditions, and what happens when something goes wrong.
Rules. The operator needs a registration policy that covers at least: who may register (the categories of eligible holder), what names will not be issued (names that imitate an institution, offensive strings, strings that conflict with trademarks), how eligibility is verified, and what happens if a holder loses access to its wallet. In education, add the reserved patterns for institutions and the exclusion of minors. The rules should be public and stable, because registrants make decisions based on them.
Issuance. Because the registry lets nobody but the TLD holder create names under a TLD, every name passes through the operator. For an education namespace that is an advantage: the operator issues institutional names one by one after verification, and open self-registration is not on offer. That means a workflow of application, verification, issuance and record-keeping. Volume will be low at first, which is manageable, but the process must be documented so that a second person can run it.
Support. Schools change bursars, alumni committees rotate, and providers merge. Holders who lose wallet access or need to move a name after a merger need a clear path. Decide in advance what you can do. An operator cannot reach into a holder’s wallet, so the options are limited to what the registry supports, and holders must be told this before they register, not after a key is lost. Recommending a multisignature wallet to every institutional holder is the most useful single piece of support advice.
Disputes. A name registered in bad faith, for example one that imitates a real school to collect donations, causes direct harm. The operator needs a way to receive complaints, a standard of evidence, and a stated outcome. The UDRP, the dispute policy that binds registrants of conventional domains through their registration agreements, was not written for onchain names and does not reach them. A complainant can still turn to the registry’s own terms or to a court, but the operator’s rules are the first and fastest route. Before promising any remedy, confirm with the registry what can be done about a name once it is issued, and write the policy around that answer.
Verification before issuance is the better protection. A dispute process deals with harm after it has happened; a careful check of each institutional applicant prevents most of it. The page for operators on this site sets out how running a market TLD as a namespace differs from simply holding one.
Revenue from names, modelled honestly
On the Freename registry, a royalty program gives the holder of a TLD part of every registration fee paid for a name under it. Up to half is the share the registry advertises, and what an education operator receives depends on the registry’s current terms and on activation conditions. Read those terms at the source before you model anything.
Worked example. Every figure below is an assumption chosen to show the arithmetic. None is a registry price or a forecast.
- Registration fee per name: USD 20
- Royalty share: half of the registration fee, the advertised ceiling
- Operator’s royalty per registration: USD 10
- Names issued in year one: 80, a pace consistent with manual verification
- Names issued in year two: 200, assuming active outreach to institutions
- Operator’s verification time: one hour per institutional name
| Period | Names issued | Royalty to operator |
|---|---|---|
| Year one | 80 | USD 800 |
| Year two | 200 | USD 2,000 |
| Two years | 280 | USD 2,800 |
The result is modest, and the last assumption shows why. At one hour per name, year one takes 80 hours of verification and returns USD 800, which is USD 10 for each hour of work before any other cost. Year two takes 200 hours for USD 2,000, the same rate. In this example the royalty does not pay for the verification that makes the namespace credible. The one cost that does not weigh on the model is holding the TLD: a Freename TLD carries no annual renewal fee. Taking part in the royalty program is another matter. It carries an annual cost set by the registry, which is not included in the figures above and must be deducted from them. An association or platform buying an existing education TLD should also know that some were registered under earlier terms with the program included for life, and should confirm with the registry before closing whether those terms pass to it as buyer.
The case for a .yoursector TLD in education therefore does not rest on royalties. It rests on what the operator already is. An association that verifies its members anyway, a platform that already onboards schools, or a provider network that already issues certificates performs the verification as part of its existing work. For such an operator the namespace adds a naming layer to a relationship it has. For an operator with no existing relationship with institutions, the example above is a warning.
Fees for services the operator provides itself (verification, onboarding support, help with credential issuance) fall outside the royalty model. They are set by the operator and should be costed separately, with the same honesty about how many institutions will pay them. The Subname Revenue Calculator estimates revenue from names issued under a TLD, so you can replace these assumptions with your own.
What to check before acquiring the TLD
Before making an offer on a .yoursector TLD, an operator needs answers to several questions that are specific to education.
Trademark exposure. Words that describe education are often also part of the names of institutions, publishers and associations. Check whether the string, or the names you expect to issue under it, conflict with a registered mark. The free Trademark Name Check on the page about trademark TLDs is a first pass. A full clearance search is work for a trademark attorney.
Resolution coverage. An onchain name lives outside the ICANN DNS root, which means an ordinary browser will not open it unless support has been added. A school or an alumni committee will find Freename names supported in three places: Bitcoin.com Wallet, MetaMask by way of Freename’s resolver, and a desktop browser in which the Freename Web3 extension has been installed. This coverage is partial and it changes. A school’s IT office will ask whether the name works on the managed devices it gives to staff, and the honest answer may be no. Tell institutional registrants exactly what works, and never promise universal resolution.
Names already issued. Check whether names already exist under the TLD and what they are. The registry record is public, so this can be done on a block explorer. Names the seller holds itself can come to you with the TLD if the two of you agree on it, while names sold to third parties remain theirs. Either way, a name issued before you acquired the TLD, particularly one that reads as an institution, is part of the namespace you answer for from the day of transfer.
Legal entity. Decide which legal entity will hold the TLD token, accept the registry’s terms and contract with institutional registrants. A TLD held by one individual, under which institutions issue credentials, is a governance risk for every holder. Schools and professional bodies will ask who stands behind the namespace before they attach their name to it. The structure is a matter for your counsel.
Standing in the sector. Ask whether institutions would accept you as the party that decides who is a school. An operator with no recognized role in education will find verification challenged at every step. Where a namespace for the sector is already in use, consider whether a second one adds choice or only confusion.
Time to first name. Acquiring the TLD is the beginning. Between the transfer and the first institutional name there is policy drafting, legal review of the minors section, and the first verification. The Launch Roadmap tool builds a launch plan for a newly acquired TLD and is a reasonable way to see that sequence before you commit.
A realistic first year
The sequence below assumes an operator with existing contacts among institutions. Without them, the fourth step takes most of the year.
- Diligence before the offerRun the trademark check, write down what resolution coverage you can truthfully state, inspect the names already issued under the TLD, and settle which legal entity will hold the token.
- TransferClose through onchain escrow. Once the token is in your wallet, confirm that a test name resolves in the supported wallets and browsers before you speak to any institution.
- Registration policyDraft and publish the rules before issuing any name: eligibility, reserved institutional patterns, prohibited strings, the complaint process and the limits of resolution. Have counsel review the section on minors.
- Anchor institutionsApproach a short list of schools, colleges or training providers you already know. Ask each for one live use (payments, completion records or wallet identity) within a period you agree together.
- Credential pilotWork with one training provider among the early holders to issue completion tokens to a single course cohort of adult learners. Document the workflow so it can be repeated.
- Alumni outreachContact a few alumni associations with active committees. A cohort name used for one reunion or one class gift is a low-risk first deployment.
- ReviewToward the end of the year, count the names that were used for at least one onchain action, note which holder types used theirs and which did not, and adjust the policy and outreach before the second year.
Judge the first year by names in use, not names issued. A small group of institutions that take donations or issue completion records through their names tells you more than a long register of dormant ones. It shows which of the three holder groups has real demand, it gives you a documented example for the next institutional conversation, and it tells you whether the verification effort is sustainable at a larger scale.
Expect the alumni and training groups to move first. They have shorter decision chains than a school’s governing body, and their use cases (a class gift, a course certificate) are small enough to try without a policy change. If neither group has put a name to use by the review, treat that as evidence about demand and not about your outreach.
Where to start if the case holds up
If the questions above leave you with a credible plan, begin with the string. Its worth to an operator in education turns on how plainly it names the sector, any trademark conflict, the names already issued under it, and the realistic path to first use, not on the abstract size of the sector. The page on how a TLD valuation is built explains the factors in more detail.
If you do not hold the TLD, an organization can mandate Hush Partners to find and approach its holder, a service described under buy-side acquisition. A standard mutual NDA covers every exchange, one named partner follows the file through to closing, and closing runs through onchain escrow on an aftermarket.
If you already hold a sector TLD and are weighing whether to run it as an education namespace, the post-transfer activation service covers putting a TLD to work after the transfer.
A sound first move costs nothing. Write the one-page registration policy, including the section on minors, and show it to two institutions you know. If neither would register under those rules, you have learned what you needed before acquiring anything. If the string has a trademark problem, weak institutional demand or a resolution gap you cannot explain honestly to a school, the right answer is to wait or to choose a different string.
Questions people ask
Can a school hold an onchain name without understanding the underlying technology?
Largely, yes. The school needs a wallet and one or two trained staff; it does not need to understand smart contracts to receive a payment to a name or print the name in a fundraising letter. The operator’s onboarding material should concentrate on the two or three actions the school will perform, and on who holds the keys.
Does an onchain name replace the school’s conventional domain name?
No, and it should not be presented as a replacement. A conventional domain sits in the ICANN DNS and opens in every browser with no extension or extra configuration, which is simply better for a public website and for email. An onchain name works only where support exists. The two coexist: the conventional domain carries the website and email, and the onchain name carries wallet identity, payments and credential issuance.
Who holds a name after a school closes?
The name stays in the wallet that holds it. If the school closes without transferring the name, it remains wherever the school’s administrators left it. The operator’s rules should require each institutional holder to name a successor and document a handover procedure. This matters most for institutions whose name is the visible issuer of graduates’ credentials.
Can a training provider give its learners names without holding a TLD?
Not by itself. Names under a TLD are created by whoever holds that TLD, so the provider asks the operator to issue them, under the operator’s rules and for adult learners who request one. A provider does not need a name for each learner in order to issue credentials: a completion token sent from the wallet that holds course.yoursector already shows who issued it.
What happens if the TLD operator stops operating?
Names already issued stay in the wallets that hold them; an onchain token does not vanish because the operator ceases to trade. What stops is the issuing of new names, the verification of new institutions and the handling of complaints. That is a material risk for institutions that have built credential records on the namespace. An operator should hold the TLD in a legal entity with documented succession, and should tell holders which wallet holds the TLD so they can check the public record themselves.
