pull down to refresh

66 sats \ 2 replies \ @megaptera 8 Oct \ on: LND Update - invoice incompatibility lightning
hi there
This long string with lots of qqqqq is the feature bit :
Feature bits allow forward and backward compatibility, and follow the it's ok to be odd rule. Features appropriate for use in the 9 field are marked in BOLT 9. The field is big-endian. The least-significant bit is numbered 0, which is even, and the next most significant bit is numbered 1, which is odd.
Could be that Binance is not parsing the invoice correctly, which is probably not a LN issue itself rather than an implementation problem on Binance side.
write
preview
0 sats \ 1 reply \ @krawall OP 8 Oct
Hey @megaptera,
thanks yes ... I completely understand that this appears to be a problem with Binance, but it's rather silly too, I mean, not supporting Binance is a big(ger) deal... so I wonder if we can just create legacy invoices that don't have this present (like it was in the minor -1 update before, it's kinda strange that they go from 18.2 -> 18.3 and have a change that affects the biggest exchange's ability to send to ...)
reply
0 sats \ 0 replies \ @megaptera 8 Oct
but it's rather silly too, I mean, not supporting Binance is a big(ger) deal...
It's rather silly to not implement the LN specs correctly :) But they are probably busy with the next stupid shitcoin.
reply