Nostr notes by Keychat

Sorry. We’ve released a new test version, 1.40.6, to try to fix ...

2026-03-15T03:35:57Z

In reply to nevent1q…skvx
_________________________

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

We’ve released a new test version, 1.40.6, to try to fix this ...

2026-03-15T03:32:34Z

In reply to nevent1q…haxl
_________________________

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

This issue seems very similar to the two reports we received ...

2026-03-14T05:09:25Z

In reply to nevent1q…zhcs
_________________________

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

Thank you for the feedback. You can now try tapping your ID on ...

2026-03-14T05:06:38Z

In reply to nevent1q…wpwt
_________________________

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.

I received your message with the Android version number. ...

2026-03-14T04:46:44Z

In reply to nevent1q…gc7u
_________________________

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.

I received your message with the Android version number. ...

2026-03-14T04:43:13Z

In reply to nevent1q…6wnx
_________________________

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.

Please try downloading the latest Keychat test version from ...

2026-03-14T04:29:21Z

In reply to nevent1q…atem
_________________________

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

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

2026-03-14T04:24:48Z

In reply to nevent1q…q87h
_________________________

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

Could you let us know which phone you’re using or your Android ...

2026-03-14T04:13:14Z

In reply to nevent1q…lupu
_________________________

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.

Very sorry. We’ll review the fix again.

2026-03-14T03:15:35Z

In reply to nevent1q…lupu
_________________________

Very sorry. We’ll review the fix again.

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

2026-03-14T03:13:28Z

In reply to nevent1q…2q0l
_________________________

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

Thank you for your feedback. May I ask what iOS version you are ...

2026-03-12T02:59:14Z

In reply to nevent1q…tk80
_________________________

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.

What I mean is: if an error appears, please reply to this note ...

2026-03-11T12:23:21Z

In reply to nevent1q…6lza
_________________________

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

Please tap the link to update Keychat to the TestFlight version. ...

2026-03-11T12:21:29Z

In reply to nevent1q…6lza
_________________________

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

When the Keychat client fetches messages from Keychat relay, the ...

2026-03-11T01:14:04Z

In reply to nevent1q…hqxs
_________________________

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.

It appears that the spam has stopped — they’re no longer ...

2026-03-11T00:50:30Z

In reply to nevent1q…jhka
_________________________

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

Over the past few hours, some Keychat users may have noticed ...

2026-03-11T00:34:20Z

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.

That’s a really strange issue. Try asking your agent directly ...

2026-03-11T00:18:27Z

In reply to nevent1q…d43a
_________________________

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.

We received a report from an iOS user that after updating to the ...

2026-03-11T00:15:30Z

In reply to nevent1q…8amw
_________________________

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.

Perhaps we can summarize it this way: Old Nostr DM (NIP-4) ...

2026-03-10T13:18:42Z

In reply to nevent1q…rjs7
_________________________

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.

@nprofile…fcfs 🫡

2026-03-10T13:08:17Z

In reply to nevent1q…rjs7
_________________________

Cody (nprofile…fcfs) 🫡

We’re happy to see that users understand and appreciate the ...

2026-03-10T13:05:22Z

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.

quoting
nevent1q…mq8s
I love the mini apps, everytime they surprise me, I guess it was gradual

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

2026-03-10T12:51:17Z

In reply to nevent1q…cf8r
_________________________

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

We hope that users of NIP-17e who also want to send and receive ...

2026-03-10T12:16:18Z

In reply to nevent1q…lf28
_________________________

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.

We want the overall design of the Keychat protocol to be easy for ...

2026-03-09T12:11:32Z

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

quoting
nevent1q…jg4l
A great explanation of Keychat protocol. naddr1qv…cza7

We want the overall design of the Keychat protocol to be easy for ...

2026-03-09T12:11:05Z

In reply to nevent1q…qz8a
_________________________

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

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

2026-03-09T12:09:12Z

In reply to nevent1q…mmh4
_________________________

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

Attaching a Stamp (Client → Relay) When publishing an event to ...

2026-03-08T13:27:52Z

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>"]

quoting
nevent1q…egfz
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

--- Good question. Keychat's built-in browser is not a ...

2026-03-08T13:15:13Z

In reply to nevent1q…0psu
_________________________

---

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.

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

2026-03-08T12:54:01Z

In reply to nevent1q…vq59
_________________________

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

Yes, we plan to provide official C FFI bindings for libkeychat. ...

2026-03-08T12:44:54Z

In reply to nevent1q…0agp
_________________________

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.

Libkeychat is written in Rust, but developers are free to build ...

2026-03-08T12:04:25Z

In reply to nevent1q…3ed6
_________________________

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.

We are close to completing the development of libkeychat. ...

2026-03-08T11:57:36Z

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.

quoting
nevent1q…v0ed
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

Keychat protocol is a sovereign messaging stack that integrates ...

2026-03-08T11:40:24Z

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

quoting
nevent1q…h70n

https://github.com/keychat-io/keychat-protocol/blob/main/MENTAL_MODEL.md

Nostr event nevent1qqsrcz3d5r5lw5nsuwwaf8fcxsk5948pwh7dystu5d4ayf6n9atjywczyzaljga2jfrqvhugcsx8mxlkrnxvplelelcxt2xt9l6vlwmzpz83unsclja

2026-03-08T11:35:37Z

https://github.com/keychat-io/keychat-protocol/blob/main/MENTAL_MODEL.md

Could you check the Keychat version on the Me page? Even quite ...

2026-03-08T11:12:44Z

In reply to nevent1q…qham
_________________________

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

Maybe try updating Keychat to the latest version.

2026-03-08T11:10:43Z

In reply to nevent1q…qham
_________________________

Maybe try updating Keychat to the latest version.

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

2026-03-08T11:09:37Z

In reply to nevent1q…qham
_________________________

Could you let me know what issue you ran into when using Manent ...

2026-03-08T09:28:30Z

In reply to nevent1q…yy69
_________________________

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.

I just sent you a DM using Primal, and previously I sent you a DM ...

2026-03-08T06:17:40Z

In reply to nevent1q…3h4z
_________________________

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?

Keychat uses the Signal protocol to encrypt one-to-one messages ...

2026-03-08T05:04:20Z

In reply to nevent1q…93wr
_________________________

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.

We’re not sure whether this is feasible. Adding extension ...

2026-03-08T03:33:04Z

In reply to nevent1q…qk5a
_________________________

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.

Thanks🫡

2026-03-08T03:21:53Z

In reply to nevent1q…2sqa
_________________________

Thanks🫡

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

2026-03-08T03:21:15Z

In reply to nevent1q…t3qf
_________________________

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

The Keychat plugin currently does not support importing an ...

2026-03-08T03:08:31Z

In reply to nevent1q…hzma
_________________________

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.

The Keychat plugin uses a seed phrase, just like the Keychat app, ...

2026-03-08T03:06:00Z

In reply to nevent1q…hzma
_________________________

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

We’re not sure what’s causing this issue yet, and so far ...

2026-03-08T02:54:16Z

In reply to nevent1q…lkzh
_________________________

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.

We've documented these two security warnings in both the ...

2026-03-08T02:46:26Z

In reply to nevent1q…q546
_________________________

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.

During installation, OpenClaw’s security scanner may show two ...

2026-03-08T02:40:29Z

In reply to nevent1q…q546
_________________________

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/zU8EkUjTrIKCv3fz.jpg

2026-03-08T02:39:13Z

In reply to nevent1q…w87h
_________________________

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

2026-03-07T14:16:59Z

In reply to nevent1q…fgjc
_________________________

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

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

2026-03-07T02:13:04Z

In reply to nevent1q…4w4p
_________________________

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

This NIP defines a mechanism for clients to attach ecash tokens ...

2026-03-06T05:10:47Z

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

The Keychat plugin on Openclaw is an independent Keychat protocol ...

2026-03-06T00:42:03Z

In reply to nevent1q…k855
_________________________

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.

Thank you for the testing. The Keychat app does not currently ...

2026-03-06T00:34:20Z

In reply to nevent1q…hlmx
_________________________

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.

We now have two clients that speak the Keychat protocol and work ...

2026-03-05T01:52:35Z

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

quoting
nevent1q…gwtj

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

Maybe agents will adopt sovereign messaging before humans do. ...

2026-03-05T01:37:09Z

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.

quoting
nevent1q…gwtj

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

I highly recommend using Nosotros (https://dev.nosotros.app/ ) ...

2026-03-05T01:27:47Z

In reply to nevent1q…srya
_________________________

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.

Keychat treats human users and agent users the same. ...

2026-03-05T00:58:49Z

Keychat treats human users and agent users the same.

quoting
nevent1q…wvyd
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://keychat.io/

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

nevent1q…azhx

Nostr event nevent1qqs20ksyxgfvvtym8vc422pxmeqtk36gxc6zyht2kjktwsa3f3pk4mczyzaljga2jfrqvhugcsx8mxlkrnxvplelelcxt2xt9l6vlwmzpz83ump2j20

2026-03-05T00:56:06Z

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

quoting
nevent1q…evdy
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://keychat.io/

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

nevent1q…azhx

In the past, everyday users really only had two “computers”: ...

2026-03-05T00:42:24Z

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.

After installing the Keychat plugin on OpenClaw, a public key ID ...

2026-03-05T00:25:24Z

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?

quoting
nevent1q…evdy
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://keychat.io/

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

nevent1q…azhx

If you run multiple agents on OpenClaw, the Keychat plugin will ...

2026-03-05T00:15:18Z

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

quoting
nevent1q…evdy
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://keychat.io/

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

nevent1q…azhx

We’re building libkeychat — the core library for the Keychat ...

2026-03-04T22:39:34Z

In reply to nevent1q…78wl
_________________________

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.

It’s possible.

2026-03-04T15:09:30Z

In reply to nevent1q…qkrh
_________________________

It’s possible.

If you’ve been with Keychat for a while, you might remember an ...

2026-03-04T14:14:43Z

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.

quoting
nevent1q…wvyd
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://keychat.io/

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

nevent1q…azhx

You can now use Keychat as a channel for your OpenClaw agent. ...

2026-03-04T12:12:06Z

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://keychat.io/

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

quoting
nevent1q…azhx
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.)

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

2026-03-04T01:00:28Z

A quick preview. 👇

Sorry, this was likely caused by a Flutter upgrade. We will ...

2026-03-03T07:07:14Z

In reply to nevent1q…vgqv
_________________________

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

https://nosotros.app/

2026-02-27T08:30:04Z

In reply to nevent1q…v3za
_________________________

https://nosotros.app/

Keychat’s Public Key ID and Bitcoin Wallet unlock four layers ...

2026-02-24T00:55:10Z

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.

When Mini Apps Meet Agents: From UI to Conversation --- Keychat ...

2026-02-24T00:32:57Z

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.

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

2026-02-23T15:26:31Z

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

Hi, do you mean importing your public Nostr ID into Keychat and ...

2026-02-22T09:36:39Z

In reply to nevent1q…740m
_________________________

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.

A public key is the agent’s native ID. Relays—free or ...

2026-02-20T03:35:35Z

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.

quoting
nevent1q…qy9a
good shit. infact, awesome shit. thank you for getting onboard the AI agent thing. This will defo make me use nostr as the default channel for comms.

First it was Signal, which required buying a temporary number. Cost money.
Then I moved to Discord and their dev platform with bot and oauth was incredible. and free. Then they announced global id and facial scan.
Installed mattermost and set that up, got it working. Took ages. Then found out it's not encrypted.
Then I moved to WhatsApp just to get it done. Cost money for a burner number. But Meta...
Re-Discovered Matrix and it's ok I guess.

now I can finally (i hope) leverage the power of nostr for a bi-drectional channel! Johnny Silverhand (npub1d2q…egdg) desperately needs to outlet his thoughts and mine included at times. Even though he's a depressing fucker, he's got optimism for the future and includes the anarchist's cookbook as reading material.

for those who find the openclaw clunky and shitty... I'm guessing the nanoclaw will run it? I throw anything at that thing and it get's the job done on a old pc. Hasn't crashed once, hasn't fallen over once... meanwhile openclaw has been reintsalled at least 5 times over multiple servers and mac machines. That thing is shaky af sadly :no:

Nostr event nevent1qqstpqyw7vrqtkxguqrwg63m6l8rwxup3jt0nfus3gf08m03w3jefuszyzaljga2jfrqvhugcsx8mxlkrnxvplelelcxt2xt9l6vlwmzpz83uwkpl3y

2026-02-19T13:51:39Z

In reply to nevent1q…4mu8
_________________________

nevent1qvzqqqqqqypzpwleyw4fy3sxt7yvgrran0mpenxqlululur94r9jlax0hd3q3rc7qyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnhd9hx2qg5waehxw309aex2mrp0yhxgctdw4eju6t0qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqqyz83aat86nmvh3j0l7ff7kkv0yd5djhx7g8jylzpqyzqaccfjnxfxn7jjwc

Imagine you’ve installed OpenClaw on your own server or ...

2026-02-19T13:44:15Z

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.

quoting
nevent1q…gv39
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

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

We’re hosting an experimental public agent, Keychat Guide, on ...

2026-02-19T13:11:06Z

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

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.

quoting
nevent1q…4670
Our team is already chatting with OpenClaw agents on Keychat.

We’re refining the experience ahead of a public release.

  

nevent1q…pwak

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

2026-02-19T01:35:26Z

In reply to nevent1q…8af4
_________________________

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

We haven’t implemented the “double-hop relay” feature yet. ...

2026-02-19T01:21:32Z

In reply to nevent1q…adhc
_________________________

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.

Correct link: ...

2026-02-19T01:18:37Z

Correct link:

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

quoting
nevent1q…yz2h
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

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

Correct link: ...

2026-02-19T01:17:35Z

In reply to nevent1q…cma6
_________________________

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

We’re hosting an experimental public agent, Keychat Guide, on ...

2026-02-19T01:10:02Z

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

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.

quoting
nevent1q…pa22
Our team is already chatting with OpenClaw agents on Keychat.

We’re refining the experience ahead of a public release.

  

nevent1q…pwak

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

2026-02-17T03:27:27Z

In reply to nevent1q…wcgg
_________________________

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

#nevent1q…9qvh

2026-02-15T04:21:28Z

In reply to nevent1q…shln
_________________________

quoting nevent1q…9qvh
Our team is already chatting with OpenClaw agents on Keychat.

We’re refining the experience ahead of a public release.

  

nevent1q…pwak

Keychat’s one-to-one messages and small-group messages are ...

2026-02-15T03:51:37Z

In reply to nevent1q…m8m9
_________________________

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.

The Keychat protocol now has two clients: Keychat for Humans and ...

2026-02-14T10:58:17Z

In reply to nevent1q…0zh5
_________________________

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

Our team is already chatting with OpenClaw agents on Keychat. ...

2026-02-14T10:19:07Z

Our team is already chatting with OpenClaw agents on Keychat.

We’re refining the experience ahead of a public release.

  

quoting
nevent1q…pwak
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.)

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

2026-02-14T03:15:09Z

In reply to nevent1q…szuw
_________________________

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

Once you understand the overall design of Keychat, everything ...

2026-02-14T02:56:15Z

Once you understand the overall design of Keychat, everything will fall into place.👇

quoting
nevent1q…n0x6
Use Amber to log into Keychat (npub1h0u…rwx8), use nip-07 to log into jumble.social, seeing a product you want being made by a small business, clicking on their link in their profile that opens in Keychat's internal browser, filling your cart, going to checkout, hit pay in bitcoin and it opening a lightning invoice I can pay with my NWC spending wallet credentials connected to Keychat, all within Keychat, might sound complicated and annoying, especially given how many times I've said Keychat.

Yet somehow to me it feels like all the frictions of how online value transfers, and concessions that come from centralized "solutions", were somehow removed.

Currently, when a Keychat user accepts a chat request, the other ...

2026-02-13T00:04:24Z

In reply to nevent1q…cplu
_________________________

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.

You’re absolutely right. However, Keychat is currently designed ...

2026-02-12T12:32:16Z

In reply to nevent1q…cqvx
_________________________

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.

When choosing a chat app as OpenClaw’s channel, it’s easy to ...

2026-02-12T02:04:34Z

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

#nevent1q…yqyf

2026-02-09T10:02:54Z

In reply to nevent1q…sj6n
_________________________

quoting nevent1q…yqyf
If you are a Keychat user, don’t miss Nosotros.

https://nosotros.app/
nevent1q…8e9k

#nevent1q…rtt8

2026-02-09T08:54:24Z

In reply to nevent1q…rl6t
_________________________

quoting nevent1q…rtt8
The latest Android version of Keychat now supports message notifications via UnifiedPush.

If you’re using Keychat on GrapheneOS, feel free to upgrade.

https://github.com/keychat-io/keychat-app/releases

If you are a Keychat user, don’t miss Nosotros. ...

2026-02-09T08:17:17Z

If you are a Keychat user, don’t miss Nosotros.

https://nosotros.app/

quoting
nevent1q…8e9k
Pushed a new version of nosotros (dev.nosotros.app 1.8.0)

* Image and Video compression is here, it uses jSquash for image compression, it's a library that comes with a handful codecs from google chrome labs Squoosh image compression app, for video it uses FFmpeg wasm, all directly in the browser.
* The upload now will happens before the image appears in the editor, both compression and upload comes with nice progress bars.
* New users table on sqlite to search for users by name or display_name, good when tagging (that might be a database migration here which might take some time to load this new version).
* You can now create any NIP-51 list, any kind, any tag, fully generic, also supports encryption.
* A bunch of other fixes.

Could you tell me which Linux phone you’re using?

2026-02-09T07:14:31Z

In reply to nevent1q…tln9
_________________________

Could you tell me which Linux phone you’re using?

Looking forward to Nostria being able to directly invoke the ...

2026-02-09T01:12:14Z

In reply to nevent1q…g3cn
_________________________

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.

Just as Bitcoiners can verify Bitcoin’s overall design, Keychat ...

2026-02-09T00:50:16Z

Just as Bitcoiners can verify Bitcoin’s overall design, Keychat users can verify Keychat’s overall design as well.

Just as Bitcoiners can verify Bitcoin’s overall design, Keychat ...

2026-02-09T00:45:13Z

In reply to nevent1q…yuyg
_________________________

Just as Bitcoiners can verify Bitcoin’s overall design, Keychat users can verify Keychat’s overall design as well.