😶 The account auto-deletion period has been changed. Accounts will now be deleted after 18 months of inactivity. Previously, the period was 12 months.

This change applies to newly created accounts and older accounts where the user has never changed this setting.

@telelakel

💎 One of the providers for buying cryptocurrency in Telegram's built-in Gram Wallet is Walt (ex. Wallet).

While analyzing how Onramp works, I was able to obtain the session data that Telegram creates when buying cryptocurrency with fiat. The server response lists wallet as the provider and telegram_wallet as the partner.

A separate session is created for the operation, after which Telegram opens @walt with the special parameter "isOnramp: true".

Currently, you can buy:
• Gram
• USDT on the TON network

The system also returns a list of available fiat currencies and checks supported currencies, payment methods, limits, and whether the operation is available in the user's region.

@telelakel

💻 Telegram is rewriting its MTProto network stack in Rust after more than 10 years

In the Beta versions of Telegram for iOS and macOS, a new MTProtoRustEngine has appeared — a network engine implementation in Rust that is gradually replacing MTProtoKit.

MTProtoKit is Telegram's old network stack for Apple platforms. It has been developed for more than 10 years and is built with C, Objective-C, and C++. Public references to MtProtoKit for iOS and OS X date back to 2014.

Telegram is now gradually moving this part of its Apple clients to Rust. The new engine already has its own network sessions, request handling, buffers, data center communication, and a separate layer for interaction between Rust and Swift. The old code isn't going anywhere yet. Both engines are present in the client at the same time — MTProtoKit and Rust. Switching between them is handled by SwitchingNetworkEngine: if the new engine can't continue working, unfinished requests can be passed back to the old one.

There are also conditions under which the Rust engine isn't used, including Web Proxy, custom data center addresses, and certain app extensions. In these cases, Telegram continues using the old MTProtoKit.

Telegram has also added the mtproto_engine_rust_disabled configuration, which allows the server to forcibly disable the Rust engine. Together with the fallback to MTProtoKit, this allows Telegram to gradually move clients to the new stack and return to the old implementation when needed — without releasing a new client version.

@telelakel | #new_tgbeta

🤖 Telegram has expanded Serverless with support for hosting Mini Apps.

The new update allows developers to host a Mini App's frontend and backend directly on Telegram's infrastructure.

The frontend can be deployed to an address like "app<app_id>.tgcloud.ai", while backend logic can be placed in tgcloud/endpoints/ and called from the Mini App using
Telegram.WebApp.Serverless.call().

Telegram handles user authorization, while the Serverless environment provides access to SQLite, the Bot API and external HTTP requests.

This means developers can run a complete Mini App without hosting the frontend or maintaining their own backend server.

The update is available with Serverless CLI 0.2.0.

Previously mentioned:
[View 1], [View 2], [View 3], [View 4], [View 5]

@telelakel