Yeah, I spent a couple days learning and implementing lud16 just so all the nostrers using lnd could send me zaps. All the while I've been able to accept bolt12.
It was a good learning experience, but I could have been outside with my goats.
#bolt12
Bolt12 can't come fast enough. But LND continues to prioritize other things.
"The most common gripe people have with lnurl is the fact that an http server is required, and either a domain, or an extra tor hidden service.
With the introduction of bolt12, users can simply provide an offer that is served at their lightning address. This is a significant improvement in privacy, especially as bolt12 supports blinded paths.
Furthermore, bolt12 offers allow users to gain access to payment flows equivalent to lnurl-pay (without a lightning address) and lnurl-withdraw, without requiring any third party to host an http server, or provide a domain."
https://github.com/lightningnetwork/lnd/issues/5594
#[0]
Discussion
⚡️
Please let us know what you had to do and share with the community.
I'll try. It was somewhat involved. What would help me document it setting it up with another person and or two, since I didn't write down what I i did.
I used cln, nginx , wireguard port forwarding, and lnbits.
Before I implemented this I did figure out what I' calling zap aliases which require less work see: https://bolverker.com/zap_aliases.txt
"A zap alias maps to a zap address (lud16). For example: sats sent to the lightning address sat@bolverker.com arrive in my bolverker@strike.army lightning address and are available in my Strike account. If you have a lightning address hosted by a third party like walletofsatoshi.com, strike.army, or getalby.com and you want to have a lightning address which uses your own domain without having to do the all heavy lifting then a few simple steps will get you going with you own zap alias."