Skip to main content

Introduction

MicroToken Exchange (MTE)​

Eclypses has developed a new low-latency, secure, and proprietary technology that empowers systems and connected devices to communicate with unprecedented levels of privacy and security. The MTE is our core technology and undeniably the future of secure communication in a digital landscape.

The MTE uses NIST-approved Deterministic Random Bit Generators (DRBGs) to create random values as a data substitute, a random stream of values! The random streams of values are not derived from your data and have no discernable relation to your data or any other generated random stream of values. A connected endpoint equipped with MTE can accept a random stream of values and recover your data. Generated substitute values are unique and completely random even when sending the same data multiple times. The MTE can operate at extremely low latency, enabling applications such as real-time, high-definition video streaming with unparalleled data security.

To accomplish this level of performance and security, MTE is written in the C language, and Eclypses provides interfaces in various languages allowing the MTE to be implemented in any application. The MTE can secure data transmissions between servers, cloud environments, connected IoT devices, Web Pages, Mobile Apps, and LoRaWAN devices. It works in most environments, including Apple iOS, macOS, Android, Windows, Linux, and MIPS. Our technology is small in disk size, has a well-defined API, and is easily implemented into most systems.

SocketX​

SocketX applies MTE protection to WebSocket traffic without requiring you to rewrite your applications. It runs on both the client and the server, and facilitates quantum-resistant data encryption for WebSocket traffic across unprotected, public networks.

Each payload is secured uniquely with a single-use key that is never repeated and not derived from the data being secured. Session entropy is established with a Kyber post-quantum key exchange, and both text and binary WebSocket frame semantics are preserved end to end.

SocketX consists of two components built on the same MTE core:

SocketX Server​

A WebSocket proxy server that runs in a Docker container. Stand it up in front of your backend WebSocket service — it terminates MTE-protected connections from SocketX clients, decodes payloads inside the proxy, and forwards standard WebSocket frames to your unchanged backend.
Click here to learn more.

SocketX Client Libraries​

Near drop-in replacements for the native WebSocket APIs on every major client platform — JavaScript for the web, plus iOS, Android, and Flutter. The MTE handshake, pairing, and encryption/decryption are handled automatically.
Click here to learn more.

How it works​

[Your client app]  ── MTE-encoded WebSocket ──▶  [SocketX Server]  ── plaintext ws:// or TLS wss:// ──▶  [Your WebSocket API]
   SocketX client SDK                              Docker container                                        Unchanged
  1. Your application creates a SocketXClient (or platform equivalent) pointed at your SocketX Server.
  2. The client and server perform the SocketX handshake: a Kyber key exchange establishes MTE entropy, and an encoder/decoder pair is created on each side.
  3. The client tells the server which upstream pathname to connect to, and the server dials your backend WebSocket service.
  4. From then on, every message between client and server is MTE-encoded. The server decodes client messages and forwards plaintext frames to your backend; backend responses are MTE-encoded before returning to the client.