mleku on Nostr: also, bitcoin doesn't have encryption. it has signatures but that is "cryptography" ...
also, bitcoin doesn't have encryption. it has signatures but that is "cryptography"
yes you can use the same secret key as you sign with for auth to generate shared secrets but that's still not encryption, still simply cryptography. the encryption part is what happens after you generate the shared secret.
but then again, even among nostr devs not all of them even understand this, i wonder if anyone picked him up on this point. probably he shadowbanned them anyway.
encryption is not when you generate an unforgeable signature. it doesn't have to be *your* secret key, it's better if you generate one for a message. the target has the secret tied to the public key and the public key of the generated secret is sent in plaintext in front of it. in nostr parlance this is a "giftwrap" and the idea is that only one side of the conversation is identified, the sender would then put their public key in the message and sign it and then encrypt the message and signature.
and then further to that is forward secrecy techniques that make forward but not reverse linkable chains of keys so the client doesn't have to keep doing ECDH. but honestly, computers are so fast now that's not even necessary, i was able to make a single core push 8mb/s of 1kb packets each packet having a unique key, and receiving is the same process. tbh i have not wrapped my head around the initial key negotiation process exactly, this is not done with nostr because it's not an interactive protocol. but instant messaging on nostr could be an interactive protocol using ephemeral events.
Published at
2025-06-03 20:51:34Event JSON
{
"id": "4fb6649e43027ebcd06878b53514d9a8b0b19e301ff30249fa7cda467eb32225",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1748983894,
"kind": 1,
"tags": [
[
"e",
"a3f9353d355bda043f57e2a7204b9cfed75a2a275830ce2788e39b1a91ce22f9",
"wss://nos.lol/",
"root",
"17538dc2a62769d09443f18c37cbe358fab5bbf981173542aa7c5ff171ed77c4"
],
[
"e",
"3e790f67f5200e89bf0c04166a1e033f0d49f2c28945a6186b7dc82eafbde19c",
"wss://nostr.mom/",
"reply",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f"
],
[
"p",
"3fc5f8553abd753ac47967c4c468cfd08e8cb9dee71b79e12d5adab205bc04d3"
],
[
"p",
"17538dc2a62769d09443f18c37cbe358fab5bbf981173542aa7c5ff171ed77c4"
]
],
"content": "also, bitcoin doesn't have encryption. it has signatures but that is \"cryptography\"\n\nyes you can use the same secret key as you sign with for auth to generate shared secrets but that's still not encryption, still simply cryptography. the encryption part is what happens after you generate the shared secret.\n\nbut then again, even among nostr devs not all of them even understand this, i wonder if anyone picked him up on this point. probably he shadowbanned them anyway.\n\nencryption is not when you generate an unforgeable signature. it doesn't have to be *your* secret key, it's better if you generate one for a message. the target has the secret tied to the public key and the public key of the generated secret is sent in plaintext in front of it. in nostr parlance this is a \"giftwrap\" and the idea is that only one side of the conversation is identified, the sender would then put their public key in the message and sign it and then encrypt the message and signature.\n\nand then further to that is forward secrecy techniques that make forward but not reverse linkable chains of keys so the client doesn't have to keep doing ECDH. but honestly, computers are so fast now that's not even necessary, i was able to make a single core push 8mb/s of 1kb packets each packet having a unique key, and receiving is the same process. tbh i have not wrapped my head around the initial key negotiation process exactly, this is not done with nostr because it's not an interactive protocol. but instant messaging on nostr could be an interactive protocol using ephemeral events.",
"sig": "5bf286cdd5e614d6687f9cc275ddfc8f165ed953a13a812ccdf4bbd74db3f12f6e942ab183d042b3299e7fe4681bea67e83079b9ac77cd7609fd1edaa9870f2f"
}