Keychat users can choose which relays to use. They can also choose not to use Keychat relays at all. Relays can charge for stamps, but they can also operate for free, although free relays often have other restrictions, such as proof-of-work requirements for messages and frequency limits. Relays decide which ecash sats issued by mints can be used as stamps. If a user uses ecash sats issued by a mint that the relay trusts, the relay receives the ecash sats and forwards the message. When a relay accumulates a certain amount of ecash sats, the relay requests the mint to convert these ecash sats into Lightning Network sats. If a user uses ecash sats from a mint that the relay has not previously encountered, the relay first receives the ecash sats and then attempts to convert them into Lightning Network sats. If the conversion is successful, the new mint can be temporarily considered trustworthy, and the message continues to be forwarded. If the conversion is not successful, the new mint is added to a blacklist, and the message is not forwarded.

Secure messaging needs to meet these five requirements as much as possible: 1. Anti-Forgery 2. End-to-End Encryption 3. Forward Secrecy 4. Break-in Recovery 5. Metadata Privacy

Why does Keychat use [ecash sat] as message stamps instead of [Lightning Network sat]? @Juraj gave a very good answer. View quoted note →

If you only have one minute to learn about Keychat, take a look at this 50-word introduction. Keychat is a chat app, built on Bitcoin ecash, Nostr protocol and Signal protocol. Keychat is inspired by the postal system — stamps, post offices, letters. Keychat uses Bitcoin ecash as stamps and Nostr relays as post offices. Keychat uses Signal protocol to ensure message encryption security and meta-data privacy. View quoted note →

Thanks for testing. Regarding point 3, we believe that future relays will add support for storing multimedia content, as Cashu sat can solve the issue of storage payment. View quoted note →

Some people have already put their Keychat ID in their Damus profile. It's best not to use your primary Keychat ID for this; using a secondary ID would be better. This is one of the advantages of being able to use multiple Keychat IDs simultaneously.

With a 12-word seed phrase, you have countless self-controlled IDs. Additionally, this ID seed phrase is also the seed phrase for your Cashu wallet. View quoted note →

If you check the NIP-4 GitHub page now, you will see "deprecated in favor of NIP-17." So, let's analyze the kind-17 using the following thought framework. Kind-17 separates the sending address from the ID, making the sending address random and hiding the sender's real ID, thereby improving metadata privacy.

GitHub

nips/04.md at master · nostr-protocol/nips

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

GitHub

nips/17.md at master · nostr-protocol/nips

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

View quoted note →

The current version of Keychat uses a seed phrase instead of nsec. This has caused a lot of controversy, with many people believing that Keychat does not understand the spirit of Nostr: having a single Nostr ID that is universally used across all Nostr apps. In fact, the first version of Keychat used nsec. Later, we intentionally switched to seed phrases. Why? Just like when we use Bitcoin wallets, we now more often use seed phrases rather than private keys. Using a seed phrase is an improvement in user experience. Moreover, NIP-6 defines the basic key derivation from mnemonic seed phrases. A single seed phrase can derive countless Nostr IDs. Using a single Nostr ID across various Nostr apps focused on public notes is reasonable because users are sending public messages, and they can better accumulate reputation. However, for Nostr apps focused on private notes, users should use multiple IDs to achieve better privacy. For example, you could use ID1 for close friends and ID2 for work colleagues. Current chat applications provided by internet giants do not encourage users to use multiple IDs simultaneously because multiple IDs affect data mining, reducing the accuracy of user profiling and, consequently, advertising revenue. In this context, using only one ID is a bug, not a feature. If you use your Damus ID to chat with others on a Nostr app that focuses on private messaging, do you want all those people to see the public notes you have posted? A seed phrase that is universally applicable to all Nostr apps allows users to choose which ID to use in a particular app, with the ID generated from the seed phrase. This is far better than using a single Nostr ID across all Nostr apps. Don't forget, there are not only Nostr apps focused on public notes but also those focused on private notes. A reasonable chat app allows users to use multiple IDs simultaneously, whereas a microblogging app’s DM often has only one ID. This is just one of the differences between the two. When we say, "Designing a DM for a microblogging app is not the same as designing a chat app," we are not playing with words; we are not that bored.