Replying to Avatar bumi

that sounds strange. can I see the code? or test it somehow.

it’s all the lnurl spec, so there should not be ang difference.
Avatar
0xtr 2y ago

Seems like the problem is that the website doesn’t support LUD-18.

When looping over the payerData key in the response from Alby, we error because we try to render the entire payerData object which apparently React doesn’t like. This is where the error essentially occurs:

https://github.com/andrerfneves/lightning-decoder/blob/master/src/app.js#L478

When I build a special handling if-block for the “payerData” key, it renders perfectly fine. I’ll try to find a way to display this data and make a PR for it.

Reply to this note

Please Login to reply.

Discussion

Avatar
bumi 2y ago

so we implement LUD18 (https://github.com/lnurl/luds/blob/luds/18.md) which is not supported by that app? this is a bug in the app then, isn't it?

LUD18 is actually pretty great and I hope more providers are going to supporting it.

Avatar
0xtr 2y ago

Oh, yeah there is nothing wrong with Alby. Alby is just the only LN wallet that I tested with that had support for LUD-18. It’s the website that doesn’t support rendering LNURLs where the response contains payerData (or any child object really in this case).