Lnd: No `channel_update` is sent to non-public channels

Created on 8 Jun 2018 · 11Comments · Source: lightningnetwork/lnd

LND currently supports routing hints in payment requests but does not send a channel_update to pop-public channels as specified at https://github.com/lightningnetwork/lightning-rfc/pull/193. Thus many mobile wallets which use non-public channels by default have no way of receiving funds when connected to LND nodes.

Source

btcontract

Most helpful comment

@Roasbeef , can you open this issue?
This issue is closed but i think it's annoying problem. I use Bitcoin Lightning Wallet and i cannot to get payments because the my own lnd (fresh commits) has this fault (if i right understand).
I think if this issue will be closed it will not resolved near time :(

Perlover on 2 Jul 2018

👍2

All 11 comments

Are you sure? We have test exercising this on a multi-hop basis even. This is the code that sends the channel update: https://github.com/lightningnetwork/lnd/blob/master/discovery/gossiper.go#L1983

Roasbeef on 8 Jun 2018

The one thing we don't do currently is ensure that it's sent reliably, so if the peer isn't connected at the time we go to send the update, then we'll never send it to them. This is documented in a TODO a few lines below where I linked.

Roasbeef on 8 Jun 2018

I have a non public channel with LND node where funding tx has 63 confirmations and no update received, looks like it's an "offline" case.

btcontract on 8 Jun 2018

Perlover on 2 Jul 2018

👍2

Indeed it's annoying, keep getting user complaints all the time. Plus, it looks like ACINQ works on receiving in their Android wallet which also uses private channels, so will face the same issues.

btcontract on 20 Jul 2018

This affects Electrum as well.
I have tried sending a query_short_channel_ids message for specifically the private channel but lnd won't send the channel update even then.
I think the easiest fix/workaround would be to at least make query_short_channel_ids work here.