Avatar
denis2342
3036e986c4cef0b2615e6bcf2d6d411310c73872f30c99b19ab7ba58a2df9f98
following bitcoin since difficulty 157416

#[0] got the 21 sats, on my side all looks good

// vec![zap_request_info.zap_request.as_json()],

vec![invoice.description],

I think this change is enough to make it work

and that means anybody zapping me and CAN see the zap has a broken client. :)

#[0] damus is checking if the description hash matches the description and your zapper is messing up the description order. this also means that nostur is not checking that

interesting, on another client I can see the zap. either your plugin is doing something wrong and the other client is not checking or damus is doing something wrong

“At times like this, I wish I was but a simple peasant.“ https://iwdrm.tumblr.com/post/4088689039

#[0] your zap got answered by the js zapper. turned that off now

I used a working zapper on the same invoice and that works. your output has the description changed and also the tags have different order. don’t know if that matters though

#[0] tried your zapper, everything looks fine in the logs, but my client can’t see the broadcastet note yet

first thing I added to lnurl-commando was checking that ID machtes the content and that the SIG matches the ID