Skip to content
lqxpPublic

About

Light QX Protocol is as lightweight E2EE irc-like network for private messaging.

Topics

Resources

Stars

13 stars

Watchers

1 watching

Forks

Repository files navigation

LQXP logo

LQXP Protocol Server

The lightweight, end-to-end encrypted messaging backbone behind QxChat. Rooms, voice, and cryptographic privacy — self-hosted in minutes.

License: MIT Rust Axum WebSocket Post-Quantum SQLite / Postgres Docker E2EE

Try the web app · Download · Wiki · Discord · GitHub


What is LQXP?

LQXP (Light Quantum X Protocol) is an open, IRC-inspired messaging protocol with end-to-end encryption at its core — and this repository is its reference server, written in Rust. It relays rooms, messages, presence, voice signaling, and files without ever seeing plaintext: every payload is encrypted client-side before it touches the wire.

Rooms are ephemeral. Keys stay with you. The server sees nothing.

flowchart LR
    subgraph clients [Clients]
        WEB["Web · qxch.at/app"]
        DESK["Desktop · Tauri"]
        MOB["Android"]
    end
    subgraph server [qxprotocol · :4560]
        WS["Axum WebSocket"]
        API["REST API"]
        DL["Downloads"]
    end
    DB[("SQLite / Postgres")]
    TURN(["TURN relay"])


    WEB <--> WS
    DESK <--> WS
    MOB <--> WS
    WEB <--> API
    DESK <--> API
    MOB <--> API
    WS <--> DB
    API <--> DB
    DESK -. voice media .-> TURN
    MOB -. voice media .-> TURN
Loading

Features

Transport & cryptography

  • ★ Blind relay core — the server stores ciphertext, routes frames, and enforces rate limits. No plaintext, no metadata mining.
  • ★ Post-quantum ready — ML-KEM-768 key exchange and ML-DSA/SLH-DSA signatures alongside ECDSA P-256 (primitives).
  • ★ QXP-PHANTOM — the ghost-rendezvous friend protocol: blind mailbox slots, sealed envelopes, opaque blocking (spec).
  • ★ QxCloudSync — device-to-device sync over the same blind relay: hybrid PQ handshake, epoch keys, self-healing mesh (spec).
  • ★ Tor-friendly — clients can route through Tor; relay directory and circuit views included.

Messaging & calls

  • ★ Rooms & DMs — tokens, roles, pins, threads, polls, whiteboard, spoiler particles.
  • ★ Voice calls — WebRTC peer-to-peer audio with TURN relay fallback and per-user volume.
  • ★ Files & media — images, audio, video, arbitrary files, link previews — encrypted like any message.
  • ★ Pseudonymous accounts — username-based identity, 12-word recovery, no email or phone required.

Operations

  • ★ One binary — qxprotocol, configured by a single TOML file, SQLite out of the box, Postgres when you grow.
  • ★ Docker & bare metal — Compose stack, systemd units, PM2 and Pelican recipes included.
  • ★ Built-in web client — the server owns a web checkout and rebuilds it on every startup; zero separate frontend deploy.
  • ★ Anti-abuse baked in — rate limits, quota tokens, VDF + CAPTCHA challenges, Privacy Pass (details).

Repositories

Repository Stack Description
lqxp/lqxp Rust This server — the protocol reference implementation.
lqxp/client Vue 3 Official web client: in-browser E2EE, WebRTC calls, offline-capable UI.
lqxp/app Tauri · Nix Packaged desktop (Linux, macOS, Windows) and Android app with reproducible builds.
lqxp/site Nuxt getqxchat.com — landing, wiki, and downloads.
qxchat.ts TypeScript High-performance selfbot SDK for QXChat, native for Bun.

Quickstart

Prerequisites: Rust 1.88+, git, bun, and a writable QXP_ROOT with outbound access to GitHub and the Bun registry.

git clone https://github.com/lqxp/lqxp
cd lqxp
cp files/config.example.toml files/config.custom.toml
$EDITOR files/config.custom.toml   # [api], [web], [network], [rtc], [database], [security]
cargo run --release
# Server listens on :4560 — open http://localhost:4560/app/

First boot with an empty database refuses to start on purpose: add createIfMissing = true under [database] once, start, then remove it. For production updates on bare metal, ./update.sh pulls, rebuilds, and restarts via PM2.

Docker

docker compose up -d --build
# mounts: files/config.custom.toml (ro), files/qxp.sqlite, files/database.json

Deployment guides: Docker · TURN · deploy/ (systemd, PM2, Pelican, TURN).


Protocol reference

The explain/ directory is the deep technical reference — the same source material as the public wiki:

Doc Covers
01 · Architecture Client/server state model and component map
02 · Accounts & auth Registration, login, recovery, sessions
03 · Client signatures Device keys, contextual keys, hybrid signatures
04 · Message transport WebSocket opcodes and the E2EE envelope
05 · PHANTOM Friend rendezvous: prekeys, slots, envelopes, roster
06 · Primitives Exact hashes, KDFs, ECDSA, ML-DSA-65, ML-KEM-768
07 · Anti-abuse Rate limits, quota tokens, VDF, CAPTCHA, Privacy Pass
08 · Changes Spec-vs-shipped gap report and changelog
09 · QxCloudSync Blind-relay device sync, epochs, deepMerge

Configuration surface

Section Purpose
[api] Public domain, ports, hosted entry points
[web] Web client source (repo, directory, fresh, or pinned tag)
[network] Upload dir, public dir, embedded webchat index
[rtc] TURN servers, relay-only mode, call switches
[database] SQLite path / Postgres URL, createIfMissing
[security] Captcha, VDF difficulty, Privacy Pass, abuse thresholds

Desktop/mobile client builds additionally accept QXP_SERVER_ORIGIN, QXP_API_BASE_URL, QXP_WS_URL, QXP_TURN_URLS, QXP_TURN_USERNAME, QXP_TURN_CREDENTIAL, QXP_CALLS_ENABLED (see lqxp/app CI secrets).


Built on Internet · Open source · No tracking
qxch.at/app | download | wiki | discord.wf/qxchat | github.com/lqxp

About

Light QX Protocol is as lightweight E2EE irc-like network for private messaging.

Topics

Resources

Stars

13 stars

Watchers

1 watching

Forks

Sponsor this project

Contributors

Languages