Brian of London on Nostr: Are you having trouble withdrawing Lightning from @binance ? I am but I know the ...
Are you having trouble withdrawing Lightning from
@binance
? I am but I know the reason and its not your fault.
For the last few weeks any attempt to withdraw Lightning from Binance to my LND based Lightning node would tell me "no route".
I could withdraw to another node: one which was ONLY connected to the rest of the Lightning network via my primary node but not to my primary (obviously withdrawing to this secondary node meant sats passing through my primary so route wasn't an issue).
After asking at LND Labs I found out that there is an issue with the current LND 0.18.3 version which inserts a whole lot of extra feature bits in the invoices.
This upsets Binance's withdraw system. The only answer is to use another system to receive sats that isn't running LND 0.18.3.
This has been fixed in the pending LND 0.18.4 release.
@binance
? I am but I know the reason and its not your fault.
For the last few weeks any attempt to withdraw Lightning from Binance to my LND based Lightning node would tell me "no route".
I could withdraw to another node: one which was ONLY connected to the rest of the Lightning network via my primary node but not to my primary (obviously withdrawing to this secondary node meant sats passing through my primary so route wasn't an issue).
After asking at LND Labs I found out that there is an issue with the current LND 0.18.3 version which inserts a whole lot of extra feature bits in the invoices.
This upsets Binance's withdraw system. The only answer is to use another system to receive sats that isn't running LND 0.18.3.
This has been fixed in the pending LND 0.18.4 release.