8000 Channel creation timeout in neutrino mode without feeurl · Issue #4770 · lightningnetwork/lnd · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Channel creation timeout in neutrino mode without feeurl #4770

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Sjors opened this issue Nov 13, 2020 · 7 comments
Closed

Channel creation timeout in neutrino mode without feeurl #4770

Sjors opened this issue Nov 13, 2020 · 7 comments
Labels
bug Unintended code behaviour fees Related to the fees paid for transactions (both LN and funding/commitment transactions) neutrino Lightweight neutrino backend-type

Comments

@Sjors
Copy link
Sjors commented Nov 13, 2020 •
edited
Loading

I tried opening a channel from Lnd to c-lightning, as well as the other way around. It would just timeout after 5 minutes with no explanation.

I configured the node to use Neutrino and connected it to my Bitcoin Core node only.

Once I configured feeurl and restarted Lnd the channel creation, which I initiated earlier, went ahead.

It should probably complain in the openchannel command or in the logs (when the other side opens) that it needs fee information.
@Sjors
Copy link
Author
Sjors commented Nov 13, 2020

As an aside, does Lnd broadcast its (channel creation) transactions to the neutrino peer? So far it didn't seem to and I had to manually broadcast the raw transaction.

@Roasbeef Roasbeef added bug Unintended code behaviour fees Related to the fees paid for transactions (both LN and funding/commitment transactions) neutrino Lightweight neutrino backend-type labels Nov 13, 2020
@Roasbeef
Copy link
Member

As an aside, does Lnd broadcast its (channel creation) transactions to the neutrino peer

If it's the initiator (which is the only person that has the funding transaction), then yeah it should. Did you see it attempt to do so in the logs? It'll also rebroadcast any unconfirmed transactions on start up as well.

@Sjors
Copy link
Author
Sjors commented Nov 17, 2020 •
edited
Loading

I initiated several channels from the Lnd node, none of the funding transactions were broadcast.

The log shows:

2020-11-14 17:48:08.267 [INF] FNDG: Initiating fundingRequest ...
2020-11-14 17:48:08.267 [INF] CHFD: Performing funding tx coin selection using 2500 sat/kw as fee rate
2020-11-14 17:48:08.287 [INF] FNDG: Target commit tx sat/kw for pendingID(...
2020-11-14 17:48:08.287 [INF] FNDG: Starting funding workflow with ...:9735 for pending_id(...), committype=tweakless
2020-11-14 17:48:08.421 [INF] FNDG: Recv'd fundingResponse for pending_id(...)
2020-11-14 17:48:08.429 [INF] FNDG: pendingChan(...): remote party proposes num_confs=3, csv_delay=144
2020-11-14 17:48:08.431 [INF] FNDG: Generated ChannelPoint(...:0) for pending_id(...)
2020-11-14 17:48:08.550 [INF] FNDG: Broadcasting funding tx for ChannelPoint(...:0): ...
2020-11-14 17:48:08.550 [INF] LNWL: Inserting unconfirmed transaction ...

Maybe I wasn't patient enough, but it didn't show up in the (max 1 GB) mempool of the only peer it's connected to (my own bitcoind node) and I had to use sendrawtransaction.

@Roasbeef
Copy link
Member

Which version are you on?

@Roasbeef
Copy link
Member

Also which bitcoind version were you running?

@Sjors
Copy link
Author
Sjors commented Nov 18, 2020

Lnd 0.11.1-beta commit=v0.11.1-beta against bitcoind v0.20.99.0-1d3ec2a1f (master branch, slightly before the new address message was merged, see btcsuite/btcd#1661

@bitcoinlizard
Copy link

I have observed the same behavior as @Sjors. I am using the current LND from the master branch:
"0.11.99-beta commit=v0.11.0-beta-534-g7e298f143425337448f95019234b22849d64aca3-dirty"

I am running btcd version 0.21.0-beta acting as the neutrino server. I don't see anything in the btcd log to indicate that LND attempted to broadcast the transaction. I needed to retrieve the raw_tx_hex with "lncli listchaintxns" and broadcast the transaction by other means. This has occurred for channel creation transactions as well as regular on chain transactions and in very limited testing seems to occur 100% of the time.

Most likely unrelated but I am connecting to btcd via .onion address.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Unintended code behaviour fees Related to the fees paid for transactions (both LN and funding/commitment transactions) neutrino Lightweight neutrino backend-type
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Sjors @Roasbeef @bitcoinlizard
0