pull down to refresh
0 sats \ 2 replies \ @netstatic 11 Aug 2023 \ on: Interest in a Lightning Address Alias Service? bitcoin
As mentioned by @TonyGiorgio, the privacy it gives is surface-level for anyone willing to put in the effort to extract and compare invoices, which is something you also noted. I don't think it's useless though. Having different lightning addresses for each of my websites will prevent them from being enumerated from just one of my lightning addresses on Google at least
Thanks for the feedback!
For users using a custodial wallet, such as Alby, WoS, right here on SN, etc. All invoices generated by those services contain the same payee public key. So you could certainly link an alias to a wallet service. But there are tens, or hundreds of thousands of users using the popular wallet services.
I'm struggling to find a way to link two invoices, from a custodial service like above, to a single user. Honestly, I'm not very familiar with how accounts work for these custodial services where many users share a single node and whether any user info is included in the invoice. Perhaps they just link the invoice to the user account on the backend, when the invoice is generated, and credit the account when the invoice is paid. @TonyGiorgio, as a wallet developer, do you have any idea?
If anyone else has any insight around that, it would be very helpful!
reply
Just use https://lnproxy.org/ to hide the destination's pubkey.
If you're self-hosting you'll need to have enough liquidity to support routing all proxied lightning invoices but you'd achieve meaningful levels of privacy.
reply