Fragment Has No UDRP: Why Trademark Owners Can’t Defend Their @Names

Fragment Has No UDRP: Why Trademark Owners Can’t Defend Their @Names

On May 4, 2026, Pavel Durov announced that Telegram would become TON’s largest validator and primary driver. The move signaled confidence in Fragment as a market. But in that same ecosystem, a trademark holder has zero legal recourse if a bad-faith actor acquires @yourcompany on Fragment and refuses to part with it. DNS has the UDRP. Fragment has nothing.

The Collision Problem Is Real

Blockchain namespace researchers identified 1,456 on-chain identifiers that collide with successfully litigated UDRP cases in DNS—brands like Google, Amazon, Nike, Disney, and Ford. WIPO saw domain name disputes spike 68% since 2020, with 6,200 cases handled in 2025 alone, the majority cybersquatting. The risk is not hypothetical.

Fragment’s position as the canonical Telegram @name marketplace, paired with TON’s #2 ranking in NFT trading volume, makes it the obvious target for trademark squatters. A single-character handle like @m or @x commands tens of thousands of dollars. A branded handle like @tesla or @samsung (if still available) would be a high-value takeover. If acquired by a competitor or scammer, there is no process—UDRP or otherwise—to retrieve it.

Why UDRP Doesn’t Exist for Fragment

The Uniform Domain-Name Dispute-Resolution Policy exists because ICANN, the body that governs DNS, enforces it. The process is fast (45–90 days), relatively affordable ($1,500–$5,000), and has strong precedent. A trademark holder proves bad faith, no legitimate interest, and confusing similarity—and the domain reverses.

Fragment operates on TON, a blockchain owned and operated by Telegram. Telegram is not ICANN. There is no neutral arbiter, no standardized dispute process, no published IP defense mechanism. If Telegram wanted to add one, it could—but it would require protocol-level governance changes, stakeholder agreement, and dispute adjudication infrastructure that does not exist today.

The Strategic Liability

This absence has two consequences. First, enterprises cannot treat Fragment @names as defensible brand infrastructure. A corporate strategy that locks identity into Fragment while leaving it vulnerable to squatting is a liability, not an asset. Second, Fragment’s market value depends partly on scarcity; issuing a dispute resolution mechanism would require Telegram to take sides and reduce the scarcity premium that drives trading volume.

Neither Telegram nor the Fragment market benefits from a UDRP analog. The platform is optimized for secondary trading, not IP protection. That trade-off is baked in.

What Trademark Owners Are Actually Doing

Sophisticated enterprises have three strategies: (1) acquire the @name early, before bad-faith actors spot it; (2) monitor Fragment and Getgems for collisions and bid defensively; (3) use Fragment for non-core identities and rely on DNS and social handles for canonical brand presence. None of these strategies are scaling. The second requires continuous market monitoring. The third concedes Fragment entirely.

The Larger Implication

This is not unique to Fragment. Ethereum Name Service, Unstoppable Domains, and other blockchain namespace systems face the same problem. Some, like Ethereum, block known trademarks during registration—a defensive move that works. Fragment does not. As long as it doesn’t, Fragment remains a trading platform, not an identity infrastructure. For enterprises, the distinction matters.