
Finally got core lightning to handle nostr zaps !
Thanks to nostr:npub1qjgcmlpkeyl8mdkvp4s0xls4ytcux6my606tgfx9xttut907h0zs76lgjw for the plugin :

Finally got core lightning to handle nostr zaps !
Thanks to nostr:npub1qjgcmlpkeyl8mdkvp4s0xls4ytcux6my606tgfx9xttut907h0zs76lgjw for the plugin :
Still buggy as the core lightning server does not allow long descriptions for the invoices and that's where the zap request is stored !
Solved it by compressing the 9734 request JSON and storing that as the description... and decoding it in the cln-zapper plugin. Oh yeah !
Well ! Found one last big bug, and now it works great.
Two questions for the pros :
1/ Why do clients make the invoice request with so many relays ? I tried to set my relays to a shorter list, but it seems the client does what it wants anyways. This is what caused my problems in the first place, core lightning invoice descriptions can only be 640 chars at most, but the 9734 Zap Request sent by most clients is over that size.
2/ Anyone can tell me how I could delete some broken 9734 messages my core lightning node broadcasted ?
That's it for now