🪙 Is Telegram making Gram Wallet harder to block?

⚫️ Telegram Desktop developer John Preston has published tproxy-server, an experimental web proxy for Telegram. Preston says he vibe-coded the project, and the repo itself describes it as a proof of concept, but the idea is laid out pretty clearly in the documentation.

⚫️ Normally, the Telegram client connects directly to Telegram’s servers. With an MTProto Proxy enabled, that traffic is routed through an intermediary proxy instead, helping users bypass network restrictions. tproxy-server adds another layer: it tunnels those proxy connections over ordinary HTTPS requests to a hostname that still behaves like a regular website to everyone else.

⚫️ Meanwhile, references to a new MTProto layer for TON have appeared in the Telegram iOS beta. According to teleLakel, requests to TON Center are routed through Telegram’s servers rather than being sent directly from the app.

⚫️ Why does that matter? Any wallet needs to talk to the network somewhere when checking balances or broadcasting transactions. Usually, that means connecting to a node or an API provider such as TON Center. If Telegram puts its own servers between the client and TON Center, the wallet no longer needs to connect to the public TON Center endpoint directly, making that connection much harder for an ISP to target or block.

⚫️ There is no confirmed link between the two developments. But amid restrictions on Telegram in Russia, one plausible explanation is that tproxy-server could help tunnel Telegram traffic over ordinary HTTPS, while the new TON layer could remove Gram Wallet’s direct dependency on publicly reachable TON infrastructure. For a wallet that is supposed to live directly inside Telegram, some extra resilience against blocking certainly wouldn’t hurt.

@thedailyton