If you’ve ever wished chat apps and browsers had built-in public-key IDs and Bitcoin wallets, 👇

MLS is built for large groups; one-to-one support is a byproduct rather than an optimization target. View quoted note →

To many people, “protocol” comes with built-in prestige, while “app” is treated as ordinary. Maybe Keychat should publish a Keychat Protocol too. View quoted note →

View quoted note →

An AI agent, like a human, needs its own autonomous identity and wallet: a public-key ID and a Bitcoin wallet.

If you’re familiar with Keychat’s overall design, the future direction of its development should be clear. 👇 View quoted note →

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:

App Store

keychat.io App - App Store

Download keychat.io by KEYME PTE. LTD. on the App Store. See screenshots, ratings and reviews, user tips and more games like keychat.io.

Android users, Linux users, MacOS users, and Windows users can download it from GitHub:

GitHub

Release v1.39.2+6495 · keychat-io/keychat-app

Keychat 1.39.2+6495 Nostr Wallet Connect (NWC) wallet based on NIP-47. Notification for macOS Fix other bugs. #149 Download based on your OS: ...

Android users can also download Keychat from ZapStore. View quoted note →

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.

This note will give you a clearer understanding of Nostr DM. 👇 View quoted note →