Encryption by default, keys you control, and a blockchain designed so private data never goes on-chain. Here’s how it works.
Messages are sealed on your device with post-quantum hybrid encryption: ML-KEM-1024 (NIST security category 5 — the highest defined level) combined with ECDH P-256, content encrypted with AES-256-GCM. Only you and your recipient can read them.
Your private key is generated and stored locally — it never reaches our servers. Non-custodial: not even we can access your account or wallet.
Our relay transports encrypted blobs and never holds readable message content. Call audio/video flows peer-to-peer and isn’t stored.
Your chats, files and wallet contents are never stored on the blockchain. The chain only keeps a tiny digital fingerprint (a checksum) that proves nothing was tampered with — it can never be turned back into your content. Everything personal stays encrypted on your device.
Sealed sender is on by default: messages arrive without a readable sender on the envelope, so the server can't log who talks to whom. Built in — not an afterthought.
Our building blocks — ML-KEM-1024 (FIPS 203) for key exchange and AES-256 for content — are the exact algorithms the NSA’s Commercial National Security Algorithm Suite 2.0 mandates for U.S. national security systems up to TOP SECRET. The same math that protects classified military communications seals your chats. (An algorithm property — not a government certification of Lemniscate.)
Our key exchange runs two locks at once: a post-quantum one (ML-KEM-1024, NIST category 5 of 5) and a classical one (ECDH P-256). An attacker would have to break both — and traffic recorded today can't be unlocked by future quantum computers ("harvest now, decrypt later").
Disappearing messages, view-once media, app lock and screenshot protection put you in control of what lingers.
An optional second step at sign-in via an authenticator app (Google Authenticator, iPhone codes and more), plus one-time backup codes.
Blocks are sealed by authorized validators operated by the team; every full node independently verifies the chain.
An open validator set across providers and regions — no single point of control or failure.
Contracts and core modules follow an audit-first approach as they move to mainnet.
Found a vulnerability? We appreciate responsible disclosure. Email [email protected] with details and we’ll respond promptly. Please don’t exploit or disclose issues publicly before they’re fixed.
Read the details or just start using it — your keys, your data, by default.