MTProto

Does not exist

Not unfinished — absent. There is no protocol layer, and no component under construction that would produce one. See implementation status.

There is no MTProto layer for GROM. Not an unfinished one — none at all, and no component currently under construction that would produce one.

This page exists because the question comes up immediately for anyone arriving from Telegram, and because several parts of the wider specification quietly assume such a layer exists. It does not.

What this means

If you are here to write a userbot, a custom client, or anything that logs in as a person rather than as a bot: you cannot, today.

• No TL schema, no DC addresses, no auth key exchange.
• Existing MTProto libraries have nothing to connect to.
• The developer portal is designed to issue api_id / api_hash pairs, but the portal itself has no sign-in yet — and a key would open a door that is not there.

What exists instead

GROM's messenger runs on its own HTTP and WebSocket core — a REST API plus a WebSocket stream, not MTProto. It is what the mobile app talks to. It is not documented for third parties and is not a public interface; treating it as one would be building against something that can change without notice.

The public surface being built for third-party code is the HTTP Bot API documented here. It covers bots. It does not cover acting as a user account.

If you need user-account access

There is no supported path right now. Two honest options:

• Model it as a bot. Most automation people reach for a userbot to do can be done by a bot with the right rights in the right chats — the exceptions are reading history the bot was not present for, and acting as a specific human.
• Wait. A protocol layer is a large piece of work with no start date. Nothing on this site should be read as a commitment that it is coming.

If your project genuinely requires user-level protocol access, plan on the assumption it will not exist, rather than on a schedule nobody has published.