Support Proposal 303 on PeakD
Vote for Brianoflondon's Witness KeyChain or HiveSigner
This is a value for value post: see the explanation in the footer.
Note: this has no effect on the v4v.app service for most users, this post is purely for background information if you're interesting in the Lightning Network and its issues.
If you ARE trying to move sats from Binance onto v4v.app then it might affect you. I hope this will be fixed soon and if you really are stuck, leave a comment here.
Are you having trouble withdrawing Lightning from Binance?
I have been having trouble moving BTC Lightning from Binance to my own node for a few weeks. At first I thought Binance had done something strange to single out my node. I now know the reason and there's a reasonable explanation.
Version LND 0.18.3
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.
More Detail
Below is a side by side comparison of similar Lightning invoices generated by v4v.app on my test Lightning node running LND 0.18.0 and on my main Lightning Node running 0.18.3.
The issue is that 0.18.3 adds a plethora of unset "feature bits" to every invoice and there is no way to stop it.
Binance generally does not acccept any invoices with most of these feature bits, but it appears that their systems right now reject invoices with too many of these feature bits flagged as false as well.
Fix in 0.18.4
I've been told by Alex Bosworth (one of the main devs) the next version of LND has fixed this. So I'm just waiting for this fix.
In the meantime I work around it by sending funds to my development node and then transferring them back to the main node (which they pass through on the way!).
Raw invoices
LND 0.18.0
lnbc2500u1pns8ygcpp57s9tv8wtq50kqwly2r3nvxz538dculdt209x3prt6ntmexegdzuqd9vwc68vctswqhxgetkyp7zq4r9wd6zq6twwehkjcm9ypnx7u3qv4u8qmrpd9hxjmn8ypxyu3pqxqhrzwpwxvs8qun0vfkx2mfqwc68vttexej4q4eq0sszx56p23fjqv34xqcrqvpq0sszx56p23fjqg6rf3z5zn3qydmrganpwpcqcqzpgxqyz5vqsp58sctj4gc2he0td9pvaaxxrsg0462f7svydv6d4s9yrj3m45zh0nq9qxpqysgqdj98ntdupn9uwr7rysgatuyxs6a9vku3e5tal2cr0cwf0pnudwl3q7y53s5z7yl9zgk8rvkg0s4spjv268vql7hvp4rwqsfka534npsqj30vy4
LND 0.18.3
lnbc2500u1pns8yqgpp54mytjzkt93mnacrd9vpqsje2sa0kuxw8e8w5ls9pudkylh7vlswsd9vwc68vctswqhxgetkyp7zq4r9wd6zq6twwehkjcm9ypnx7u3qv4u8qmrpd9hxjmn8ypxyu3pqxqhrzwpwxvs8qun0vfkx2mfqwc68vttexej4q4eq0sszx56p23fjqv34xqcrqvpq0sszx56p23fjqg6rf3z5zn3qydmrganpwpcqcqzzsxqzxgsp570ke7way52ed6v4ts7hev9jzlxkrxast6gjp65r0ykpaxev5vqls9p4gqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqpqysgqwl98qxwjgsqyjmdsyxhyk8vtxwlw6cm5xxfue7e5k6uyt3a4s2v8d0vwsrnxe5v5v564n9ntq8khgaz3605g9c68qkw7sjgjyhayjwqqtz68zu
Value for Value
For the last few months while building @v4vapp I was generously supported by the DHF. Going forward I have a much more modest support which covers direct server costs and a little of my time.
If you appreciate the work I do on and around Hive, you can express this directly: upvoting posts on Hive is great. Also consider a direct donation (there's a Tip button on Hive or a Lightning Address) on all my posts.
Support Proposal 303 on PeakD
Support Proposal 303 with Hivesigner
Support Proposal 303 on Ecency
Vote for Brianoflondon's Witness KeyChain or HiveSigner
