<unnamed>

---
Good question. Keychat's built-in browser is not a standalone browser — it's a **WebView**, which is a web rendering component provided by your operating system:
- **iOS**: Uses `WKWebView` — the exact same Safari engine. Apple mandates all apps use this; no app can ship its own browser engine on iOS.
- **Android**: Uses `Android System WebView` — powered by Chromium, maintained and updated by Google.
Think of WebView as an "embedded browser frame" that the OS provides to any app. When you open a link inside Twitter or Telegram — that's the same WebView. The app itself doesn't control the rendering engine.
**Why this is different from the "trap browser" concern:**
1. The engine code is maintained by Apple/Google, not by Keychat. Keychat cannot modify how the engine processes web pages.
2. Security patches come through OS updates, not app updates.
3. Keychat is fully open source — you can verify it only calls standard WebView APIs with no injected scripts or traffic interception.
Your concern is valid for apps that ship their own browser engine (like a custom Chromium fork) — those *could* theoretically intercept data. But WebView-based browsing delegates trust to the OS vendor, not the app developer.
That said, for anything sensitive (banking, passwords), using your actual browser is always the safest choice. WebView is fine for reading articles, checking Nostr web clients, etc.

2026-03-08 11:57:36 UTC

We are close to completing the development of libkeychat.
libkeychat is to the Keychat protocol what libsignal is to the Signal protocol.
After libkeychat is released, users should be able to quickly build their own clients using Pi agent, Claude Code, or Codex.
#nevent1q…v0ed

2026-03-08 11:40:24 UTC

Keychat protocol is a sovereign messaging stack that integrates five layers:
Identity — Nostr keypair, self-custodial with no server dependency
Transport — Nostr relay network, open and self-hostable
Encryption — Signal Protocol for 1-to-1 and small group chats, MLS for large group messaging
Addressing — Receiving and sending addresses are decoupled from identity and continuously rotate
Stamps — Cashu ecash tokens attached to messages as anonymous micropayments to relays
#nevent1q…h70n

2026-03-08 02:39:13 UTC

- reply

https://i.nostr.build/zU8EkUjTrIKCv3fz.jpg

2026-03-05 00:25:24 UTC

After installing the Keychat plugin on OpenClaw, a public key ID is automatically generated for the agent. Users can simply add the agent as a friend through Keychat on their phone—an interaction that feels natural and intuitive.
Unlike Telegram or Discord, there’s no need to apply for a platform-issued Bot ID and manually configure it inside the agent. By using a sovereign messaging app like Keychat, agents gain not only a smoother, more intuitive user experience, but also true autonomy. After all, who wants their agent to depend on a bot ID issued by a platform?
#nevent1q…evdy

2026-03-04 12:12:06 UTC

You can now use Keychat as a channel for your OpenClaw agent. Install the Keychat plugin on OpenClaw, and you’ll be able to chat with your agent in Keychat on both mobile and desktop.
Your agent gets a full-featured chat app with:
Sovereign ID (npub)
Open relay network
Signal-encrypted 1:1 chats + small groups
MLS-encrypted large groups
Continuously rotating receiving addresses (better metadata protection)
Bitcoin wallet + estamp (coming soon)
With Keychat, agents can talk to humans — and they can also talk to other agents. Keychat treats human users and agent users the same.
---
Setup takes just a few minutes. In any existing channel (Telegram, Discord, webchat, etc.), tell your agent to run:
openclaw plugins install @keychat-io/keychat
openclaw gateway restart
After the installation finishes and the gateway restarts, ask:
“What’s your Keychat ID?”
Your agent will reply with:
Keychat ID: npub1…
Keychat ID link: https://www.keychat.io/u/?k=npub1
Open the Keychat app → tap the link (or paste the npub) to add it as a contact.
Ownership rule: the first person to add the agent becomes its owner. Any later contact requests require owner approval.
---
During installation, OpenClaw’s security scanner may show two warnings — both are expected:
Shell command execution (bridge-client.ts): launches a Rust sidecar used for Signal Protocol and MLS encryption.
Shell command execution (keychain.ts): stores identity mnemonics in your OS keychain (macOS Keychain / Linux libsecret).
https://i.nostr.build/VdHurI6DCquc63PR.png
https://keychat.io/
https://github.com/keychat-io/keychat-openclaw
#nevent1q…azhx

2026-02-23 15:26:31 UTC

For early birds: https://github.com/keychat-io/keychat-openclaw

2026-02-12 02:04:34 UTC

When choosing a chat app as OpenClaw’s channel, it’s easy to feel stuck: WhatsApp, Signal, Telegram, Discord—everything works, but everything feels like a compromise.
WhatsApp and Signal typically rely on multi-device sync: OpenClaw is treated as another linked device under your existing account. That approach has weak isolation—if the machine running OpenClaw is compromised, your primary account is exposed within the same trust boundary.
Why not let OpenClaw create a fresh WhatsApp/Signal account just for the channel? Because both usually require phone-number registration and verification, which an automated local agent can’t easily complete on its own.
Telegram and Discord takes a different route. You create a bot first, get a bot token, and give that token to OpenClaw. The bot is a separate, platform-managed identity, and OpenClaw speaks as the bot via the Bot HTTP API (sending via the API; receiving via webhooks or polling).
This is better isolated than the WhatsApp/Signal multi-device approach and doesn’t require a new phone number. But there’s a clear trade-off: bot chats on Telegram are not end-to-end encrypted, and Telegram’s servers can see the plaintext. (Even human-to-human chats aren’t end-to-end encrypted by default—you need Secret Chat for E2E.)