Recently, the web3 domain track has become very popular, with various suffixes emerging one after another. As the most important track for web3 in the future, decentralized domains have many more use cases compared to traditional domains, which can only be used for building websites.
Currently, the most common use case for web3 domains is for transfers. However, these demands are not very strong. The second largest use case is resolving IPNS on IPFS, allowing you to directly access decentralized front-end pages built on IPFS using browsers that support IPFS, such as Brave, by using domains like uniswap.eth/vitalik.eth.
The greatest potential lies in the future use of web3 domains as IDs. In the cryptocurrency community, @viamirror is widely used. Previously, there was a decentralized blog built on IPFS+ENS called @PlanetableXYZ, a decentralized live streaming application using the IPFS protocol called @huddle01com, and a decentralized comment plugin built on Arweave called @0x_ECHO. The upcoming decentralized gateway dappnet also has numerous use cases for decentralized domains as IDs.
If web3 social networks explode in the future, the entire track of decentralized domains will undoubtedly be the first to benefit. In the web2 era, not everyone needed a .com domain for building websites. However, in the web3 era, everyone needs a domain as an ID. Most people won't want to use a long string of addresses for social interactions. This represents a huge demand from a potential user base of 1 billion.
Of course, the ultimate victory will come after achieving the goals of web3 domains and bringing in massive traffic, forcing mainstream browsers to support IP mapping resolution for web3 domains. This will bypass the centralized hierarchical resolution of root domain name servers managed by ICANN, providing an opportunity to decentralize the DNS protocol and realize the vision originally proposed by Satoshi Nakamoto in BitDNS.
Source:
https://mirror.xyz/tradingscience.eth/hmomZXOYJOdLdl4By4VGUQg9SFZ2riO0vXPwJtb2XAM