Replying to Avatar StevenB

If I understand correctly, the idea is to move to an externally hosted file that has all of your payment options. As your options change, it’s simply a matter of updating that one file. Right now, if you’re a guest on a podcast and your wallet changes, you have to ask every single podcaster to update every single value block you appear in. With the external file, you update one file and every app will now pull in the new address.
Avatar
bitpunk.fm is typing 1y ago

Ok so the idea is to pick lnurl so that podcast hosts have this lnurl with options. Guests, presumably have just a lnurl either from their own host or with a custodial wallet or some service that hosts the lnurlp for them.

?

Reply to this note

Please Login to reply.

Discussion

Avatar
StevenB 1y ago

I think the original idea was to call it lnaddress and just use it to fetch a static file with all of your payment options, which would include lnurl. At some point it got hitched to lnurl, and I’m not take sure why. I like the idea of having a link to a static file I control with all my payment options, which may include lnurl. Tying it to lnurl or lnurlp as an options file has line of made it more confusing and I’m not sure what the rationale for it is.