Still feels like we're beholden to the wallets doing it this way which is the point Alecks Gates was making by moving this out of the payment flow and into the feed.

All of this payment metadata stuff has always been broken and that's why Helipad on a Node is still king for all of this.

What's the fix? idk but this stuff makes my head hurt.

"Can't see your BoostBox URL? Get a better wallet." Coming soon.

@ChadF not sure I understand what's happening. You mean your payments don’t carry the url in the comments?

@ChadF

The way the BoostBox should work is the app POSTs the TLV record to the url in the feed. BB will return a unique link and/or identifier to the app. The app then makes the payment and includes that link or identifier in the payment message. With something like a Webhook, when the payment goes through, the BoostBox would be notified through the Hook with the unique identifier to verify the TLV is valid and tied to the payment. The link could also be used by the splits to look up the TLV.

@francosolerio

yeah this is from Castamatic in my AlbyHub but I cant always get this info to send with my app.

Some work and some dont. Strike and Zeus for example are fine so i think its just based on the wallet the payment is being sent to.

@ChadF probably not all wallets support sending comments

@francosolerio

I think thats it since it does work. I've had this issue before testing other stuff.

@ChadF @francosolerio is the problem for you specifically when you're using the Alby web browser extension? If yes, have you asked Alby about it?

It'd be great if we had a list of what LN wallets support sending metadata with lnaddress transactions.

@mitch @francosolerio

I think it depends on the receivers wallet but I'm not 100% sure on that and honestly need to read up on all of this.

I've only tested the Alby extension with BoostBox in my app so far but I think I have it working so I can try others.

Strike and Primal so far seem to handle receiving these well so far. Primal is kind of nice because it shows up as a click able link in the wallet.

@francosolerio @ChadF hmm I suppose it would make sense if the ability to receive a memo with an lnaddress is configured on the recipients LN node itself? And since Alby lets people connect their own node, there would be no guarantee that an “Alby wallet” accepts a memo with an LN-Invoice? Are you bringing your own node by chance?

@merryoscar could you help shed some light on the lnaddress memo behavior? Is it controlled by the LN node? I’m probably getting some of my terminology wrong…

@mitch @francosolerio @merryoscar

I'm on my own node but I think AlbyHub is the same everywhere and I'm just running it on my own hardware.

Take Castamatic for example, I'm logging in with Alby using my email and password like always but now it's just on my own hardware and not Albys.

I was wondering if how you connect to Alby makes a difference because Castamatic seems to work better with BoostBox than my app does.

@mitch @francosolerio @ChadF

The ability to receive a comment alongside a payment to a Lightning Address is configured by the Lightning Address server - it's defined here - https://github.com/lnurl/luds/blob/luds/12.md

To include the comment you pass it as a query string parameter in the pay request like ?comment={rss::payment...}

Most Lightning Address providers support this feature - Fountain, Strike, Primal, Alby etc

@ChadF what receiving wallet did you test with that wasn't accepting the comment param?