MTProto encryption protocol
E357597
MTProto encryption protocol is Telegram’s custom-designed cryptographic protocol that secures user data and message transmission across its messaging platform.
All labels observed (7)
| Label | Occurrences |
|---|---|
| MTProto | 1 |
| MTProto 1.0 | 1 |
| MTProto 2.0 | 1 |
| MTProto encryption protocol canonical | 1 |
| MTProto message encryption | 1 |
| MTProto protocol specification | 1 |
| MTProto transport protocol | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T3419604 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MTProto encryption protocol Context triple: [Telegram, securityFeature, MTProto encryption protocol]
-
A.
Secure Authentication Version 5
Secure Authentication Version 5 is a security enhancement for the DNP3 protocol that provides robust authentication and protection against unauthorized control and cyber attacks in industrial control systems.
-
B.
SSH Encryption Algorithm Names
SSH Encryption Algorithm Names are standardized identifiers used within the SSH protocol to specify which cryptographic ciphers are employed to secure data in transit.
-
C.
ZRTP
ZRTP is a cryptographic key-agreement protocol designed to enable end-to-end encryption for real-time voice and video communications over RTP-based systems.
-
D.
Diffie–Hellman key exchange
Diffie–Hellman key exchange is a foundational cryptographic protocol that enables two parties to securely establish a shared secret over an insecure communication channel.
-
E.
DTLS
DTLS (Datagram Transport Layer Security) is a protocol that provides TLS-like encryption, integrity, and authentication for datagram-based communications such as UDP.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MTProto encryption protocol Target entity description: MTProto encryption protocol is Telegram’s custom-designed cryptographic protocol that secures user data and message transmission across its messaging platform.
-
A.
Secure Authentication Version 5
Secure Authentication Version 5 is a security enhancement for the DNP3 protocol that provides robust authentication and protection against unauthorized control and cyber attacks in industrial control systems.
-
B.
SSH Encryption Algorithm Names
SSH Encryption Algorithm Names are standardized identifiers used within the SSH protocol to specify which cryptographic ciphers are employed to secure data in transit.
-
C.
ZRTP
ZRTP is a cryptographic key-agreement protocol designed to enable end-to-end encryption for real-time voice and video communications over RTP-based systems.
-
D.
Diffie–Hellman key exchange
Diffie–Hellman key exchange is a foundational cryptographic protocol that enables two parties to securely establish a shared secret over an insecure communication channel.
-
E.
DTLS
DTLS (Datagram Transport Layer Security) is a protocol that provides TLS-like encryption, integrity, and authentication for datagram-based communications such as UDP.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
cryptographic protocol
ⓘ
secure messaging protocol ⓘ |
| designedBy | Telegram ⓘ |
| documentationURL | https://core.telegram.org/mtproto ⓘ |
| doesNotProvideProperty | end-to-end encryption for default cloud chats ⓘ |
| encryptionLayer |
MTProto encryption protocol
self-linksurface differs
ⓘ
surface form:
MTProto message encryption
|
| firstUsedBy | Telegram mobile apps ⓘ |
| hasCriticism |
limited external peer review compared to open standards
ⓘ
use of non-standard cryptographic constructions ⓘ |
| hasVersion |
MTProto encryption protocol
self-linksurface differs
ⓘ
surface form:
MTProto 1.0
MTProto encryption protocol self-linksurface differs ⓘ
surface form:
MTProto 2.0
|
| improvedInVersion | MTProto 2.0 addressed weaknesses of MTProto 1.0 ⓘ |
| keyDerivation | based on nonces and server salt ⓘ |
| messageStructure | binary, TL-serialized messages ⓘ |
| providesProperty |
confidentiality
ⓘ
forward secrecy (in secret chats) ⓘ integrity ⓘ replay protection ⓘ |
| purpose |
client-server communication security
ⓘ
end-to-end encryption of messages ⓘ protect user data in transit ⓘ |
| securityModel | custom, non-standard design ⓘ |
| specificationMaintainedBy |
Telegram
ⓘ
surface form:
Telegram Messenger LLP
|
| status | proprietary ⓘ |
| supportsFeature |
cloud chats
ⓘ
secret chats ⓘ |
| supportsPlatform |
Android
ⓘ
Linux ⓘ Windows ⓘ iOS ⓘ macOS ⓘ |
| transportLayer |
MTProto encryption protocol
self-linksurface differs
ⓘ
surface form:
MTProto transport protocol
|
| usedBy |
Telegram
ⓘ
surface form:
Telegram Messenger
|
| usedFor |
VoIP signaling in Telegram
ⓘ
desktop messaging ⓘ mobile messaging ⓘ |
| usesConcept |
authorization key
ⓘ
message key ⓘ sequence numbers ⓘ server salt ⓘ |
| usesHashFunction | SHA-256 ⓘ |
| usesKeyExchange |
Diffie–Hellman key exchange
ⓘ
surface form:
Diffie–Hellman
|
| usesMode | AES-256-IGE ⓘ |
| usesPrimitive |
Advanced Encryption Standard
ⓘ
surface form:
AES
Diffie–Hellman key exchange ⓘ RSA ⓘ SHA-256 ⓘ |
| usesPublicKeyAlgorithm | RSA-2048 ⓘ |
| usesSerializationFormat | Telegram TL language ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: MTProto encryption protocol Description of subject: MTProto encryption protocol is Telegram’s custom-designed cryptographic protocol that secures user data and message transmission across its messaging platform.
Referenced by (7)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject surface form:
MTProto
this entity surface form:
MTProto 1.0
subject surface form:
MTProto
this entity surface form:
MTProto 2.0
MTProto encryption protocol
→
transportLayer
→
MTProto encryption protocol
self-linksurface differs
ⓘ
subject surface form:
MTProto
this entity surface form:
MTProto transport protocol
MTProto encryption protocol
→
encryptionLayer
→
MTProto encryption protocol
self-linksurface differs
ⓘ
subject surface form:
MTProto
this entity surface form:
MTProto message encryption
this entity surface form:
MTProto
this entity surface form:
MTProto protocol specification