Managing the tDNS: 12 types of decisions for a domain name service

As the tomi team launches the domain name auction for the tomi Domain Name System (tDNS), we’ll also be simultaneously developing the DAO that manages the tDNS. The responsibility for domain names is tremendous and a DAO is the perfect way to ensure that the system cannot be corrupted by large entities. As we determine the governing mechanisms over the coming year, it’s important to understand what governing responsibilities are given to a domain name registrar, and what we can learn from past efforts to govern name registrars.

This is the first in a series which will look into the complexities of Domain Naming Systems and exploring how we can construct a DAO that will appropriately manage the tDNS. If you’re interested in getting more involved, join the general chat or the proposal discussion chat on our Discord. These are complex issues and we’re happy to have your input as we consider the best governing mechanisms for tDNS.

What’s a domain naming system?

Most people are familiar with the today’s world wide web (WWW) Domain Name System (DNS) which assigns domain names. The purpose of the DNS is to take machine-readable IP addresses, and translate them to human-readable addresses. For an example of how complex this can be, you can read this article about the IP address ranges used by Google. There are lots of them, and the DNS server makes it such that when you type google.com, you get served by the right server.

What other name systems are out there?

In the Web3 space, you may have heard of services like Namecoin and Ethereum Name Service (ENS). In both of these cases, teams of developers created naming services to create a human-readable name for your public keys. By purchasing an ENS address, you no longer need to send a long, confusing name or connect your Metamask. You can buy an address that translates the public key to something sensible that people can remember. It’s perfect when you want to type your name into a form to get a POAP, for example.

Namecoin is a service that provides *.bit address. It was the first fork of Bitcoin, and although it’s still functional, it’s not in common use. Another Bitcoin address system was created by Blockstack, which created the Stacks network that includes a decentralized domain name system called BNS (Blockstack Naming Service). Unlike traditional DNS, BNS operates on the blockchain and allows users to register and control domain names that are tied to a user-owned private key. The Stacks ecosystem is still functional today, but it has evolved from the primary objective to creating a full L2 on the Bitcoin blockchain, so the naming service is a lesser-known function of the Stacks network.

Web3 projects based on other forms of Distributed Ledger Technology, such as IPFS and Holochain, have created their own addressing services, which are different from name services but have similar issues in terms of governance.

Other types of name services are implemented in Web3 social networks, such as the Lens Protocol, which issued .lens NFTs for its user names. Similarly, Cardano Spot and other types of social networks always need a system for issuing user names. Auctions, airdrops, and other types of public issuing events are typical for Web3 name issuance.

Decisions a DNS makes

When looking at how name services are managed, the original WWW has taken a centralized approach. While it seems as if the ICANN is decentralized, in that it has 13 organizations on the board, most of them are US government agencies or institutions, so it’s almost completely defined by US law. Blockchain-based systems are a combination of centralized and decentralized governance. Decisions about the code integrated in the ENS system are under the full control of the core team, primarly luc.eth. Conversely, the way the ENS names are sold is completely decentralized, which means there are absolutely no controls on who can own and use a name. That might be fine for a wallet address, but for a website, some form of supervision is generally desirable — otherwise you end up with something similar to the darkweb, which is completely uncensored but also unsafe.

But let’s go back to the first question in governance: What are you governing? Most of us never delved deeply into the questions of what a DNS needs to govern. If we’re going to have the tomiDAO govern the tDNS, it’s essential to figure out what kinds of decisions are being made.

1. Name Resolution: The core function of a DNS is to resolve domain names into IP addresses. Generally, tDNS will be using the existing protocols (like DNS over HTTPS) so that the system is compatible with the existing way people browse the web. Some may remember the discussions of IPv6, which was necessary to implement because the WWW got so much larger than its initial founders envisioned.
2. Registry-Registrar Model: The legacy DNS uses a model where ICANN releases the Top Level Domains (TLD) through a bureaucratic process, where they issue a call every few years (one is coming up now) for “registry providers” to represent these TLDs. Those registry providers, in turn, release the domain names to the domain name providers that then sell them to the public. That’s a lot of opaque pricing layers! When you go to a host and ask to buy a domain name, it’s already been through that process, and as most people know, when you go to renew, it’s a completely different price than it was when you first bought the domain name. Like other Web3 projects, tDNS is looking at a completely automated process of registries, with no middlemen involved. Anyone who wants to can open and mint a domain name.
3. Pricing: Guess what? In the legacy WWW, the costs of the TLD extensions are priced based on contracts between the registry providers and the US government. And the last time those contracts were set was in 2016. That doesn’t sound reasonable or fair to tomi. The initial price of domains at tomi is set at $100, and the auction is direct to the public. After the first year, the DAO will be able to set prices for other TLDs, and set up specific ways to acquire them that will be appropriate for the jurisdictions they represent. At this time, tomi is not setting any policies on domains for different countries or non-profits (such as .org and .net), because that needs to be left to the DAO. The default will remain as it is, but the DAO can make changes in the future.
4. Domain Registration and Renewal: As we pointed out above, your domain name pricing can change from year to year. You might change your hosting provider, getting a better deal on the price, but moving from one provider to another is a technical issue, and it may result in your domain being down for a bit. With the tDNS every registration is forever, and you get the .com, the .tomi and your tomi wallet name.
5. Domain Name Structure: The current DNS uses a hierarchical system with different levels (TLDs, second-level domains, subdomains, etc.). While we plan to use the same structure in tDNS, we want to remain agile over time.
6. Release of TLDs: ICANN (Internet Corporation for Assigned Names and Numbers) and IANA (Internet Assigned Numbers Authority) manage the issuance of TLDs through the Top-Level Domain Program, which last open in 2016 and is entering another round in 2023. The tDNS can open up the TLDs and sub-domains at any time for minting and determine the conditions for minting associated NFTs.
7. Dispute Resolution: Right now, tomi has a completely capitalistic model in terms of how domain names are acquired. ENS has also had success with this first-come-first-served model. Over time, however, there may be domain name disputes due to domain squatting or other issues. We can’t foresee everything. How will the tDNS manage disputes? This is important for the long-term viability of any project.
8. Content Management: Technically, content management is outside of the realm of ICANN and IANA, but in the tomiNet, setting community guidelines and moderating content is important. Today, one of the central powers in content management is Google, which maintains something called the Google Safe Browsing list, referenced by ISPs and browsers worldwide. Wherever you are and however you are browsing, you are probably subject to censorship through this list — which, by the way, is not public. Google publishes its guidelines but not the list of what’s banned, and there’s no oversight committee. At tomi, we take this as a major violation of freedom of speech. We need to create a DAO that will appropriately balance freedom of speech and content moderation, blocking only extremely violent sites.
9. Privacy: The original WWW DNS required people to register with the WHOIS registry. Everyone with a domain name needs to update annually who they are and provide their country and other identifying information. This is a throwback to government control of the internet, because the WWW was invented by US government agencies. However, at tomi, we believe in the right to privacy, so people do not have to self-identify to own a tomi URL and NFT. Over time, the DAO may implement certain policies, particularly if there are repeat offenders in terms of violations of community guidelines. However, disclosures will be through a self-sovereign identity wallet that gives tomi users the freedom to control their identity. The DAO is currently discussing the specifications of this SSI wallet, so please join the discussion on the proposal discussion channels on Discord.
10. Abuse Prevention: In this article, we won’t go into specific types of abuse of the DNS system, like content violations, spamming, domain sinkholing, etc. Threats to DNS operation are always an issue, and the DAO will need to address these attacks as they evolve.
11. NFT Art: With tomiDAO, every URL is associated with an NFT. Currently, there is no difference between each NFT visually, similar to Lens Protocol. However, it’s quite easy to imagine a future where URLs are issued with limited-issue artwork, similar to stamps and coins. The tDNS will be able to determine how such an art program would be implemented.
12. Meta-Governance: The initial tomiDAO is governed by the tomi Pioneers, but as you can tell from the list above — there are a lot of factors to consider! The DAO will also need to self-govern, making changes to itself as it evolves.

But wait, there’s more! The list above isn’t complete. Issues like interoperability, security, scalability, content moderation, reliability, and language compatibility are also known areas of governance for DNS systems. We’ll be taking a deep dive into each of these areas on this blog, in the Discord channels, on the DAO Forum, and within the tomi team, so that we can develop the appropriate mechanisms for managing the tDNS in a decentralized and democratic way.

Is a year even enough?

tomi has set the tDNS auction time at one year, so we can work together with you, our community, to fully decentralize these decisions. A year should be enough to develop the right teams and working groups and to improve the DAO functionality to be able to handle such complex tasks. Unlike other DAOs in Web3, we are starting with a deep analysis of what we need, instead of just adopting a voting tool that isn’t fit to our purpose. We think that the discussion, problem-definition, and proposal-making phases are more important than the voting. Great proposals will lead to great implementations.

We’re looking forward to having you as our partners for creating a DNS that builds on learnings from today’s Web2 and Web3 worlds. If you’re interested in being part of the development of the DAO for the tDNS, join the conversation on Discord and reach out to Owl with your ideas!

Follow us to get the latest information:

Website | Twitter | Discord | Telegram Announcements | Telegram Chat | Medium | Reddit | TikTok