reply on: LN bug?? CLN invoices without final-cltv-delta set failing \ stacker news ~litdevs

238 sats \ 3 replies \ @k00b 22 Dec 2023 \ on: LN bug?? CLN invoices without final-cltv-delta set failing litdevs

This was so weird to troubleshoot because the invoice looked good. The final cltv delta was the only thing that stood out, which depending on how I decoded it was reported as 9 or not at all.

0 sats \ 2 replies \ @shibe 23 Dec 2023

withdrawals seem to be broken now? Just says "could not decode invoice" on stacker.news regardless of what invoice I put in

1 sat \ 1 reply \ @k00b 23 Dec 2023

I just withdrew fine. To be clear this post is about a protocol interoperability issues you’d only experience if you’re running core lightning.

If you’d like help with your issue, you can share your invoice here or dm me on other socials.

392 sats \ 0 replies \ @anon 23 Dec 2023

The first sentence sounds like CLN is at fauilt in this case. To be clear, the change in the specification was initiated 3 years ago by the LDK team, and LND have simply not followed the spec change.

CLN has a backwards compatibility shim in the invoice generation intended to be there until the rest of the network upgraded to also default to 18 blocks. After 3 years we went and removed this backwards compatibility shim, expecting all nodes to be long updated, but LND had not, and so we re-added that shim.

So, while CLN users would encounter this problem, despite behaving correctly, the larger share of LND nodes out there, forced our hand to take a step backwards rather than forwards...