The .gram Domain: Telegram’s Bid to Own Your Digital Identity – or a New Walled Garden?

We chart the code, but the soul chooses the path. This phrase echoes in my mind every time I see a platform claim to liberate its users while quietly tightening the chains. Telegram’s recent application for the '.gram' top-level domain feels like one of those moments—a promise of sovereignty wrapped in the language of user empowerment, yet carrying the seeds of a new centralization. Let me be clear: I’m not here to cheerlead or condemn. I’m here to dissect, because in this bear market, when every project is bleeding, the only thing that matters is whether the architecture you’re building on can survive the winter. The news is simple: Pavel Durov announced that Telegram has applied to ICANN for the '.gram' domain. The vision: every Telegram username becomes a second-level domain (e.g., durov.gram). Users could then, through a simple command, create a website hosted on Telegram’s Mini App platform—no DNS configuration, no hosting purchase, just a click and a link. On the surface, it’s a beautiful idea. It lowers the barrier to personal publishing for 1 billion users. It turns a username into a digital asset. It’s the kind of move that makes Web3 idealists nod in approval. But having spent years auditing decentralized identity systems—from ENS to Ethereum Classic’s early experiments—I see a different story. Let’s dig into the architecture. Telegram’s infrastructure is strong for messaging and app containers. The Mini App environment is a mature HTML/JS sandbox, and the existing t.me URL scheme already resolves usernames. Technically, mapping usernames to DNS is feasible. But here’s where the soul meets the code: Telegram would need to run its own authoritative DNS server cluster, maintain DNSSEC signing, and handle abuse complaints. These are not trivial. During my 2022 audit of failing L1 protocols, I found that the most common centralization vulnerability was not in consensus but in infrastructure dependencies—single points of failure in DNS, relayers, or oracles. Telegram has never operated a global DNS root. Its privacy-first ethos, which I deeply respect, will clash with ICANN’s requirements for WHOIS data collection and law enforcement cooperation. The moment a user registers a .gram domain, Telegram becomes a registry operator, subject to ICANN’s contract, including the obligation to suspend domains for abuse. For a platform that prides itself on censorship resistance, this is a fundamental contradiction. The code is not the law here; the contract is. Now, the core of the matter: what is .gram really selling? It’s not a domain in the traditional sense. It’s a platform identity layer, similar to ENS (name.eth) but with a crucial difference: ENS is a decentralized protocol on Ethereum, owned by its users, governed by a DAO. .gram is owned by Telegram. The username-to-domain mapping is a reserved list controlled by a single company. If Telegram decides tomorrow that your username violates its terms, your .gram website disappears. The switching cost is high—once you’ve built your brand on durov.gram, moving to another platform means losing that link. This is not user sovereignty; it’s user lock-in disguised as a digital asset. The network effect is real: with 1 billion users, the identity value of a .gram domain grows as more people use Telegram. But that network effect is a walled garden, not an open protocol. It’s the difference between owning your keys and owning a key to a room in someone else’s house. The contrarian angle I want to offer is this: the greatest risk of .gram is not that it will fail, but that it will succeed—and in doing so, create a monoculture of identity. Imagine a world where every Telegram user has a .gram domain, and every website is built on Mini Apps. That’s a centralized social graph masquerading as a decentralized identity layer. The collapse of FTX taught us that trust in a single entity—even a beloved one like Durov—is a ticking time bomb. In a bear market, when survival matters more than gains, we need to ask: if Telegram’s servers go dark, or if a country blocks the platform, what happens to your .gram website? The answer is nothing. It’s gone. That’s not sovereignty. That’s dependency. Yet, I don’t want to dismiss the opportunity entirely. Telegram has a chance to do something genuinely different. If they open the .gram registry to a decentralized governance model—perhaps using the TON blockchain for ownership records, and allowing users to export their domains to other DNS providers—they could build a bridge between traditional web and Web3. I’ve seen similar hybrid models in my work with Ethereum Classic’s identity layer, where immutability was preserved through a permissioned yet transparent system. The key is to treat the domain not as a product but as a protocol. But that requires a philosophical shift from Durov, who has always been a benevolent dictator, not a decentralized steward. Let’s look at the competitive landscape. ENS already has a strong brand in crypto, with 2 million+ .eth names. ton.site, the TON-based web hosting, is already live. Telegram’s .gram would directly compete with these, creating confusion: do I register durov.eth, durov.ton.site, or durov.gram? The user’s attention is finite. And the ICANN process itself is a multi-year slog, with a $185,000 application fee and no guarantee of approval. The window for new gTLDs opens in 2026, but Telegram’s application may already be in the queue. Even if approved, the registry must comply with constant VDP (Vulnerability Disclosure Program) and abuse monitoring—costs that Telegram, as a private company, may not be willing to bear indefinitely. When I think about the cultural memory of digital identity, I remember the early days of the web, when everyone had a GeoCities page. That was a platform-controlled identity layer too. It died when Yahoo shut it down. .gram could be the same: a nostalgic experiment that fades when the next pivot comes. The projects that survive bear markets are those with structural honesty—protocols that can function without a single leader, without a single server. Bitcoin, Ethereum, even ENS at its core—they have a degree of decentralization that allows them to weather storms. Telegram’s .gram, as currently conceived, does not. So where does that leave us? The takeaway is not to reject .gram outright, but to demand more. We need to see the technical implementation before we celebrate. Will Telegram use DNSSEC? Will it allow domain transfers? Will it integrate with TON for ownership records? Will it provide a mechanism for users to exit? These are the questions that separate a tool from a trap. As I’ve written many times, we chart the code, but the soul chooses the path. The code for .gram is being written now. The question is whether the soul of Telegram—its commitment to user autonomy—will choose the path of true decentralization or the path of a polished walled garden. In a bear market, when every protocol is bleeding, the ones that survive are the ones that treat their users as sovereigns, not as tenants. I hope Telegram makes the right choice. But I’m not holding my breath.