[ GC/1 ] post-quantum · invitation-only
Encrypted chat with no center to compromise.
GChat is a leaderless messenger: every message is sealed end-to-end with hybrid post-quantum cryptography and relayed by hosts that hold nothing but ciphertext in memory. No account. No phone number. No server that can read, block, or enumerate the network.
public source + GitHub — coming soon | protocol spec — coming soon
- No accounts
- No phone numbers
- No tracking
- RAM-only relays
- End-to-end by default
[ 01 ] Security
Built for the worst case
Every layer assumes the network is hostile and that any single service can be compromised — including ours.
-
[ CRYPTO ]
Post-quantum from the first byte
Identity keys are ML-DSA-65; sessions combine X25519 with ML-KEM-768; groups use MLS (RFC 9420). Hybrid by default — there is no classical-only mode to fall back to.
-
[ NETWORK ]
No center to seize
A leaderless relay network with no accounts and no address-book service. Each message picks a fresh relay path, and every hop carries sealed cells it cannot read.
-
[ MEMORY ]
Relays keep nothing
Relay queues, overlays and peer views live in RAM only. There is no stored history to subpoena and nothing to reconstruct after a restart.
-
[ PRIVACY ]
Deniable by design
Message contents carry no signatures, so a delivered message cannot be proven to a third party. A Double Ratchet with a skipped-message window tolerates loss and reordering.
-
[ DEVICE ]
Local-first
Your archive is encrypted on your own machine with Argon2id-derived keys and AES-256-GCM. One local daemon serves both the terminal client and the web UI.
-
[ IDENTITY ]
Verifiable, pseudonymous
Safety numbers let two people confirm each other's keys out of band. Channels use per-channel pseudonyms and single-use invites with an expiry.
[ 02 ] How it works
Four steps, none of them a sign-up
No central account, no phone number, no directory of who talks to whom.
-
01
Create an identity
Keys are generated on your device. No email, no phone number, no sign-up server.
-
02
Invite someone
Single-use invitations carry a private introduction. The network is invitation-only by design.
-
03
Messages travel sealed
GC/1 splits traffic into padded, fixed-size cells and routes them through layered relay paths.
-
04
Only you can read it
Your client verifies the peer and decrypts locally. History stays in your encrypted archive.
// GC/1 · post-quantum hybrid · MLS (RFC 9420) · RAM-only relays
[ 03 ] Status
Where it stands
The honest version: what exists today, and what does not.
-
spec
v0.1-draft. The protocol specification and conformance vectors are being prepared for public release.
-
network
Live. An invitation-only relay network is running; access opens gradually.
-
clients
In development. Terminal client and local web UI; no public release yet.
-
audit
Not yet. No independent security audit has been performed; results will be published when it has.
Next
- public source release
- independent security audit
- signed builds for macOS, Linux and Windows
- wider availability
// this page lists only what exists today — nothing is marked shipped before it ships.
[ 04 ] FAQ
Questions
Is GChat open source?
Not yet publicly. The protocol specification, conformance vectors and clients are being prepared for a source release; the GitHub link will appear here when it lands.
How do I get access?
The network is invitation-only and there is no public sign-up. Access opens gradually.
What do I need to use it?
A desktop system and a passphrase. No account, email address or phone number.
Which platforms does it run on?
A terminal client and a local web UI, with per-user service support for macOS, Linux and Windows.
Can I run my own relays?
Yes. Relays and catalog services are self-hostable, and the network's defaults are signed so clients can verify what they connect to.
Has it been audited?
No. The protocol is a v0.1 draft and has not had an independent audit yet. Treat it as pre-release software.