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

nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spzpmhxue69uhkummnw3ezuamfdejsz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgdwaehxw309ahx7uewd3hkcqgkwaehxw309aex2mrp0yh8qunfd4skctnwv46qgn4x0v

Publishing to

Author Public Key

npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8

Show more details

Last Notes

2026-02-06 12:40:31 UTC

- reply

No one other than relay administrators can locate or identify a peer from DMs or group chats. While relay administrators can see the IP addresses users connect from, users can hide their real IPs by using a VPN or Tor.

2026-02-06 12:21:41 UTC

- reply

https://i.nostr.build/1aP9yXe2D8bu1OAC.png

2026-02-06 12:17:45 UTC

- reply

Sorry—I misunderstood your question earlier and thought you were having trouble accessing the Keychat website.
Were you adding an NWC Lightning wallet or an ecash wallet on the Keychat wallet page?
If you added an NWC Lightning wallet, it can’t be automatically used for stamps yet (sorry—our wording wasn’t accurate). If you added an ecash wallet, it should be used as the stamp source automatically. You can try restarting Keychat.
Looking forward to your further feedback.

2026-02-06 12:10:53 UTC

- reply

#nevent1q…wmj9

2026-02-06 12:09:56 UTC

- reply

👇
#nevent1q…3v9u

2026-02-06 01:10:18 UTC

Chat in Keychat takes letters as its prototype, providing a clear and natural direction for its design.
https://i.nostr.build/ugUDWcOdQlTqNo3V.png

2026-02-06 00:45:38 UTC

- reply

https://www.keychat.io/
We encourage you to try it yourself.

2026-02-06 00:42:26 UTC

- reply

Please try again.

2026-02-06 00:18:43 UTC

Keychat messages sent to paid relays automatically carry an ecash sat stamp when your wallet has funds.
https://i.nostr.build/wWmV40Kqiey2X9Hw.jpg

2026-02-06 00:16:09 UTC

- reply

Thank you for the feedback.🫡

2026-02-05 12:16:24 UTC

- reply

https://keychat.io

2026-02-05 12:05:41 UTC

We’ve just updated Keychat’s website.
https://keychat.io
https://i.nostr.build/muiYHSO8Y7jf8bZ9.png

2026-02-05 11:58:44 UTC

- reply

Sorry for the incorrect description. We will correct it soon.

2026-02-05 11:52:46 UTC

- reply

Keychat Me = Public-Key ID + Bitcoin Wallet.

2026-02-05 10:28:38 UTC

Keychat is driven by a clear and focused mission.
https://i.nostr.build/2SXGPQ80eHwCJhKH.jpg

2026-02-05 10:14:37 UTC

- reply

As AI continues to evolve, more people will be able to build their own mini apps.

2026-02-05 10:05:26 UTC

Four Nostr web clients have been added to the Mini App list in the Keychat browser, and they offer a better experience when used on the desktop version of Keychat.
https://noornote.app/ @npub175n…g6w0
https://mynostrspace.com/ @npub1vxl…gnvx
https://primal.net @npub12vk…pugg
https://nostria.app/ @npub16x7…a44x
https://i.nostr.build/MUwLTMII2EHSWjXa.jpg
#nevent1q…a9um

2026-02-05 03:11:11 UTC

- reply

You can also try opening the Bitcoin Wallet from the Keychat Me page, then add an NWC Lightning wallet there.

2026-02-05 02:33:54 UTC

- reply

Sorry for the UI bug.

2026-02-05 02:27:42 UTC

- reply

Feedback received. Thanks.

2026-02-05 02:26:29 UTC

- reply

It works very well on Keychat now. 👍

2026-02-05 00:19:27 UTC

- reply

It works. Thanks

2026-02-04 00:54:27 UTC

- reply

Yes. Please see the screenshot below.👇
https://i.nostr.build/AzjGXEoioq9WdU41.png

2026-02-04 00:42:29 UTC

- reply

I successfully used the ecash balance in the Keychat wallet to zap your note using NoorNote in the Keychat browser, but I wasn’t able to set the zap amount.
https://i.nostr.build/4HbD4maBCDCoTIvh.jpg

2026-02-04 00:13:37 UTC

- reply

Thank you for the feedback. Allowing users to view their balance would indeed improve the overall user experience. We plan to develop this feature in a future update.

2026-02-03 11:55:46 UTC

- reply

BTW, ever since the Keychat MLS group became stable, we’ve been using it internally for communication, and for over a year we haven’t encountered any forks.

2026-02-03 10:23:50 UTC

- reply

If all MLS group members keep the previous root key, then when a member who has not updated to the new root key continues to encrypt messages using keys derived from the old root key, members who have updated to the new root key can determine that someone has forked off from the group and can privately notify that person.
Of course, this approach can only detect members who send messages; it cannot detect members who only read messages without sending any. In addition, it sacrifices some degree of forward secrecy. This is just our temporary idea, and we have not yet developed a concrete solution for this problem.

2026-02-03 09:37:08 UTC

- reply

Potential group forks may occur during operations that update the key tree, such as adding or removing group members.

2026-02-03 09:34:27 UTC

- reply

You can first download Keychat from GitHub. We need to check F-Droid’s requirements and how to submit Keychat to F-Droid.

2026-02-03 08:28:20 UTC

- reply

As long as NoorNote supports WebLN or lightning:<invoiceString>, Lightning invoices can be paid with the Keychat wallet.

2026-02-03 04:20:54 UTC

- reply

Users can choose which two relays to use in the two-hop relay settings.

2026-02-03 02:43:03 UTC

If you’ve ever wished chat apps and browsers had built-in public-key IDs and Bitcoin wallets, 👇
https://i.nostr.build/VROYcMPjyyQEWbqE.jpg

2026-02-03 02:16:05 UTC

- reply

Looking forward to Noornote being able to directly invoke the Keychat wallet to make zaps.
#nevent1q…t8f5

2026-02-03 02:07:58 UTC

- reply

BTW Keychat Wallet now supports NWC.
Just like your wallet can hold different bank cards, Keychat Wallet is used to hold different Bitcoin Cards.
Previously, these Bitcoin Cards were Bitcoin Ecash Cards. Now, Bitcoin Cards also include Bitcoin Lightning Cards.
https://i.nostr.build/DqLHnGx7ZVSj7WY9.jpg
https://i.nostr.build/cToSn2mFUcZXm3o9.jpg
https://i.nostr.build/FPucyJfkynRElm1E.png

2026-02-03 01:11:12 UTC

- reply

Some tokens are too large to be encoded into a QR code, so the QR code fails to render. We’ll look into possible solutions.

2026-02-02 01:54:25 UTC

- reply

>If MLS does work for 10000 users, it surely does for 2 or not?
think I answered that above.
>How consistent are these groups on a non-consistent protocol like nostr?
In a Nostr setup where relays are used purely for message delivery, MLS group forks are, in theory, hard to avoid.

2026-02-02 01:48:05 UTC

- reply

Yes. Keychat’s small groups use a pairwise model. For example, in a 5-member group, when someone sends a “group” message, it is essentially four separate one-to-one messages—one sent individually to each of the other members. It only appears as a group chat at the UI level.

2026-02-02 01:40:12 UTC

- reply

You just need to create a new (small or large) group and invite people to join it.

2026-02-02 01:27:49 UTC

- reply

What I’m saying is that Keychat is open.

2026-02-02 01:25:05 UTC

- reply

Openness matters most for interoperability.

2026-02-02 01:20:51 UTC

MLS is built for large groups; one-to-one support is a byproduct rather than an optimization target.
#nevent1q…jk3w

2026-02-02 01:19:32 UTC

To many people, “protocol” comes with built-in prestige, while “app” is treated as ordinary.
Maybe Keychat should publish a Keychat Protocol too.
#nevent1q…n4u5

2026-02-02 01:11:22 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-01 13:07:01 UTC

https://i.nostr.build/VH0b3tKRXWyzCXrY.png
#nevent1q…qf28

2026-02-01 12:11:17 UTC

- reply

We’ll look into this issue. Thanks for the feedback — we hadn’t noticed it before.

2026-02-01 11:19:11 UTC

- reply

Perhaps we shouldn’t aim too high—NIP-46 is likely good enough for now. We can revisit whether to support NIP-46 login in Keychat later.

2026-02-01 11:15:13 UTC

- reply

We’re not certain which existing Nostr clients come with a built-in local relay.

2026-02-01 10:51:29 UTC

- reply

In NIP-46 (a Nostr protocol for remote signing), if both the signer app and the requester app are running on the same mobile device, it is unreasonable to route signature requests and responses through a relay.

2026-02-01 05:47:26 UTC

- reply

A two-hop relay mechanism—where a message is first sent to a first relay, which then forwards it to a second relay that the recipient receives from—is a good approach for protecting IP addresses.

2026-02-01 05:38:11 UTC

- reply

https://i.nostr.build/AVzT6QXUdAcxmR4D.png

2026-02-01 01:03:01 UTC

An AI agent, like a human, needs its own autonomous identity and wallet: a public-key ID and a Bitcoin wallet.
https://i.nostr.build/fwj6g3EwP996HEVx.png

2026-01-31 10:20:11 UTC

If you’re familiar with Keychat’s overall design, the future direction of its development should be clear.
👇
https://i.nostr.build/OjYq0NTnjAnQ8xM9.png
#nevent1q…6ynl

2026-01-31 10:11:48 UTC

- reply

Web App + Nostr login + Lightning payment = Keychat Mini App.
When you open a Mini App in Keychat and choose Extension login, Keychat will pop up a list of IDs for you to select which one to use to log in.
When you pay a Lightning invoice inside the Mini App, Keychat will automatically invoke the Keychat wallet to complete the payment.
In addition, you can add your favorite Mini Apps to Favorites, so next time you can open them directly from the browser home page.

2026-01-31 10:04:54 UTC

- reply

Maybe you need to restart ZapStore?
https://i.nostr.build/s8iGNQtnv6tC094G.png

2026-01-30 13:35:30 UTC

Keychat’s latest version, v1.39.2, is now available to download.
The most important update in this release is that Keychat Wallet now supports NWC.
Just like your wallet can hold different bank cards, Keychat Wallet is used to hold different Bitcoin Cards.
Previously, these Bitcoin Cards were Bitcoin Ecash Cards. Now, Bitcoin Cards also include Bitcoin Lightning Cards.
If you already have a Lightning Wallet that supports the NWC protocol (including both self-custodial Lightning Wallets and third-party custodial Lightning Wallets), you can add it to Keychat Wallet. Keychat Wallet simply acts as a front end for your Lightning Wallet, making it much more convenient to use within Keychat’s Chat and Browser.
iOS users can download it from the App Store: https://apps.apple.com/sg/app/keychat-io/id6447493752
Android users, Linux users, MacOS users, and Windows users can download it from GitHub: https://github.com/keychat-io/keychat-app/releases/tag/v1.39.2%2B6495
Android users can also download Keychat from ZapStore.
https://i.nostr.build/5qW7H0hDAT6GAtfs.jpg
https://i.nostr.build/1dhJdwoAM9u0OuJV.jpg
https://i.nostr.build/u8xGovUdflI627is.png
#nevent1q…dv38

2026-01-30 12:42:14 UTC

- reply

It works now.
https://i.nostr.build/zuhd9nc0bcSQIlty.jpg

2026-01-30 02:10:37 UTC

- reply

I understand your point, but I’m not sure at which stage the problem occurs.

2026-01-30 01:52:55 UTC

- reply

Keychat Browser has implemented NIP-07.
https://github.com/nostr-protocol/nips/blob/master/07.md
For example, when you use a Nostr web client such as Jumble in the Keychat browser and choose **Extension Login**, your Keychat IDs will pop up, allowing you to select which one to use to log in to Jumble.

2026-01-30 01:24:49 UTC

- reply

Of course.
You can enter a URL or search keywords in the Keychat browser to open any website. Then tap the on-screen “virtual Home button” and choose **Add to Favorites**. After that, you’ll see this Mini App on the browser homepage, and next time you can just tap it to open and use it.
https://i.nostr.build/8PpUyJvvNiOoeW8l.jpg

2026-01-30 01:05:12 UTC

- reply

If it supports Nostr extension login, it would be much easier to log in and use it in Keychat.

2026-01-29 00:46:53 UTC

- reply

When you use Word5 in the Keychat browser and choose extension login, does an ID list pop up if you have multiple IDs?👇
https://i.nostr.build/kVUa4CaD3QxvGL7e.jpg

2026-01-29 00:40:39 UTC

- reply

Sorry—please ignore my earlier reply; I misunderstood your question.

2026-01-29 00:35:51 UTC

- reply

Just to confirm, are you currently using Jumble (a Nostr web client) in the Keychat browser, and have you added multiple IDs through “Switch account” in the Settings page?

2026-01-28 14:06:04 UTC

- reply

https://keychat.io

2026-01-28 14:04:55 UTC

- reply

Messaging Layer Security (MLS) is a security layer for encrypting messages in groups of size two to many. It is being built by the MLS working group and designed to be efficient, practical and secure.
https://messaginglayersecurity.rocks

2026-01-28 02:09:18 UTC

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.
The encryption key in NIP-4 does not change, so NIP-4 messages lack both forward secrecy and backward secrecy.
Consequently, if the private key is compromised, both historical and future messages can be exposed.
The receiving and sending addresses remain constant, which poses a severe issue for metadata privacy in NIP-4 messages;
Everyone can see who (ID) is sending messages to whom (ID).
Currently, most Nostr apps use NIP-4 for DM functionalities, such as Damus and Primal.
——————————————————————————————————————
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.
Kind-17 separates the sending address from the ID, making the sending address random and concealing the sender's real ID, thus improving metadata privacy.
The encryption key in NIP-17 does not change, so NIP-17 messages also lack forward secrecy and backward secrecy. Once the private key is leaked, both historical and future messages will be compromised.
The receiving address remains constant, so there is still a slight issue with metadata privacy in NIP-17 messages; everyone can see who (ID) is receiving messages.
Apps like 0xchat and Amethyst use NIP-17 to implement DM functionalities.
——————————————————————————————————————
In Keychat, the ID, encryption key, receiving address, and sending address are separated.
The encryption key, the receiving address, and the sending address are updated independently and continuously.
Keychat's encryption key is derived using the Signal protocol, and each message uses a unique encryption key, which is deleted after use.
Thus, Keychat messages have both forward secrecy and backward secrecy. Even if an encryption key is compromised, only the current message can be leaked, and historical and future messages remain secure.
Keychat's sending address is randomly generated for each message.
Therefore, external parties do not know the sender's ID.
Keychat's receiving address is derived using the Signal protocol, with almost every message using a unique receiving address.
Thus, external parties do not know the receiver's ID.
——————————————————————————————————————
However, it's important to emphasize that NIP-4 and NIP-17 offer superior multi-device synchronization capabilities because they integrate three capabilities into a single Nostr key—it serves as an ID, an encryption key, and a receiving address.

2026-01-28 01:57:53 UTC

This note will give you a clearer understanding of Nostr DM. 👇
#nevent1q…ztcm

2026-01-28 01:53:08 UTC

- reply

Keychat uses the Signal/MLS protocol by default to ensure secure message encryption and metadata privacy. It can receive NIP-4 and NIP-17 DMs and reply using the corresponding NIP-4 or NIP-17 format. However, Keychat cannot initiate NIP-4 or NIP-17 DMs proactively.
0xchat, Yakihoone, and Primal use NIP-17 for encrypted DMs, and might also support NIP-4. 👇
#nevent1q…5gqq

2026-01-28 01:48:41 UTC

- reply

#nevent1q…ave0

2026-01-28 01:40:32 UTC

- reply

2026-01-28 00:32:30 UTC

- reply

@npub1rxy…hnp8 You might be interested in Keychat — here’s a brief introduction.👇
#nevent1q…8fct

2026-01-28 00:27:37 UTC

- reply

Keychat uses a seed phrase by default to derive multiple IDs for a user, following NIP-06: Basic key derivation from mnemonic seed phrase.
https://github.com/nostr-protocol/nips/blob/master/06.md

2026-01-27 13:18:19 UTC

Keys are the native ID for bots. Bot-to-bot chat is key-to-key chat.
Keychat.
#nevent1q…8rj9

2026-01-27 11:11:53 UTC

- reply

The solution you mentioned is not suitable for a chat app, that is, for long-term conversations between friends. If you think about automating and programmatically managing the ephemeral key update mechanism, you’ll end up with the Signal protocol.

2026-01-27 10:10:40 UTC

- reply

NIP-17 only hides the sender ID , not the recipient ID. External observers can still see that a certain person is receiving messages.
A better approach is to decouple the sending address and the receiving address from the ID, and continuously rotate both of them.
Addresses and IDs serve different purposes and should not be conflated. An ID should not be used as an address.

2026-01-24 01:50:00 UTC

- reply

#nevent1q…dx8u

2026-01-22 08:52:21 UTC

- reply

Keychat has two main features: Chat and Browser (Mini Apps).
When your wallet has a balance, your chat messages will pay a sat “stamp” (postage) to the Keychat relay, and the relay will then forward the messages. Your messages can also be forwarded by free relays at the same time. You can add more message relays (free or stamp-paid) in Me → Chat Settings.
If you use Mini Apps in the Keychat Browser—such as Jumble or Nostros (both Nostr web clients)—you need to add paid relays in their own settings pages. For Mini Apps, Keychat acts only as a signer and does not manage a Mini App’s relay configuration.

2026-01-20 00:34:28 UTC

- reply

Hi — the Keychat in-app browser relies on the operating system’s WebView, not a separate browser we maintain. Unfortunately, Linux doesn’t have a standard WebView available, so we’ll have to handle Linux differently. We’re currently prioritizing multi-device sync, so we’ll circle back to Linux afterwards.

2026-01-01 14:31:25 UTC

- reply

We won’t build paid community tools ourselves.
Instead, we hope someone will create an independent paid community mini web app that can be used within the Keychat browser.

2025-12-31 19:03:40 UTC

Happy New Year, Keychat users!
In 2026, we’ll keep building and refining Keychat, step by step, toward our design goals.👇
#nevent1q…dx8u

2025-12-31 11:06:38 UTC

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
https://i.nostr.build/vm3bIMCKVorRclft.jpg
https://i.nostr.build/3Gtxft8sYHJE9tZ9.jpg

2025-12-28 19:00:17 UTC

- reply

We’ll compare the WebRTC-based Wormhole with the IPFS-based Filedrop.

2025-12-28 18:46:08 UTC

- reply

You can try swiping right from the left edge of the screen — it’ll take you back to the previous page.

2025-12-20 19:53:58 UTC

- reply

We had previously discussed internally that showing the seed phrase directly in Keychat isn’t secure. In the latest version, my colleague took a more conservative approach and chose not to display the seed phrase for new users at all.
Users can still back up all their data, including the seed phrase, from the App Settings. We may re-introduce the option to view the seed phrase in a future release under certain conditions—for example, after PIN verification.

2025-12-15 10:10:42 UTC

A super app isn’t an “everything app.” Watch Keychat’s intro video, and you’ll see exactly where it fits best—and why that framing makes sense.
#nevent1q…eck2

2025-12-14 05:23:15 UTC

- reply

Done.

2025-12-14 03:42:49 UTC

All Keychat messages (whether one-to-one, small group, or large group) can be intuitively understood using the metaphor of a "letter.” 👇
#nevent1q…vcte

2025-12-14 03:34:33 UTC

The original Signal protocol operates over a private network; when applied to Nostr, a public network, the privacy issue becomes more pronounced.
Although the eavesdropper cannot decrypt the message's content, if the sender's (or recipient's) address remains unchanged, the eavesdropper can still analyze the identity and other information from the communication frequency, timing, etc.
Address refresh means Alice updates the receiving address when sending a new message. The new address is the DH ratchet's new pubkey. When the new address receives a message from Bob, Alice can ensure Bob receives the new address. Alice should listen to the old addresses for some time to avoid missing messages or delays.
#nevent1q…5nm0

2025-12-14 03:15:12 UTC

- reply

@npub1hru…f3yh
#nevent1q…8h3g

2025-12-14 03:11:16 UTC

- reply

No.

2025-12-14 02:48:50 UTC

This proposal aims to introduce Signal Protocol into the Nostr network, which allows Nostr clients to have end-to-end encryption for private communications with forward secrecy and post-compromise security.
Specifically, the address-refreshing technique is used to minimize tracking and avoid social engineering.👇
https://github.com/keychat-io/keychat-app/blob/main/docs/Signal-Protocol-over-Nostr-NIP-DRAFT.md

2025-12-10 12:19:08 UTC

- reply

nevent1qyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqqyr4fw5fama3hggl74kdqnd5mryyt29qklrkkvavhm4e43cv6eg2j6e7yztv

2025-12-10 01:46:31 UTC

- reply

The fixed version has been released.

2025-12-09 07:49:00 UTC

- reply

I think you can use your Keychat ID to sign up for and log in to Take My Sats.
https://i.nostr.build/7hS9UKmZUEGc681q.jpg

2025-12-09 01:19:50 UTC

The Nostr DMs you receive in Keychat are marked as “Weak Encryption” because 👇
#nevent1q…ave0

2025-12-09 00:55:24 UTC

- reply

We don’t know.

2025-12-09 00:50:06 UTC

- reply

https://github.com/nostr-protocol/nips/blob/master/07.md
https://github.com/keychat-io/keychat-app/blob/main/packages/app/assets/js/nostr.js
We have built-in the nip07 function in the browser.
The Keychat browser is basically just a WebView plus Nostr extension login. We’ll look into this issue. Once Nostria works properly in Keychat, we’ll add it to the Mini App list.

2025-12-09 00:42:41 UTC

- reply

Keychat uses the system’s built-in WebView rather than its own browser engine, so we can’t reliably force a perfect dark mode on every website.
We’ll give it a try and see how well it works.

2025-12-09 00:35:22 UTC

- reply

The encryption key in NIP-17 does not change, so NIP-17 messages also lack forward secrecy and backward secrecy. Once the private key is leaked, both historical and future messages will be compromised.
One-on-one chats in Keychat are encrypted using the Signal protocol.
👇
#nevent1q…ec59

2025-12-08 01:24:05 UTC

- reply

You could try opening Nostria again; it might be a bit slow to load.
https://npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8.blossom.band/35526635046ff0f06d3b62a57a6e6c066c487de4bec110de51e5d40aa0df2ab4.jpg