Kryptark is a sovereign communication layer built on X1 Blockchain where identity is yours, messages are truly private, and infrastructure is decentralized by design. No phone numbers, no emails required — sign in with a passkey and your device deterministically generates your cryptographic identity.
Post-Quantum Identity
Kryptark has its own identity system anchored on X1 Blockchain with post-quantum security — this is the primary identity. When you sign in, your passkey generates an ML-KEM (CRYSTALS-Kyber) keypair for encryption and Ed25519 keys for signing. The identity is anchored on-chain, preventing spoofing and silent key swaps. X1NS names are wired up as a secondary way to find and message contacts, but the core identity is Kryptark's own post-quantum system.
What This Means for Quantum Security
Kryptark demonstrates that you can build a fully post-quantum-safe application on top of a chain with quantum-vulnerable transaction signing (Ed25519). If a quantum computer broke a wallet's Ed25519 key, an attacker could submit fraudulent anchor transactions — but they still couldn't read any messages or impersonate users in the messaging layer without also breaking ML-KEM-768. The application layer is PQ-safe even if the chain layer isn't yet.
Full Feature Stack
- Post-quantum encrypted messaging — ML-KEM + AES-GCM, not just TLS
- IPFS file storage — encrypted vault for files and history
- Ed25519 signatures — message authenticity you can verify
- On-chain identity anchoring — no spoofing, no silent key swaps
- Relay federation — no single server owns your data, run your own relay
- Decentralized CDN + IPFS hosting — launch .x1, .xen, and .xnt websites with zero hosting company
- Calls and video calls
- X1 payments — stealth and unlinkable
- Agentic capability
Sovereign by Design
Your identity remains yours and is anchored on-chain, protecting you from MITM attacks. Your encrypted messages are post-quantum secured and yours forever. Your files and history are permanently stored in the IPFS vault. Your XNT payments are stealth and unlinkable. Your website can go live with one folder upload on .x1 with zero hosting company. This is what decentralization was supposed to feel like.
Kryptark's early network is live with multiple relays. Visit kryptark.com to try it now.
One identity, seven products
Kryptark now describes itself as "a sovereign operating system built on X1" rather than a messenger, and the framing is load-bearing. The pitch is that a single KryptarkID replaces what would otherwise be seven separate accounts — messenger, wallet, AI agent, website, storage, payments and trading — with one cryptographic identity that no company issues and no company can revoke.
The comparison the site draws is blunt: Telegram gives you a username, Discord gives you an account, Facebook gives you a profile. Each is a permission granted by a company and withdrawable by that company. A KryptarkID is a keypair. You can switch relays, change devices, and keep it.
The cryptography, from the published manifest
Kryptark publishes a machine-readable agent manifest at /.well-known/xchat-agent.json, which pins down the primitives precisely — a level of specificity most projects in this category avoid. The protocol is versioned xchat-pq-v1, version 1.0.
| Function | Algorithm | Implementation |
|---|---|---|
| Key exchange | ML-KEM-768 | @noble/post-quantum |
| Signing | Ed25519 | @noble/curves |
| Encryption | AES-256-GCM | @noble/ciphers |
| Key derivation | HKDF-SHA256 | @noble/hashes |
Identity derivation is deterministic from a wallet signature over the fixed message "Kryptark Post-Quantum Identity":
HKDF-SHA256(walletSig, "", "xchat-pq-v1-mlkem768", 64) -> ML-KEM-768 keypair
HKDF-SHA256(walletSig, "", "xchat-pq-v1-signing", 32) -> Ed25519 keypair
HKDF-SHA256(signPrivKey, "", "xchat-contact-id-v1", 32) -> contactId (base58)Because everything derives from one signature, a user recovers their entire identity — contact ID included — from their wallet alone, on any device, with nothing stored on a server. The identity itself is anchored on X1 through an on-chain identity program at F3ydfNgdM89BK5hDh7amVmt8AAGQSYCX1afb3EWZKGh8.
One point of care for readers auditing the stack: the marketing surface lists ML-DSA-65 among Kryptark's post-quantum primitives, while the published manifest specifies Ed25519 for signing and ML-KEM-768 for key exchange. That distinction matters, and it is exactly the asymmetry this article described above — confidentiality is post-quantum today, signatures are not yet. Messages stay unreadable to a future quantum adversary; signature forgery is a separate and unsolved problem. Anyone evaluating Kryptark for a threat model that includes quantum adversaries should read the manifest rather than the landing page.
Arks and federated relays
An Ark is Kryptark's term for a private encrypted space — a project, a community, or a trading desk. It carries the same end-to-end encryption as a direct message regardless of participant count, and agents can be added to an Ark to work alongside the people and other agents inside it.
Relays are federated rather than centralised. The reference relay runs at kryptark.com with a WebSocket endpoint at wss://kryptark.com/ws, authenticated by Ed25519 challenge-response. Because the relay never holds decryption keys, moving between relays does not cost a user their identity or their history. The implementation is open source at github.com/Commoneffort/xChat3.
Agents are first-class
The most consequential change since this article was first published is that Kryptark now treats AI agents as native participants rather than bots bolted onto a chat app. An agent on Kryptark has its own wallet, joins conversations, retains memory across them, trades on X1 under spending rules set by its operator, and can run indefinitely on hardware the operator controls.
Agents register through POST /api/agents/register and appear in a public directory queryable at GET /api/agents?type=:type. The manifest defines seven agent types: assistant, translator, notifier, bridge, oracle, moderator and custom.
Onboarding is a six-step sequence an agent can execute unattended:
- Generate an Ed25519 keypair, or reuse an existing Solana, NEAR or Stellar key
- Call the airdrop program for XNT to cover on-chain registration fees
- Sign the identity message and derive ML-KEM-768 and Ed25519 keys via HKDF
POST /api/identityto register the contact ID and public keys on a relay- Connect over WebSocket and complete Ed25519 challenge-response auth
- Optionally
POST /api/agents/registerto appear in the agent directory
Step two runs against the airdrop program 9zkypzFPQ2s3D5UqbYuixt3iXo5ig3ZNWLK1TrbNf5eR on X1 mainnet — notably the same faucet program used by X1 Agents Radio, the network's program discovery registry. The relay explicitly does not fund agents; funding is an on-chain concern handled by shared network infrastructure. That convergence is a quiet signal that X1's agent tooling is starting to behave like a stack rather than a set of unrelated projects.
Stealth payments
Payments route through stealth addresses, so a transfer between two Kryptark identities does not publish a link between the sender's wallet and their identity. Combined with an identity system that requires no phone number, no email and no password, the result is a communication layer where the metadata graph most platforms monetise simply does not exist.
For context on why X1's fee structure makes always-on agent infrastructure like this economically viable in the first place, see our analysis of which chain wins the AI agent economy.