The Lightning Network has been changing and trying to work around UX with different implementations of BLIPs and BOLTs.
True every use case is different, which is great that we have so many options, which one do you think is most appropriate, and for what?
Traditional QR code scan12.5%
Send to a LN address29.2%
Share LN invoice string in other medium4.2%
BOLT12 reusable address20.8%
ZAPs over nostr29.2%
Ecash tokens4.2%
24 votes \ poll ended
I chose "Zaps over Nostr", but that's because boosting through Podcasting 2.0 apps is not on this poll. This has been my primary use case for the lightning network to this point through 2.0's value-for-value focus.
Most of the apps n the Podcasting 2.0 are probably using LNURL (not included above), maybe I'm wrong! Thanks for bringing it up and sharing this option.
I wouldn't know, but I'll take your word for it lol. I know Fountain has its own wallet it managed, and Podverse leverages Alby, since those are the two I've used. Others I don't 100% know.
I'd like to see LND projects adopt bolt 12
It maybe will come soon... who knows. BOLT12 is definitely a marketing advantage CLN have.
why not about all of them?
There are so many use cases for LN that only one method will not be enough or fit for all aspects.
Also you missed keysend. A very important one.
In regards of "static" reusable codes, we also have the AMP invoices, that were around waaaay before any BOLT12... I wonder why did you ignore that.
Yes, indeed. I thought was a good way to get what stackers use more.
Keysend dam... Forgot about that! it' great, so underevaluated unfortunately, and should be used and implemented more across products and services.
Unfortunately...
Source: https://github.com/lightning/blips/blob/master/blip-0003.md#keysend-drawbacks
Also a good question here:
https://bitcoin.stackexchange.com/questions/100271/is-lightning-offers-an-improvement-over-key-send
so is AMP another one that should be in the list above?
definitely yes.
I use it myself several times.
All but bolt12 but that’s because I run LND
maybe it will come to LND one day?
I think so bolt 12 was merged to the spec
NIP-69
view on x.comMan thanks for all your work and knowleedge sharing, this video is particularly interesting!
is NIP-69 already in the list under "ZAPS UNDER NOSTR"? Or are the current "zaps" using LNURL atm, and you're proposing this NIP-69, that btw, the nip number itself explains everything LOL
I suppose technically yes because as you point out Zap's currently are using LNURL, so I guess that makes NIP-69 the only way to actually Zap over Nostr...
... just wait till you see NIP-68 ;)
We published a bridge for NIP-69 upgrades to Lightning Addresses too: https://github.com/shocknet/bridgelet
https://xcancel.com/shocknet_justin/status/1833602834081988725
Another option.
Browser extension for better UX. Might use any of the methods above as long as it obfuscates it from the user.
Browser extension only work on PCs and yes, most of them are using LN invoice strings or LNURL (not in the list)
I don't favor any specific form. I think they are all valid at the appropriate time. SO ALL OF THEM
True, most of them have really specific use case. Which one do you find yourself using more often?
It depends on why are you sending SATs.
For donations, the best way is to a lightning address.
For comercial use, the best way is to pay an invoice.
I've never used ecash...not sure about the use case of it yet.
like gift cards, tokens redeemable for sats #397764
Reusable addresses are what I use most often and are easiest for me personally. Second would be a lightning @ address but about half of the platforms I'm using lightning for/on don't support that.
Do they not support reusable addresses nor LN addresses? What exactly are the platforms not supporting it?
Cwallet only lets you withdraw to an old school invoice. And deposits are done via bolt 12 but they expire after a certain timeframe, which is really odd. Stacker.news also doesn't let you send to a reusable static bolt 12 deposit address and I've been advocating for this for a while now.