Keychat is built on the shoulders of giants: Nostr protocol, Cashu protocol, and Signal protocol. Thanks, giants! View quoted note →

By the way, we don't intend to make Keychat a closed application. Users have the option to choose which relay to use and which Cashu mint to use. After the code is open-sourced, we will write a NIP so that everyone can develop applications that are compatible with Keychat. We want Keychat to become a chat browser. View quoted note →

We are considering trying out "pay to chat." Imagine you created a special ID solely for chatting with bots. You add an AI bot as a friend on Keychat, and it first informs you that asking a question costs 2 sats. If you agree to this price, every message you send to the AI bot will automatically include 2 sats (Cashu token). The AI bot collects the sats and then returns an answer to you. No registration, no subscription. Pay per use anonymously. Anyone can run such an AI bot, and it can be various types of bots. Think of it as chat bot as a service. View quoted note →

Perhaps users should consider posting to the relay as renting a billboard for display, with the user deciding whether to continue paying for the display. It is essential to save the note locally, as the relay is merely a display medium. View quoted note →

Compared to the PoW solution, the stamp solution not only solves the spam problem but also generates income for relays. This allows relays to operate sustainably. View quoted note →

One major difference between email and mail is that email doesn’t use a stamp, while mail uses a stamp. View quoted note →

Use ecash sat as a stamp for notes. View quoted note →

A common misconception in the Nostr community is that Nostr is not suitable for private things. View quoted note →

Npub.pro brings a space-based structure to Nostr. Thanks @brugeman @Npub.pro The Keychat website on Npub.pro is:

Keychat

Keychat

Keychat is a chat app, built on Bitcoin ecash, Nostr protocol and Signal protocol. Keychat is inspired by the postal system — stamps, post offic...

View quoted note →

The privacy leakage of metadata in encrypted messaging can be divided into two levels: application level and network level. At the application level, using registered accounts as addresses makes it easy for server to know who is messaging whom. A better practice would be to use different and updated sending and receiving addresses for each message. At the network level, metadata privacy is compromised when the user's client connects to the server, as the server can identify the user's IP address. Network level issues can only be solved at the network level. MASQUE Proxy holds great promise for addressing network level metadata privacy issues. View quoted note →