Old Nostr DM (NIP-4) integrates four capabilities into a single Nostr key—it serves as an ID, an encryption key, a receiving address, and a sending address.
The encryption key in NIP-4 does not change, so NIP-4 messages lack both forward secrecy and backward secrecy.
Consequently, if the private key is compromised, both historical and future messages can be exposed.
The receiving and sending addresses remain constant, which poses a severe issue for metadata privacy in NIP-4 messages;
Everyone can see who (ID) is sending messages to whom (ID).
Currently, most Nostr apps use NIP-4 for DM functionalities, such as Damus and Primal.
——————————————————————————————————————
New Nostr DM (NIP-17) integrates three capabilities into a single Nostr key—it serves as an ID, an encryption key, and a receiving address.
Kind-17 separates the sending address from the ID, making the sending address random and concealing the sender's real ID, thus improving metadata privacy.
The encryption key in NIP-17 does not change, so NIP-17 messages also lack forward secrecy and backward secrecy. Once the private key is leaked, both historical and future messages will be compromised.
The receiving address remains constant, so there is still a slight issue with metadata privacy in NIP-17 messages; everyone can see who (ID) is receiving messages.
Apps like 0xchat and Amethyst use NIP-17 to implement DM functionalities.
——————————————————————————————————————
In Keychat, the ID, encryption key, receiving address, and sending address are separated.
The encryption key, the receiving address, and the sending address are updated independently and continuously.
Keychat's encryption key is derived using the Signal protocol, and each message uses a unique encryption key, which is deleted after use.
Thus, Keychat messages have both forward secrecy and backward secrecy. Even if an encryption key is compromised, only the current message can be leaked, and historical and future messages remain secure.
Keychat's sending address is randomly generated for each message.
Therefore, external parties do not know the sender's ID.
Keychat's receiving address is derived using the Signal protocol, with almost every message using a unique receiving address.
Thus, external parties do not know the receiver's ID.
——————————————————————————————————————
However, it's important to emphasize that NIP-4 and NIP-17 offer superior multi-device synchronization capabilities because they integrate three capabilities into a single Nostr key—it serves as an ID, an encryption key, and a receiving address.
keychat / Keychat
npub1h0…srwx8
2024-08-31 08:02:42
Author Public Key
npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8Published at
2024-08-31 08:02:42Event JSON
{
"id": "fc3003d84abf1d314d0b6a4105287e77c7d8489ee759802948908dc38baeb4c1",
"pubkey": "bbf923aa9246065f88c40c7d9bf61cccc0ff3fcff065a8cb2ff4cfbb62088f1e",
"created_at": 1725084162,
"kind": 1,
"tags": [],
"content": "Old Nostr DM (NIP-4) integrates four capabilities into a single Nostr key—it serves as an ID, an encryption key, a receiving address, and a sending address.\n\nThe encryption key in NIP-4 does not change, so NIP-4 messages lack both forward secrecy and backward secrecy. \n\nConsequently, if the private key is compromised, both historical and future messages can be exposed.\n\nThe receiving and sending addresses remain constant, which poses a severe issue for metadata privacy in NIP-4 messages; \n\nEveryone can see who (ID) is sending messages to whom (ID).\n\nCurrently, most Nostr apps use NIP-4 for DM functionalities, such as Damus and Primal.\n\n——————————————————————————————————————\n\nNew Nostr DM (NIP-17) integrates three capabilities into a single Nostr key—it serves as an ID, an encryption key, and a receiving address.\n\nKind-17 separates the sending address from the ID, making the sending address random and concealing the sender's real ID, thus improving metadata privacy.\n\nThe encryption key in NIP-17 does not change, so NIP-17 messages also lack forward secrecy and backward secrecy. Once the private key is leaked, both historical and future messages will be compromised.\n\nThe receiving address remains constant, so there is still a slight issue with metadata privacy in NIP-17 messages; everyone can see who (ID) is receiving messages.\n\nApps like 0xchat and Amethyst use NIP-17 to implement DM functionalities.\n\n——————————————————————————————————————\n\nIn Keychat, the ID, encryption key, receiving address, and sending address are separated.\n\nThe encryption key, the receiving address, and the sending address are updated independently and continuously.\n\nKeychat's encryption key is derived using the Signal protocol, and each message uses a unique encryption key, which is deleted after use.\n\nThus, Keychat messages have both forward secrecy and backward secrecy. Even if an encryption key is compromised, only the current message can be leaked, and historical and future messages remain secure.\n\nKeychat's sending address is randomly generated for each message.\n\nTherefore, external parties do not know the sender's ID.\n\nKeychat's receiving address is derived using the Signal protocol, with almost every message using a unique receiving address.\n\nThus, external parties do not know the receiver's ID.\n\n\n——————————————————————————————————————\n\nHowever, it's important to emphasize that NIP-4 and NIP-17 offer superior multi-device synchronization capabilities because they integrate three capabilities into a single Nostr key—it serves as an ID, an encryption key, and a receiving address.",
"sig": "f5c4d796663ec2247c28c8aff0f84003882059e33877be991d2be1bb63cc0de9a2dece2e159f764b97c5eb1e758d76b8c952a03e78954740f854aa58ad702bee"
}