Data

◼️34/100: Block-by-Block

One thing I learned about: Web3 domain services

Blockchain addresses are not intuitive for everyday users.

Web3 domain services provide memorable names tied to on-chain accounts. This is similar to how DNS resolves domain names into IP addresses.

This should help Web3 users own a domain and send/receive transactions.

But, there are adoption challenges.

🔽📝Details🔽

Learn & build with web3 data: https://skool.com/data3

🔽🛠️Resources🔽

- Unstoppable Domains kills .coin in the name of .wallet (2022): https://domainnamewire.com/2022/10/18/unstoppable-domains-kills-coin-in-the-name-of-wallet/
- What is ENS? by @ensdomains: https://support.ens.domains/en/articles/7900404-what-is-ens
- About Handshake by Namebase: https://learn.namebase.io/about-handshake/about-handshake
- Understanding DNS, Onchain & Web3 Domains (2025) by @unstoppable: https://unstoppabledomains.com/blog/categories/education/article/understanding-dns-onchain-web3-domains
- Brave Becomes First Browser to Launch On‑Chain Naming Service, Unlocking .brave for Over 85M Users (2025): https://brave.com/blog/brave-tld/

Challenge 2: Browsers do not resolve web3 domains without additional configuration or plugins.

They use the default DNS servers of the operating system or the browser.

The only partial exception is Brave, which resolves some domains (e.g. .crypto, and .eth)

While you can set up a custom Web3 DNS resolver, you cannot expect every visitor of your Web3 domain to do the same.

Challenge 1: No single resolver but parallel providers.

Examples:

- ENS
- Unstoppable Domains
- Solana Name Service
- Handshake
- Tezos Domains

Each service resolves domains only within a set of networks but not in others.

This is bad because...
- Users need to register their domain at each network
- Domains can collide with each other