Technical DocsProtocol

Protocol

Inline Protocol v1 carries Realtime V3. It uses the MTProto 2.0 secure-transport construction with Inline endpoints, keys, sessions, schema, and RPCs.

Construction

  • Handshake: pinned RSA keys, RSA_PAD, finite-field DH, nonces, and transcript validation.
  • Records: MTProto 2.0 KDF, AES-256-IGE, message keys, salts, sessions, message IDs, sequences, and direction checks.
  • Authorization: permanent device key plus bound temporary keys.
  • Temporary keys: 24-hour lifetime; rotate at 80%.
  • Reliability: containers, ACKs, resend/state requests, cached results, clock correction, and replay rejection.
  • Carrier: obfuscated abridged framing over binary WebSocket.
  • Application: inline.invoke, inline.result, and inline.update contain Protocol Buffer bytes.
  • No Telegram API or endpoint compatibility.

Specification

Implementations