From the publisher · ITANU

ITANU publishes this magazine and makes the products this article is about. It is the company’s own account, not news reporting.

KolChat checks its encryption against published standards on every device

KolChat's encryption reproduces the test vectors published with RFC 7748, RFC 8032 and RFC 5869, and all 133 of its protocol tests pass. Encrypting a message takes 0.58 milliseconds.

Numbers in brackets link to the sources listed below.

Every message, file, voice note and call in KolChat, our chat app, is encrypted on the sender's device and can be opened only on the devices of the people in the conversation[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. On 21 November 2026 we ran the full set of checks behind that sentence[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. The building blocks reproduced the test vectors published with the standards they implement, all 133 tests of the protocol passed, and encrypting a message took 0.58 milliseconds[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]].

What stays between the people talking

The keys that open a KolChat conversation exist only on the devices of the people in it[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. That covers message text, edits, reactions, read receipts, files, photos, voice notes, the notification preview, the set-up of a call and its audio and video[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. Our servers pass sealed data between devices and store it sealed until it is delivered[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. They hold no key that opens it[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]].

Two-person chats in KolChat follow X3DH and the Double Ratchet, the designs published by Signal[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. X3DH lets two people agree on a shared secret key even when one of them is offline[3SignalThe X3DH Key Agreement ProtocolOpen sourceSources [3]]. The Double Ratchet derives a new key for every message, so that a key obtained later cannot be used to work out earlier ones[4SignalThe Double Ratchet AlgorithmOpen sourceSources [4]]. KolChat deletes each message key after it is used[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]].

The same answers as the standards

RFC 7748, RFC 8032 and RFC 5869 each include test vectors, fixed inputs printed together with the outputs an implementation is expected to produce[5RFC EditorRFC 7748: Elliptic Curves for SecurityOpen sourceSources [5], 6RFC EditorRFC 8032: Edwards-Curve Digital Signature Algorithm (EdDSA)Open sourceSources [6], 7RFC EditorRFC 5869: HMAC-based Extract-and-Expand Key Derivation Function (HKDF)Open sourceSources [7]]. We check KolChat's key exchange against the test vectors of RFC 7748, its signatures against those of RFC 8032, its key derivation against those of RFC 5869, and its encryption against a NIST test case for AES-256-GCM[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. All pass[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]].

We do not stop at our own machines[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. Before a phone or a computer uses its native implementation of the key exchange and signatures, KolChat runs the RFC 7748 and RFC 8032 test vectors on that device and then compares 64 random inputs with a reference implementation[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. A device that gives a single different answer uses the reference implementation instead[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]].

All 133 protocol tests pass

The protocol's test suite has 133 tests, and all 133 passed on 21 November 2026[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. They run a long two-way conversation, deliver messages out of order, skip messages across key changes and replay an old message, which is refused[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. A message changed in transit is refused and the conversation carries on[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. A one-time key works once[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. A forged device signature is refused[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. In a group, a member the server tried to add receives no key[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]].

Files get the same treatment[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. Each file has its own random key and is encrypted in pieces, and a file that was cut short, reordered or changed by a single bit does not open[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]].

Half a millisecond for a message

We measured the cost of all this on an Apple M5 Max Mac on 21 November 2026, taking the middle value of three runs[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. Starting an encrypted conversation with a new contact took 11.6 milliseconds of computation[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. Encrypting a 200-byte message took 0.58 milliseconds and decrypting it took 0.12 milliseconds[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. A group message took 2.8 milliseconds to encrypt and sign and 1.9 milliseconds to check and decrypt[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]].

What a person sees

Each device on an account has its own keys, and KolChat encrypts a message separately for every device of every recipient[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. Two people can compare a 60-digit security code, or scan a QR code, to confirm they hold each other's keys[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. If a contact's code changes, KolChat says so, and for a contact you had verified it stops sending until you accept the change[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]]. When someone leaves a group, the group's keys are replaced, so a person removed from a group cannot read what is sent afterwards[1ITANUITANU's own account: KolChat's encryption, checked against the public standardsOpen sourceSources [1]].

These are our own tests of our own implementation, run on our own machines[2ITANUKolChat checks its encryption against the published standards on every device before using itOpen sourceSources [2]]. The test vectors are public, in the documents named above[5RFC EditorRFC 7748: Elliptic Curves for SecurityOpen sourceSources [5], 6RFC EditorRFC 8032: Edwards-Curve Digital Signature Algorithm (EdDSA)Open sourceSources [6], 7RFC EditorRFC 5869: HMAC-based Extract-and-Expand Key Derivation Function (HKDF)Open sourceSources [7]].

Sources

  1. 1
    Material supplied by ITANU

    SuppliedITANU's own account: KolChat's encryption, checked against the public standardsAccessed

  2. 2
    Material supplied by ITANU

    SuppliedKolChat checks its encryption against the published standards on every device before using itAccessed

  3. 3
    The X3DH Key Agreement Protocol

    PrimarySignalAccessed

  4. 4
    The Double Ratchet Algorithm

    PrimarySignalAccessed

  5. 5
    RFC 7748: Elliptic Curves for Security

    PrimaryRFC EditorAccessed

  6. 6
    RFC 8032: Edwards-Curve Digital Signature Algorithm (EdDSA)

    PrimaryRFC EditorAccessed

  7. 7
  8. 8
    CAVP Testing: Block Cipher Modes

    PrimaryNational Institute of Standards and TechnologyAccessed

ITANU’s newsroom system produced this article with AI and checked it against the sources listed above. How we work

ITANU Magazine

AI, computing and science news