{"type":"rich","version":"1.0","title":"Brian of London wrote","author_name":"Brian of London (npub18h…wfmgv)","author_url":"https://yabu.me/npub18hz8xs2tafx7rhclzukrr94gypcemw6ch2hcwe9eak4q03k4a8wq2wfmgv","provider_name":"njump","provider_url":"https://yabu.me","html":"Are you having trouble withdrawing Lightning from \n@binance\n ? I am but I know the reason and its not your fault.\n\nFor the last few weeks any attempt to withdraw Lightning from Binance to my LND based Lightning node would tell me \"no route\".\n\nI 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).\n\nAfter 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.\n\nThis upsets Binance's withdraw system. The only answer is to use another system to receive sats that isn't running LND 0.18.3. \n\nThis has been fixed in the pending LND 0.18.4 release."}