The collision between Web3 naming systems and trademark law is exposing a fundamental gap in how intellectual property works on decentralized networks. Traditional domain disputes have a referee—ICANN, courts, trademark offices. Web3 domains like .eth on the Ethereum Name Service or .crypto on Unstoppable Domains operate on different rules entirely, and that difference is already causing friction.
In traditional DNS, a trademark holder can file a complaint under the Uniform Domain-Name Dispute-Resolution Policy (UDRP), and an arbitrator can order the registrar to transfer or cancel the domain. The system works because there's a central authority—the registrar—with the power to act. Web3 domains don't work that way. Once a .eth name is minted on-chain, no single entity can unilaterally delete or reassign it. A court can issue a judgment, but enforcement stops at the blockchain's edge. A registrar can delist a name from its user interface, making it harder to find and harder to interact with, but the record itself persists.
This creates asymmetric consequences for different actors. A brand owner can sue for trademark infringement and win a court order, but the defendant's domain name keeps working on-chain. Platforms like OpenSea can voluntarily delist flagged addresses from their marketplaces, but someone determined enough can still transact directly on the blockchain. The legal system has tools to punish conduct, but not to delete or repurpose on-chain names the way UDRP does.
The practical trade-offs
Brand enforcement in Web3 naming comes down to three levers: civil courts, platform policy, and social reputation. Courts can award damages and issue injunctions against specific defendants, but those remedies don't scale to squatting or automated phishing infrastructure. Platforms can choose not to serve certain addresses, but that's a business decision, not a legal guarantee. Reputation—the social and commercial cost of operating under a flagged name—may be the most effective deterrent, but it's fragile and uneven across regions and industries.
The decentralization that makes Web3 domains censorship-resistant also makes them resistant to the enforcement mechanisms trademark law relies on. Removing that friction would require either centralizing the registry (defeating the point) or building new dispute-resolution systems native to blockchain (which still won't bind everyone, since anyone can run a full node and verify a name independently).
What happens next
Some Web3 naming services are experimenting with hybrid approaches. They maintain on-chain records that no single actor can control, but they also run resolvers and UIs that they do control, giving them a chokepoint where they can respond to legal demands. That's not the same as traditional enforcement, but it's not nothing either. It shifts the liability risk to platforms rather than distributing it across the network.
Brand owners who can't afford to wait for legal infrastructure to catch up are registering preemptively across major Web3 name systems. That's defensive squatting under a different regime. It works, but it's expensive and it doesn't solve the underlying problem: the technical rules and the legal rules are now operating in different jurisdictions, and the person who got there first owns the name regardless of who owns the trademark.
The harder question is whether this gap should be closed at all. Web3 domains were designed to be tamper-proof and namespace-neutral, explicit rejections of the centralized control that made traditional domain enforcement possible. Every measure that makes enforcement easier also makes censorship easier. The trade-off is real, and different stakeholders value it differently.