Keychat seals not only the sender but also the recipient.
nostr:note1p78u60rdhtgta0cjuc6rluflqaw3jjvgwaf5w96t9rmayxq0uhqs9q3exa
Discussion
Interesting 🤔 Bob's almost one-time receiving address] - you say “almost” can you elaborate?
P.S. I still think in order to use nostr in a “private way” relay specs should be changed as well as key management.
If Alice and Bob chat using Keychat, when Alice sends a message and Bob replies, both of their receiving addresses are single-use. If Alice sends three consecutive messages and Bob then replies with one message, Bob's receiving address will have been used three times.
In summary, as long as the other party responds, the receiving address will be updated.
Not having identity is better approach than having it. Your public key still can be traced across the network if not managed carefully. The goal is the minimal digital footprint right ?
Why did SimpleX Chat previously only have 1-time invitation links, and now added the SimpleX contact address? What exactly is the SimpleX contact address?
You think with a broken nostr key pair you outsmart this guys? 
You don’t understand why Simplex Chat added the contact address.
I’m discussing specific point with you, but you blindly trust Simplex Chat. Do you really understand Simplex Chat?
There is no need to continue the discussion.
Yo already told you the flow the chat you are building ! The beginning is of the trace starts from the public and private key creation ! Then it goes to the relays !
I’m not saying that simplex servers are good and they are about to censor and you can run your own one and same applies to the relays but the public key trace is 💩
nostr:note18ef8r2naprhyv956syrjyaapc3pqngef7n6ax36ku7g8djfesltqhx6m8s