Wallet Connect
Metamask
Coinbase
Solflare
- Wallet Connect
Connect your wallet
Tap Connect — pick MetaMask, Coinbase, Trust, Solflare or WalletConnect. One signature. That's onboarding.
Whoever holds the keys
holds the messages.
No emails. No phone numbers. No central server that can read, delete, or surrender your conversations — and no future quantum computer that can break them.
5 chains · 1 inbox
One signature with the wallet you already own — keys derive locally, never leave the device, then talk to any address on chain.
Wallet Connect
Tap Connect — pick MetaMask, Coinbase, Trust, Solflare or WalletConnect. One signature. That's onboarding.
See you at 8pm tonight!
10:24 AM
a7f2:9c8e: b14d:3f01: 8b2c:
Your encryption keys derive in-browser from your wallet — wrapped in a hybrid X25519 + Kyber-1024 handshake. They never leave the device.
a7f2:9c8e: b14d:3f01: 8b2c:
Search by ENS or paste a wallet address. Inbox requests gate strangers. Group chats encrypt at every epoch.
Wallet-based identity, AES-256-GCM, MLS RFC 9420, Kyber-1024 and Dilithium3 — composed from open standards, never proprietary.
Today
Your wallet is your identity.
Open Keychat with MetaMask, Coinbase, Solflare, Trust or WalletConnect. No signup. No KYC. ENS names resolve automatically.
Post-quantum encryption
Kyber-1024 for key exchange, Dilithium3 for signatures. Safe against tomorrow's quantum adversaries — and today's harvest-now, decrypt-later attackers.
See you at 8pm tonight!
10:24 AM
→ a7f2:908e: b14d:3f01…
NIST PQC · ML-KEM · ML-DSA
Encrypted groups
Role-based group chats — encrypted at every epoch, no plaintext leaves the device.
see more…
Encrypted attachments
Files up to 100 MB, encrypted client-side and pinned via IPFS / Web3.Storage.
Multichain native
BTC, ETH, Polygon, Tron, Solana. One inbox for every wallet you already use.
8 themes · fully customizable
Custom accent color, chat background, density. Export as a shareable string.
Wallet-based identity
Your private key is the password we will never see, store, or recover.
Consent inbox
Inbox requests gate strangers. You decide who gets through — before any message reaches you.
Telegram founders get arrested. Meta quietly disables E2EE. Signal still wants your phone number. We started Keychat because none of those things are accidents — they are the architecture.
No. Messages are encrypted on your device with AES-256-GCM and wrapped in MLS (RFC 9420) before they ever leave your browser. Only you and your recipient hold the keys — relays only see ciphertext, and there is no Keychat server in the middle.
Take the key back. Start sending messages only you and your recipient can read — secured by AES-256-GCM, MLS RFC 9420, Kyber-1024 and Dilithium3.