Hi All,

I'm writing to gauge interest for a lightning address alias service for privacy before I spend the time deploying the proof of concept I've built.

Problem: Lightning addresses are public identifiers that are generally tied to a single wallet. This can raise privacy concerns for individuals that work on multiple projects or have multiple online identities. For example, I go by different handles on Reddit, nostr, and Twitter and may like those identities to remain separated. Putting my lightning address in all 3 places would easily link those identities together.

Solution: Lightning Address Aliases

I'm proposing a completely free service that would allow users to generate unlimited lightning addresses that serve as aliases to a single, existing, lightning address. Similar to SimpleLogin and AnonAddy services that exist for email.

Example:

• Lightning Address Alias Service is hosted at https://privacy.ln (example for demonstration, not real domain)
• Main Lightning Address I want to keep private, the Destination Address: privnut@stacker.news
• Users can create unlimited aliases such as alias1@privacy.ln (I envision multiple domains being available for selection) and set those aliases to point to the Destination Address privnut@stacker.news
• Further alias examples: MyTwitterHandle@privacy.ln, MyRedditHandle@privacy.ln, MyNostrHandle@privacy.ln, you get the point
• Sats sent to any of these aliases would arrive at privnut@stacker.news without revealing that privnut@stacker.news is the destination or even exists.
• Users would be asked for an email address, any email address, when creating an alias. Users could then log in to a dashboard to manage their aliases, create new ones, or redirect them to a new Destination Address (handy if you move to a new wallet provider, so you don't have to update your lightning address everywhere).

These aliases would not touch the sats, redirect them, or change their route. LNURL-Pay requests sent to any of the aliases linked to a Destination Address would all generate the same invoice.

That leads us to, Drawbacks:

• Requires having an existing lightning address to use as the Destination Address
• The payee pub key would be the same for all aliases and the Destination Address. Theoretically aliases and the Destination Address could be linked by mass requesting invoices from addresses, decoding them to gather pub keys and using those pub keys to link addresses, breaking the privacy of the aliases.

Thoughts? Suggestions? Concerns? Would this be something you'd use? Is this even necessary? or do the drawbacks listed (and maybe some I've missed) make it worthless?