In Web2 a collision occurs when an attempt to resolve a domain name in a private namespace results in a query to the public DNS. When private and public domain namespaces overlap, it Yeahcan create security risks, confusion, and systems failure. While traditional Web2 domain names are organized by ICANN , there is no such governing body or alliance in Web3.
Name Collision in Web3
In Web3, “domains” are used to send and receive cryptocurrency in place of lengthy alphanumeric wallet addresses and are a vital component of Digital Identity. The risks and dangers of collision with Web3 domains can be pretty serious. Imagine sending Bitcoin to the wrong james.defiwallet, or connecting your wallet to opensea.crypto and getting a scammer’s website instead of the real OpenSea.
So how likely are Web3 Domains to Collide? Very likely…
The lack of a governing body or domain library in the Web3 space enables duplicate creation of TLDs and SLDs by competing blockchain DNS registrars such as Handshake, Decentraweb, FreeNameio, Unstoppableweb & more.
How do we resolve this in the future?
The recall of .coin SLDs created and sold by Unstoppableweb is the one example of how the issue with colliding Web3 TLDs may play out. Unstoppableweb didn't know that a company called Emercoin had started offering .coin “domains” 8 yrs ago. Not surprisingly, Unstoppableweb has now led the charge with creating a formal solution and alliance to combat this issue in the future. Their solution, the Web3 Domain Alliance, has been met with scrutiny by Unstoppable critics, but it is a step in the right direction.
Join the pride of kings and queens, and explore all the possibilities of the metaverse. We’re on a mission to build the premier Web 3.0 brand together with our community, driven by our shared passion for NFTs, gaming, and the metaverse.