An incomplete guide to stealth addresses

Re:An incomplete guide to stealth addresses by lysergia on Monday January 23, 2023 @02:57PM (#34494083)

> Basic stealth addresses can be implemented fairly quickly today, and could be a significant boost to practical user privacy on Ethereum. They do require some work on the wallet side to support them

So how easy is it realistically? I hope it's not going to un-ergonomic like PGP where novices are sometimes seeing to be pasting their private key into e-mails and sending things in plaintext which should have been ciphertext, or otherwise leaking info.

I imagine you have to be really careful not to mess things up here.

[ Parent | on HN ]

Re:An incomplete guide to stealth addresses by zaroth on Monday January 23, 2023 @03:17PM (#34494353)

There’s no reason for there to be any sharp edges or foot guns.

The “meta-address” published by the receiver has everything in it needed to generate a one time address on the sender side, and it should all “just work” from a sender’s wallet perspective once a standard is reached.

There’s nothing a sender can do wrong really unless the wallet code is broken. On the receiver side the private key will never look like an “address” so it would be hard to confuse the two.

[ Parent | on HN ]

Re:An incomplete guide to stealth addresses by westurner on Monday January 23, 2023 @08:38PM (#34497913)

Oh, there's WKD: Web Key Directory https://wiki.gnupg.org/WKD#How_does_an_email_client_use_WKD....

  gpg --homedir "$(mktemp -d)" --verbose --locate-keys [email protected]

  https://example.org/.well-known/openpgpkey/hu/0t5sewh54rxz33fwmr8u6dy4bbz8itz2

Is there a pinned certificate for `gpg recv-keys` (that isn't possible with WKD) https://en.wikipedia.org/wiki/Key_server_(cryptographic)#Pro... ?

This depends upon TLS and preshared CA certs in all forms AFAIU:

  gpg --recv-keys [email protected]

W3C DIDs are encodable into QR codes, too. And key hierarchy is optional with DIDs.

[ Parent | on HN ]