Nostr Web 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

thesimplekid 2y ago

Ah okay thanks for letting me know. Been using amethyst and iris so they must not be checking either. Will fix

Reply to this note

Please Login to reply.

Discussion

thesimplekid 2y ago

That is in the nip so my oversight

denis2342 2y ago

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

vec![invoice.description],

I think this change is enough to make it work

thesimplekid 2y ago

Yes testing that now. I'll zap this note can you see it in damus?

denis2342 2y ago

klabo 2y ago

I had issues with this as well, it was the deschashonly flag on CLN I was missing.

https://klabo.blog/posts/setting-up-nip-57-support

thesimplekid 2y ago

I'm using clnurl whitch does set that to true. Good to know though

denis2342 2y ago

I made a PR which works for me

thesimplekid 2y ago

Intresting thats what im running and broadcasted zaps you couldnt see. But thats inline with the nip so will merge thank you

denis2342 2y ago

zapped you and I see nothing, did you restart? :)