I have spent the better part of a decade watching blockchain projects promise to reinvent the internet’s plumbing. Most of them fail because they confuse a technical possibility with a human need. When Pavel Durov announced that Telegram had applied for the '.gram' top-level domain, I felt a familiar tension between the allure of a new identity layer and the gravitational pull of legacy systems. The announcement was light on details—no ICANN filing number, no timeline, no technical whitepaper. But the ambition is clear: turn every Telegram username into a resolvable, web-accessible domain.
Context: The Landscape of Digital Identity Telegram’s move is not happening in a vacuum. The Domain Name System (DNS) has been the backbone of internet addressing for decades, governed by ICANN under a complex web of contracts and policies. In 2026, ICANN is expected to open a new round of new generic top-level domain (gTLD) applications, the first since 2012. Meanwhile, Web3 identity protocols like ENS (Ethereum Name Service) have already mapped wallet addresses to human-readable names like 'vitalik.eth', creating a parallel namespace that bypasses traditional DNS. Telegram’s existing infrastructure—10 billion users, the Mini App platform, and deep integration with TON—positions it uniquely to bridge these two worlds. If successful, '.gram' could become the default identity layer for the Telegram ecosystem, linking social profiles, websites, and on-chain activity under a single, human-readable string.
Core: The Technical and Ethical Architecture From a technical standpoint, the proposal is plausible but fraught with hidden complexity. Telegram already operates a username system that resolves to t.me/username. Mapping that to username.gram is a straightforward DNS delegation—provided Telegram can operate a registry with the required ICANN infrastructure: DNSSEC signing, WHOIS/RDAP services, abuse handling, and a 24/7 NOC. Based on my experience auditing the Compound Finance governance mechanism, I know that operational maturity is often the silent killer of ambitious protocols. Telegram has never run a DNS registry; its core competency is encrypted messaging, not root zone management. The Mini App platform, which allows users to build interactive websites through Telegram’s WebView, could be the killer use case. A user could type durov.gram into a browser and see a dynamic Mini App, hosted on Telegram’s servers. This collapses the distance between social identity and web presence, reducing the friction of building a personal website to nearly zero. But it also introduces a governance nightmare: every .gram domain becomes a potential phishing vector, and Telegram, as the registry, would be responsible for takedowns, disputes, and compliance with local laws. The philosophical tension is acute. Telegram markets itself as a champion of privacy and free speech, yet running a gTLD requires it to police content, collect registrant data, and cooperate with law enforcement.
Contrarian: The Pragmatic Test The contrarian question is whether this is really a step toward decentralization—or a clever centralization of identity under Telegram’s control. ENS, for all its flaws, is permissionless: anyone can register an .eth name without a gatekeeper. Telegram, on the other hand, would control the entire namespace, deciding which usernames map to domains and which don’t. If Telegram retains the right to revoke a domain, the system is no different from a traditional registrar. Moreover, the ICANN process itself is a multi-year, multi-million dollar undertaking. The evaluation fee alone is around $185,000, and the application can be contested by other parties. Even if approved, Telegram must comply with ICANN’s registry agreement, which includes obligations like “equal access” and “non-discriminatory” treatment—rules that could conflict with Telegram’s desire to reserve all existing usernames as domains. Meanwhile, the Web3 community has already moved on. ENS, Unstoppable Domains, and TON’s own .ton.site provide similar functionality without the ICANN overhead. If Telegram’s goal is to create a Web3 identity, why not align with these existing standards? The answer may be that Telegram wants to capture the economic value of the namespace itself—a classic platform play.
Takeaway: A Signal Worth Watching I do not dismiss the potential of .gram. The combination of a massive user base, existing social graph, and a lightweight web hosting layer could lower the barrier to entry for millions of people who have never owned a domain. But the path from application to production is strewn with regulatory landmines, operational challenges, and philosophical contradictions. We audit the logic, for humans will always err. The true test will come when ICANN opens the next round and the world sees whether Telegram’s ambition matches its execution. Until then, I remain skeptical but attentive. Hype burns out; robustness remains in the ledger. Code is the only law that does not sleep—but ICANN’s rules are written in ink, not code.