The company principles are following:

Authority. Own X.509 certificate authority [CA] ECC SECP384R1 SHA384. Each time user is being registered new PKCS-10 X.409 certificate enrollement is happened. It can be done by using command line utility.

Hierarchical domains. Own domain name server [NS] DNSSEC. The structure of hosted service is driven by own DNS server;

Distributed directory. Distributionally controlled [ABAC] support for multi-hierarchy domains. Top-level domain selects security admins for LDAP servers of the second-level;

Always encrypted. Encrypt any message GCM/CCM [N2O] X.509 Envelope. Each message being sent is encrypted with GCM/CCM symmetric cipher, no unsecure messages are allowed.

No message storage. Transient in-memeory (no-storage) queue [MQ]: TLS 1.3 Mosquitto or QUIC EMQX. No storage is used for storing messages. One massage receive is acknoledged by correspondent it is being deleted from MQTT transient in-memory queue;

No metadata. The messanger doesn't store any metadata information like IP addresses, hardware client information, etc. The CHAT is using only client, device, profile, roster internal identifiers for message routing purposes inside MQTT;

Client only roster storage. Roster subscription trees or messages [LDAP] are stored exclusively and paranoidal at client-side and transfered to new registered clients through MQTT. User can select not to store peer-to-peer subscriptions in LDAP directory but to store exclusively on client;

LDAP roster storage. Roster subscription trees [ROSTER] are stored in LDAP directory. Users can select to store their peer-to-peer subscriptions in LDAP directory;

Multi-roster with profile phone and mail table verification. Phone is not mandatory, email is not mandatory;

Open source foundation. Erlang ssl implementation outlived heartblead so all infrastructure services are written in Erlang and open sourced for verification. We remain compatible will all cerrified TLS clients. The sole author (BDFL) and technical architect is Namdak Tonpa.




The SYNRC CHAT division company structure is following:

Market competitors team: Threema, Signal, WhatsApp, Session, Element, Wire, Wickr;

Protocol team: BERT/ASN.1 protocol [Swift] [Erlang];

Frontend Development team: Swift iOS Client [Chat X.509] Sesign UX [Figma] [Swift];

Backend Development team: Erlang/OTP CA NS LDAP AUTH MQTT [mac] CHAT CLI;

Deployment and Operations team: NetBSD, Linux;

Client support team: Certs [SYNRC.PEM] Schema [SYNRC.LDIF] Zone [SYNRC.DNS].



Forms of cooperation:

— Autonomous deployments [Your Own] instance;
— Hosting by subscription [Our] instance;
— Multi-roster profiles support by subscription;
— Integration API SDK for public services [PARTNERS];
— Node analytics.



Made for people:

— Integrated alert channel system;
— B2C service channels (housekeeping);
— Calendar vCard iCal events tasks database;
— Clean iOS UI Zero deps package;
— Public text command line client with directory search;
— Governmental or Corporate X.509 identity ДСТУ 4145 authorisation.



The protocol specification:

The protocol entities:

Topics. The CHAT protocol communicates with actions/:client, events/:client, devices/:phone, contacts/:roster, private/:roster/:roster, room/:room MQTT topics.

Records. Sending through them Index, Typing, Search, Feature, Service, Presence, Friend, Tag, Link, Message, Member, Room, Contact, Star, Ack, Auth, Roster, Profile, History, push, io ETF-serialized messages.

Modules. The CHAT protocol is implemented in the set of sub-protocol modules: FILE, HISTORY, LINK, MESSAGE, PRESENSE, PROFILE, PUSH, ROOM, ROSTER, SEARCH, AUTH. For full specification follow priv/proto folder. The CHAT server implementation relies only on ISO/IETF connections such as DNSSEC, X.509 CSR, LDAP, QUIC, WebSocket, MQTT.

Applications. CHAT is a simple instant messaging server based on ISO standards. It uses MQTT protocol and ETF binary serialization from Erlang/OTP across applications: MQTT, N2O, KVS, MAIL, LDAP, NS, CA. Secure by default. The CHAT application has Sign/Verify, Encrypt/Decrypt feature enabled for every single message passed by. The delivered messages are being deleted from MQTT instance after recipient acknowledgment. This is Keybase, OTR, PGP (you name it) replacement for secure X.509 ASN.1 defined communications.


iOS 13.0

Here you can download the open source iOS client written in Swift:


UNIX X Windows

The default X Windows client application globally available for WSL, Linux and Mac written in C. The X.ORG CHAT X.509 client is based on: 1) X Windows Toolkit (Xt), 2) X Windows Library (Xlib) and 3) OpenGL for X Windows (GLX 1.3).

CHAT-X509-GUI.PDF — C console client for X Windows (xt, xlib, GLX, C99).



Here you can download the open source command line client:

The CHAT includes text message delivery system base on SYN buil-in Erlang/OTP message broker along with MQTT. The implementation of SYNRC CHAT CLI protocol is trying to be informative but not excessive, it should take care of run-time edge cases but not too stable. CLI text protocol is dedicated for demo purposes and really short message when you don't have access to mobile clients, it doesn't support file upload and voice calls. It is basically SMPT done right: HELP, BOX, CUT, AUTH, SEND, LIST.

$ chat-x509 -c wss:// > HELP < AUTH <user> | SEND <user> <msg> | BOX | CUT <id>. > AUTH buddha < USER buddha > SEND rocco HELO < ERROR user doesn't exist. > AUTH rocco < USER rocco > SEND buddha OK < NOTIFY rocco:buddha:1556151953113322286:OK < ACK "1556151953113322286" > AUTH buddha < USER buddha > BOX < LIST rocco:buddha:1556151953113322286:OK > SEND buddha this is me < NOTIFY buddha:buddha:1556152151055371152:this is me < ACK "1556152151055371152" > SEND buddha back again < NOTIFY buddha:buddha:1556152157283311935:back again < ACK "1556152157283311935" > BOX < LIST rocco:buddha:1556151953113322286:OK buddha:buddha:1556152151055371152:this is me buddha:buddha:1556152157283311935:back again > CUT 1556152157283311935 < ERASED 3 > BOX < LIST >



[1] 2010-10-18 LDAP
[2] 2020-02-03 Кваліфікований Електронний Підпис
[3] 2023-06-22 CMS Месенжер (Пітч)
[4] 2023-06-30 ЧАТ X.509 (Домашня сторінка)
[5] 2023-07-05 CMS S/MIME
[6] 2023-07-16 CMS Compliance
[7] 2023-07-20 LDAP Compliance
[8] 2023-07-25 LDAP 13.7.24 (Домашня сторінка)
[9] 2023-07-30 CA X.509 (Домашня сторінка)
[10] 2023-07-21 CMP/CMC/EST
[11] 2023-07-21 MLS ROOM CHAT
[12] 2023-08-05 CA CURVE
[13] 2023-08-07 CHAT ASN.1
[14] 2023-08-08 ASN.1 Компілятор