KrayChat uses your Bitcoin Taproot keys for zero-knowledge encrypted messaging. DMs, Groups, and AI Agent channels — all E2E encrypted. No servers store your messages. Just pure cryptography.
No trust required. Verify everything.
Your Bitcoin address IS your chat identity. No phone numbers, no emails, no accounts. Just your Taproot key.
Messages are encrypted on your device before leaving. Only the recipient can decrypt. Even we can't read them.
Messages are stored only on your device. Delete them and they're gone forever. No cloud backups.
We don't track who talks to whom, when, or how often. The relay only routes encrypted packets.
Open the app, unlock your wallet, start chatting. No sign-ups, no verification, no waiting. On the browser extension, your password is only ever typed inside the extension popup — never on a web page.
Built on standard Bitcoin cryptography (secp256k1, ECDH, AES-256-GCM). Auditable and transparent.
Command your AI agent through a self-channel secured by Bitcoin signatures. Two auth modes: direct signing (pure crypto) or revocable bot tokens (zero crypto on the agent).
Create encrypted group chats. Each message is individually encrypted for each member. Admins manage members with signed operations.
Simple for users, bulletproof under the hood.
Unlock your wallet to activate the chat session — on the extension this happens in the KrayWallet popup (your password never touches the page); on mobile, inside the app. Your private key is derived locally (never leaves your device), and your public key becomes your Chat ID.
Give your Chat ID to anyone who wants to message you. It's safe to share - it's a public key, like a Bitcoin address.
Enter someone's Bitcoin address. The system automatically finds their Chat ID if they're registered on the network.
Using ECDH key exchange, a shared secret is created. Messages are encrypted with AES-256-GCM before sending.
The recipient uses their private key + your public key to derive the same shared secret and decrypt the message.
┌─────────────────────────────────────────────────────────────────────┐ │ KRAYCHAT ENCRYPTION FLOW │ └─────────────────────────────────────────────────────────────────────┘ YOUR DEVICE RELAY SERVER THEIR DEVICE ──────────── ──────────── ───────────── ┌─────────────┐ ┌─────────────┐ │ Your Private│ │Their Private│ │ Key │ │ Key │ └──────┬──────┘ └──────┬──────┘ │ │ │ + Their Public Key Your Public Key + │ │ ▼ ▼ ┌─────────────┐ ┌─────────────┐ │ ECDH │ │ ECDH │ │ Key Exchange│ │ Key Exchange│ └──────┬──────┘ └──────┬──────┘ │ │ ▼ ▼ ┌─────────────┐ ┌─────────────┐ │ SAME │ │ SAME │ │ Shared │ │ Shared │ │ Secret │ │ Secret │ └──────┬──────┘ └──────┬──────┘ │ │ Message + Secret Ciphertext + Secret │ │ ▼ ▼ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │ AES-256-GCM │────────▶│ Only sees │─────────────▶│ AES-256-GCM │ │ Encrypt │ │ ciphertext │ │ Decrypt │ └─────────────┘ │ (garbage) │ └─────────────┘ └─────────────┘ ╔═══════════════════════════════════════════════════════════════════╗ ║ ❌ Server NEVER sees: ║ ║ • Your private key ║ ║ • The shared secret ║ ║ • The message content ║ ║ ║ ║ ✅ Server ONLY sees: ║ ║ • Encrypted blob (ciphertext) ║ ║ • Public keys (to route messages) ║ ╚═══════════════════════════════════════════════════════════════════╝
The most secure way to command an AI agent. Two auth modes. Zero compromise.
KrayBot opens a channel where your address sends to your own address (from === to). This creates a cryptographically sealed private channel that only your private key can access.
When you send a command, your KrayWallet encrypts + signs the message with your Bitcoin private key. This proves you are the owner. No one else can impersonate you.
The relay detects from === to, recognizes it as a self-channel message, and routes it to your bot device. Token-based bots receive a plaintext bot_command; direct-signing bots receive the encrypted payload.
Token-based bots send a plaintext bot_reply (relay wraps and delivers). Direct-signing bots respond through the encrypted self-channel. Either way, the reply appears in your KrayBot tab.
┌─────────────────────────────────────────────────────────────────────┐ │ MODE A: TOKEN-BASED AUTH (Recommended for Platforms) │ └─────────────────────────────────────────────────────────────────────┘ YOUR DEVICE RELAY SERVER YOUR AI AGENT (Extension/Mobile) (kray.space) (Vitruvia/OpenClaw) ───────────────── ──────────── ────────────────── ┌──────────────┐ ┌──────────────┐ │ Your Wallet │ │ Bot Token │ │ Private Key │ │ (kbt_...) │ └──────┬───────┘ └──────┬───────┘ │ │ │ 1. Owner signs challenge 3. bot_auth(token) │ → relay issues kbt_ token → registered as │ → token goes to agent bot device │ │ │ 2. Encrypt + Send 4. Receive bot_command │ (ECDH self-key) (plaintext text) │ │ ▼ ▼ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │ Send message │────────▶│ from === to │────────────▶│ Receive as │ │ from: bc1p.. │ text + │ Route as │ bot_command│ { text: "…" }│ │ to: bc1p.. │ payload │ bot_command │ (plaintext)│ Process AI │ └──────────────┘ └──────┬───────┘ └──────┬───────┘ │ │ │ ┌──────────────┐ │ │◀─────│ bot_reply │◀─────┘ │ │ (plaintext) │ │ └──────────────┘ │ ▼ ┌──────────────┐ │ Route to │ │ owner devices│ └──────┬───────┘ │ ▼ You see the reply in KrayBot tab ╔═══════════════════════════════════════════════════════════════════╗ ║ TOKEN-BASED ADVANTAGES: ║ ║ ║ ║ • Agent needs ZERO crypto libraries (only WebSocket) ║ ║ • Private key NEVER leaves your KrayWallet ║ ║ • Token is revocable by owner at any time ║ ║ • Any platform (Vitruvia, OpenClaw, etc) can integrate easily ║ ╚═══════════════════════════════════════════════════════════════════╝
┌─────────────────────────────────────────────────────────────────────┐ │ MODE B: DIRECT SIGNING (Maximum Security) │ └─────────────────────────────────────────────────────────────────────┘ YOUR DEVICE RELAY SERVER YOUR AI AGENT (Extension/Mobile) (kray.space) (Self-hosted node) ───────────────── ──────────── ────────────────── ┌──────────────┐ ┌──────────────┐ │ Your Wallet │ │ Same Private│ │ Private Key │ │ Key │ └──────┬───────┘ └──────┬───────┘ │ │ │ Sign + Encrypt bot_register + │ (ECDH self-key) Schnorr signature │ │ ▼ ▼ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │ Send message │────────▶│ from === to │────────────▶│ Decrypt ECDH │ │ from: bc1p.. │ payload │ Route to bot │ encrypted │ Process AI │ │ to: bc1p.. │(E2E enc)│ devices │ payload │ Send reply │ └──────────────┘ └──────┬───────┘ └──────┬───────┘ │ │ │◀────────────────────────────┘ ▼ Fully E2E encrypted Relay sees NOTHING ╔═══════════════════════════════════════════════════════════════════╗ ║ DIRECT SIGNING ADVANTAGES: ║ ║ ║ ║ • Relay CANNOT read your commands or responses ║ ║ • True E2E — no intermediary can see content ║ ║ • Ideal for self-hosted nodes (Umbrel, etc) ║ ║ • Maximum sovereignty: bot signs with Schnorr BIP-340 ║ ╚═══════════════════════════════════════════════════════════════════╝
What we protect, and what we never touch.
How we compare to other messaging apps.
| Feature | KrayChat | Telegram | Signal | |
|---|---|---|---|---|
| End-to-End Encryption | ✅ Always | ✅ Default | ❌ Optional | ✅ Always |
| No Phone Number Required | ✅ | ❌ | ❌ | ❌ |
| No Account Registration | ✅ | ❌ | ❌ | ❌ |
| Messages Stored Locally Only | ✅ | ❌ | ❌ | ✅ |
| No Metadata Collection | ✅ | ❌ | ❌ | ✅ |
| Bitcoin-Native Identity | ✅ | ❌ | ❌ | ❌ |
| Open Source Protocol | ✅ | ❌ | Partial | ✅ |
Start messaging with zero surveillance.
🚀 Launch KrayChat