keychat on Nostr: There is a type of solution that initially seems hard to conceive, but once ...

There is a type of solution that initially seems hard to conceive, but once disclosed, almost everyone can verify that it's a good solution. These solutions are not particularly complex; they are simply overlooked. This might be what is referred to as insight. We believe that Keychat's use of Bitcoin ecash as postage for messages and the separation of sending and receiving addresses from the ID, with continuous updates, are examples of such insights. They are easily verifiable because they are simple.

quoting note1f6v…gmq6

Current chat applications and email have forgotten that an address is not the same as an ID, treating the ID as the address. Emails and current chat applications send messages as [from: Alice's ID to: Bob's ID]. Regardless of how your geographical address changes, when Alice sends an email to Bob, it’s always [from: Alice's ID to: Bob's ID]. This compromises metadata privacy.

However, letters work differently; they are [from: Alice's current geographical address to: Bob's current geographical address].

Keychat separates the receiving address and sending addresses from the ID, and the receiving address and sending addresses are also different. Keychat messages are [from: Alice's one-time sending address to: Bob's almost one-time receiving address]. This makes it difficult for outsiders and relay administrators to determine who is sending messages to whom.

(The new note has modified some expressions, making it clearer.） note1h84…gse4