If you’re browsing Jumble in the Keychat browser and find an interesting note, you can instantly share it to any chat room.

While using Jumble via the Keychat browser, I noticed a Keychat note being quoted. Zapping the note triggered an automatic zap invoice payment from my Keychat wallet.

We recommend you try the web app in the Keychat browser. While using these web apps, if you come across an "Extension Login" option, you can log in with your Keychat ID by clicking it. Similarly, when you encounter a Lightning Network invoice and an "Open Wallet" button, clicking it will allow you to pay using your Keychat Wallet. View quoted note →

Great news — Keychat is now live on the Apple App Store! We’re still waiting for Google Play approval. iPhone users can download it here:

Keychat APP

Keychat is the super app for Bitcoiners. Autonomous IDs, Bitcoin ecash wallet, secure chat, and rich Mini Apps — all in Keychat.

If you need some ecash sats to try out Keychat’s unique sats stamp feature, you can add this Keychat ID as a friend.👇 @npub17a6f...7x39 By quoting this note, you’ll also get zapped with sats.

Telegram groups do not have end-to-end encryption, so you can join a group by clicking on a group link, similar to a forum. Keychat groups are end-to-end encrypted and provide both forward and backward secrecy. It’s difficult—if not impossible—to allow users to join a group simply by clicking a group link, like in Telegram. Keychat group chats are designed for friends, and new members are invited by existing ones. Nostr NIP-29 groups are more similar to Telegram groups. View quoted note →

It’s great to see a growing number of apps offering simultaneous support for all three wallet types. View quoted note →

Many people say they dislike super apps, yet they have no problem with web browsers—which are arguably the ultimate super apps. Why? Because browsers give access to services from many different providers, not just one company. It’s not super apps people object to — it’s putting all their personal data under the control of a single corporation. View quoted note →

We’re currently working on packaging Keychat for Linux and Windows. View quoted note →

It’s been two weeks since we submitted Keychat to the Apple Store and Google Play. Still under review. Maybe Keychat is just a little too avant-garde. 😂

From our perspective, the two most important design choices in Nostr are: first, it boldly allows users to use public keys directly as IDs; second, it has chosen a relay model (neither federated nor peer-to-peer) in which relays do not communicate with each other. These two aspects are not biased towards a public social network and are equally applicable to private chat apps. View quoted note →

Keychat’s improvements are centered around user sovereignty—something that should never be a luxury. View quoted note →

Let me use the metaphor of a letter to explain how Keychat processes messages: encrypting the content and filling out the envelope. The content of the message is encrypted using either the Signal protocol or the MLS protocol. These protocols continuously derive new encryption keys behind the scenes for every message, ensuring forward and backward secrecy. Keychat leverages these open-source libraries directly, reusing libsignal and OpenMLS for encryption. When filling out the envelope, it’s important to understand that the user name, sending address, and receiving address are all separate concepts. The envelope doesn’t include the name. The sending address can be left blank, which effectively means a new random sending address is generated for each message. The receiving address, on the other hand, is constantly rotated—but it must be known only to the two communicating parties, so it can’t be purely random. Now you might ask: should each message include the next receiving address in its content? That approach works, but there’s a simpler solution. During encryption, a continuously evolving key—tied to the message encryption process and known only to the sender and recipient—can be used to deterministically derive the next receiving address. Then attach a sat stamp, and finally send it to the Nostr relay.

Nick Szabo’s 1999 essay “Micropayments and Mental Transaction Costs” explores why micropayments have been slow to take off in the internet economy. He argues that while technical solutions can reduce the cost of processing payments, the real hurdle lies in the mental effort users must spend evaluating each transaction—what he calls the “mental transaction cost.” In Keychat, users make micropayments by sending sat stamps to the relay or sats to the bot. But these payments don’t suffer from the mental overhead Szabo described. Why? Because the price is fixed—1 sat equals 1 stamp—and the payment process is completely automated by the app. There’s no need for the user to stop and think each time they send a message.

Micropayments and Mental Transaction Costs | Satoshi Nakamoto Institute

Advancing and preserving bitcoin knowledge