How qwexaro/zephyr works
Zephyr is an early-stage F# Telegram MTProto library. Its principal documented workflow connects a TCP transport to a three-phase handshake that produces an AuthKey; the README’s sandbox invokes the transport and handshake. Other documented capabilities include TL binary serialization and schemas, cryptographic primitives, and secure session storage. Relationships beyond those shown in the README are omitted or marked unverified: no source excerpts were provided.
Main entry points: HandshakeEngine.fs Handshake engine · TcpTransport.fs TCP transport · AesIge.fs AES-IGE · Hash.fs Hashing
Components 14
Network and handshake
- TCP transport
Core/TcpTransport.fs - Handshake engine
Core/HandshakeEngine.fs - Auth key
Core/HandshakeEngine.fs
Cryptography
- AES-IGE
Crypto/AesIge.fs - Hashing
Crypto/Hash.fs - Key derivation
Crypto/Kdf.fs - Prime mathematics
Crypto/Prime.fs - RSA
Crypto/Rsa.fs
TL encoding
- TL writer
TL/TlWriter.fs - TL reader
TL/TlReader.fs - API schema
TL/Schema.fs
Session storage
- Session manager
Core/Session.fs
Other components
- Sandbox caller
- Telegram DC
Connections 11
- Sandbox caller → TCP transport: connects
README.md - Sandbox caller → Handshake engine: runs phases
README.md - TCP transport → Telegram DC: opens socket
README.md - Handshake engine → TCP transport: uses transport
README.md - Handshake engine → Auth key: generates
README.md - Handshake engine → TL writer: may serialize with
- Handshake engine → AES-IGE: may use
- Handshake engine → Hashing: may use
- Handshake engine → Key derivation: may use
- Handshake engine → Prime mathematics: may use
- Handshake engine → RSA: may use