ENS Subnames vs Freename TLDs: Community Naming Models
Compare ENS subnames and Freename Web3 TLDs by member use, control, operating work, revenue conditions and costs.
ENS subnames and Freename Web3 TLDs are different ways to organize a community namespace. ENS puts member names under a parent such as yourproject.eth. Freename offers a custom extension inside its Web3 naming system. Choose around the member’s actual use and the operator’s responsibilities before comparing an advertised revenue share.
Define who would register, why they would use the name and what service you would maintain.
- 01Compare the complete identifiers
- 02Compare controls and operating work
- 03Model costs before assuming sales
Compare the actual products
| Question | ENS subname program | Freename Web3 TLD program |
|---|---|---|
| Illustrative identifier | member.yourproject.eth | member.customextension |
| What the operator holds | A parent ENS name and the chosen issuing setup. | A Web3 extension asset and any selected program options. |
| Member control | Depends on parent policy, issuing contracts, permissions and expiry. | Depends on the exact Freename product, minted asset and service conditions. |
| Possible revenue | Your registration, renewal or service charges under the implemented system. | A share of qualifying registrations when the royalty option is active. |
| Operating work | Issuance, customer support, technical maintenance and parent continuity. | Attract registrants, maintain the offering and reconcile eligible balances and payouts. |
These example names are hypothetical. A matching label, available extension or familiar provider logo does not prove app support. Verify how members would actually use the complete identifier.
Where the ENS model fits
An ENS parent may fit a project whose members already use ENS-aware apps and recognize the project’s .eth identity. A small managed allocation can serve internal team roles. A public self-service program needs a registration mechanism and a clear member agreement about control and ongoing service.
ENS documents wrapped subname sales and renewal charging through registrar contracts. That is technical infrastructure an operator must select, build or maintain. The ability to issue names is not evidence of paying demand. Start with the team subname guide to define the scope before designing a commercial program.
Where the Freename model fits
A custom Freename extension may fit an audience that has a specific reason to adopt that extension and whose required apps support it. The operator must distinguish the TLD asset, royalty service and optional reseller tools. Freename’s Custom Pricing help identifies Reseller Tools as a separate requirement for its category-price controls.
A royalty percentage says how eligible activity may be shared. It does not tell you how many customers will register. Use the royalty setup and payout guide to distinguish internal Credits, available stablecoin balances and received wallet payments.
Compare control before comparing income
Write the member-facing promise first. Can a maintainer reassign a name? Can the holder transfer it? Who renews the parent or selected services? What happens if the organization stops supporting the program?
For ENSv1 wrapped arrangements, permissions and expiry determine the answers. ENS warns about locking names and fuse restrictions during its announced transition. For Freename, read the selected product and program conditions. Neither the word “ownership” nor a token image is a complete description of every dependency.
A Freename Web3 extension should also not be confused with an ICANN DNS delegation. Provider accreditation or sales of traditional domains do not make every Web3 suffix resolve as an ordinary DNS website. Check the exact product and app route in our provider directory.
A small commercial comparison without a forecast
Consider a hypothetical community with twenty people who express interest in names. That is research, not twenty paid registrations. Record how many can complete the required app workflow, how many understand the control policy and what they would pay for the actual service.
For each proposed model, list acquisition, recurring services, transactions, development, support and promotion. Then model zero registrations as well as a stated sales assumption. Keep receipt currency consistent. In the Freename model, internal Credits should not be counted as cash available to cover an unrelated bill.
Use a narrow pilot and a defined review point. A larger inventory or higher asking price does not repair missing customer evidence. Our earning overview separates these models from resale and referrals.
Use a practical selection rule
- Remove any model that fails a required member workflow.
- Make the control and maintenance policy understandable before taking money.
- Choose operating work your team can actually deliver.
- Use verified receipts and costs to review the program.
- Keep an exit or handover plan for members.
This framework is editorial judgment, informed by official product documentation. It is not a ranking based on verified participant returns. We have not operated a paid namespace or received a royalty payout for this comparison.
Finished when: the proposed model has a supported member workflow, an understandable control policy and a cost budget that still makes sense with zero sales.
Sources and review
Official documentation reviewed 23 October 2026. Procedures and compatibility below are documentation-based; no purchase, wallet transaction or payout was performed.
ENS subname creation controls ↗ENSv1 wrapped subname issuance and commercial models ↗ENSv1 Name Wrapper fuse permissions ↗ENSv2 announced changes, not live at review ↗Freename Web3 TLD purchase, minting and eligibility ↗Freename Custom Pricing and separate Reseller Tools ↗Freename contractual terms ↗Freename internal Credits and withdrawable royalties ↗