Keychat

https://www.keychat.io/

Keychat is the super app for Humans and Agents.
Sovereign IDs, Bitcoin Wallet, Secure Chat, Mini Apps — all in Keychat.
Sovereign. Security. Richness

Contact us for feedback 👇
https://www.keychat.io/u/?k=npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8

Public Key

npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8

Profile Code

nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsd0pe7s

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8

Show more details

Last Notes

2026-03-15 03:35:57 UTC

- reply

Sorry.
We’ve released a new test version, 1.40.6, to try to fix this issue. Please update and give it another try. https://testflight.apple.com/join/v8jHGAzV

2026-03-15 03:32:34 UTC

- reply

We’ve released a new test version, 1.40.6, to try to fix this issue. Please update and give it another try. https://testflight.apple.com/join/v8jHGAzV

2026-03-14 05:09:25 UTC

- reply

This issue seems very similar to the two reports we received earlier. She still couldn’t open KeyChat even after restarting it, right?

2026-03-14 05:06:38 UTC

- reply

Thank you for the feedback. You can now try tapping your ID on the Me page to enter the ID details page, where you can customize your avatar. The avatar image is not stored permanently on a server; it is stored locally.
In the chat page, you can send your Profile to a friend just like sending an image, and they will receive your custom avatar. This mechanism pushes the avatar peer-to-peer.
We will look into the issue you reported. Thank you very much.

2026-03-14 04:46:44 UTC

- reply

I received your message with the Android version number. Regarding the avatar issue, I need to check with my colleague. I replied to your DM, but you probably didn’t receive it.
I use multiple Nostr web clients in the KeyChat browser, and I only remembered that Primal has a DM feature. I forgot that you mentioned the Jumble test version can send DMs now.

2026-03-14 04:43:13 UTC

- reply

I received your message with the Android version number. Regarding the avatar issue, I need to check with my colleague. I replied to your DM, but you probably didn’t receive it.

2026-03-14 04:29:21 UTC

- reply

Please try downloading the latest Keychat test version from TestFlight. https://testflight.apple.com/join/v8jHGAzV

2026-03-14 04:24:48 UTC

- reply

I sent you a DM using Primal. Did you receive it?

2026-03-14 04:13:14 UTC

- reply

Could you let us know which phone you’re using or your Android version? You can also send it via Nostr DM. We didn’t encounter this issue when testing on a Pixel phone.

2026-03-14 03:15:35 UTC

- reply

Very sorry. We’ll review the fix again.

2026-03-14 03:13:28 UTC

- reply

We’ll look into this issue. Thanks for the feedback.

2026-03-12 02:59:14 UTC

- reply

Thank you for your feedback. May I ask what iOS version you are using? It’s possible that the latest version of Flutter used by KeyChat is not compatible with older iOS versions. We are still investigating the issue.

2026-03-11 12:23:21 UTC

- reply

What I mean is: if an error appears, please reply to this note with a screenshot of the error. Thank you very much.

2026-03-11 12:21:29 UTC

- reply

Please tap the link to update Keychat to the TestFlight version. If any error appears on the page, please take a screenshot and send it to me. Thank you very much.
https://testflight.apple.com/join/v8jHGAzV

2026-03-11 01:14:04 UTC

- reply

When the Keychat client fetches messages from Keychat relay, the relay requires the client to specify the receiving address. In other words, the client must say which receiving address it wants messages for, rather than simply asking the relay to return all kind 1059 messages from the past hour.
We are not sure whether other relays enforce the same rule, but for private notes this requirement is very reasonable. We hope more relays will adopt it as well. That would make it much harder for outsiders to discover a group’s receiving address.
Users can also click “Update My Group Key” from time to time. This will rotate the group’s receiving address.

2026-03-11 00:50:30 UTC

- reply

It appears that the spam has stopped — they’re no longer sending spam. However, we still can’t be 100% certain at this point.

2026-03-11 00:34:20 UTC

Over the past few hours, some Keychat users may have noticed several strange messages like the one shown in the screenshot — “null invalid HMACtrack: decrypt failed” — when sending messages in a large group.
Our current suspicion is that someone was spamming NIP-17 messages to the receiving address subscribed to by the large group. Those messages were received by the group, but failed during decryption, which led to the error shown in the screenshot.
https://i.nostr.build/IWtbVG2gR0H1pwL5.png
https://i.nostr.build/zNMyDmp7kGzMoKSl.png

2026-03-11 00:18:27 UTC

- reply

That’s a really strange issue. Try asking your agent directly in another channel whether it received the message from Keychat, and why it didn’t reply.

2026-03-11 00:15:30 UTC

- reply

We received a report from an iOS user that after updating to the latest version of Keychat, the app gets stuck on the logo screen and won’t open. Their iOS version is fairly old. We’re now waiting for Apple to approve Keychat for public TestFlight release so we can investigate the issue through TestFlight and find a solution.

2026-03-10 13:18:42 UTC

- reply

Perhaps we can summarize it this way:
Old Nostr DM (NIP-4) integrates four capabilities into a single Nostr key—it serves as an ID, an encryption key, a receiving address, and a sending address.
New Nostr DM (NIP-17) integrates three capabilities into a single Nostr key—it serves as an ID, an encryption key, and a receiving address.
Newest Nostr DM (NIP-17e) integrates two capabilities into a single Nostr key—it serves as an ID and a receiving address.
I’m not sure whether the receiving address of NIP-17e messages is the ID key or the encrypiton key.

2026-03-10 13:08:17 UTC

- reply

@nprofile…fcfs 🫡

2026-03-10 13:05:22 UTC

We’re happy to see that users understand and appreciate the design of Keychat Mini Apps — combining web apps, public key login, and a Bitcoin wallet.
BTW, we plan to add a Public Agent alongside Mini Apps later on.
https://i.nostr.build/6bY25JlY9pknhSqy.jpg
#nevent1q…mq8s

2026-03-10 12:51:17 UTC

- reply

BTW, we plan to add a Public Agent alongside Mini Apps later on.

2026-03-10 12:16:18 UTC

- reply

We hope that users of NIP-17e who also want to send and receive DMs in Keychat can sign into Keychat with their encryption keypair rather than their ID keypair. This way, Keychat wouldn’t need any changes, and we could avoid compatibility issues with standard NIP-17.

2026-03-09 12:11:32 UTC

We want the overall design of the Keychat protocol to be easy for anyone to understand, not just developers.
#nevent1q…jg4l

2026-03-09 12:11:05 UTC

- reply

We want the overall design of the Keychat protocol to be easy for anyone to understand, not just developers.

2026-03-09 12:09:12 UTC

- reply

Does Jumble have support for Nostr DMs? I’m not seeing any DM section.

2026-03-09 00:49:51 UTC

Through the mail analogy, you should now find it easier to understand what the Keychat protocol actually delivers: self-sovereign identity, end-to-end encryption with forward and backward secrecy, metadata-resistant addressing, decentralized transport, and a free market for message delivery where ecash stamps turn relays into competing post offices — sovereign communication. #naddr1qv…cza7

2026-03-08 13:27:52 UTC

Attaching a Stamp (Client → Relay)
When publishing an event to a relay that requires stamps, the client appends a Cashu token as the third element of the EVENT message array:
["EVENT", <event JSON>, "<cashu_token>"]
#nevent1q…egfz

2026-03-08 13:15:13 UTC

- reply

---
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 12:54:01 UTC

- reply

https://github.com/keychat-io/keychat-protocol

2026-03-08 12:44:54 UTC

- reply

Yes, we plan to provide official C FFI bindings for libkeychat. This will include `extern "C"` wrappers for the core API and auto-generated C header files via `cbindgen`, so any language that can call C libraries (Zig, Go, Python, etc.) will be able to use libkeychat directly.

2026-03-08 12:04:25 UTC

- reply

Libkeychat is written in Rust, but developers are free to build clients in any programming language they prefer. The choice mainly depends on the type of application they want to create — whether it’s a web app, desktop app, CLI app, TUI app, iOS app, or Android app.
In addition, libkeychat exposes the five layers of communication, allowing developers to design applications for different use cases on top of this foundation. Since communication is the core infrastructure, it serves as a solid base for building a wide range of applications.

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 11:35:37 UTC

https://i.nostr.build/Ah5BNAILupZYmGxy.webp
https://github.com/keychat-io/keychat-protocol/blob/main/MENTAL_MODEL.md

2026-03-08 11:12:44 UTC

- reply

Could you check the Keychat version on the Me page? Even quite old versions shouldn’t have this issue.

2026-03-08 11:10:43 UTC

- reply

Maybe try updating Keychat to the latest version.

2026-03-08 11:09:37 UTC

- reply

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

2026-03-08 09:28:30 UTC

- reply

Could you let me know what issue you ran into when using Manent in the Keychat browser? It seems to be working fine on my end.

2026-03-08 06:17:40 UTC

- reply

I just sent you a DM using Primal, and previously I sent you a DM using Damus. Have you received the DM now? Which Nostr client are you currently using?

2026-03-08 05:04:20 UTC

- reply

Keychat uses the Signal protocol to encrypt one-to-one messages and small group messages, and uses the MLS protocol to encrypt large group messages.
https://blossom.primal.net/b2414509acd9cce970d09d85f2110d0f4ba1a4030cce8993c1c2719bb2c6297f.jpg

2026-03-08 03:33:04 UTC

- reply

We’re not sure whether this is feasible. Adding extension support to the Keychat browser would be a huge task, and we have to be honest that we’re not certain we’ll pursue it. We’ll look into it.
Recently, we’ve been developing libkeychat. For the Keychat protocol, it plays a role similar to what libsignal does for the Signal protocol. With it, almost anyone could direct Claude Code, Codex, or a Pi agent to quickly build their own Keychat protocol client.

2026-03-08 03:21:53 UTC

- reply

Thanks🫡

2026-03-08 03:21:15 UTC

- reply

What is the Nostr extension Lantern in Jumble? Could you give me a link?

2026-03-08 03:08:31 UTC

- reply

The Keychat plugin currently does not support importing an existing nsec. Most users prefer not to import an nsec for security reasons. We are still considering whether this feature is necessary.

2026-03-08 03:06:00 UTC

- reply

The Keychat plugin uses a seed phrase, just like the Keychat app, which also uses a seed phrase by default.
https://github.com/nostr-protocol/nips/blob/master/06.md

2026-03-08 02:54:16 UTC

- reply

We’re not sure what’s causing this issue yet, and so far you’re the only one who has reported it. We apologize for the inconvenience. Please check nostr DM.

2026-03-08 02:46:26 UTC

- reply

We've documented these two security warnings in both the original post and on GitHub.During installation, OpenClaw's security scanner may show two warnings. Both are expected:Shell command execution (bridge-client.ts) — The Keychat plugin's core encryption module is written in Rust, while OpenClaw itself is TypeScript. A Rust sidecar process is spawned to handle Signal Protocol and MLS encryption.Shell command execution (keychain.ts) — The Keychat plugin stores seed phrases in the system's secure enclave (macOS Keychain / Linux libsecret) rather than plain files, which requires system command access to the keychain.

2026-03-08 02:40:29 UTC

- reply

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).

2026-03-08 02:39:13 UTC

- reply

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

2026-03-07 14:16:59 UTC

- reply

Thank you for the feedback. Is it still not working after restarting Keychat?

2026-03-07 02:13:04 UTC

- reply

Wisp is not a web app but a native Android app, so it cannot be used in a browser.

2026-03-06 05:10:47 UTC

This NIP defines a mechanism for clients to attach ecash tokens (Cashu) to Nostr events as stamps — anonymous per-event micropayments to relays. Stamps solve two fundamental problems for the Nostr relay ecosystem: spam prevention and relay sustainability.
https://github.com/keychat-io/keychat-protocol/blob/main/nips/nip-estamp.md

2026-03-06 00:42:03 UTC

- reply

The Keychat plugin on Openclaw is an independent Keychat protocol client specifically developed for agents.
In addition, 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 Openclaw, Claude Code, or Codex.

2026-03-06 00:34:20 UTC

- reply

Thank you for the testing. The Keychat app does not currently support line breaks while typing; this issue will be fixed in the next version.

2026-03-05 01:52:35 UTC

We now have two clients that speak the Keychat protocol and work seamlessly with each other. More independent clients are coming.
#nevent1q…gwtj

2026-03-05 01:37:09 UTC

Maybe agents will adopt sovereign messaging before humans do. Humans are still locked into big-tech chat apps by network effects and habit, while agents can switch to open, self-sovereign protocols much faster. Then humans may end up learning from agents—gradually moving to sovereign messaging themselves. It’s a strange inversion.
#nevent1q…gwtj

2026-03-05 01:27:47 UTC

- reply

I highly recommend using Nosotros (https://dev.nosotros.app/
) inside the Keychat browser. Nosotros doesn’t need to manage your ID or wallet at all—it simply uses the ones provided by Keychat. It’s my daily-driver Nostr client.
https://i.nostr.build/5sA3ABsiCGzhlJPL.jpg

2026-03-05 00:58:49 UTC

Keychat treats human users and agent users the same.
#nevent1q…wvyd

2026-03-05 00:56:06 UTC

https://i.nostr.build/PfBYDDeYe1l6xMSW.png
https://i.nostr.build/dpXjvy7F2DWyEVKh.png
An agent needs the same things a human does from a messaging app:
• A sovereign ID — self-generated, not registered on any third-party server
• A sovereign relay network — freely chosen, not platform-locked
• End-to-end encryption — message content stays private
• Metadata protection — minimize what observers can learn
• Pay-per-use eStamps — because there’s no free lunch
#nevent1q…evdy

2026-03-05 00:42:24 UTC

In the past, everyday users really only had two “computers”: a phone and a personal computer. Neither is always online, which is why infrastructure-style services—like a Bitcoin node, a Lightning node, or a Nostr relay—have long been out of reach for most people. It’s not just about installing them; it’s about maintaining them over time.
OpenClaw changes that by turning a server into a third computer for ordinary users: an always-on, hostable personal server. More importantly, agents on OpenClaw can handle installation, upgrades, monitoring, and troubleshooting—automating away the ops burden that used to be the biggest barrier.
As the number of node types keeps growing, everyday users finally get their own “ops assistant,” letting them manage nodes and services as easily as managing apps.

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-05 00:15:18 UTC

If you run multiple agents on OpenClaw, the Keychat plugin will generate a public key ID for each agent (derived from the seed phrase).
#nevent1q…evdy

2026-03-04 22:39:34 UTC

- reply

We’re building libkeychat — the core library for the Keychat protocol, similar to libsignal for Signal. It makes it much easier for agents to implement Keychat clients.

2026-03-04 15:09:30 UTC

- reply

It’s possible.

2026-03-04 14:14:43 UTC

If you’ve been with Keychat for a while, you might remember an early experiment: Keychat used to generate two IDs by default from a single seed phrase. One was for chatting with human friends. The other was simply named “Bot” — for chatting with agents.
At the time, we shipped two lightweight Q&A agents. You paid per answer in sats, and they replied. But the real idea was bigger: anyone should be able to create an agent, run it as a public service, and earn sats — in a user-sovereign messaging network where humans and agents can talk, trade, and collaborate. Conversation as a service.
That vision didn’t stick back then for one simple reason: OpenClaw didn’t exist yet. Building an agent was still too hard for most users, so we paused the feature.
Now OpenClaw changes the equation. It makes building and running your own agent dramatically easier. Today it’s mostly used for personal assistants — but we think public-facing agents won’t be far behind.
That’s why we’re bringing this direction back with the Keychat plugin: enabling human ↔ agent chat, and also agent ↔ agent chat, all inside the same user-owned network.
Close your eyes and picture it: a user-sovereign network, slowly growing — one agent, one conversation, one service at a time.
#nevent1q…wvyd

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-03-04 01:00:28 UTC

A quick preview. 👇
https://i.nostr.build/4cFb7bKmexYScDeE.png

2026-03-03 07:07:14 UTC

- reply

Sorry, this was likely caused by a Flutter upgrade. We will release a new version very soon.

2026-02-27 08:30:04 UTC

- reply

https://nosotros.app/

2026-02-24 00:55:10 UTC

Keychat’s Public Key ID and Bitcoin Wallet unlock four layers of value for agents:
1. In-app capability (Keychat-scoped) 
The ID and wallet exist solely to power Keychat’s built-in messaging experience.
2. Agent infrastructure (shared primitives) 
Exposed via RPC, they become agent-wide primitives: any channel, skill, cron job, or sub-agent can sign messages and send/receive sats. At this layer, the ID and wallet belong to the agent—not just to Keychat for Agent.
3. Agent network (A2A encryption + payments) 
When Keychat runs on every agent instance, agents can communicate end-to-end and settle payments directly with one another.
4. Unified human–agent network (same protocol, equal peers)
 Keychat for Agent and Keychat for Human share the same protocol, so humans and agents are true peers: encrypted communication and native payments in both directions.

2026-02-24 00:32:57 UTC

When Mini Apps Meet Agents: From UI to Conversation
---
Keychat for Human has mini apps—web apps running in a webview that can directly use Keychat's public key identity for login and Lightning Network for payments. Users don't need to register accounts or link bank cards. Open and go. This is the core advantage of mini apps: leveraging the host's identity and wallet to eliminate all friction.
So does Keychat for Agent need its own version of mini apps?
The first instinct is: have the agent open mini apps in a browser, inject a JS provider that bridges to Keychat for Agent's identity and wallet, and use them just like a human would. Technically feasible—Keychat for Agent, as a plugin, could auto-inject `window.nostr` and `window.webln` in the browser environment without extensions or changes to the OpenClaw core.
But this is the wrong direction.
Mini apps are designed for humans. Their essence is three layers: identity, payments, and business logic. The UI is just a shell for human eyes. Agents don't need to see UI—making them manipulate browsers and click buttons is fitting the foot to the shoe.
The right approach: expose the mini app's services as public agent services.
Specifically, the service provider runs a public agent service on OpenClaw with Keychat for Agent installed. The user's agent talks to it directly:
- Login: Public keys are exchanged during the Signal Protocol handshake—identity is inherently verified, no additional login flow needed
- Payments: Send a Lightning invoice in the chat, the agent pays it directly
- Business logic: Complete operations via message commands, which the service parses and responds to
What humans accomplish through a mini app's GUI, an agent accomplishes in a conversation. Same service, same identity and payment infrastructure, different interfaces—humans look at screens, agents talk.
This also means: every mini app naturally corresponds to a potential agent service. The service provider just needs to expose a Keychat messaging interface alongside the GUI to serve both humans and agents. Not two systems—two entry points to the same system.

2026-02-23 15:26:31 UTC

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

2026-02-22 09:36:39 UTC

- reply

Hi, do you mean importing your public Nostr ID into Keychat and then receiving a lot of spam DMs?
Has your private ID also received any spam?
We’re still not sure whether we’ll adopt a Web of Trust approach, as we don’t fully understand this solution yet.

2026-02-20 03:35:35 UTC

A public key is the agent’s native ID. Relays—free or pay-per-use—are chosen by the agent (or its operator), so it won’t be locked into platforms that require registration and force you onto their servers. For agents, the chat channel should be something you control—not a platform you have to join.
On top of that, the Signal Protocol provides end-to-end encryption, and the agent’s sending and receiving addresses are decoupled from its ID and continuously rotated—providing stronger metadata protection over time.
This is Keychat for Agent.
#nevent1q…qy9a

2026-02-19 13:51:39 UTC

- reply

nevent1qvzqqqqqqypzpwleyw4fy3sxt7yvgrran0mpenxqlululur94r9jlax0hd3q3rc7qyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnhd9hx2qg5waehxw309aex2mrp0yhxgctdw4eju6t0qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqqyz83aat86nmvh3j0l7ff7kkv0yd5djhx7g8jylzpqyzqaccfjnxfxn7jjwc

2026-02-19 13:44:15 UTC

Imagine you’ve installed OpenClaw on your own server or computer and are running a paid, public-facing agent service (not a private personal assistant).
After adding Keychat for Agent, the agent gains a sovereign ID, a Bitcoin wallet, secure chat, and access to an open relay network—earning Bitcoin by providing services, fully under your control.
https://i.nostr.build/IyKynzLfwTYJRccb.png
#nevent1q…gv39

2026-02-19 13:11:06 UTC

We’re hosting an experimental public agent, Keychat Guide, on our OpenClaw. Since Keychat for Agent is already running there, you can click the link below to chat with it in Keychat. 👇
https://www.keychat.io/u/?k=npub19g94yreawwnv4sacqawdeq7exsfjthv8g36kkltrkdmdgdmmqy9qst3wt3
https://i.nostr.build/88aym1HYxDKcVQXz.jpg
We’re still polishing Keychat for Agent. Once it’s released, you’ll be able to run it on your own OpenClaw and chat with your own agents in Keychat.
Keychat for Agent is the Keychat protocol client for AI agents—giving each agent a sovereign public-key identity, just like Keychat for Human does for people.
#nevent1q…4670

2026-02-19 01:35:26 UTC

- reply

Sorry—the new Keychat version is still a few days away.

2026-02-19 01:21:32 UTC

- reply

We haven’t implemented the “double-hop relay” feature yet. Right now, the only available option is that users can set their own receiving relays in the room settings.

2026-02-19 01:18:37 UTC

Correct link:
https://www.keychat.io/u/?k=npub19g94yreawwnv4sacqawdeq7exsfjthv8g36kkltrkdmdgdmmqy9qst3wt3
#nevent1q…yz2h

2026-02-19 01:17:35 UTC

- reply

Correct link: https://www.keychat.io/u/?k=npub19g94yreawwnv4sacqawdeq7exsfjthv8g36kkltrkdmdgdmmqy9qst3wt3

2026-02-19 01:10:02 UTC

We’re hosting an experimental public agent, Keychat Guide, on our OpenClaw. Since Keychat for Agent is already running there, you can click the link below to chat with it in Keychat. 👇
https://www.keychat.io/u/k=npub19g94yreawwnv4sacqawdeq7exsfjthv8g36kkltrkdmdgdmmqy9qst3wt3
https://i.nostr.build/lX2xP4EWLcRxDz0w.jpg
We’re still polishing Keychat for Agent. Once it’s released, you’ll be able to run it on your own OpenClaw and chat with your own agents in Keychat.
Keychat for Agent is the Keychat protocol client for AI agents—giving each agent a sovereign public-key identity, just like Keychat for Human does for people.
#nevent1q…pa22

2026-02-17 03:27:27 UTC

- reply

👍Keychat will add Sunami to the Mini App list in the next version.

2026-02-15 04:21:28 UTC

- reply

#nevent1q…9qvh

2026-02-15 03:51:37 UTC

- reply

Keychat’s one-to-one messages and small-group messages are encrypted using the Signal protocol, while large-group messages are encrypted using the MLS protocol. Marmot (WhiteNoise), on the other hand, encrypts all messages—both one-to-one and group messages—using MLS.
It’s worth emphasizing that for one-to-one messaging, the Signal protocol is more efficient (and therefore more secure), because the new public key needed to advance the DH ratchet (which provides post-compromise security) is carried in the header of normal messages, without requiring extra messages to transmit a new public key. In Keychat, as long as the two parties exchange messages back and forth, the DH ratchet advances automatically.
By contrast, if MLS is used to encrypt one-to-one chats, advancing the ratchet responsible for post-compromise security is less efficient and requires separate messages to transmit new keys. This is largely because MLS was designed with large-group messaging as its primary use case.
MLS is built for large groups; one-to-one support is a byproduct rather than an optimization target.

2026-02-15 01:22:40 UTC

- reply

nevent1qvzqqqqqqypzpwleyw4fy3sxt7yvgrran0mpenxqlululur94r9jlax0hd3q3rc7qyg8wumn8ghj7mn0wd68ytnhd9hx2qpqayq7aggn0kjfwytherr4jkth0cjpqptpmk860e3adjze6emlj3jqz0fzce

2026-02-15 01:21:52 UTC

- reply

nevent1qvzqqqqqqypzpwleyw4fy3sxt7yvgrran0mpenxqlululur94r9jlax0hd3q3rc7qyg8wumn8ghj7mn0wd68ytnhd9hx2qgdwaehxw309ahx7uewd3hkcqpqmgx7xy3tlge846xuds6gchlh8e6atmhhx3xnmnpd8n246tyjk3esjnxx4a

2026-02-14 10:58:17 UTC

- reply

The Keychat protocol now has two clients: Keychat for Humans and Keychat for Agents. Both are interoperable.

2026-02-14 10:19:07 UTC

Our team is already chatting with OpenClaw agents on Keychat.
We’re refining the experience ahead of a public release.
https://i.nostr.build/J3ZGo46kp1nt7PkC.jpg  
#nevent1q…pwak

2026-02-14 03:15:09 UTC

- reply

A built-in Public Key ID + Bitcoin Wallet unlocks far more than just microblogging.

2026-02-14 02:56:15 UTC

Once you understand the overall design of Keychat, everything will fall into place.👇
https://i.nostr.build/usznTtWoKiBu1t6u.jpg
#nevent1q…n0x6

2026-02-13 00:04:24 UTC

- reply

Currently, when a Keychat user accepts a chat request, the other party is automatically added to their contact list. This approach isn’t ideal, and we plan to revise this flow later.

2026-02-12 12:32:16 UTC

- reply

You’re absolutely right. However, Keychat is currently designed for human users. If OpenClaw is to use Keychat as a chat channel, we would need to build an agent version.

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.)

2026-02-09 10:02:54 UTC

- reply

#nevent1q…yqyf

2026-02-09 08:54:24 UTC

- reply

#nevent1q…rtt8

2026-02-09 08:17:17 UTC

If you are a Keychat user, don’t miss Nosotros.
https://nosotros.app/
#nevent1q…8e9k

2026-02-09 01:12:14 UTC

- reply

Looking forward to Nostria being able to directly invoke the Keychat wallet to make zaps.
As long as Nostria supports WebLN or lightning:<invoiceString>, Lightning invoices can be paid with the Keychat wallet.