Thread - Nostr Hypermedia

> He's wrong about unencrypted receiver (or meant something else) I meant what I said: monero does not encrypt the receiver. If it did, monero devs could tell me what encryption standard they use (in lightning, we use the Sphinx encryption standard specified in bolt4) and they could point me to the code where the recipient's key gets encrypted (in lightning, that code is here:

GitHub

lnd/htlcswitch/hop/iterator.go at b068d79dfbd2f583d890fd605953d0d4fb897a27 · lightningnetwork/lnd

Lightning Network Daemon ⚡️. Contribute to lightningnetwork/lnd development by creating an account on GitHub.

Monero does not encrypt the recipient's public key -- it gets published in plaintext on the blockchain -- so the protocol does not specify any encryption standard for that and there is nothing in the codebase where it gets encrypted.

↑ Parent

Replies (3)

Saberhagen The Nameless 8 months ago

Maybe technically it's more like hashing? Regardless, the practical effect is the same since it's a string of indecipherable and seemingly random characters that are seen once and never again. Third parties can't link a stealth address to a public address off-chain or to any other stealth address.

1 replies ↓

npub1deml...thv4 8 months ago

Alright, that's true. But it's not a good argument against Monero privacy because the link between UTXO and the receiver is still hidden from third parties and the link between receiver and his subsequent receiver is also hidden from the sender. The link between sender's sender and the sender is somewhat obscured, as you said with probability 1/15. I do agree that LN has better privacy than Monero, but using bad arguments doesn't help anyone.

npub1deml...thv4 8 months ago

It's diffie-helman which does involve hashing but only as a layer of protection and the most significant thing doing the unlinking is the diffie-helman computation.